asked 2014-12-23 12:41:13 +0300
Hello! After update to Vaarainjärvi screen brightness changes too frequently. Even when I slightly bend the phone the brightness immediately changes. It looks very annoying :(
Does anybody have the same behavior?
answered 2014-12-29 10:18:10 +0300
Previously adjustments due to ambient light sensor / brightness setting changes were done using constant velocity - which basically meant large changes took looong time to finish and made users feel nothing happened.
Now the transitions are finished in constant time (600 ms) regardless of the magnitude of change -> the device reacts faster which is good or bad depending on user expectations and reason for the change -> the logic probably needs to be revisited, perhaps something like delaying the reaction to sensor change to avoid unnecessary pumping up and down.
Meanwhile the default time value can be adjusted from command line. Using something like 1500 ms should make things much calmer:
(mcetool can be installed via: pkcon install mce-tools)
EDIT:
How it works is that there is optional 9 point median filter with configurable sample time that "eats away" temporary changes / slows reaction to longer lasting changes in light level, followed by either constant time or constant velocity display brightness change.
The 1.x behavior (instant reaction to sensor change in relatively slow 8%/s brightness change) can be activated via:
mcetool --set-als-input-filter=disabled --set-brightness-fade-als=-8
The 2.x default behavior is: ignore short living changes (lasting < 625) ms and then perform the display brightness change within one second:
mcetool --set-als-input-filter=median --set-als-sample-time=125 --set-brightness-fade-als=1000
If that seems too flickery, you can require the change in lightning to last longer before any action is taken, say 2.5 seconds:
mcetool --set-als-sample-time=500
And/or slow down the rate of finishing the brightness level change, say 1.5 seconds:
mcetool -set-brightness-fade-als=1500
Or if you like it really subtle, use both slow to react filtering and low constant velocity change:
mcetool --set-als-sample-time=800 --set-brightness-fade-als=-5
answered 2015-02-12 11:33:10 +0300
I've got the Jolla Phone now for couple of days. so i can't tell how it was before the update came.
Today i was sitting in a unlit bus outside it was still Dark, playing around with my Jolla but I was nearly trowing up because the Jolla was changing the screen brightness according the streetlamps! the Sensor was doing what it should but waaaaay to fast! everytime the streetlamp came the screen got dark and after bright again till the next streetlamp came.
maybe there should be a delay of 1sec. or an averaging of the signal over 1 or 2 sec. and adjusting according to that? i had now couple of different Mobile phones but that is the worst of all.
Asked: 2014-12-23 12:41:13 +0300
Seen: 1,043 times
Last updated: Oct 11 '16
Are you putting your finger in front of the brightness sensor (top-right) or is this just moving the phone around? I agree that it seems to have become quite a bit more "responsive" whereas before it used to be slower
vitaminj ( 2014-12-23 13:09:21 +0300 )edit@vitaminj, just bend the phone. No any obstacles in front of it. Room with low level of light, single glow lamp. Seems like light sensor became too sensitive.
Valerij ( 2014-12-23 15:00:06 +0300 )editWas riding the bus yesterday, and with every street light we passed the brightness went up, then down again. Confusing!
sunnystar ( 2014-12-23 15:33:49 +0300 )editI have also saw this behaviour. Sensor indeed seems to be too sensitive. Would be great to have a way to change that sensitivity via terminal (and later on in the settings app?)
Flickta ( 2014-12-23 17:00:39 +0300 )editI also recognized that the brightness changes more frequently since the update. And would prefer the lazy behaviour of before too.
Halo2 ( 2014-12-23 18:55:11 +0300 )edit