My phone has a very noticeable delay on incoming calls. I'll see it light up and flash for a bit, take a few seconds to get caller ID, then it will finally ring once before going to voicemail. All the while the caller is hearing the phone ring but I'm not...I tested it. Since I don't stare at my phone all day I have a high volume of missed calls because many times I only get the last ring. Any ideas what's going on? I tinkered with settings in Advanced Config and DiamondTweak. No dice. I'm using the stock Fuze Rom.
Isn't this normal behavior?
I've set my Kaiser on GSM mode and I can hear calls coming in on my computer's speakers a full 2-3 seconds before the phone actually rings.
diar said:
My phone has a very noticeable delay on incoming calls. I'll see it light up and flash for a bit, take a few seconds to get caller ID, then it will finally ring once before going to voicemail. All the while the caller is hearing the phone ring but I'm not...I tested it. Since I don't stare at my phone all day I have a high volume of missed calls because many times I only get the last ring. Any ideas what's going on? I tinkered with settings in Advanced Config and DiamondTweak. No dice. I'm using the stock Fuze Rom.
Click to expand...
Click to collapse
I have the same problem (htc org. rom)
Maybe this will work
I noticed that when someone calls my phone, they get two rings before my ringtone turns on.
After a second, my Fuze's LED starts flashing, then my ringtone starts playing after another second.
I have an idea:
1. Go into "Start > Settings > Phone"
2. Go to the "Services" tab
3. Highlight "Call forwarding" and then click the "Get Settings..." button.
4. Change the "Forward after:" dropdown box to something higher (e.g. "30 seconds")
It won't help the ring delay, but I think this will give you a little more time before the call is sent to your voicemail. I haven't tried it, but let me know if that helps
NuShrike said:
Isn't this normal behavior?
I've set my Kaiser on GSM mode and I can hear calls coming in on my computer's speakers a full 2-3 seconds before the phone actually rings.
Click to expand...
Click to collapse
I wouldn't call this normal. This is the first mobile phone that I've had that has had delays that long. If I didn't keep my phone next to me for most of the day, I'd probably miss more of my calls as well.
adamantypants said:
I wouldn't call this normal. This is the first mobile phone that I've had that has had delays that long. If I didn't keep my phone next to me for most of the day, I'd probably miss more of my calls as well.
Click to expand...
Click to collapse
I agree with you, this lag is very big problem, I missed a lot of calls, most of people must call me again because they are forwarding to voicemail at first time before I find TP (I cannot change in forwarding to 30 sec.
I'm wondering how it is in Diamond.
This is very frustrating. Nothing seems to fix this problem. I've reduced the call ID match to five digits instead of eight. I've made sure that Ring Time is set to "without delay" in DiamondTweak. I'll try the idea to change the call forwarding time but this seems to be a major problem in the OS itself. With this issue, Voice Command problems, the GPS lag and other issues I might have to jump to another phone.
Do cooked ROMS have these same issues?
I've got the same issue.. using T.I.R. V8R ROM, so yes, this delay is present also on custom ROMS. It has to do with the dialer skin?
This was discussed in a thread on an app that causes the vibrate pattern to match the ring pattern in hacks & discussions (I think called VAlert). The vibrate pattern starts immediately and the ring is delayed so the app isn't perfect (unless you build a delay into the vibrate but that's separate). The solution seems to be an app from tweaks2k2.net that I hear removes the delay. This is an issue with all WM phones. I haven't tried tweaks2k2 but I hear it works.
the tweaks2k2 fix - to eliminate the 3 second ringer delay - didn't work for me. so i went into the network phone settings and set the call forwarding to 25 seconds (it was 10). that didn't fix the ringer delay but now at least my phone rings three or four times before going to voicemail. i guess that will have to do for now.
diar said:
the tweaks2k2 fix - to eliminate the 3 second ringer delay - didn't work for me. so i went into the network phone settings and set the call forwarding to 25 seconds (it was 10). that didn't fix the ringer delay but now at least my phone rings three or four times before going to voicemail. i guess that will have to do for now.
Click to expand...
Click to collapse
it don't work sorry
Doing some debugging, on the Fuze at least the ringer delay seems to be tied to the bloatedness of the dialer.. it has a whole bunch of imports so its loading alot of stuff up every time you get an incoming call.. I'm afraid the only solution for this will be a dialer that does not bring in those kind of dependancies (PTT, Video Share, G-Sensor, etc)
The fastest way to go would be using the default windows dialer, but you'd lose all that functionality.. but hey. It would ring instantly!
I'll look into stripping the dialer from my clean ROM and providing a cab..
Confirmed. Removed the AT&T dialer skin from my rom and called my phone, rang as fast as any other phone would.. So the dialer skin is indeed the culprit.
Dang AT&T. Dang them and all their bloatware.
I'm going to corporate store to complaint. To all of them within a 10 mile radios.
I've posted my Beta 1.5 with the dialer removed. It's not an official fix by AT&T, but it is a fix..
I'll see if I can whip up a .cab to stop the dialer from loading in the stock AT&T ROM, that should help there too.
i like this dialer...but not that much. how do i disable it? in advanced config, i saw an option to enable the phone dialer skin or the default windows mobile dialer. would switching to the default fix it without causing any other problems?
EDIT: switched to default dialer and that fixed it. it also seems to have fixed the problem of having to re-enter the data connection password after a soft reset.
This set of cab's should do the job for anyone who doesn't want to install Advanced Config (it's a single registry entry HKEY_LOCAL_MACHINE\Security\Phone\Skin - Enabled=0/1)
Wow it really is about two seconds before the phone rings. Hm I never missed a call yet on this phone. where do you keep your phone that it takes so long to answer it?
AT&T's network lets you set the number of seconds before the call rolls over to voicemail, as do others, I believe the default on AT&T is 20 seconds, with a minimum of 5 and a maximum of 30, so if someone has it set to 5, that leaves only 3 seconds..
Of course they could just set it higher, but that's a different issue
So then a simple fix would be to go into your voicemail and set it to 22 seconds and then you still have the same time to pick up that phone. But still how does the 2 second dely really make you miss all them calls?
So I was typing a message this morning when a call came in. Before I even realized it, the incoming call screen popped up and I hit the Decline button. Is there an app or mod or setting I'm not aware of that will keep the incoming call screen from coming up when another app is in use? I read that CyanogenMod has a setting like that. The phone rings and a notification appears but the Accept/Decline buttons don't pop up immediately. Is there a way to get that functionality on a Sense ROM?
Since updating to Lollipop, whenever I have a phone call I hear the ring tone (even if custom for the person), but when I open my LG cover I get a lock screen instead of the usual incoming call screen I used to get pre-update.
I have to unlock my phone, go to Phone App and choose "return to incoming call" to get the screen so I can answer it.
Has anyone else noticed this issue? Have I inadvertently set something to cause this?
Similar Issue
karnesh said:
Since updating to Lollipop, whenever I have a phone call I hear the ring tone (even if custom for the person), but when I open my LG cover I get a lock screen instead of the usual incoming call screen I used to get pre-update.
I have to unlock my phone, go to Phone App and choose "return to incoming call" to get the screen so I can answer it.
Has anyone else noticed this issue? Have I inadvertently set something to cause this?
Click to expand...
Click to collapse
Hi, I am also facing similar issue after updating my Nexus 5 to Lollipop.
While the screen is locked, incoming call is shown as notification on the locked screen. It needs to be tapped twice to open and then swipe to respond to the call.
I have the same issue. No solutions yet
This is just really dumb made from Google..
So I've been having this problem for a while now. Basically, when someone calls me on Whatsapp, I can hear ringtone but turning locksreen shows nothing. Same thing when I unlock the phone, say for example I am on the home screen, I can hear ringtone, but no pops up notification to tell that a Whatsapp call is taking place.
So, this means: 1) if I'm at the lockscreen and get Whatsapp call, I would have no way to answer or end call. 2) if I unlock and use the phone and the Whatsapp calls come, I also dont know if it is Whatsapp and also cannot swipe down from notification and accept/reject call.
So, I would need to physically open Whatsapp and then it would show a call is coming through and so i can accept/reject call.
Reinstalling whatsapp fixed this problem. However, I believe it is only temporary. My settings: AOD off, Edge Lightning off and does not send notification for Whatsapp.
Does anyone else experience similar problem? Strangely, Whatsapp call is the only thing that causes problem.
This is a new phone, and the problem is that during an incoming call:
Phone does not wake up, and has to be tapped to wake, or power.
Then, the Incoming call is shown in the notification area and the phone still needs to be unlocked.
I've searched for the resolution to this without success.
Anyone know what I can try?
I sometimes have the same issue. I don't know why. It's difficult to answer when they call