Support for Screen.safeArea on notch iPhone X like Android devices

Hi just wondering if there are any plans to support all of the android devices that replicate the notch and have different ‘safe area’ values. There’s a growing list of devices:

https://www.theandroidsoul.com/android-phones-with-notch-like-iphone-10/amp/

Or do you support some of these already? It would be handy if the docs specified which devices the Screen.safeArea returns values for.

 

Thanks, sounds good. Makes sense it’s Android API driven, so unity doesn’t have to define it per device but lets just hope manufacturers actually implement it properly haha... the preview would be great, we’ve created our own aplies and overlay for now.

 

Hi!
Android P started to rollout 4 days ago on the Pixel phones.
Any news on the issue?

PS: The in-editor preview would be awesome as well ^^

 

Just making sure, in devices where the API is not there, does Screen.safeAreas return 0,0,Screen.width, Screen.height? (so that it's safe to use everywhere, even if it doesn't do anything special)

 

Any news on the Android safeArea support?

 

Would really like to get this rolled into 2017.4 LTS at the same time as 2018 versions, please.

 

is anybody have any solution to add safe area on android notch phone?

 

Hello @FaiziFazal,

I was interested in avoiding the vertical space occupied by the notch. In order to do that I created a minimal Android library to work as a native plugin for Unity and used:

Code (CSharp):

1.  
2. Window unityWindow = UnityPlayer.currentActivity.getWindow();
3. DisplayCutout displayCutout = unityWindow.getDecorView().getRootWindowInsets().getDisplayCutout();
4. if (displayCutout != null) {
5.        return displayCutout.getSafeInsetTop();
6. }
7.  

On the Unity side I had to move a Canvas element, for that I had to use the scaler of the parent. Something like:

Code (CSharp):

1.  
2. int pixels = DeviceHandler.GetCutOutSafeTop ();
3. if (pixels != -1) {
4.     Canvas parentCanvas = GetComponentInParent<Canvas> ();
5.     RectTransform rectTransform = GetComponent<RectTransform> ();
6.     rectTransform.localPosition += Vector3.down * (pixels / parentCanvas.scaleFactor);
7. }
8.  

Hope that helps.

 

Hi Yury, will the Unity implementation work for devices that don't have Android P too?

 

It would make sense that for devices pre-P, Screen.safeArea returned a rect of dimens (0, 0, Screen.width, Screen.height)

 

Will support for safe areas in android 9 be coming to 2017.4 LTS?

 

From our testing on 2017.4.11f1 unity still registers touch input in the black bars. This doesn't seem like an ideal scenario.

 

How can I use it in my project?

 

Hello @itayganor,

You'll need to create an Android Library Plugin (https://docs.unity3d.com/Manual/AndroidAARPlugins.html).

Other than the above documentation you can follow one of the many tutorials on the web.

Cheers

 

Hello

Thanks for that ! I'm going to try your solution, and hopefilly it'll work !

EDIT :

I did that 2 month ago, I was not able to test before because notch was not out.
Maybe we don't need a small library and can only do that on C# side.

What do you think ?

Code (CSharp):

1. // We get the current window from the current activity
2. AndroidJavaClass unityPlayer = new AndroidJavaClass("com.unity3d.player.UnityPlayer");
3. AndroidJavaObject currentActivity = unityPlayer.GetStatic<AndroidJavaObject>("currentActivity");
4. AndroidJavaObject currentWindow = currentActivity.Call<AndroidJavaObject>("getWindow");
5.  
6. // Get the current view and inset
7. var currentView = currentWindow.Call<AndroidJavaObject>("getCurrentFocus");
8. var currentWindowInset = currentView.Call<AndroidJavaObject>("getRootWindowInsets");
9.        
10. // Should return something, but because the Android Pixel 3 has no "physical" notch, seems to return ... Nothing.
11. var displayCutout = currentWindowInset.Call<AndroidJavaObject>("getDisplayCutout");"

 

Hi @Kaiymu_ ,

I personally do not like to write Android plugins directly in C# for the sake of modularity, dependency management and testability.

If this is fine for you, go for it

 

Will the Screen.safeArea on android device support in 2018.3?

 

Is Screen.safeArea already implemented for Android?
Will it be included in 2018.2?

 

Can it add on 2017.4?

 

I'm still getting the black bar on notch area after activating the "render outside safe area" option (2018.3). Am I missing some configuration? I'm testing on a Pixel 3XL.

 

Submit a bug report?

AFAIK there isn't another requirement.

 

How can we use that code? I use Xiaomi Mi 8 and it didn't work for me

 

I'm seeing the same thing. Also still getting a black bar on the notch area of a Pixel 3 XL, even after setting "Render outside safe area", using Unity 2018.3.4f1, and target API level 28.

 

Please submit a bug report, this sounds serious, it seems like "Render outside safe area" does nothing.

(I would do a bug report myself, but I don't have an android with a notch handy)

 

@Yury-Habets Is there a reason Android's Player Settings has 'Render outside safe area', which we use, but iOS Player Settings does not have this same option? It seems like this would be very helpful to have. Because of this I have to write special logic just for iOS.

 

I see. So, the only possible approach is to write out own system with Screen.safeArea? Or does that not work on iOS as well?

If Screen.safeArea does work on iOS, wouldn't the Unity devs be able to use that to add a checkbox for iOS in PlayerSettings or no?

 

Ok. As long as Screen.safeArea works on iOS, that's enough to get started. Thanks for the explanation.

 

I'm uploading a bug report now for the issue reported above where "Render outside safe area" does not work as expected. I also discovered that the issue is related to the Orientation->Default Orientation setting. "Render outside safe area" appears to only work when the Unity default Orientation value of "Auto Rotation" is selected. Our game is set to Portrait and it doesn't work. If I instead select Auto Rotation, and within the allowed orientation list select only Portrait, then it does work. Not sure whether there are any other behavior changes when switching from Portrait to Auto Rotation (Portrait), so I'm reluctant to change this just to workaround the notch issue. Hopefully Unity can fix this.

 

Thanks for report and information It works in same fashion for me, so if I choose auto rotation+select portrait it works fine. BTW Unity's splash screen only uses safe area, but I guess that's not a bug but expected behavior.

 

I heard u guys like notches

 

Is there any progress on this issue?
I test the 2018.3 and it still not correct on android device.

 

Is it possible to use the Camera.pixelRect to have the camera only render to the Screen.safeAre?

 

I wanted to move the camera rect inwards to prevent our game from rendering under the iPhone X's notch. The only way I can think to do that is set its rect to the Screen.safeArea. But when I first tried this, it did not seem to work.

 

This is bad news for many live projects, particularly at larger studios. Thanks a lot.

 

@rjonaitis @JuliusM. Any chance you all (UT) could implement Screen.safeArea and Screen.dpi into the the game-view pre-defined resolutions. Currently, there is not good way to actually test UI layouts for several mobile devices in the editor without creating complicated editor tools.