Hi,
Do any of you 750 owners have seen this before?
Lately (a week or so ago) I started to get calls and the "notification" popup won't come up. I hear the ring and vibrate and there is a phonecall icon on the top bar next to the data arrows but the notification is missing so I can't see who's calling.
If/when I answer I can finally see the caller information.
This doesn't happen with every call (probably with about half of them per day).
Any idea or did you hear about something similar?
Thanks,
Zax.
Haven't had that particular problem, but I've had other issues when calls come in.
Sometimes (after I've put the device from silent to regular mode using the top slider) the phone doesn't ring and doesn't vibrate although the call notification is showing on screen. This gets fixed after one or more soft resets.
On a fair few other occasions - this is intermittent and extremely annoying - the phone doesn't react at all when someone calls me (no notification, no vibrate, no ring - nothing) but I get a audible and visible missed call notification after the caller has given up / been diverted to voicemail. This problem goes away of its own accord eventually; restarts don't seem to have any effect.
Seriously, if this device wasn't a fairly good PDA as well as a phone, I'd put it in the bin.
I have some strange bug in Call Timers. Before hard reset I had 19 calls and they lasted about 1 hour, but Call Timers showed that all calls were about 14 mins. Now after hard reset I have one call 3 mins 10 secs, but call timers all calls shows 1 min 7 secs. Any suggestions why?
I've noticed the same; settings - device information - call duration seems to have correct total talk time, whereas 'call timers' in the call history seem to show significantly less.. In my TP the All Calls and Recent Cellular Calls (in call history) also show the excact same time, which looks like a bug..
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?
Ok this is wierd, I went out for a cycle this afternoon and was listening to music using the headset on my Desire S the whole time.
When I got back I went to use the phone to make a call and noticed that the last call in my log was an outgoing one to my voicemail timed at 15 minutes into my cycle ride, and lasting for 46 seconds.
How could this happen? I did a quick check and if the music app is running and you go to make a call then the music cuts out on the headset and of course you hear the call. So it can't have been any accidental screen press on the phone in my pocket.
I'm now getting a bit paranoid that there is some rogue app on my phone trying to make calls. If there is, how do I find it?
For info I'm using the VoidU rom with the Unity kernel and latest radio from the recent OTA update.
therecluse said:
Ok this is wierd, I went out for a cycle this afternoon and was listening to music using the headset on my Desire S the whole time.
When I got back I went to use the phone to make a call and noticed that the last call in my log was an outgoing one to my voicemail timed at 15 minutes into my cycle ride, and lasting for 46 seconds.
How could this happen? I did a quick check and if the music app is running and you go to make a call then the music cuts out on the headset and of course you hear the call. So it can't have been any accidental screen press on the phone in my pocket.
I'm now getting a bit paranoid that there is some rogue app on my phone trying to make calls. If there is, how do I find it?
For info I'm using the VoidU rom with the Unity kernel and latest radio from the recent OTA update.
Click to expand...
Click to collapse
I have the exact same config as you at the moment. The only way to find out which application could be responsible would be to check which applications have access to the dialer.
Settings > Applications > Manage Applications > "Application Name", then scroll right down to the bottom to view permissions.
very strange!
if there is some app trying to make call, it should not be appeared in the call log, i think
After I noticed another phantom call in my log the other day, I've finally solved this...
Seems that a double-click on the headset button when you're listening to music will redial the last number called.
In the original situation I'd forgotten that I'd paused the music briefly and taken my earbuds out, to talk to someone at some traffic lights. Must have double-pressed the button by mistake and by the time I put the earbuds back in, the voicemail call had timed-out as I had no messages so I was unaware what had happened.
Can't see this double-click, redial, function documented in the manual anywhere!
Every time I make a call the dialer automatically switches into conference calling mode and wants me to input another number or contact. I can't get out of this screen to end the call or end the call from the notification pane. Killing the dialer app causes it to retry the call when it restarts. The only way to stop this loop is to restart the device. Resetting the phone hasn't fixed the problem.
Note: Even though I typed this in the first person it's actually my friend's device. I'm just too tired to remember to keep to 3rd person and wanted coherence.
Note 2: I have witnessed the fault but I was not present for the reset so I'm not 100% certain that it was done properly.