search

ubports / ubuntu-touch

Ubuntu Touch's issue inbox is now migrated to GitLab.
https://gitlab.com/ubports/ubuntu-touch
1.28k stars 110 forks source link

FP2: On wakeup brightness of the screen first drops [to minimum?] then after delay gets back to "usable". #1162

Open kwah-gh opened 5 years ago

kwah-gh commented 5 years ago

Steps to reproduce

When phone is in "standby"

Expected behavior

Actual behavior

Logfiles and additional information

dmesg seems to be not updated.

logcat.txt

Ingo-FP-Angel commented 5 years ago

Do you have auto adjust brightness enabled? Is there a difference if that's on or off?

kwah-gh commented 5 years ago

Yes, auto adjust brightness is enabled. And yes, it makes a difference.

Ingo-FP-Angel commented 5 years ago

I've just checked with auto brightness + brightness slider set to minimum. In fact I see the behaviour that the screen first dims down and after quite a while gets brighter again. But it's nowhere near as dark that it would be unusable (in a room with no lights on, not in direct sunlight).

kwah-gh commented 5 years ago

I do have difficulty with dimmed screen in a daylight while in the room, and if I am outside (no direct sunlight either) screen appears almost black to me.

UniversalSuperBox commented 5 years ago

I can also confirm this issue. When waking up the device, it goes to minimum brightness and then turns the brightness up. This can also be seen when turning on automatic brightness for the first time. I'll speculate the sensor returns "very dark" when it's first turned on then gives a real data point later.

vokimon commented 5 years ago

Indeed this buggy behavior also happens with the preinstalled Android in my FP2. So it could be the sensor. Yet, having this fixed in Ubuntu is a nice incentive to jump in.

Flohack74 commented 5 years ago

I dont see we can fix this is the sensor comes up with unreliable data. We have to follow its values otherwise the whole function gets sluggish and makes no sense anymore. I would close this as a problem of the firmware of FP2.

kwah-gh commented 5 years ago

Only sensor? There maybe more to this, since sensor controlled brightness can get lower than brightness level, which one gets on a minimal manual setting. I would expect these two should match each other at least at two points: 0% and 100%.

FPfabi commented 4 years ago

Hello,

having the same issue with FP2.

Device: FP2, New Camera Module Channel: Edge Build: 2020-W18, 16.04 LTS

in case other devices could have the same problem in the future, would it be solved by an additional feature "Min. Screen brigthness on wakeup" setting? E.g. UT OS takes the sensor reading and compares to the user specified minimum, after X sec. transitions to raw sensor value?

Flohack74 commented 4 years ago

Well it seems the sensor reports that values, its not 100% sure if we can fix that. We rely on what we get from the Android sensors.