Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.3.X
Votes
0
Found in
2018.2.5f1
Issue ID
1090830
Regression
No
[Android] Display.systemHeight and systemWidth return rendering values instead of screen native values
Steps to reproduce:
1. Open user attached project
2. Build & Run on an Android device
3. Set the app resolution to 1280x720 or 640x480
4. Click on "List" and observe that that Display.main.systemHeight does not return the actual device height
Expected result: Display.systemHeight and systemWidth should return screen native values
Reproduced in: 2019.1.0a5, 2018.3.0b6, 2018.2.13f1, 2017.4.13f1, 2017.2.4f1
Fixed in: 2019.1.0a10, 2018.3.5f1, 2017.4.20f1
No repro on Windows Standalone
Tested devices:
VLNQA00093, Samsung Galaxy S6 edge (SM-G925F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00106, Samsung Galaxy S2 Plus (GT-I9105P), Android 4.2.2, CPU: Broadcom BCM28155, GPU: VideoCore IV HW
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 5.0.2, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00153, Google Pixel XL (Pixel XL), Android 8.0.0, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00028, Samsung Galaxy Note4 (SM-N910F), Android 6.0.1, CPU: Snapdragon 805 APQ8084, GPU: Adreno (TM) 420
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Add comment