Delay between receiving call and phone ringing

[Laks]

This has been touched on in a few previous threads but i could not really find a solution. What happens is i get a call, I have vibrate and ring selected, there is a slight delay from the phone coming out of sleep to the lock screen then a second or two to vibrating then another short delay to actually ringing.

this can be quite annoying as by the time i hear it and get it out to answer its gone to voicemail.

some people have suggested increasing the ring time before going to voicemail and this is a work around but is there a way to reduce the "lag" or delay when a call is received and to when it rings.

I have tried both standard ringtones and mp3 ringtones and even tried reducing bitrate of mp3's right down to reduce size but it does not work.

this problem also goes to receiving other notifications like sms, the screen comes out of sleep and the notification pops up but the sound will come 3-4 seconds later!!

any other solutions or work arounds would be very much appreciated!

[Laks]

cheeky bump up

[Shel]

Don't have a solution, but I can tell you that I experience the same problem, and it's a pain!

I now try to keep my bluetooth headset on. At least then, I hear the ring tone instantly through the bt headset, and can answer the phone in time.

What's strange is, for me, it isn't consistent. Sometimes I see that a call came in and went to voice mail, and I didn't even hear the phone ring... even though it was sitting right next to me. Other times, I have plenty of time to answer the call.

It IS annoying!

[Laks]

that is true, have had the odd occasion where I switch on phone and there is a missed call notification, but i am sure it didnt ring. oh well...will try increasing ring duration, and just hope the dev team are aware of this.

[BAMAToNE]

I've noticed this, too. Also, a lot of times the phone will start vibrating but the screen won't show anything for about 5 seconds? I have no idea who's calling, so I have no idea if I should answer it or not.

I chalked it up to the phone's memory and processes. The calling part of the phone is probably just a process/app like all the rest, so if you've been using other apps a lot (music, Twidroid, Opera Mini, Chomp SMS, USA Today for me), then it takes a few seconds to launch the caller app because it has to free up some memory. At least, that was my take, anyway. Still quite annoying.

[Scythe]

I've noticed this, too. Also, a lot of times the phone will start vibrating but the screen won't show anything for about 5 seconds? I have no idea who's calling, so I have no idea if I should answer it or not.

I chalked it up to the phone's memory and processes. The calling part of the phone is probably just a process/app like all the rest, so if you've been using other apps a lot (music, Twidroid, Opera Mini, Chomp SMS, USA Today for me), then it takes a few seconds to launch the caller app because it has to free up some memory. At least, that was my take, anyway. Still quite annoying.

Typically it's one of the following (if you're running on 1.5 or better):
- There's a broadcast receiver intercepting prior to the UI showing. Things like SMS Popup, Chomp SMS, etc. If that receiver doesn't let go of the context quick enough, it'll lag. If you have tons of apps receiving it'll do the same.
- Memory, if apps are using up all the RAM then Android has to "force-flush" apps running in the background to gain back memory before continuing on with spawning the activity

[BAMAToNE]

Typically it's one of the following (if you're running on 1.5 or better):
- There's a broadcast receiver intercepting prior to the UI showing. Things like SMS Popup, Chomp SMS, etc. If that receiver doesn't let go of the context quick enough, it'll lag. If you have tons of apps receiving it'll do the same.
- Memory, if apps are using up all the RAM then Android has to "force-flush" apps running in the background to gain back memory before continuing on with spawning the activity

I don't use any notification features in Chomp SMS, but I do run SMS Popup and Missed Call, so that could be part of it. I've been thinking about ditching Missed Call anyway.

As for the second point, it's as I thought.

[JPH3]

I'm gonna blame the 1.5 update. The update has left my G1 bloated and laggy everywhere. The delayed caller ID issue was mostly corrected with RC33, then got 2x worse after 1.5.

[iPhone2MyTouch]

I've been having the identical problem. Determined to try my hand at a fix, I wiped the phone after backup, then added apps one by one, using hubby's phone to call myself each time. Long story short, I've removed handcent SMS as well as Missed Call. No problems thereafter. I truly miss Missed Call, but hey, I need PROMPT ringers more. Shame though.

(MyTouch Donut 1.6)