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?
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
Hi guys, i've had some issues with WM 6.5 i've tried a lot of roms for test and common use, but ive had an issue in most of the roms, im not sure if the problem is the rom or any other installed program, sometimes (not always) when i have an incomming call, appears the window to answer the call with the slider, then i use the slider to answer the call, and then my screen is frozen, the call was not answered and the phone is still ringing, it stops til i loose the call and then i have to call back, ive tried to find whats happening but im not able to find an answer, could you please help me or point me to the right forum?.
Thank you.
Hi all,
i have a question about the phone app.
Every time i receive a call, my phone get's locked, i can't do anything, until the caller hangs up. So i cannot mute or turn on speakers etc.
When i call someone myself, i have to press the powere button a few times to get the caller in the forground so i can enable speaker, numpad, etc..
I'm running OpenSensation, but i have the same issue on all the other aosp roms (ICS)
I did flashed the firmware by mike, so that one should be up to date.
Anyone else having the same issue ?
EDIT
Maybe there is something broken, now i have it on all other roms... too.
Wonder if you can check the sensor status with adb, any ideas ?