asked 2020-03-23 11:02:20 +0300
with my XA2 I can do calls, but when I want to terminate, I often look at a completely black screen, and I must wait the other party to hook up. Now my screen will light up and show the relatively silly call terminated popup briefly. How are we supposed to terminate calls from a black screen without hardware button? For short calls, the screen is only dimmed and I can terminate via tapp on end call, which is quite ok.
answered 2020-03-23 11:47:10 +0300
That "for short calls, the screen is only dimmed" part makes me think: are you using headset? Or speaker?
Which would mean the display is going through normal dim after inactivity and then blank sequence -> Just press the power button to turn display on & terminate normally via call ui.
(The fact that end of call leads to display lighting up to show call terminated dialog indicates that this is not related to some proximity sensor woes.)
EDIT 2020-03-25:
The way it is supposed to work is ...
Incoming call (phone is ringing): if/when proximity sensor is not covered, display is turned on and then kept on until call is answered or ignored.
Active call (you called someone or answered incoming call): display is blanked when proximity sensor is covered, and unblanked when proximity sensor is uncovered. If display is on long enough, normal dimming/blanking timeouts do apply and display will eventually turn off (and e.g. power key needs to be used to turn it on again). Also, if speaker/headset is used, the proximity sensor rules do not apply.
If proximity sensor is misbehaving so that it constantly reports "covered"
If proximity sensor is misbehaving so that it constantly reports "not covered"
Now, with that in mind
@danfin: Your original description plus "always calling phone to ear" comment -> sounds like you have situation with proximity sensor stuck in "not covered" state.
and @filip-k: "can't switch the display on as it only show itself for a brief moment" -> implies proximity sensor stuck in "covered" state. (Also, both cover and proximity sensor are used for determining whether it is ok to unblank display - if either one is misbehaving, problems are similar even if the other sensor is still functioning as expected).
It is more or less expected that dirt/sweat/grease can cause proximity sensor to incorrectly report "covered" (swiping the sensor are with cloth is usually enough to remedy such situations). As device ages (scratches on display, dust gets under display, whatnot) these situations are more likely to occur and/or harder to recover from.
Having proximity sensor stuck at "not covered" state is much more rare. Basically the only situation where I've seen it happen is XA2, Xperia 10 & co where some underlying sw issue causes the sensor to stop reacting to changes - at which state it reports whatever the last value happened to be until the sensor is power cycled (normally p-sensor is always kept powered on, but as a workaround in these devices it is kept powered off except during calls etc).
As a quick and temporary relief to sensor-stuck-at-covered situations: Doing a triple power key press will make the system ignore both proximity and cover sensor until they start reporting changes again -> display will power up, calls can be answered and terminated. However, effectively the sensor is now stuck in not-coverd state -> pocket calls etc are more likely.
Thank you. Always calling phone to ear. Probably forgot I might need to switch the phone on to be able to terminate a call via menu.. A quite complicated sequence. (On the X, I can't remember ever pressing any buttons to then terminate the call via menu). And yes, proximity wise the XA is quite well working.
danfin ( 2020-03-23 12:50:18 +0300 )editOn a few % of long calls on my XA2 I noticed that I can't switch the display on as it only show itself for a brief moment. It doesn't react to any screen tap. Even magnetic case doesn't help to switch on the screen. After a while (I didn't find how long or how yet) the screen start to react properly and I can test proximity sensor and it passes. Puzzling and annoying :(.
Filip K. ( 2020-03-24 08:54:29 +0300 )edit"always calling phone to ear" -> proximity sensor stuck in "not covered" state. Could be true. After putting several calls on hold inadvertently by triggering the pulley menu with my ear, I am anxious not to touch too closely.. 'power key is reserved for ignoring the call': I can't reproduce that one. My power key always shuts off the screen. However, after a call, pressing powerkey to activate the screen may take a while. I'd suggest to set powerkey to terminate call.
danfin ( 2020-03-25 08:44:38 +0300 )edit@danfin: "Reserved for ignoring call during incoming call" i.e. when phone is ringing, pressing power key silences the ringing. Similarly ringing alarm/timer can be snoozed/ended with power key. Other than those exceptions power key is used for display control.
spiiroin ( 2020-03-25 12:52:11 +0300 )editanswered 2020-03-31 11:56:08 +0300
of course, as I switched to XA quite late, I did not know of that patch: Markkyboy, Pulley menu removed Now I don't have a option to put calls on hold, but so what.
how does this answer correlate to your original question?, I ask as I am the author of the patch you have linked, so I am curious as to how that patch helps your problem....or not, again I ask because your answer seems a little sarcastic, what do you mean by "but so what"..?
I made the patch in response to a question posed by another user, who said that calls were accidentally being put on hold, but you are saying in your original question that you struggle to end calls, so I am curious as to what you are getting at, please clarify/quantify your answer.
Spam Hunter ( 2020-03-31 14:35:49 +0300 )edithullo @Edz, sorry, not at all.. it's a mistake: Actually I am having two issues with my XA2, 1) inadvertent setting calls on hold and b) not being able to terminate as the display is off. Happy to have found your patch, I now 'answered' the wrong question... ( actually hoping for a hardware button call terminate solution )
danfin ( 2020-03-31 16:08:53 +0300 )editAsked: 2020-03-23 11:02:20 +0300
Seen: 774 times
Last updated: Mar 31 '20
