[Q] No calls when screen in standby GT540 2.3.4 CM7 Swiftdroid v2.0 RC1 and 2 - General Questions and Answers

I have had some problems with the last 2 releases of CM7 2.3.4Swiftdroid RC1 and RC2,and I just wandered if anyone else is having the same issues here?
- When my phone screen display is on, my phone accepts calls without a problem
- The screen turns off automatically after not been used and it will accept calls for a good 5-10 minutes after this without a problem
- However, once the screen has been off for more than 10 minutes,if I receive a call my phone does not ring the caller just gets my voicemail immediately The call shows in my missed call log when I next power on the screen or the phone wakes up to send me an SMS to notify me if a voicemail has been left? Its as though the phone has gone to sleep and doesn't wake up to accept the call...?
I have been into Call Settings->Incoming call in background and checked an unchecked but this doesn't make any difference?
Version RC3 has just been I am unsure whether upgrading will resolve?

Related

Can't see who's calling... (?)

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.

Phone beeps every few minutes in a call

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.

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?

Incoming calls in background

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?

[Q] MikShifted ROM - Lost ability bypass lock screen with incoming calls

So i upgraded my MikShifted ROM to the latest release (was running 1.7 before I believe) and now i lost the feature that bypasses lock screen on an incoming call. Before when a call came in it would jump straigh the ANSWER/IGNORE screen while showing me all the info of who is calling, etc.. now when the phone rings I can't even see who is calling until i unlock the screen. is there any way to disable lock screen for calls? I went through all the settings but can't find anything
It should still say answer or ignore, on the LS upon an incoming call. Also the device wakes when you have a call. If it's the 3.0 LS just pull the ring to the green circle to answer. The red to ignore. You can also just flip the phone face down to ignore, and silence an incoming call.
TEAM MiK
MikROMs Since 3/13/11
Ok so i tested it out with all 3 lock screen options:
1) Sense - worked as expected, i see who is calling and the Answer/Decline buttons to pull the ring into
2) Andriod - Just the lock screen with no indication of who is calling and no shortcut to answer/decline
3) Honeycomb - same as #2
Yes that's right. You can also still just flip it over to silence, and ignore.

Categories

Resources