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

[3.0.3.8] Glance screen (low power mode) no longer activated on Xperia XA2

asked 2019-04-24 23:55:52 +0200

adekker gravatar image

updated 2019-04-25 00:14:58 +0200

On the previous release (3.0.2.8) the proximity sensor would still trigger the activation of the glance screen, but it no longer does.

It only seems to affect the Xperia XA2

Usual activation commands:

mcetool --set-low-power-mode=enabled
mcetool --set-lpmui-triggering=from-pocket,hover-over

Edit: On the Jolla tablet it also no longer works, Xperia X still works fine

edit retag flag offensive close delete

Comments

Confirmed. On my XA2, LPM works immediately after the screen turns off, but stops working after a few seconds. It looks like the proximity sensors does not wake the phone once it goes to sleep. (this may be related to the announced battery drain fix?)

lethe ( 2019-04-25 05:21:03 +0200 )edit

yes. it works only 1 time

TMavica ( 2019-04-25 05:56:02 +0200 )edit

I am overall happy with Xperia X since the glance screen is working as well as the fingerprint sensor. But cant use Wire to its fullest do to the lack of updated Android support. So I flashed Sailfish on XA2 this morning and Wire works just fine. I thought I'll be fine with no LPM and no fingerprint working, but it feels awkward to press the power button every time I see the led blinking, and then enter the unlock code. My XA2 came with SBH90C case. So in the settings menu under screen I allowed the cover of the case to control the activation of the screen. Now when I open the cover the lock screen is on and at least I don't have to push the power button. Closing the cover puts the phone to sleep. Thought this might be a helpful info to someone who likes using a case. I'll move the sim back to Xperia X for now. It only needs a fingerprint when taken out of pocket.

777 ( 2019-05-14 23:08:49 +0200 )edit

1 Answer

Sort by » oldest newest most voted
10

answered 2019-04-25 09:06:59 +0200

spiiroin gravatar image

Proximity sensor in XA2 starts to misbehave if it is kept powered on for long periods of time.

To keep things like in-call proximity blanking working, we have implemented "on-demand" proximity sensor mode and activated it by default on XA2. Basically the sensor is kept powered off unless there is some immediate need to know the sensor state.

Unfortunately this is more or less mutually exclusive with all features that require having always up-to date proximity sensor state - such as the glance/low power/sneak peek mode.

Note that once the sensor is powered on, there is some hysteresis for powering it off - which explains the "lpm triggering works for a while after putting the phone to sleep" type symptoms.

edit flag offensive delete publish link more

Comments

@spiiroin Thanks for your answer.

Is Jolla actually planning to completely resolve the proximity issues on XA2 instead of bypassing it with a workaround? :/

Alex ( 2019-04-25 11:02:30 +0200 )edit

I still do not understand your explanations completely. My major issue with the proximity sensor was that it did not disable the touch screen during a call. This lead to unwanted actions like disabling the microphone or speaker during the call by the ear. Is this issue addresse with this, too? I've updated 13 hours ago, so I had no chance to experience it.

SagaciousT ( 2019-04-25 11:22:21 +0200 )edit
4

@Alex It used to be so that there are sensor drivers in kernel and problems can be fixed. Nowadays the norm starts to be that actual sensor hw access happens somewhere in dsp side black box where we have zero visibility and there is little to nothing that can be done about some issues...

spiiroin ( 2019-04-25 11:26:48 +0200 )edit
1

@SagaciousT: What we could gather the problem was: After some time something somewhere powers off the p-sensor while sfos sensorfwd is left believing that it is still powered on -> effectively the sensor state gets stuck to whatever was the latest reported value (restarting sensorfwd/similar actions which were used as workaround by some users power cycle the sensor and get things back to sync again). Now we more or less ensure the sensor is powered on when needed by keeping it off until something like incoming/active call happens.

spiiroin ( 2019-04-25 11:36:56 +0200 )edit

@spiiroin: Thanks for explaining this. I'll see what happens when receiving a call following a longer uptime period. I'll not forget to complain if something's still wrong ;-)

SagaciousT ( 2019-04-25 11:40:19 +0200 )edit
Login/Signup to Answer

Question tools

Follow
10 followers

Stats

Asked: 2019-04-24 23:55:52 +0200

Seen: 882 times

Last updated: Apr 25 '19