Database Info

Ringer delay causing lots of missed calls.

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?

Get the phone out of the case + Answering a call = Impossible?

Does this happen to any one or is it just me?
I have an ordinary case for my Touch Pro. Almost 10 out of 10 times when the phone rings and I reach out to my phone, try to take it out - boom - the call becomes a missed call. I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call. It is very annoying and how to avoid this????
Thanks

kmahesh said:
Does this happen to any one or is it just me?
I have an ordinary case for my Touch Pro. Almost 10 out of 10 times when the phone rings and I reach out to my phone, try to take it out - boom - the call becomes a missed call. I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call. It is very annoying and how to avoid this????
Thanks
Click to expand...
Click to collapse
there is a key disabler cab look for it

There are many options how to disable the touchscreen.
There was a topic not long ago about this.
Answerkey Disabler
PocketShield (I currently use this one)
TouchProLock
Sensorlock
Throttlelock
S2U2 (not recommended for TP, drains the battery for unknown reason)
All these deal with locking the TP.
Sorry for not posting links but I don't have much time. All of them are available on XDA though.

You do have the option of extending the time it takes for a call to go to voice mail, it can be extended up to 30 seconds. The option is under settings > phone > Services > Call Forwarding
There is also a lot of lag on between the time the caller's phone is ringing and you get a ring on the Fuze

I guess this is not because of the keys. Just keep the phone in front of you and try to call your phone and see your self, first you will see the incoming call indicator light, and after some time you will start hearing the ring tone. Now by the time you take the phone from the case - it's a miss call. I tried to search all over XDA but didn't find a way to start ringing immediately when call comes, I read some where that this is due to the dialer skin and by using default WM dialer this can be fixed. I didn't try this.

kmahesh said:
Does this happen to any one or is it just me?
I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call.
Click to expand...
Click to collapse
I think he was talking about the touchscreen being active on incoming calls.
If however the problem is in the delay, then the dialer skin is the key.
You have to change it to the WM default (it does work, the lag is almost gone) and have the ringtone in WAV format (not tested, I didn't bother to put any wavs).

if you get rid of the dialer and switch to WM
you will lose functionality including the symbol to show bluetooth being on or off

I downloaded and installed disableanswerkeys and it works fine. It took a while for me to understand the cryptic question it asks in the beginning - i get stumped if there are two negatives in a sentence So It is on and i tried and it works ok. I also downloaded sensorlock and throttlelock. Yet to try these ... will post my comments.
the lag in answering the call - i believe there is a separate thread about that, right?
Thanks for the help

lbhocky19 said:
if you get rid of the dialer and switch to WM
you will lose functionality including the symbol to show bluetooth being on or off
Click to expand...
Click to collapse
LOL, that's what happened to my bluetooth......thanks

Problem with "Phone" app on Nexus One

Hello,
I have been having random problem with Nexus One since the first day I got it. (Stock Firmware, Stock Firmware-rooted, Cyanogen-beta3)
Symptom : Once in a while, when making a call you will hear just one ring on Nexus One, then silence for another two rings (the other end is still ringing), then the call is cut off. --- When dialing problem shows up, you won't be able to receive a call either. When the phone rings and you slide to receive a call, it will just hang up right a way.
Temporary Fix : I found temporary fix for this issue by restarting the phone, or just killing all the running apps.
This is my first android phone, so I'm really not sure if I done something wrong. I did some search but found no topics covering this issue.
Cheers!

Problem: Making call results in silence

I've been having a weird problem that has become very frequent in the past couple days. When I place a call, I will just get complete silence while the counter starts to indicate the call is being made. I thought it was just a failed attempt to connect to the network, until I did some testing and found out that the call is actually being placed and the other person can answer - but they also get silence. When this happens, I don't get that initial little digital S3 tone you hear to indicate a call is being placed, and also don't hear the normal phone ringing tone you hear when you are waiting for someone to pick up. This is now happening on 25-50% of calls I place, so when I don't hear that tone, I just have to hangup and retry a couple times until I get the tones to indicate the call is going to work. It seems like this used to happen maybe once in a very long while, like maybe if you hang up and then immediately try to dial out again...but again, it's now happening very frequently. Anyone know what is going on here?
FYI, I've been on CleanRom 6 for quite a long while with no issues, and I haven't made any changes to my phone setup in weeks that would seem to account for this new issue. Any help would be appreciated. If I can't figure it out, looks like I'll try to wipe everything and start from scratch to see if it'll get rid of the problem.

Update: Tracked this issue to Soundabout app I had recently installed. Verified by uninstalling and reinstalling that app to fix/recreate the problem.

Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls

Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.

beejuan said:
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.
Click to expand...
Click to collapse
If you don't have issues with the Pixel 2 and do have issues with the Pixel 2XL, why don't you ask in the Pixel 2XL forum?
Sent from my Pixel 2 using Tapatalk

ajrty33 said:
If you don't have issues with the Pixel 2 and do have issues with the Pixel 2XL, why don't you ask in the Pixel 2XL forum?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Quite simply, I missclicked into the wrong forum. Ta!

beejuan said:
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.
Click to expand...
Click to collapse
Hey, did you get any answers on this,. I'm having the same frustrating issue.

I just started to have this problem a few days out of nowhere. Some on Reddit are having issues too.
https://www.reddit.com/r/GooglePixel/comments/80qh32/pixel_2_xl_dialer_problems/
I found that plugging the phone into charge or computer fixes the issues for a little bit...

Had similar issues with my Verizon Pixel 2. After some searching, I restarted the phone in safe mode and the problem went away, meaning it's a non-stock app interfering with the phone app. I restarted in 'normal' mode, uninstalled Facebook (it's always f'ing Facebook), and have had zero issues since.

thibadude said:
Had similar issues with my Verizon Pixel 2. After some searching, I restarted the phone in safe mode and the problem went away, meaning it's a non-stock app interfering with the phone app. I restarted in 'normal' mode, uninstalled Facebook (it's always f'ing Facebook), and have had zero issues since.
Click to expand...
Click to collapse
Thanks for the fix! Phone.app was killing me!