Related
ok, i am really hoping someone can help me out here. so ever since froyo came out i have been having weird call problems, i will be on a phone call and randomly it will mute me. the mute button won't be activated and the only way to fix the problem is to toggle the speakerphone on/off. now i have tried several roms (syndicate, bonsai, ace) and they all have the same problem. i recently tried ace and it worked fine for a couple of days and then suddenly it did it this morning. i have also swapped out my phone and it still does it!
some people suggested playing with the voodoo sound options and none seemed to work.
if anyone has had this issue or knows of things i could try i would appreciate it extremely. this problem is driving me insane (along with all my friends who it constantly happens to while on the phone with me.)
thanks!
Moved to Q&A.
It could be a manufacturer defect? Does it happen on stock?
thegnargnarshredder said:
It could be a manufacturer defect? Does it happen on stock?
Click to expand...
Click to collapse
Only for about a day. I could try it longer. Wouldn't swapping the phone like I did cover a phone defect though?
This use to happen to me back on the DK28 build even DI18 I think but haven't seen it since official EB13 and even on EC05 now. That's weird. Did it start all of a sudden or has it been an ongoing problem? When did you get your phone? Oh wow you said it's a new one? Refurbished? WHen you got your new phone did you restore a backup from your old phone or start fresh?
phynias said:
ok, i am really hoping someone can help me out here. so ever since froyo came out i have been having weird call problems, i will be on a phone call and randomly it will mute me. the mute button won't be activated and the only way to fix the problem is to toggle the speakerphone on/off. now i have tried several roms (syndicate, bonsai, ace) and they all have the same problem. i recently tried ace and it worked fine for a couple of days and then suddenly it did it this morning. i have also swapped out my phone and it still does it!
some people suggested playing with the voodoo sound options and none seemed to work.
if anyone has had this issue or knows of things i could try i would appreciate it extremely. this problem is driving me insane (along with all my friends who it constantly happens to while on the phone with me.)
thanks!
Click to expand...
Click to collapse
p3dr0maz said:
This use to happen to me back on the DK28 build even DI18 I think but haven't seen it since official EB13 and even on EC05 now. That's weird. Did it start all of a sudden or has it been an ongoing problem? When did you get your phone? Oh wow you said it's a new one? Refurbished? WHen you got your new phone did you restore a backup from your old phone or start fresh?
Click to expand...
Click to collapse
i started fresh, except for a couple apps i restored settings for. but i didn't restore any system stuff. this happened right after froyo update for me. at first i thought it was a voodoo thin, but ive tried genocide with the updated voodoo, plus how can i be the only one having this problem. it makes no sense to me.
i guess i could try stock, but i mean i really don't want to run stock....ugh.
---oh new phone was straight from sprint about a week ago.
This is happening to me as well. I'm stock rooted froyo with all stock apps still in place. Very annoying. I never had this issue before the froyo update.
Anyone know of a fix for this yet?
I'm about to take a B.F.H. and "fix" the phone. My epic is doing this on every call I recieve or make.
Anyone have any ideas? I can't deal with this much longer. Really want to smash the phone. Guess I'll unroot and take it into bb or sprint...
iTbagdUrMac said:
Anyone have any ideas? I can't deal with this much longer. Really want to smash the phone. Guess I'll unroot and take it into bb or sprint...
Click to expand...
Click to collapse
yeah i got a new phone and it made no difference. good luck though!
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
I was having the same problem with EF02 and the EF02/EF10 modems. I switched back to the EC05 modem and haven't had the problem since (knocking on wood)...
Sent from my Transformer TF101 using Tapatalk
Try ee03 modem..
Sent from my SPH-D700 using Tapatalk
masaidjet said:
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
evancg said:
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
Click to expand...
Click to collapse
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Sure you are not hitting the mute button by accident? Sounds dumb but I've done that before.
Blankrubber said:
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have the SAME EXACT PROBLEM and just like the OP it hasn't always been like that, did this work for you?
Sent from my rooted, suited, & booted Epic 4G kno dat!
I was having the same issues so I just applied this. People couldn't hear me on speakerphone at all...seriously. hopefully this helps. Thanks for the tip
Sent from my SPH-D700 using XDA App
evancg said:
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Click to expand...
Click to collapse
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
edonnelly said:
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
Click to expand...
Click to collapse
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
I have the same issue. I am completely stock. It usually happens 10 to 15 minutes into a phone call. I've already called sprint, taken it to a store but only reflashed the os, and I just recently spoke to someone on chat, who said the problem has been solved. If it happens again should I get a replacement phone?
Blankrubbers fix actually worked for me
Sent from my SPH-D700 using XDA App
steviee7 said:
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
Click to expand...
Click to collapse
I had this problem as well. I odinned stock and problem solved. Now I'm back on bonsai with no problems.
Edit: I just noticed that I don't have voodoo sound installed, I know that I used to, maybe deleting that solved my problem and not odinning back to stock.
Sent from my SPH-D700 using Tapatalk
evancg said:
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Click to expand...
Click to collapse
speak up i can't hear you
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
I just discovered that I'm having the same problem after I Odin'd back to stock EC05 for a different reason. So, EC05 and EC05 modem, and I'm having a problem that I didn't think I was having before I tried EF02.
Could something have been changed that going back to EC05/EC05 modem didn't resolve?
Sent from my Transformer TF101 using Tapatalk
evancg said:
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
Click to expand...
Click to collapse
This problem is not generated by Voodoo. I have a stock Epic (rooted) and have never had Voodoo installed on my device and I have intermittently had this problem in the past (haven't seen it for a while, though). My friend has an Epic (never rooted) and also has this problem.
About the only thing I've heard that people have said fixes this is to wipe cache and dalvik and then flash something using Odin. Stock or custom I don't think matters.
As others have noted, uninstalling Voodoo didn't fix it for me. I think what must be causing this is everytime I wipe and install a clean ROM I restore some data through TiBackup and SOMETHING I'm restoring is causing this. Guess I'll just have to wipe and be very careful about what I'm restoring.
This might be completely random, but by chance did other people that experience this problem happen to install NZBAir?
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.
Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....
infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....
Hey guys... as it says in the title, I am having issues with my G-nex randomly losing connection/signal but then coming back again. From what I have read, this is a common problem... anyone have any tips? Also wanting to know if I flash a custom ROM if that would possibly fix the problem. Thanks!
Not necessarily the ROM, but the radios. Try that.
There are a few 4.0.4 ROMs for the LTE GNex out now you could try as well if you want to go the ROM route.
Is this happening to you? (See attachment)
If so.. I've been trying multiple radios and multiple roms all day without any progress, this still happens. Would love it if someone has a solution to this... I'd have having to send in my phone again.
The signal issues seem to stop when the phone is awake though... :/ But I'm missing a lot of phone calls since my phone is "off" when people try to call me.
XanderDelores said:
Is this happening to you? (See attachment)
If so.. I've been trying multiple radios and multiple roms all day without any progress, this still happens. Would love it if someone has a solution to this... I'd have having to send in my phone again.
The signal issues seem to stop when the phone is awake though... :/ But I'm missing a lot of phone calls since my phone is "off" when people try to call me.
Click to expand...
Click to collapse
yeah, that's exactly what's happening... it does seem to happen more when the phone is off, but I think it still happens when it is on. it is so weird! I went into the verizon store, one of the reps said that he had just been having this issue today and that he put it into airplane mode and back off again and it seemed to fix the problem... I did it, and it seems to have helped, but that was only about 20 min ago lol. see if it helps you!
in_dmand said:
yeah, that's exactly what's happening... it does seem to happen more when the phone is off, but I think it still happens when it is on. it is so weird! I went into the verizon store, one of the reps said that he had just been having this issue today and that he put it into airplane mode and back off again and it seemed to fix the problem... I did it, and it seems to have helped, but that was only about 20 min ago lol. see if it helps you!
Click to expand...
Click to collapse
Hmm.. interesting. The problem here is that this started on March 24th... :/ But, still trying Airplane mode, even though I'm not optimistic..
I emailed my provider, asking them for info, but a friend of mine has been working beside me for the past few days, on the same network with the same phone, without problem. So I guess it's time to bring it in..
Thanks for the info! I may try to put the latest rom/radio on it and see if that helps... if not i'll un-root it and send it in I guess.
I'm having a similar issue with my GSM model, It started when my phone was updated to 4.0.4. Phone signal suddenly drops and comes back again in less than 10 seconds. Sometimes it happens with 1 minute intervals between signal losses, sometimes 5 or 20 minutes, it's very random. After noticing the issue thanks to "Light Flow" that blinks the notification light in white when there is a signal loss, I installed this app (https://play.google.com/store/apps/details?id=com.smartandroidapps.missedcall&hl=en) to track it properly. The results are very frightening, I'm about to do a full wipe in hopes that the issue will be gone :|
ps: like you guys, I did notice that it's very most likelly to happen while the screen is off. Actually, it has never happened while the screen was on.
Same here, post 4.0.4 update on my GSM GNex.
Found this explanation....
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 ;(