It happened to me again today. But maybe I found a workaround: when the screen went dim, I covered the front-facing camera for 5 seconds: the screen went a bit brighter (weirdly enough, it should go dimmer when it detects darkness) and when I removed my thumb, it went back to full brightness.
I’ll try to confirm whether this trick works next time it happens.
I’m also trying to see if setting the brightness slider a bit lower all the time helps: I have a feeling the bug might be caused by some sort of overflow in some variable. So perhaps if the overflow occurs in the variable that controls brightness, setting its base value lower might give it more room to get brighter before it hits the overflow.
This is all speculation of course. I’m just playing around to see if I can find a workaround, and perhaps find clues as to why this happens
Yes, usually the proximity or ambient light detector sensor isn’t far. That’s what I meant to hit when I covered that area with my thumb. I didn’t describe it well, sorry.
Edit: I falsely assumed I installed a new fairphone patches. Turns out, it was only CalyxOS patches. So actually nothing new on the Fairphone side of things.
Wait, are you sure that you have the July update? AFAIK, it hasn’t been publicly released yet. The topic you commented on is actually about the June update:
you’re right of course. I got an update, but it only was the calyxOS kernel update. I just assumed it included a fairphone update without actually checking. The vendor and firmware versions are still on May 5ths, so nothing has changed there. Well, this means there still is hope … Thanks for pointing that out!
Now it’s gone really dark and the brightness isn’t returning to normal. The phone is quite cool and I’m in the shade. Rebooting ain’t fixin it. It’s been like this for 2 hours now.
Really quite annoying. I’m willing to tolerate this and more because I’ve internalized that there is sadly a price to pay for the right to repair one’s property, and escape Google’s fascist corporate surveillance a little in 2023. Had I not, I’d be returning the phone at this point.
Hi everyone, I’ve made some other tests and debug yesterday.
Can confirm that it’s related to the quiet-therm-usr sensor.
With an sh script like this:
for VARIABLE in $(seq 0 95)
do
cat /sys/devices/virtual/thermal/thermal_zone$VARIABLE/type
cat /sys/devices/virtual/thermal/thermal_zone$VARIABLE/temp
cat /sys/devices/virtual/thermal/thermal_zone$VARIABLE/trip_point_0_temp
done
I have got all the name, actual temperature and threshold of the sensors.
The list is long, but quiet-therm-usr is:
quiet-therm-usr 39416 43000
So, 39,4 C° actual temp and 43 C° the threshold.
Then I’ve tried to poll data while using the phone and the display dimmed when this sensor hit the threshold:
When the threshold is reached this sensor send an uevent and trigger a “cooling_device” called:
panel0-backlight
255
168
When the display is at full brightness is like this:
panel0-backlight
255
0
The value 255 is the “max_state” and 0 or 168 is the “cur_state”.
To fix this there is a thermal-engine.conf in the system folder, that actually is empty.
Or probably there is some configuration in the ROM firmware or proprietary blob.
Anyway I have updated the issue in Gitlab and asked if it can be fixed/patched with the next beta release.
Hope they are not on vacation, because now with high weather temperatures it’s dimming even indoor, when the air conditioning is off.
Yes, hope that it can help them to resolve the issue quickly.
Anyway it’s only an analysis of a user, probably there’s is some other related issue under the hood.
Because from what I have read it started with Android 12.
So, I don’t know if something changed on the OS side.
E.g. : Android Dynamic Performance Framework
But for now, like Bon Jovi said, I will “keep the faith”.
@anon64862762 , would be great to have an update. again many days have passed with your idealistic customers tolerating issues which are actually pretty unacceptable.
I have a question for those who know - first time for me with an alternative ROM, so I don’t really know how this goes.
My Fairphone runs CalyxOS. Since Fairphone 4s running stock Android or /e/ are also affected, I presume the issue is either with one of the drivers or with AOSP.
Assuming it’s a driver: will Fairphone push the fix as some APK to install? Or is it done through a system OTA update in all cases? If the latter, do I have to wait for the CalyxOS folks to pick up the fix and push an update of their own my way?
Your last messages about debugging motivated me to do some stuff as well. I found this requesting nits when no mapping exists line interesting as well and when I Ducked/Googled it I got back to this topic
I see the error pop up quite often. When the screen times out and when the screen is turned on again. But also indeed when the brightness error is triggered when e.g. calling. Which I guess relates more to the issue below. But might also be completely unrelated since the error line seems to happen all the time, but not one of the those bugs themselves occur.
So then I tried my old Google Pixel 3. Ran the same command and filtered only for the Error log level and above that with adb logcat -s *:E, as I also did with my Fairphone 4. And wow, the difference is day and night. On the Pixel there are hardly ANY errors. On the Fairphone 4 you get to see so many of the error tags it’s almost as if it’s a demo of logcat or as if I enabled a low level debug mode. But even worse, I excluded info level logs and such… I knew Fairphone was bad, but jezzzzz.
Anyway, will dig into this more some other time. Maybe I have to setup an Elastic Search cluster to make sense of this amount of errors
