We have moved to a new Sailfish OS Forum. Please start new discussions there.
8

[3.x.x] Automatic display brightness adjustment stuck

asked 2020-05-03 13:51:00 +0300

rastakajakwanna gravatar image

updated 2020-05-03 19:52:25 +0300

Affects: Xperia XA2-Ultra Dual SIM

I am not able to say at what version this start appearing, but it's around the last three updates.

Sometimes the display insists on keeping too dark even on full sun light. Before this started happening, I didn't have to adjust the automatic level from level around 20% and it was covering comfortable level of brightness the whole day. But after the recent updates I am getting into situations when I have to disable automatic brightness in order to see anything on the display.

It appears to me like it would get stuck at low display brightness level during evening/night and then it's unable to set max during the day.

If I disable and enable the function there is no immediate change. It gets unstuck next day (I have to confirm) or after phone reboot.

I am using only apps from Sailfish store but I am also participant to early access, maybe there could be a link.

edit retag flag offensive close delete

Comments

which device ? please tag accordingly

pawel ( 2020-05-03 19:39:58 +0300 )edit

Description updated. It's Xperia XA2 Ultra D-S

rastakajakwanna ( 2020-05-03 19:48:04 +0300 )edit

Please see this post as well, as it may help your case: https://together.jolla.com/question/211211/light-sensor-stops-responding-xa2/

jiit ( 2020-05-06 14:27:16 +0300 )edit

2 Answers

Sort by » oldest newest most voted
3

answered 2020-05-03 22:48:46 +0300

AkiBerlin gravatar image

updated 2020-05-05 13:42:40 +0300

Happens to me with the Xperia 10 as well.

Co-occurrs with not waking up the phone with the fingerprint sensor. Touching the fingerprint senor results in vibration but the display stays dark. It can be lit with the ON/OFF switch

Only reboot helps

EDIT: Lacking basic skills I only managed to make a screenshot of what I believe might be relevant in journalctl with respect to the problem

journalctl

edit flag offensive delete publish link more

Comments

@AkiBerlin Your log has failures to start proximity sensor and accelerometer -> likely that all sensors are failing (except fingerprint sensor which is not handled via the same route as "regular" sensors). Which then explains things like ...

If the last value reported by proximity sensor is "covered" -> fingerprint wakeup is not allowed to turn display on. (Power key turns display on even when p-sensor is covered and thus still works.)

If the last value light sensor reported was "low light" -> automatic brightness tuning leaves display too dark.

Accelorometer is used for orientation -> switches between landscape and portrait probably do not work, and so on with other features that rely on sensors.

spiiroin ( 2020-05-06 06:10:29 +0300 )edit

@spiiroin: thank you - accordingly my problems go along with the other problems reported here in TJC (which in a way is good with respect to fixing the problems).

I wonder what causes the sensors stopping to work.

BTW: I do not have this problem with the XA2, only with the Xperia 10 (both on 3.3.0.16)

AkiBerlin ( 2020-05-06 09:36:44 +0300 )edit
3

answered 2020-05-04 10:33:28 +0300

spiiroin gravatar image

Automatic brightness requires functioning light sensor.

Problems with proximity sensor can affect fingerprint wakeup.

-> Use CSD tool to check whether these sensors are functioning as expected.

Possibly related: Xperia 10 rotation sensor problems -> https://together.jolla.com/question/217920/bugxperia-10-autorotation-stops-working/

edit flag offensive delete publish link more

Comments

@spirion: very good hint, thank you! Indeed I have this problem after for example using the Zoom App with Android support on the Xperia 10. Annoyingly, the proximity sensor is active when using Zoom so that touching UI elements close to the proximity sensor is rendered impossible. Even after quitting the Zoom app, the proximity sensor stays active. Stoping Android support also stopps the proximity sensor form being active.

The problem with the very dark screen (it is not black!) cannot be cured by stopping Android support, however. I know it co-occurs with the fingerprint sensor wake-up fault, but it seems not to be related to the proximity sensor because touching the finger print senor triggers a signal (I feel vibration) but does not result in a lit up screen.

I will check the sensors with the CSD tool next time I encounter one of these problems (btw: they are rare)

AkiBerlin ( 2020-05-04 15:00:44 +0300 )edit

CSD tool identified correctly that the issue is caused by light sensor which is not working when this happens.

Could it be also hw-related due to failing compass test?

Anyway, I suspect some Android app, I have to figure out which one is causing it. Weird thing is that I wanted to lower the risk of incompatibility and issues and I install apps only with Aurora store.

Although, can I check system logs for some pattern? Any ideas?

rastakajakwanna ( 2020-05-05 00:02:39 +0300 )edit

Regarding the Xperias 10 sensor rotating problem, this also occurrs to me from time to time

AkiBerlin ( 2020-05-06 18:45:23 +0300 )edit

Still just observation of the problem, but it seems to be related to Android apps when handling display dimming.

If I watch a video, pause it and keep it like that, application, which will try to keep the display on, is more likely to cause that issue.

Please let me know where to look for logs and I will try to gather it.

And yes, sensors get stuck on some unsupported value which effectively disables them.

rastakajakwanna ( 2020-06-09 14:38:07 +0300 )edit
Login/Signup to Answer

Question tools

Follow
4 followers

Stats

Asked: 2020-05-03 13:51:00 +0300

Seen: 358 times

Last updated: May 05 '20