Screen turns on sluggishly
When unlocking the phone, the screen first turns on, but is dim. After a half a second or so it brightens to normal. Only seems to come up when brightness is set to the minimum and automatically adapts to brightness
We have moved to a new Sailfish OS Forum. Please start new discussions there.
When unlocking the phone, the screen first turns on, but is dim. After a half a second or so it brightens to normal. Only seems to come up when brightness is set to the minimum and automatically adapts to brightness
When display is off, also the ambient light sensor is powered off. It is supposed to work so that the last known ALS value is used while display and sensors are being powered up -> the display wakes up to the same brightness as what was used before the display was turned off. If the device is moved from dark to bright environment (or the other way around) while the display is off, the last known value is wrong and brightness is adjusted once fresh reading from the sensor is available.
I.e. waking up to wrong display brightness once after change in lightning is normal, but it seems that something is not working as expected - possibly due to re-introduction of lpm display states, see: https://together.jolla.com/question/50246/bug-10819-brightness-at-100-on-waking-up/
Anyway, I'll need to do thorough inspection of ambient light sensor logic during display power cycling.
EDIT: It was the same bug. During display wakeup "automatic" setting ended up being ignored (in "sensor not in use" instead of "no sensor data available yet" kind of way) and "manual" setting took effect. The bigger the difference between manual vs automatic, the more visible the glitch is -> in dark environment the display is initially too bright, and in bright environment too dim; once the sensor is powered up and delivers data, the brightness gets back to expected level.
This thread is public, all members of Together.Jolla.Com can read this page.
Asked: 2014-07-17 09:05:26 +0200
Seen: 368 times
Last updated: Aug 01 '14
We want to create our own TOH [answered]
[Fixed in 1.0.3.8] Crash when linking contacts? [not relevant]
Time slider usage in video player of Gallery app causes the app to hang [duplicate]
QAudioOutput isn't integrated with system volume and libresource like QMediaPlayer
Bug: E-Mail synchronization does not work as configured [released]
Word prediction should be always turned off when entering passwords in Android apps [released]
Don't enforce focus to textfield [answered]
[Implemented in 1.0.3.8] Email: Honour Reply-To header [answered]
You might want to check resources on the phone. Run "top" command from Terminal app (q quits). See if there are processes eating CPU or memory, or if swap is running low, or system is eating resources (Cpu(s): sy, wa, ...).
penpen ( 2014-07-17 13:33:34 +0200 )editconfirmed. only happens when brightness is automatic and set to minimum
virgi26 ( 2014-07-17 14:04:51 +0200 )editHave the same problem since 1.0.8.19. Sometimes the light sensor even has no influence on display brightness after wake up. What helps for me is to change the brightness manually to a higher level and back to minimum to make the auto brightness work again.
Stefan P ( 2014-07-18 15:04:30 +0200 )edit