Hey all,
I just did a little test as I had seen some people reporting problems of there phones not ringing when someone calls them until the 4th or 5th time that it rings on there end, well turns out I'm having the same problem. My phone is not ringing when it should be and when it finally does ring, it only does so for about 5 seconds and then I miss the call.
What's the problem here? I did a search on the forum and google and can't really find a solution. Thanks for your help!
BTW: Running Myns 2.2 RLS 3, Netarchy 4.2 More Agg HAVS, SetCPU with screen off profile, and Launcherpro Plus.
You may have your screen off min clock speed set too low,if your min is at 128mhz,try raising it to 245mhz.I've also found that 128mhz min will work ok on some phones as long as you set the screen off max to 245mhz.
Sent from my PC36100 using XDA App
I think you might want to check your slot cycle index. It's a setting that determines how often your phone checks the tower for incoming calls. Good reading here.
I have had that problem before too, but never really pinned it down. But one thing you can do to improve your phones response time for incoming calls is to edit the Slot Cycle Index. It is a setting in the EPST menu that decides how often your phone should check for an incoming call or message. By default it is set at 2 I believe, if you change it to a 1 it will check twice as often. Or go all the way to 0 for full effect. It can be draining on your battery in low service areas though!
To edit your Slot Cycle Index, dial ##DATA# and pick edit mode, enter your MSL# for a passcode, then pick Advanced. Find and pick Slot Cycle Index, edit it to whatever you want, select ok. Then tap menu and pick commit modifications. Your phone will reboot and then it's good to go. I have been setting my phones to 0 for a while, and you can definitely measure the difference from the stock setting.
erikivy said:
I think you might want to check your slot cycle index. It's a setting that determines how often your phone checks the tower for incoming calls. Good reading here.
Click to expand...
Click to collapse
LOL, I type too slow!
I'm having a delay in texts though too, and I don't think that it has anything to do with my screen off being set to 128 because even when i have my phone plugged in with the screen on, it still will ring about 4 times before it actually rings on my phone. (I tested this out with my home phone and cell phone right in front of me.)
Have you guys tried flashing to the latest radio yet ? Or the radio suggested by the ROM cook ??
How would I go about obtaining my MSL#? Would I have to call Sprint?
Any other suggestions of how I can fix this?
Also, how would any altercation that I made to the phone make it have a delayed ring? How would your typical evo owner go about handling this situation? If I called Sprint would they do the same thing that you told me to do, just on their end? I don't want to lose battery life over it.
Bump because it's on second page and this is becoming a very annoying problem and resulting in a lot of missed calls...
Msl Reader from the market will get you your msl.
Sent from my PC36100 using XDA App
Related
hi, considering all the amazing work going on here by the devs, this is really minor.
using Clemsyn froyo 2.2 with Haret but maybe typical question.
when it wakes from sleep with power button the screen stays alight for about 2secs. sometimes it will black out before the white/multicoloured screen goes.
can i change to say 1 min this anywhere like the screen timeout. i always have it set to 10mins for the main display. its no prob to just press end or power to relock.
ps. did have some probs with sound but solved after changing radio from 1.64.08.21,
tried 1.71.09.01 and 1.65.21.18 but no good either. using 1.65.24.36 on kaiser now and seems to be ok.
what is strange about sound is how LOUD everything is compared to the barely audible winmo and whispering ringtones
gazzacbr said:
hi, considering all the amazing work going on here by the devs, this is really minor.
using Clemsyn froyo 2.2 with Haret but maybe typical question.
when it wakes from sleep with power button the screen stays alight for about 2secs. sometimes it will black out before the white/multicoloured screen goes.
can i change to say 1 min this anywhere like the screen timeout. i always have it set to 10mins for the main display. its no prob to just press end or power to relock.
ps. did have some probs with sound but solved after changing radio from 1.64.08.21,
tried 1.71.09.01 and 1.65.21.18 but no good either. using 1.65.24.36 on kaiser now and seems to be ok.
what is strange about sound is how LOUD everything is compared to the barely audible winmo and whispering ringtones
Click to expand...
Click to collapse
The timeout is related to the number of fake v-syncs the phone is doing. There is a parameter to adjust that. Run a search for it as I forget where/how to adjust it.
aceoyame said:
The timeout is related to the number of fake v-syncs the phone is doing. There is a parameter to adjust that. Run a search for it as I forget where/how to adjust it.
Click to expand...
Click to collapse
hmm, ok thanks. will have to do some reading then.
a google search came up with some stuff to check...
and a youtube video:
"Britney Spears : Lip-Sync + Boobs being Fake"
so maybe check that one out also sometime :-D
lmao I wouldn't use google for this search. I would search inside the kaiser forums only. I am pretty sure no other phones have a need for fake v-sync's except us. I remember asking L1qu1d to add the ability to be able to adjust it several weeks ago which he did. Before it was a static value that couldn't be changed.
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Running the stock ROM, and rooted with unrevoked.
michelbites said:
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not rooted? These are things you should remember to post when you're having issues. Makes diagnostics much easier
All I have done was root it. I didn't install any rom or anything. I only rooted it to get the wifi tethering.
So screen turns on, but you are not able to press "answer" when a call is incoming?
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
nikon_rh50 said:
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm inclined to agree. Custom ROMs definitely go waaaaay above and beyond the stock one. I use a combination of MyBackup Root and Titanium Backup free for contacts/messages and apps, respectively. Once you go custom, you never go back
What I was trying to say is that the screen is locked when the phone rings and then when I go to answer the phone it will not unlock until the phone stops ringing. But like I said in the first post this doesn't happen all the time. I would say about 25% of the time it does this. Sooo... Thats what I was trying to say.
Are you using Google Voice?
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
reisa said:
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
Click to expand...
Click to collapse
I thought it was GV also but its not I uninstalled it and it would still do it.
Manitook said:
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
I'm not sure if I would like the no lock because I tend to put my phone in my pocket all the time and it would just turn on and pocket dial people. LoL
Manitook said:
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
App protector sounds like a good app for you.
Sent from my ADR6300
SetCPU?
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
smtom said:
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
Click to expand...
Click to collapse
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
POQbum said:
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
Click to expand...
Click to collapse
Well, there's something to try then - if the kernel is making the device slow to wake, use SetCPU to bump up the screen off profile and see if the issue persists.
Couple folk note just this issue in the kernel threads.
This is a known problem I struggle with myself. You may find that you can stroke up to deny the call but not unlock. It seems that this is some kind of grounding problem. Hearing that I tried setting the phone down and swiping while I wasn't touching it otherwise with some success. I've heard a quick cycle of the power button followed by an immediate swipe down can work. Some report pressing the screen firmly before swiping works. I usually just swipe up, call back and say "sorry about that, what's up?" After all, most people are used to drops and stuff because of Iphones.
I periodically goog "incredible can't answer" looking for the golden bullet.
I have I really annoying problem, when I use sense roms (only sense, not AOSP) my phone freezes almost instantly when going to sleep.
This results in the phone not ringing when people call me, and first receiving texts after i reboot the phone.
And the only way to reboot it, is to remove the battery.
If anyone knows what is causing this, please let me know how to fix it, this problem have made me miss many really important calls.
Thanks in advance
i had the same problem with official 2.2 sense rom (don't know with 2.3, i switched yesterday) , but only when i was on a place with bad network.. In big town like Paris no problem, but when i moved to smallest town with bad network i experienced same freeze...
When you hit a button only the button backlight turn on?
Exactly, only the button backlight comes on.
But I have fine reception at my location
Thanks for the reply
KasperHermansen said:
Exactly, only the button backlight comes on.
But I have fine reception at my location
Thanks for the reply
Click to expand...
Click to collapse
Did you use setcpu?
Usually it happen when you use setcpu and you make screen off profile 128 mhz.
Sent from my HTC Desire using XDA Premium App
Not anymore, because I had the same idea that that could be the problem, but it still freezes
Thanks for the reply
Today it has frozen 4 times.
And every time with massive battery drains, about 15% in a short period of time.
Well, for the moment ICS (any version) is making my phone unusable as a phone itself.
I saw some people complaining about the GSM hangups (including me), so if you let the phone sleep, you wont recieve any call. The caller will hear the same tones, as if you dont pick up the call. If you send an sms on a phone in such state, it will only appear after turning it on manually (often having duplicate SMS). When you turn the phone on - you wont even get a missed call, no signs of anything.
This problem is very hard to reproduce, it happens from time to time.
I've tried to flash any other ICS based rom on the phone - any has the same problem. The only rom i hadn't such issue is 2.3 stock/modified. But i want ICS!
Anyone have any thoughts, what can be causing this? I'm tired of this happening, people complain that the cant tell me something urgent, and i dont even know they wanted to.
UPD: There is a parial fix for this issue by Maruzko by installing an app that prevents deep sleep (but thats battery consuming offcourse).
I think that there should be some internal fix for this issue, only devs can help up with that.
UPD2: My opinion that problems that people have with clock not synced is somehow connected, coz when you turn on the phone in that state, you see the clock changing rapidly and stopping at wrong time, so changed title to include that also.
UPD3: There is an alternative way to fix the issue, but not much tested. Thanx to sideshow03.
Tests and reports are much appreciated.
Hey! I'm having the same issue as you. I'm surprised no one came up with a solution yet.
kekehi said:
I'm surprised no one came up with a solution yet.
Click to expand...
Click to collapse
Yup, me too. Currently at miui based on pac rom, havent noticed the issue, but cant be sure its really gone, or just "lucky time" until reboot.
Sent from my SGH-I927 using xda app-developers app
I'm having the same issues on a couple roms but later on today I'll flash CM10.1 and see if it goes away...
Just did with cm10.1
im in the club
braintweaker said:
Well, for the moment ICS (any version) is making my phone unusable as a phone itself.
I saw some people complaining about the GSM hangups (including me), so if you let the phone sleep, you wont recieve any call. The caller will hear the same tones, as if you dont pick up the call. If you send an sms on a phone in such state, it will only appear after turning it on manually (often having duplicate SMS). When you turn the phone on - you wont even get a missed call, no signs of anything.
This problem is very hard to reproduce, it happens from time to time.
I've tried to flash any other ICS based rom on the phone - any has the same problem. The only rom i hadn't such issue is 2.3 stock/modified. But i want ICS!
Anyone have any thoughts, what can be causing this? I'm tired of this happening, people complain that the cant tell me something urgent, and i dont even know they wanted to.
Click to expand...
Click to collapse
I have the same 'No response to a call' issue after flashing AT&T UCLJ3 rooted on a Rogers i927R Glide.
Essentially, after the Glide has been idle for a while, not sure how long, at least 30 mins I think,
there is no response from the Glide when calling it, and it goes to voice mail, but not straight away though.
I can hear a ringing tone from the phone I'm calling from, but the Glide just sits there in sleep mode.
Try several calls but the Glide does not wake up.
Haven't tried sending it an SMS when this has happens though.
If I then wake up the Glide manually, and then put it into standby again and call it, it responds as normal and starts ringing.
The thing is, it doesn't happen every time, sometimes the phone could be idle for 2 hours and still respond to a call, others times it doesn't after say 30mins on standby.
Hard to troubleshoot as its so intermittent.
This did not seem to happen on stock Rogers GB.
braintweaker said:
Well, for the moment ICS (any version) is making my phone unusable as a phone itself.
I saw some people complaining about the GSM hangups (including me), so if you let the phone sleep, you wont recieve any call. The caller will hear the same tones, as if you dont pick up the call. If you send an sms on a phone in such state, it will only appear after turning it on manually (often having duplicate SMS). When you turn the phone on - you wont even get a missed call, no signs of anything.
This problem is very hard to reproduce, it happens from time to time.
I've tried to flash any other ICS based rom on the phone - any has the same problem. The only rom i hadn't such issue is 2.3 stock/modified. But i want ICS!
Anyone have any thoughts, what can be causing this? I'm tired of this happening, people complain that the cant tell me something urgent, and i dont even know they wanted to.
Click to expand...
Click to collapse
Should this thread be merged into this one ?
http://forum.xda-developers.com/showthread.php?t=2057948
Yup, the threads are the same, but mine is older
Sad thing - cm and other jb roms higher than 4.0.4 have the issue aswell
Currently have the 312 min value with interactive governor - this does not help, some deep sleep problem not frequency related
braintweaker said:
Yup, the threads are the same, but mine is older
Sad thing - cm and other jb roms higher than 4.0.4 have the issue as well
Currently have the 312 min value with interactive governor - this does not help, some deep sleep problem not frequency related
Click to expand...
Click to collapse
It doesnt appear to be just a Glide problem with ICS from internet searching but there doesnt appear to be a solution anywhere.
I found a reference to using an App called Wake Lock which some have found may fix it but at the cost of some battery life.
https://play.google.com/store/apps/...t#?t=W251bGwsMSwxLDMsImV1LnRoZWRhcmtlbi53bCJd
Choose PARTIAL_WAKE_LOCK in the config apparantly.
Ive installed it but not activated it yet.
Still testing with WiFi sleep policy set to "Only when plugged in", where as previously I had it set to "Always".
Anyways, there are devices on ICS that do not have such issue. May this be connected only with the tegra2 platform? Even have no idea how is this issue called to search.. sleep of death? As i know, its the state, when device does not wake at all, even after pressing power. Not our case.
braintweaker said:
Anyways, there are devices on ICS that do not have such issue. May this be connected only with the tegra2 platform? Even have no idea how is this issue called to search.. sleep of death? As i know, its the state, when device does not wake at all, even after pressing power. Not our case.
Click to expand...
Click to collapse
Good point, maybe it is to do with the Tegra 2 platform or the sub revision of this ICS 4.0.4.
Yes, 'sleep of death' seems something different, when ieven the power button does not wake it.
I think our issue is referred to as not coming out of 'deep sleep' when a call/sms is supposed to wake it up.
Yesterday I had WiFi sleep policy set to be on only when on charge.
So all day I was on 3G data not WiFI. I called the Glide intermittently through out the day and it always woke up.
Today going back to normal setting of WiFi Always on to stay connected to an access point when in sleep mode. Will see how that goes.
Next I'll try:
https://play.google.com/store/apps/...t#?t=W251bGwsMSwxLDEsImV1LnRoZWRhcmtlbi53bCJd
Choose PARTIAL_WAKE_LOCK in the config apparently.
I don't have any issues with that.. sounds like a sysctl or build.prop mod though.. that's all I have changed myself without the community here.. everything works well in ICS and I do run litekernel 1.1.1 which may also be a + for the no hang issue
Maruzko said:
I have the same 'No response to a call' issue after flashing AT&T UCLJ3 rooted on a Rogers i927R Glide.
Essentially, after the Glide has been idle for a while, not sure how long, at least 30 mins I think,
there is no response from the Glide when calling it, and it goes to voice mail, but not straight away though.
I can hear a ringing tone from the phone I'm calling from, but the Glide just sits there in sleep mode.
Try several calls but the Glide does not wake up.
Haven't tried sending it an SMS when this has happens though.
If I then wake up the Glide manually, and then put it into standby again and call it, it responds as normal and starts ringing.
The thing is, it doesn't happen every time, sometimes the phone could be idle for 2 hours and still respond to a call, others times it doesn't after say 30mins on standby.
Hard to troubleshoot as its so intermittent.
This did not seem to happen on stock Rogers GB.
Click to expand...
Click to collapse
I'm running CM10.1 and not having this issue.
I did notice something though.
Hypothesis: Each ICS leak came with a different baseband. So there is an I927UCLG9 baseband, a I927UCLH2 baseband, and a I927UCLJ3 baseband. UCLJ3 introduced some ABI change that the libsec-ril we're using in AOSP ROMs doesn't know how to handle (or it straight up just has a bug).
I currently have the I927UCLH2 baseband as I never flashed UCLJ3.
Could someone more wizardlike than me whip up some baseband-only Odin images for testing?
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
braintweaker said:
Anyways, there are devices on ICS that do not have such issue. May this be connected only with the tegra2 platform? Even have no idea how is this issue called to search.. sleep of death? As i know, its the state, when device does not wake at all, even after pressing power. Not our case.
Click to expand...
Click to collapse
"Sleep of death" already has an established meaning. It means there's an intermittent whole-system freeze that only happens when the device is in standby, giving a "dead" appearance. It's been the bane of Kindle Fire developers for some time now.
I'd call this "no radio wake" personally.
roothorick said:
Could someone more wizardlike than me whip up some baseband-only Odin images for testing?
...
I'd call this "no radio wake" personally.
Click to expand...
Click to collapse
Nice term, tottaly agree.
I just can say, that I have tested the lite rom, based on 4.0.4, that has a baseband chooser in aroma installer. I've tried running it with a baseband from 2.3.6 stock rom (that was my only hope), that did not give any difference, radio still did freeze Anyway, I cant be sure I did everything right that time, and your way of solving this must be tested.
Also, my thoughts are about some ATT frequency specific things, as I cant say everybody here is complaining (most are from North America, right?). May this be caused by using glide outside of US and Canada?
braintweaker said:
Nice term, tottaly agree.
I just can say, that I have tested the lite rom, based on 4.0.4, that has a baseband chooser in aroma installer. I've tried running it with a baseband from 2.3.6 stock rom (that was my only hope), that did not give any difference, radio still did freeze Anyway, I cant be sure I did everything right that time, and your way of solving this must be tested.
Also, my thoughts are about some ATT frequency specific things, as I cant say everybody here is complaining (most are from North America, right?). May this be caused by using glide outside of US and Canada?
Click to expand...
Click to collapse
That's quite possible, as I'm on AT&T towers even though I don't have service through them (I'm with a prepaid MVNO) and I'm not having problems.
roothorick said:
That's quite possible, as I'm on AT&T towers even though I don't have service through them (I'm with a prepaid MVNO) and I'm not having problems.
Click to expand...
Click to collapse
I'm also on AT&T towers but I don't have service through them, I'm with a prepaid MVNO just like you but I'm having these problems
yivkhar said:
I'm also on AT&T towers but I don't have service through them, I'm with a prepaid MVNO just like you but I'm having these problems
Click to expand...
Click to collapse
What is your baseband version (under About Phone)?
roothorick said:
What is your baseband version (under About Phone)?
Click to expand...
Click to collapse
I927UCLJ3
braintweaker said:
Well, for the moment ICS (any version) is making my phone unusable as a phone itself.
I saw some people complaining about the GSM hangups (including me), so if you let the phone sleep, you wont recieve any call. The caller will hear the same tones, as if you dont pick up the call. If you send an sms on a phone in such state, it will only appear after turning it on manually (often having duplicate SMS). When you turn the phone on - you wont even get a missed call, no signs of anything.
This problem is very hard to reproduce, it happens from time to time.
I've tried to flash any other ICS based rom on the phone - any has the same problem. The only rom i hadn't such issue is 2.3 stock/modified. But i want ICS!
Anyone have any thoughts, what can be causing this? I'm tired of this happening, people complain that the cant tell me something urgent, and i dont even know they wanted to.
Click to expand...
Click to collapse
I'm having this issue too ;(
Hello,
I have been struggling recently to answer or reject calls when given the swipe up or down option.
When its unlocked and I get the tap to answer or reject as a notification its fine.
I'm just wondering if anyone else had a similar issue or had found a fix.
I'm on the official firmware, running 8.1.0
I've experienced something similar too. Sometimes I find myself swiping over and over again just to get one call answered or rejecte I have no idea why it does that, or when, it seems to be random on mine
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
I've found you can swipe down from the top of the screen and can answer it from the notification menu instead.
Just takes longer.
cobben said:
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
Click to expand...
Click to collapse
Just after having written the above, the phone corrected itself.
Now I can answer calls on the first swipe.
Interesting . . .
Sometimes my phone will let me answer normally. most of the time however I have to use the notification bar.
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Yup, been having the same issue. Stock phone, no root. What's frustrating is there as no further updates.
iliais347 said:
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Click to expand...
Click to collapse
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
cobben said:
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
Click to expand...
Click to collapse
What i did is i added the google dialer app to my phone, then to game booster and set its fps to 40. Now i can answer the calls.