Replies: 1 comment 4 replies
|
One UI updates can change the Samsung setting or service that a threshold feature depends on, but I would first separate a permission problem from a model-specific behavior change. Please check the Galaxy Max Hz version, exact One UI 8 build, whether adaptive brightness is enabled, and the two threshold values. Also confirm that the feature still has the privileged access it requires after the system update. The project documentation notes that some secure-settings features need WRITE_SECURE_SETTINGS on non-rooted devices, so re-granting that permission after an upgrade is worth testing. A useful diagnostic is to capture a log while crossing the threshold in both directions, then compare it with a manual brightness change. If the manual change works but the threshold event is never logged, the trigger or Samsung setting key changed. If the event is logged but the value is rejected, it is more likely a permission or One UI restriction. Testing with adaptive brightness off and a moderate threshold can also rule out Samsung's automatic brightness loop fighting the app. The device model, build number, app version, permission method, and a short log around the threshold transition would make this much easier to reproduce than the model name alone. |


Uh oh!
There was an error while loading. Please reload this page.
Hi, the brightness threshold option is no longer working on my phone, which is a Galaxy A73 with One UI 8. What is the problem? 🤔
All reactions