phone not coming out of sleep when ringing - Galaxy S I9000 General

This has happened a few times, I get a call, my ringer goes off but the screen is stuck in sleep and doesnt switch on no matter what I do, in the process I miss the call.
Just wondering if anyone else has had trouble bringing phone out of sleep, not necessarily when ringing, but it has also happened at other times, I have to press menu 4-5 times before I get a response sometimes.

Related

Different kind of notification issue

I recently installed the day light savings patch to my cingular 8525 so I don't know if this has anything to do with it. However, my pre-set alarms now will chime when they're supposed to, but the "notification" in the bottom left hand corner does not come up. Now, the alarm goes on and on until I turn the phone off for a short period of time. Even then, sometimes the alarm continues to ring, maybe until it times out. But I can't seem to turn off my alarm.
Anyone have an idea of what might be causing this?
I've noticed that if I turn off ALL of my alarms that it no longer does this (no alarms to come on!) but the secondary issue is then I no longer get notices when my meetings are about to start. So either I get notification for when my meetings start and every morning I struggle with turning my alarm off, or I get no notices whatsoever.
The missed calls and text message notifications are working normally.

Trouble answering calls

After I got RC33 update over the air, I've been having problems answering phone calls. My phone rings, and I press the green telephone button to accept the call, this silences the ring tone, but shortly afterward it just starts up again. Pressing the green telephone button continues silencing the ring tone and it seems like the phone will answer a call at random presses. This problem seems to only come up when the screen has timed out and requires an un-lock pattern. Any help would be appreciated.
same damn thing happens with mine after the update i press the answer button and nothing happens just silences the phone....it really annoying and since the update my home screen freezes alot more

immediate sleep screen when in call. How to disable it ?

I guess post title says it all..
Whenever I start a phone call, the screen goes off...it is very annoying.
Any way to stop that behavior ?
I have searched this forums with no luck.
I am running Modaco's 2.3 ROM on an unbranded hero.
I have tried using Powermanager tools to define a 2min timeout in the "screen off during call" feature but with no luck.
thanks for the help!
Cheers,
-Eric
There is an app called shake awake which wakes up the screen during a call when you move it away from your face.
http://www.cyrket.com/package/com.maplekeycompany.apps.shake
Thanks. i'll give a try but the bad reviews are scaring me.
Is there a setting anywhere for that screen turning off while on call ?
i didn't liked "shake awake" the calls got dropped when the phone "shaked" sometimes i had to call the same person 3 or 4 times because the call ended. first i thought it was my phone but the problems started after installing shake awake. after i removed it my phone worked again
Keepscreen does the trick. Works absolutly great. The full version is able to keep the screen on with every application. Very handy when reading mail, browsing etc. You must set youre screenout delay in settings from the phone to 30sec.
http://nl.androlib.com/r.aspx?r=keepscreen
I'd like an app that actually does kill the screen as soon as the call button is pressed. Sometimes the Hero is too slow to turn off the screen and you hang up the call with your cheek.
Thats annoying.

black screen of death after a missed call

i wonder if anyone else is expriencing this problem. if im away from my phone and i get a phone call and miss the call when i wake up my phone it will vibrate once then the screen goes black and vibrates twice and then reboots itself or will stay balck and vibrate occasionally. after this happens i have to reboots serveral times to get the phone working again. alot of time once i hit the power button to put it to sleep the phone will get thje black screen of death. any workartounds or solutions to stop this from happening it has happened on all dk28 roms i have tried
adamw1101 said:
i wonder if anyone else is expriencing this problem. if im away from my phone and i get a phone call and miss the call when i wake up my phone it will vibrate once then the screen goes black and vibrates twice and then reboots itself or will stay balck and vibrate occasionally. after this happens i have to reboots serveral times to get the phone working again. alot of time once i hit the power button to put it to sleep the phone will get thje black screen of death. any workartounds or solutions to stop this from happening it has happened on all dk28 roms i have tried
Click to expand...
Click to collapse
Try flashing back to stock DK28 through Odin and see if that fixes it. I have encountered this problem before, Odin fixed it for me with no issues.
Sent from Carl Sagan through the Cosmos
I had that happen before on stock DI18. It would reboot if I got an email/text/message/missed call/etc, and if I changed the notification sounds to something other than default, it would work fine.
Since I did a hard reset, it hasn't happened.

Mysterious vibrating once a second

I saw some very strange behavior from my Verizon Galaxy S5 (running OptimalROM) this morning. I was watching a video at my computer with the phone (screen off) sitting on my thigh, when I start hearing something about once a second -- I pause the video, and figure out it is my phone -- I pick up my phone and discover the noise is actually the phone vibrating. It is vibrating for a full second, then nothing for a second, then it vibrates again for a full second, and this kept repeating. I turned the screen on, thinking there was an incoming call or an emergency alert, or something, but there's no phone call and no notifications of any sort. After the vibrating continued for about a minute, I finally decided to reboot the phone to see if that would stop it -- which it did, and it has yet to reoccur.
I've never seen this behavior from any Android phone, so I thought I would ask the community if they've seen it and know why it was doing it.

Categories

Resources