Bug Android Phones Returning Screen.safeArea Incorrectly

On any Android mobile phones I tried in the Device Simulator, the Safe Area option displays the safe area in green correctly.


(Samsung Galaxy S10e)

However, when I attempt to run: Screen.safeArea.y Screen.safeArea.yMax, returns an incorrect value for Screen.safeArea.y: 0; But according to the Device Simulator, should be > 0



When switch the Device Simulator to iPhone XR, the Screen.safeArea.y returns 68 which looks to be correct.

Not sure what's going on here.

Using Unity 2020.2.2f1

 

Yes. It was checked.


After un-checking it, it does render below the notch but the Screen.safeScreen.y is still 0. I'm guess if I wanted to put something in the notch area, I would need to go positive in the Y which is different on iOS where the top of the notch is 0 and the Screen.safeScreen.y is 68 (or so). I wish it was consistent across platforms.

 

I am facing the same issue:
I have a couple of Android devices with the front-facing camera within the screen area (Xiaomi Mi 10T Pro 5G, Google Pixel 5, Xiaomi Mi A3, Samsung Galaxy S10).
On all of these devices Screen.safeArea returns wrong rects in portrait rotation and in portrait upside down rotation.
The size of the safeArea rect (width and height) seems to be right, but the position (x,y or xMin,yMin) is not. min Position is alwas (0,0) in portrait rotation. In portrait upside down rotation the rect is at the bottom most position. I tried to illustrate this.
blue: actual safe areo of device
red: rect returned by Screen.safeArea




In landscape left and landscape right orientation everything works as expected (blue and red area overlap completely).
I'm using Unity 2020.3.7f1. and "Render outside safe area" is enabled.

 

Yes, you are absolutely right, that was my mistake. Thanks!

 

I write a code Screen Safe area its looks pretty fine in Device Simulation but It's not running in build what should I do code files is attached below ...

 

This is inconsistent..?

On Android:
Render outside safe area enabled -> Screen.safeArea.y = 0
Render outside safe area disabled -> Screen.safeArea.y = 0

On iOS:
No render outside safe area option -> Screen.safeArea.y = 68

So on Android the Screen.safeArea does nothing useful? I want to render the entire app outside the safe area, but I need to know the safe area to move elements away from any notches/ cameras that will get in the way.

I would expect, that when rendering outside safe area is enabled, that Screen.safeArea.y would return a value greater than 0... and when rendering outside safe area is disabled, Screen.safeArea.y = 0.

 

Samsung Galaxy S10*, on Android 11 always returns 0 for Screen.safeArea.y.
So do all of the Android devices in Device Simulator (I'm using v2.2.4).

Rotating the Device Simulator to landscape gives an accurate value for Screen.safeArea.x, going back to portrait and Screen.safeArea.y is always 0.



* I'm only working with 1 device while I dev. Our QA reported the issue on all their test devices too.

 

So, how do I get the safe area from the top..? The bit that everyone is going to want from the API..

 

Don't you think this should be part of the safeArea API?
So that it's easily accessible and that the same code isn't being re-written by every dev and every project that needs it and expects this to be part of the safeArea API?

Sure, the bottom bit is good to have, but it is no where near as important as the notch areas at the top of the screens...

 

Nope. I want to move UI down into the safe area, and expected the safeArea API to actually give me easy access to the top of the rect so I know how far to move it ...

Screen.safeArea.y gives a value for offset from the bottom, for the 2 phones that need it.. why not have the same thing for the top? Where a lot more phones actually have something that would get in the way.

Additionally, thanks for the docs link.. but it's void of any actual useful information. Needs updating with information and an example.

 

Can’t you do Screen.height - (Screen.safeArea.y + Screen.safeArea.height) ?

 

Of coruse I can..

My point is, that the safeArea API should include this already. Why wouldn't it? It's half an API as is atm..

 

The API returns a rect which has x, y, width, height. From this perspective it is complete.

You might argue that returning a rect is a stupid idea, and I might agree, because rects kinda suck, but also... eh.

Converting it to any other format is trivial.

For example in our project we do this:

Code (CSharp):

1. float safex = Screen.safeArea.x / (float)Screen.width;
2. safex = math.clamp(safex, 0f, 0.2f);
3.  
4. float safey = Screen.safeArea.y / (float)Screen.height;
5. safey = math.clamp(safey, 0f, 0.2f);
6.  
7. float safez = (Screen.safeArea.x + Screen.safeArea.width)  / (float)Screen.width;
8. safez = math.clamp(safez, 1f - 0.2f, 1f);
9.  
10. float safew = (Screen.safeArea.y + Screen.safeArea.height) / (float)Screen.height;
11. safew = math.clamp(safew, 1f - 0.2f, 1f);
12.  
13. normalSafeArea = new float4(safex, safey, safez, safew);

And we just use that.

 

I think returning ONLY the rect is stupid.

You've written that code for your project.. and so, every other dev using safeArea will need to do the same thing. I find it pretty poor that this kind of thing isn't just part of the API so that we're not all writing the same code over and over, in all our projects.

If this was an asset on the store, I wouldn't buy it as is.

 

I wanted mine to be normalized because I wanted to use them with Camera.ViewportToWorldPoint. Maybe you want something different, maybe someone else wants something else. Maybe someone actually wants a Rect.

Listen, I'm all for yelling at Unity for doing a poor job, I'm actually starting (?) to get notorious about it at this point, but if most of my Unity problems could be solved with 9 lines of code, I would be really happy with Unity.

 

May I ask how can I get the safeArea in any orientation? The Screen.safeArea returns as full screen when the device is not landscape left. But that is not what I expected. I test in both real android phone and Unity Editor Simulator.

 

Why Screen.width is less than Screen.safeArea.width and Screen.height is less than Screen.safeArea.height?
I expect with and height falls into Screen resolution
and here is my code

Code (CSharp):

1. GUILayout.Label("Safe area :"+Screen.safeArea);
2.  GUILayout.Label("ScreenWidth and Height :"+Screen.width+"   "+Screen.height);

 

and why safeArea.x,and y are both o ,You said the value starts from bottom-left,but even I rotate the device ,I got the values both zeros