As the title says the phone's screen won't turn on after I ended a longer call, i have to press the power button to get the screen working.
Did it happen to you also?I have this phone for 2 months but it never happened in the beginning, this seems to be a recent issue.
Is it a hardware issue or a software bug?I've tested the proximity sensor and it works just fine as much i can tell, it switches the screen of and on, it never happened to wake the screen during a call and to activate random keys.
Another strange thing that i noticed during a call:If have the keypad up and i lay the phone horizontally the screen won't turn off if i hover my hand over the proximity sensor but if i put the phone vertically the screen goes off or if i hide the keypad the screen also goes instantly off.
Whenever I receive a call, the screen does not turn on unless I hit the power button to mute the call, eventually it turns on. Even when using the phone, a call would show the heads-up notification and it seems like the entire phone lags. Hitting the answer button takes at least 1 second for the call the to be receieved and even longer for the screen to switch to the calling screen. I am on CM12.1 0904 with ak303 and a custom profile for the kernel.
After every reboot,the proximity sensor works fine for the first few calls. It properly turns off the screen during a call when the device is near your ears & turns the screen on when it is moved away.
But post 4-5 calls, the sensor stops working. Irrespective of how you hold the device, the screen does not get turned off. User needs to manually turn the screen off & on using the lock button. This continues for all calls after that.
Rebooting the device fixes this problem again but only for 4-5 calls...
Can Anyone Found The Fix???
I don't use a lock-screen, so sometimes I get a call, and the screen turns on in my pocket, but I may not hear it, and all mayhem happens as the touchscreen is constantly in contact with my pants. Is there a setting to keep the screen off even if there is an incoming call.
Hi. I've had this annoying issue as long as I've owned by 2S. I usually use the phone on speaker phone. On both incoming and outgoing calls in probably 50% of the calls I make, after around 1 minute, the caller can no longer hear me and I can no longer hear them. I have figured out if I press the 'hold' icon to turn hold on then off again, audio works again but at the time the call goes silent, 'hold' is definitely showing as off. Really can't figure out what is going on. Anyone else had this or know of a remedy? Thanks if you can help me out.
Most probably you pressed the hold button with your cheek while talking. I am not joking. The proximity sensor is... peculiar on this phone. Eventually the screen turns on during the conversation even if the phone is close to the ear.
Make a test: just after answering the incoming call (green button), switch off the screen with the power button. Unless you receive a notification, the screen will not turn on.
Hi guildamx. Thanks a lot for your input. I had read about the strange proximity sensor issue but don't think this is directly the cause in my case. Most of the time at home, I use the phone on speaker (placed on desk in front of me with no proximity sensor being activated) and am sure that the screen is never touched during the call as it is hands-free on my desk. I have done some more experimenting this morning and on multiple tests, the audio works fine when the screen in on (at the start of a call) but after screen timeout (I have mine set to 1 minute), the audio in and out is blocked. Switching the screen back on doesn't rectify, only putting on hold then off hold. Oddly, if I use the phone without speakerphone (held to ear), the proximity sensor kicks in and turns off the screen as expected, the blocked audio issue doesn't occur. It only occurs when the screen times out the screen. Very strange.
Apparently when the phone goes into deep sleep the audio is somehow killed. Very strange and never happened to me.
I would suggest testing a different rom. Definitely it seems software related.
Sorry for not being able to provide further help.