Hey Shaun, thank you for your efforts and replies. Are you using this ane?
https://github.com/mesmotronic/air-ane-fullscreen
If so, are you using the latest version?
Thx!
Detect if phone has Notch (iPhone XS, XR, X)
(46 posts) (7 voices)-
-
-
Do you still specify a value for android.max_aspect in your application.xml as suggested above Shaun or not for your solution?
Posted 2 months ago # -
yes, its:-
<meta-data android:name="android.max_aspect" android:value="2.1" />
Posted 2 months ago # -
Thanks Shaun. In the meantime I have done some more testing (on an online service with real devices) and your solution fixes indeed the cut off problem.
My app is in portrait mode and on taller devices like the Samsung S9 and the LG V40 thinQ, the screen is not fullscreen, there are black bars on top and bottom. But there is no more cutting off happening, the whole viewport is visible. In my test the android.max_aspect being there or not and its value didn't make a difference.
I wonder if there is a solution to the cutting off problem without losing the full screen on these devices.Posted 2 months ago # -
-
Screenshots of for example LG V40 thinQ:
homescreen, app with cut off problem, app with the solution but the trade-off: less full screen
https://imgur.com/a/Ek0wBm7Posted 2 months ago # -
Ok, i think this issue is there in LG V40 thinQ. We need somebody with this phone to test out and see if other app are also having this issue.
Posted 2 months ago # -
Also could you please tell us which online service are you using to testing it!
Posted 2 months ago # -
Well the V40 is just an example, I see the same behavior on a Samsung S9. I'm using kobiton.com to test.
But I'm thankful the cut off problem is solved, it would just be nice if there was some sort of fullscreen solution for all devices.Posted 2 months ago # -
I am pretty sure, somebody else should be able to help you here!
Let's wait and see!Posted 2 months ago # -
I got an answer on the Air forum:
https://forums.adobe.com/thread/2567541
So it seems the issue of the bottom part being cut off can be solved without the ANE, as long as the max_aspect value is higher than 2.0.
It seems it's the 2.0 value that causes the incorrect letterboxing with the bottom part cut off on recent models.Posted 2 months ago # -
did it fix the issue for you? i believe for apps in landscape mode an ane is required.
Posted 2 months ago # -
-
-
With the iPhone's 'notch' now present on their 3 new phones, as well as last year's iPhone X, detection of the 'notch' is necessary.
Prior to these new phone announcements, I set a new variable notchFlag=1 if either of these two conditions exist. But instead, we need code that will compare the safeArea properly so that notchFlag can be set to account for any current or future iPhone notch. Can someone familiar with the safeArea parameter who has a real iPhoneX help with this?
1) if system.getInfo("environment")=="simulator" and display.viewableContentWidth=1125 and display.viewableContentHeight=2436 then --this only accounts for current iPhoneX simulator model
and
2) if system.getInfo("platform")=="ios" then
local archInfo=system.getInfo("architectureInfo")
if (string.find(archInfo,"iPhone10,3",1,true) or string.find(archInfo,"iPhone10,6",1,true) then
--this works for iPhoneX, but what about XS and XR?Posted 2 months ago #
Reply
You must log in to post.