Screen stays blank when moving the phone [duplicate]
There are situations where my Jolla 1 would activate a sleeping screen - for example when the alarm goes off or someone calls. My impression was that the motion sensor would activate the screen in these situations. On my XA2, the screen stays blank and I need to press the power button. This usually has a side effect like muting the alarm which I would like to avoid.
In another situation, I managed to take the call but then the screen would blank out again. When I pressed the power button, the screen only activated for a second, which didn't allow me to hang up before it went blank again. After the other side hung up, everything was back to normal.
Does someone have an idea what could be the cause and how I would fix it? The screen is set to blank after 2 minutes and the lock is set to 5 minutes. I'm not sure which other settings are relevant but I only flashed the phone a few days ago, so there should not be much change.
Duplicate of: https://together.jolla.com/question/193485/any-workaround-for-malfunctioning-proximity-sensor-xa2/
That's probably the the problem with the proximity sensor acting up, there are several temporary workarounds, such as disabling the sensor (not good, as your ear tends to disconnect) or a timer resetting the sensor at (more or less) regular intervals, this is the one I prefer but it's not perfect as the timer does not run or runs very slow during sleep.
Search for proximity sensor to find the possible solutions.
Kim ( 2019-04-17 14:59:18 +0200 )editThanks, I'll give it a try! Having the correct keyword to look for is half the solution :-)
lambda ( 2019-04-17 15:00:50 +0200 )edit@lambda - press the power button quickly three times in a row. I use a flip cover, so it works as a great indicator when the proximity sensor starts acting up - if the display doesn't wake up when the flip cover is opened -> 3 x power button -> back to normal working mode agian. :)
raketti ( 2019-04-17 15:06:06 +0200 )editThank you very much, it's a good work around! The other question mentions that this is also going to be fixed in 3.0.3
lambda ( 2019-04-17 15:07:29 +0200 )edit