Essential Phone PH-1 camera notch issue on Android

After recently getting my app updated for iPhone X and dealing with the “notch”, I had a user on Android report to me that display is not rendering correctly on their “Essential Phone” that also has a “notch”.  Apparently there are a number of Android phones with notches with more on the way.

https://www.essential.com/

https://www.androidauthority.com/iphone-x-notch-coming-android-phones-816563/

Should the “safe area” functions work properly on Android devices with a notch?  e.g.

Or is this just on the iPhone X?

Attached are screenshots that were sent to me.  One shows the app in landscape mode and left side is cut-off.

The portrait mode screenshot should have Navigation icons and Title text at the top but they are not being displayed.   

@dvboren,

A read through the display.safe* docs mentions that some devices don’t have the concept of a safe area.  Thus, I think the answer is that this is not universally supported.

https://docs.coronalabs.com/api/library/display/safeScreenOriginX.html

For devices which do not feature the concept of a safe area, this value is the same as display.screenOriginX.

 

You may have to identify special cases on your own for now.

If you are like me, you’re probably cursing Apple for introducing the ‘notch’ which I am quickly coming to dislike.

Agreed. The notch is a major PITA. 

We’ve also received feedback about problems with this model. 

Does anybody know what system.getInfo(“architectureInfo”) returns for Essential phones?

@dvboren,

A read through the display.safe* docs mentions that some devices don’t have the concept of a safe area.  Thus, I think the answer is that this is not universally supported.

https://docs.coronalabs.com/api/library/display/safeScreenOriginX.html

For devices which do not feature the concept of a safe area, this value is the same as display.screenOriginX.

 

You may have to identify special cases on your own for now.

If you are like me, you’re probably cursing Apple for introducing the ‘notch’ which I am quickly coming to dislike.

Agreed. The notch is a major PITA. 

Sorry for resurrecting an old thread. I also received a complaint. I don’t believe that the current Oreo release of Android has a mechanism to report the safe area. The “P” version of Android finally has an API for the “window cutout”.

https://medium.com/exploring-android/exploring-android-p-display-cutouts-42885e8a2a96

Since corona does not yet have access to the “P” api the display.safe* could not return the correct information. Thanks to Amazon Prime day I finally have a phone with a dreaded cutout.

Essential PH-1

@zutgames Architecture Info: ARM Neon

Safe area Y: 0 (part of my UI is being eaten by the cutout on the top).

We’ve also received feedback about problems with this model. 

Does anybody know what system.getInfo(“architectureInfo”) returns for Essential phones?

Sorry for resurrecting an old thread. I also received a complaint. I don’t believe that the current Oreo release of Android has a mechanism to report the safe area. The “P” version of Android finally has an API for the “window cutout”.

https://medium.com/exploring-android/exploring-android-p-display-cutouts-42885e8a2a96

Since corona does not yet have access to the “P” api the display.safe* could not return the correct information. Thanks to Amazon Prime day I finally have a phone with a dreaded cutout.

Essential PH-1

@zutgames Architecture Info: ARM Neon

Safe area Y: 0 (part of my UI is being eaten by the cutout on the top).