Skip to main content
bontegames
Known Participant
Nov 30, 2018 12:15 PM UTC
Question

Android phones with a notch: fullscreen starts below the notch so bottom part is cut off

I have reports and screens from users with Android phones with a notch like the Pixel 3 XL, that my apps are no longer fullscreen: there is a black bar on top, the screen starts below the notch, so the bottom part is cut off.

See this example:

How can I solve this? Preferably without using an ANE.

I'm using AIR29 and <fullScreen>true</fullScreen>. Or is this just a question of migrating to the last AIR version?

This topic is closed to new replies. Start a new post to keep the conversation going.

10 replies

Felix af Ekenstam
Participant
Apr 10, 2019 12:38 PM UTC

I think you would need to manually confirm that your app supports "cutouts" for the notch. Have not implemented this myself but it should be the cause of your black bar:

Support display cutouts  |  Android Developers

Translate
bontegamesAuthor
Known Participant
Dec 17, 2018 9:04 AM UTC

I have created a new thread specifically for the Pixel 3 XL because none of the suggested solutions works for this device.

In one of comments above I thought I found a solution, but I had mistakenly used

stage.displayState = StageDisplayState.NORMAL;

which does not have the cut off problem, but keeps showing the system bars on top of the stage.

Translate
bontegamesAuthor
Known Participant
Dec 14, 2018 2:39 PM UTC

Well the solution is not 100% yet: if I wait 2 seconds, the screen is fullscreen without cut off but there are transparent system bars on top and bottom that stay there...

Translate
bontegamesAuthor
Known Participant
Nov 30, 2018 2:00 PM UTC

I have just tried using AIR31 but the problem stays the same.

Translate
Flipline
Flipline
Inspiring
Dec 5, 2018 5:09 PM UTC

For your app XML file, are you using a "max_aspect" tag to allow for the extra-tall devices like this?  We had similar issues with devices that were larger than 16:9, and that tag usually fixes the nudging and black bars we were getting.  Here's how ours is set up, within the "android" section of the XML file:

<android>

     <manifestAdditions>

          <![CDATA[

               <manifest android:installLocation="auto">

                   

                    <!-- other tags here -->

                    <application android:hardwareAccelerated="true">

                              <!-- this lets you support devices larger than 16:9 ratio -->

                              <meta-data android:name="android.max_aspect" android:value="2.16" />

                    </application>

               </manifest>

          ]]>

     </manifestAdditions>

</android>

Different values work as well, but you'd need at least 2.06 for the Pixel 3 XL's ratio of 18.5:9.

Translate
    bontegamesAuthor
    Known Participant
    Dec 7, 2018 7:47 PM UTC

    Thanks for the answer Flipline! I was using the max_aspect but with a 2.0 valiue. This has always worked before, but seems like it is now indeed causing the incorrect letterboxing and bottom part cut off problem on recent models.

    Translate
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices