Intermittently, when initiating a call, the screen goes blank/ black for 5-6 seconds, or longer, and does not wake up. During this time, the phone does not respond to any tactile or soft input, but ringing and other audio continues to emit from the earphone.
I do not have any sort of screen cover/ protection, or any other obtrusion to the proximity sensor.
This is extremely annoying, as sometimes, I would like to immediately hang up, or place the call on speaker, but cannot do either as no input registers.
Is this an isolated issue to me, or CM7 on the AT&T SGS2? I am not running any special apps or background services.
It 'feels' as if this is mostly caused by some sort of lag, as it does happen intermittently. i can't pin down a particular pattern during which this persists. Anyone else experience any similar symptoms?
sweetrobot said:
Intermittently, when initiating a call, the screen goes blank/ black for 5-6 seconds, or longer, and does not wake up. During this time, the phone does not respond to any tactile or soft input, but ringing and other audio continues to emit from the earphone.
I do not have any sort of screen cover/ protection, or any other obtrusion to the proximity sensor.
This is extremely annoying, as sometimes, I would like to immediately hang up, or place the call on speaker, but cannot do either as no input registers.
Is this an isolated issue to me, or CM7 on the AT&T SGS2? I am not running any special apps or background services.
It 'feels' as if this is mostly caused by some sort of lag, as it does happen intermittently. i can't pin down a particular pattern during which this persists. Anyone else experience any similar symptoms?
Click to expand...
Click to collapse
this same issue is what made me drop cm7 and go to UnNamed
I had it and would just hit the power button to turn it back on.
Dropped this on their forums:
http://forum.cyanogenmod.com/topic/34235-cm7-screen-temporarily-5-6-seconds-black-when-placing-call/
Related
Does anyone know how to stop the screen from turning off during a call?
Move the phone away from your head?
Otherwise, why would you need it to be one when you're talking on it?
turn on the speaker, i think that disables the sensor.
This is a huge problem with 2.1.
In Android 1.5 on the Eris, you could push the TRACKBALL during a call to wake up the screen.
In 2.1, you only have two options. Pull the phone away from your head (often works, but not always, especially if you're trying to get through a phone tree, and often going back to the screen) or push the 'End' button.
If your phone's screen has been off LONG enough, the 'end' button will wake it up.
If it hasn't, the 'end' button will both wake up the screen AND END THE CALL!
It's a huge risk, and unnecessary. THE MINUTE the OTA comes out, I'm calling HTC about it, and asking them.
Oh, and for what it's worth, Screebl Lite takes care of this.
Just set up Screebl, mine is like 20-90 degrees for both portrait and landscape, and for the in-call activity, I have it not be active when up to my ear.
Screebl works GREAT to keep the screen on properly during a call.
Still calling HTC about it. That functionality should be built in better, or at least give me a way to wake up the screen when it gets stuck.
That is exactly my problem. When i go to wake it up to navigate the through menu options it hangs up alot. Very irritating! I will try Screebl.
Thanks!
you can also press any of the two volume buttons and that will wake it up without any bad effect except for a volume change.
Good tip about the volume buttons, I wasn't aware of that trick.
thanks
sometimes my phone won't wake up when I pull it away from my ear, but I usually just move my hand over the prox sensor and then back and it generally wakes up.
Keep Screen
This is a good thread. I had this problem too. After reading your posts I used the copy of KeepScreen that I already had and it worked also! May be my imagination but proximity sensor seems more responsive too.
This is a strange one. When placing a call, the screen immediately goes to sleep. If I want to access the keypad or end the call, I can't seem to awaken the screen either by moving the phone away from or toward my ear or by pressing any of the buttons on the phone itself. The only thing that seems to work is plugging in headphones as it triggers an event that wakes the phone.
I've been through the motion settings and can't see anything related to this that would be disabling my screen from waking. Any ideas?
Thanks
Ok, so lately I've noticed when I've had to call a few numbers that need me to Press 1, 2, 3 etc on the dialpad that I can't do it right away. When I put the phone to my ear, as I would expect the screen switches itself off. When I pull the phone away from my face the screen comes on again immediately, but there's about a 5-7 second delay before I can actually press anything. In those seconds after the screen comes on, it wont accept any touch input whatsoever. It's not delayed, presses I make during those seconds just aren't registered at all, then suddenly it begins accepting input as normal. It isn't just number keys either, it's the entire screen, so I can't press End Call until nearly 10 seconds after I've actually pulled the phone away from my face, nor can I move the phone away and press the Speaker Phone button quickly.
This only happens when the screen comes on after being against my face though. If the screen is just turned off and I press the power button, or double tap to wake, it accepts input immediately, so I don't believe it's a hardware problem.
Currently running 4.4.4 rooted, image was made from stock and pre-rooted prior to being flashed onto the phone.
Has anyone else experienced this issue?
yeah i've experienced this as well. doesn't happen on speaker though.
No, doesn't happen on speaker phone. If the screen goes off from that and I turn it back on then the screen responds immediately. It only seems to happen in cases where the screen auto shuts off due to it detecting that it's against your face.
Please let me mention that I'm not holding the phone in any weird manner, certainly no different that all the previous phones I had.
I'm also with the global international miui rom on the snapdragon version using the default dialer.
While on the call, and although the screen is black, I somehow manage to activate the mute or on hold function.
What typically happens is that the other person suddenly complains, I check the phone and I find either of the two buttons highlighted.
It happens so often that I'm certain its not by accident. Without being absolutely certain, the screen is dark when this happens. Its very difficult to check because at the moment you try check, the proximity sensor kicks in and the screen lights up. What I know is that at the beginning of the call my face is touching the screen and as expected nothing happens. But later and very unexpected it mutes.
Any ideas would be welcome.
Its happens to me to. Did you succeeded to resolve it ?
Not sure if this issue is specific to the ROM I'm running or what, but has anyone else noticed that the call recording just randomly tries to turn on when taking calls?
My setup is as follows, 'Kate' device running LOS 13.0-20170301 with Radon kernel (though it did this with the stock LOS kernel too) and it happens fairly intermittently, but I can't figure out how it's happening. What happens is I'll be on a call, and suddenly my phone will vibrate once, and the 'enable call recording' pop up is displayed on my screen. I can only assume that somehow the proximity sensor randomly turns the screen on and my cheek hits the call recording button, as I'm being very cautious about not hitting any buttons, or even the touch sensor on the back, in case one of these things triggers it.
I guess the next question I'd have, does anyone know what sort of shortcuts could enable call recording? I guess my next step if this doesn't ring any bells will be to try and catch it on a logcat.