Search Issue Tracker
Fixed
Fixed in 2021.3.32f1, 2022.3.12f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a11, 7000.0.0a1
Votes
1
Found in
2021.3.30f1
2022.3.9f1
2023.1.12f1
2023.2.0b8
2023.3.0a4
7000.0.0a1
Issue ID
UUM-48141
Regression
No
[Android] The value of "Screen.brightness" doesn't match the device's screen brightness
Steps to reproduce:
1. Open the attached “TestScreenBrightness” project
2. Build And Run the project on the device
3. Observe the “Screen brightness” value on the device’s screen
Expected result: At 50% of device brightness the value is 0.5, and at 100% the value is 1
Actual result: The value doesn’t match the device’s screen brightness
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.12f1, 2023.2.0b8, 2023.3.0a4
Reproducible on: macOS Ventura 13.5 (Intel)
Not reproducible on: No other environment tested
Reproducible with devices:
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11 (0.11 at 50% and 1 at 100%)
VLNQA00017 - Huawei Nexus 6P (angler), CPU: Snapdragon 810 MSM8994, GPU: Adreno 430, OS: 8.0.0 (always 1)
VLNQA00293 - OPPO R17 Pro (PBDM00), CPU: Snapdragon 710 SDM710, GPU: Adreno 616, OS: 10 (4.01 at 100%)
Not reproducible with devices:
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00513 - OnePlus Nord N10 5G (BE2029), CPU: Snapdragon 690 SM6350, GPU: Adreno 619, OS: 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Properties window is not closed when the GameObject is deleted and the Properties window is not focused
- ComputeBuffer readback fails when Render Graph is enabled
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
Add comment