My phone (T-mobile Wing) has Open Touch v3.0 installed on it, but the problem is that every few minutes during a call, it makes a beep and the call counter restarts at 0. Later when i check my phone, i have a missed call from the person I was on the phone with. I don't know why it does this and would like to fix it. Anyone have an idea? I think its a rom setting, but I don't know how to disable it.
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?
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.
Twice now this has happened today:
Phone is on wireless charger for some time (over 30 min, less than 2 hrs)
Incoming call comes in
Phone vibrates but does not ring (I have calls set to do both), but otherwise looks/acts normal (wakes up, displays caller, etc.)
After the call is completed I put the phone back on the charger and place a test call to it. Both vibration and ringtone work as they should.
My only hypothesis thus far is that the phone doesn't ring the first time after the phone locks during charging, but this is probably not correct.
1. Has anyone else experienced this issue; and if so, how should I/we notify google if they haven't been already
2. Any ideas on how to fix this
FYI I have unlocked BL and root but otherwise stock.
This is happening also to me(and not only during the charging), i have set both of them(ring and vibrate),after a long period of inactivity it only vibrates, after this it works fine until it gets a long period of inactivity again..?
Is this a hardware issue?
There is a bunch of other posts about a problem with the speaker working intermittently. I have the same issue (unrelated to charging or not). I can check every ten minutes and half the time sound is working, the other half silence. Seems like a serious bug (or hardware fault?).
wakd said:
There is a bunch of other posts about a problem with the speaker working intermittently. I have the same issue (unrelated to charging or not). I can check every ten minutes and half the time sound is working, the other half silence. Seems like a serious bug (or hardware fault?).
Click to expand...
Click to collapse
I tend to belive it's a software issue, else the speaker works just fine.
Discovered this morning that my alarm doesn't seem to work when charging. Could this be related at all?
It's not related to charging as I have got this multiple times without having the phone charging.
Also, I noticed that sometimes in some apps, sound doesn't work either.
I have the same issue, It doesn't seem to be related to charging for me as well. My phone will ring for one second and then vibrate from then on. I find that it works normal after rebooting for the first call and then after that it happens again for every call there on after. I am completely stock 5.0 btw
I bought the phone since sep, phone calls drops happens in every single situation home, in work,
I tried every possible solution, even flashed custom lineage rom, while calling the other side voice suddenly dissappear then call drops after 5 secs, this can be avoided if i removed the phone off my ear and let the display turn on. Do u think the phone has a hardware prob?