Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0b18
2023.3.0a13
Issue ID
UUM-55696
Regression
No
[Android] The value of "Screen.brightness" is always 1 when changing the device's 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
4. Change the brightness of the device
5. 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 is always 1
Reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0b18, 2023.3.0a13
Testing environment: macOS Sonoma 14 (Intel)
Not reproducible on: No other environment tested
Reproducible with devices:
VLNQA00017 - Huawei Nexus 6P (angler), CPU: Snapdragon 810 MSM8994, GPU: Adreno 430, OS: 8.0.0
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
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
VLNQA00293 - OPPO R17 Pro (PBDM00), CPU: Snapdragon 710 SDM710, GPU: Adreno 616, OS: 10
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note:
I feel like the OS in the device or the device itself is broken.
When I tested it, I found that changing the system brightness by command or the source code doesn't change the system brightness settings on the device.
When I run this command "adb shell settings put system screen_brightness 130", it doesn't change the system brightness settings on the device.
And after changing the system brightness settings, when I ran the command "adb shell settings get system screen_brightness", I could see it didn't return the proper brightness.
As a result, when I created an app using Android Studio, it showed the same broken results as in an app created using Unity.
This issue is not caused by Unity.