Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.
Related
Does anybody else have this problem? It happens to me about once a day..I'll go to check my phone and its totally off and I have to pull the battery to get it to power up again. It only happens when the screen is off.
I've had this happen a few times, and other have as well. There is a thread about it, with various theories on the cause, but a definitive cause(s) has not been found.
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
One user claimed the GPS was the culprit. But this was not my personal experience. I was never using GPS when it happened to me. Mine might (possibly) have been linked to having screen-off profiles under CPU Tuner. I uninstalled CPU Tuner, and went back to SetCPU, and have not had the issue re-occur in over a month. Do you use either of these CPU over/underclocking apps, any overclocking?
Thanks for the reply I actually just found the thread you linked to right after I started the thread.. My desire Z is rooted but other then that totally stock.
EDIT: It also did this before I rooted.
My Z also did this a couple times the first few days I had it, and it was pretty much stock. Then it didn't do it for a while, during which time I flashed the overclocked Godspeed kernal, and installed SetCPU. Then the power-on issue cropped up again (almost immediately) when I tried using CPU Tuner. The issue stopped after uninstalled CPU Tuner, and hasn't come back in over a month.
My only hypothesis is that its related to some combination of the kernal and CPU Tuner, in my case. But it also may have been a complete coincidence, and have nothing to do with either of those.
ive had this happen to my g2, no setcpu profiles had been set. mine was charging both times i noticed this. had to pull battery and unplug it before i could get it back on
I think this is an ec05 thing. I never noticed out until ec05. What happens is, after talking on the phone for 30 minutes or so, if anything wakes the screen like another call or like today a low battery warning, the phone will freeze. Sometimes I can still talk and other times the call will drop.. I have noticed that sometimes when I hang up it will freeze and I will have to pull the battery and reboot. usually it is plugged into a charger, but also does this just by itself. It is not the wake from sleep thing, as I have had that and this is different.. Like the thing is getting to hot or something.. I am currently running a stock rooted only ec05. I have re ch lashed and all and I still have this problem here and there. It isn't every call and I can't reproduce it over and over.. Any ideas or things to try to narrow this down...
Thanks.
I've noticed this as well, both on bone stock, and on SRF 1.1.1.
Are your overclocked or undervolted? This could be causing funky cpu frequency jumps you otherwise normally don't see and causing your phone to freeze or even reboot.
Sent from my SPH-D700 using XDA App
Stock rooted phone with no modifications, no over or under.. Not sure what is going on..
Take that droid over to Mos Eisley and get the memory flushed.
Sent from Bonsai 7.1.1.1
Oh how I wish it was that easy!!
ROM/kernel Not Playing Nicely- No "Deep sleep" & "Titanium Backup" & More
I'm on Juggernaut v4.1 & Synergy kernel v.10 with an undervolt at all times in different profile modes.
I noticed this a few days ago, I'll go in order of the "symptoms" my SGS2 T-989 experienced:
1. Random shut downs which won't allow me to reboot without taking the battery out or long-pressing the power button.
2. Titanium backup lags like CRAZY. If I go to my app list, it freezes while I'm scrolling, with the only solution of a Force Close. Batch backup freezes at any random point and doesn't ever pick back up. Even a force close/reboot doesn't make any difference.
3. If I get a text message or notification, the screen doesn't turn off (only stays at the lockscreen). At one point everything worked okay.
4. My phone doesn't "deep sleep" when my screen is off. I know for a fact that this is a problem because I use CPU Spy very frequently to check up on what states my processor runs. Deep Sleep has been inactive/never used in the last few days since I reset my CPU Spy timers once I suspected a flaw.
I suspect that all of the above symptoms are all propagated by the same issue.
As a general statement, I could just format/reFlash my ROM/kernel but I would like to backup my stuff beforehand. I had this problem earlier when I first got my SGS2 but had nothing on my phone at the time so I never bothered posting about it. I'm hoping it isn't just my phone and someone has some sort of solution.
Thanks for peaking and helping out.
Joy2DaWurld said:
I'm on Juggernaut v4.1 & Synergy kernel v.10 with an undervolt at all times in different profile modes.
I noticed this a few days ago, I'll go in order of the "symptoms" my SGS2 T-989 experienced:
1. Random shut downs which won't allow me to reboot without taking the battery out or long-pressing the power button.
2. Titanium backup lags like CRAZY. If I go to my app list, it freezes while I'm scrolling, with the only solution of a Force Close. Batch backup freezes at any random point and doesn't ever pick back up. Even a force close/reboot doesn't make any difference.
3. If I get a text message or notification, the screen doesn't turn off (only stays at the lockscreen). At one point everything worked okay.
4. My phone doesn't "deep sleep" when my screen is off. I know for a fact that this is a problem because I use CPU Spy very frequently to check up on what states my processor runs. Deep Sleep has been inactive/never used in the last few days since I reset my CPU Spy timers once I suspected a flaw.
I suspect that all of the above symptoms are all propagated by the same issue.
As a general statement, I could just format/reFlash my ROM/kernel but I would like to backup my stuff beforehand. I had this problem earlier when I first got my SGS2 but had nothing on my phone at the time so I never bothered posting about it. I'm hoping it isn't just my phone and someone has some sort of solution.
Thanks for peaking and helping out.
Click to expand...
Click to collapse
Why not just try a different kernel? You can flash a different kernel without loosing anything(if all goes well) ... I use the Faux kernel, and I have no sleep or standby issues ... and have used it with Jug
I don't know if this possible but I really like to find out if there is something causing the SOD that we can actually do something about(as in it isn't hardware causing it). I get SOD's on some repack kernels but not on others. When I get it has quite frequently. I am not running setcpu nor do I have any other software controlling the cpu. I have however been using juice defender. I like the product. I am going to remove it and flash a repack kernel that I know gives me SOD's and see if something in the power saving on the JD might be contributing to it. I would like to hear from others that have this issue and see if you are running anything like setcpu or JD.
I've been thinking of something. I don't have sod at all. For those that do have sod how good is your phone at overclocking? Meaning can it run stable at like 1.6 or where does it freeze at?
I'm wondering if its something to do with the difference of processors.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84
I dont really overclock anymore but when i used to, my phone froze at 1.6. This was back when i was on calk eg30 rom. Idk what would now if i tried again
Sent from my SPH-D710 using xda premium
I haven't oc'd mine so I am not sure what it is capable of. Tomorrow I will disable the JD and flash a repack and see if that has any effect. It is frustrating because I love the repack rom's. For now I use mobile odin to flash a repack and boot to recovery if I want to nandroid then flash the stock kernel back again.
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
badname said:
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I was just curious because on the original epic I had sod on some kernels and that phones processor was terrible. It froze when I tried to overclock it. The next one I got I wad able to overclock and I never had sod. Just seeing if phones with not being able to overclock might have an issue right now.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84
Are you using SetCPU? If so, don't fix screen off at 200-500.
Yeah we really meed to figure out what the heck is going on. For the last few days i've been trying to figure out why i've been having SoD. Im on blazer ROM and ive found out that if I don't flash a new kernel i'm fine. But as soon as I flash rouge 1.4.1 or 1.4.0 I get an onslaught of SoD. Things ive tries to fix it are:
-Installing set CPU and raising the voltage and changing gov. to on demand.
-taking all the init.d scripts out of the blazer ROM zip before flashing.
-I find that when the phone is on the charger it never gets SoD
That last point leads me to believe that it has something to do with deep sleep. Because when the phone Is plugged in it isnt allowed into deep sleep mode and idles at 200Mhz. Ill be looking into this more tonight. If anyone would like to work with me i'm always in the e4gt ics dev channel on freenode.
Sent from my SPH-D710 using XDA
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
ElAguila said:
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
Click to expand...
Click to collapse
you know....oddly enough I did install juice defender a few days ago....then flashed the 1.4.0 kernel and thats when everything started.....BUT ive since reflashed the rom a million times without re installing JD and i still get SoD with the 1.4.0 kernel
If you continue to not get Sleep of deaths...will you try flashing 1.4.1 or 1.4.0?
Just to clarify, does the SOD issue include texts/calls not going thru whatsoever while phone sleeping on or off charger for more than ten minutes? I get this with any ICS up to 06, when people call me it goes to VM directly, texts go to sprint limbo. Or, do these leaks just horribly handle low signal areas? I was on stock 85 prl, and signal was about 0-1 bar sprint and force roamed on 1xrtt for 2-3 bars... since this screwed me on a couple important calls I reverted to EL29 and flashed 111115 PRL... anyone have these issues with ICS, or is it just my **** reception and network issues?
Oh, and I SWEAR... no conspiracy theory... but anyone notice pretty much all samsung leaks have issues that are magically fixed for final release? Epic froyo, GB, now ICS on the Epic Touch... just sayin... its like they dont want us daily driving these... just use em enough to beta test (really this site should be renamed XDA Beta Testers)?
The issue you are talking about sounds more like the loss of service bug that has plagued some of these phones. the sleep of death is when the screen turns off and then you can't get the phone to come back on with out holding the power button for 10 seconds or pulling the battery. I am still doing fine. I enabled juice defender but selected advanced settings and disabled jd from controlling the auto sync. I set the controls options to default. So far I haven't had an sod. I will see if I can flash those repacks but I am not sure if it will work right since I am on an ICS rom.
SoD almost certainly involves the cpu going into deep sleep and not coming out. I have never experienced this issue on the E4gT on any rom/kernel combo, but I dealt with the issue extensively on the nook color it it's early days. I can definitively say that because a large number of users are using the repacked kernels and are not having SoD issues, then it is 100% NOT repacked kernel related. SoD is caused by voltage issues or cpu step switching problems. The repacked kernels are identical in these regards across all users, therefore the repacked kernels are not causing the SoD issues.
I've had the SoD a few times on FC05 and FC06 - I'm in the process of downloading FC07 right now. It doesn't happen often (3, maybe 4 times in a few days) and I cannot pinpoint any actions preceding it. I no longer have Juice Defender installed. It's odd though, I've also had problems receiving Kik messages after a reboot. My girlfriend sent me a few messages 6 hours ago that I didn't get until I opened the app, then it's back to normal. This is a pretty regular problem. It's like I have to kick start the app before it starts. But over that 6 hours I streamed Pandora just fine and Gmail has been syncing as normal.
It is a puzzling issue. I also don't think the repack kernels acutally cause it to happen but there is something about the issue that causes it to happen frequently when using a repack. I can go back to any of the stock kernels and it works fine even with juice defender running. That is why I thought perhaps it was some app like juice defender that was causing it but people still have the issue without juice defender. Fortunately for me it seems the fix was to disable juice defender. Unfortunately for my battery though.
Well so far it seems that ive found my solution. All i did was grab the 1 click Odin to Stock Rooted EL29 and wiped everything. I wiped internal storage and flashed back to rooted stock with odin. Then i Odin'd a kernel and flashed back to blazer rom and then had to re odin the rouge kernel that was originally giving me issues. So far all is well. I suggest giving it a shot
hey,
so im having some kind of trouble with my HOX.. when its just sitting on my desk it wakes itself up every now and then, sometimes very frequently and sometimes not.. with no specific pattern.. when im working on my laptop i just notice the screen turns itself on and then goes back to sleep.. i dunno whats causing it and its starting to get really annoying!! it's been happening for 2 days now, im running viperX 2.. any ideas on what may be causing this?
PS. i didnt install anything or change any settings before this started to happen
thanks in advance
Waseem Manneh said:
hey,
so im having some kind of trouble with my HOX.. when its just sitting on my desk it wakes itself up every now and then, sometimes very frequently and sometimes not.. with no specific pattern.. when im working on my laptop i just notice the screen turns itself on and then goes back to sleep.. i dunno whats causing it and its starting to get really annoying!! it's been happening for 2 days now, im running viperX 2.. any ideas on what may be causing this?
PS. i didnt install anything or change any settings before this started to happen
thanks in advance
Click to expand...
Click to collapse
Same issu here... I think that all custom roms has this problem... But I was told that could be a recovery problem(because it also wakes up when charging) so I'm using AOKP(v1.2 AWESOME battery life now) with TWRP recovery (I was using CWM)... Tonight I'm gonna check if it still waking up itself.
The recovery has little to do with the running ROM. Clockworkmod switches on the phone when nearly charged.
The phone waling and screen.coming on is much more likely to be a rogue app.
Waseem Manneh said:
hey,
so im having some kind of trouble with my HOX.. when its just sitting on my desk it wakes itself up every now and then, sometimes very frequently and sometimes not.. with no specific pattern.. when im working on my laptop i just notice the screen turns itself on and then goes back to sleep.. i dunno whats causing it and its starting to get really annoying!! it's been happening for 2 days now, im running viperX 2.. any ideas on what may be causing this?
PS. i didnt install anything or change any settings before this started to happen
thanks in advance
Click to expand...
Click to collapse
try a fresh install performing full wipe, clearing cache and dalvik cache and also use fastboot erase cache command before flashing boot img
i am also on viper 2.01 and don't have any such problems
There is no way...
I just tried everything..
With any custom rom and custom recovery, the phone wake up itself when charging off...
Only with the stock rom and oficial recovery it works Ok. Hope they find a solution..
I noticed there is some kind of pattern, the screen all of a sudden starts to turn itself on and off slowly and then faster and then it reaches a point where it stays on for about 10 seconds and then goes back off for a while.. it's very strange !! i've been using viperX for a long time and this never happened... at first i thought it was the productivity lockscreen notifying me of new emails or smth but that wasnt it... i only have google apps, xda app, facebook and chrome.. could it be one of these?? maybe its an app that uses internet because i noticed it happens much less or sometimes doesnt happen at all when i turn wifi off
task killer or smart stay ex
Had happened to me last evening. Random auto wakeup, first the touch buttons lightup and then
the screen. Then it goes to sleep on its own and then wakeup again. At first I thought it was related
to motion sensor because it always managed to coincide when I started typing in my laptop. But later
I noticed it wasn't the case as I was away from the table when it reached a very fast frequency
similar to notification LED,flashing sleeping flashing sleeping.... then complete sleep.
Went in task manager in search of rouge app, found "HTC Hub","Google Search","Google Play"
and a few other were constantly being slaughtered by the "Android Task Killer Free".
Exited the "Android Task Manager Free" and the auto wakeup has completely disappeared since then.
I also closed smart stay EX, which might have been the culprit as well since I have got dust in my front
camera and those might be recognized as faces or eyes?
I suggest you check for stray apps or task killers.
Make sure that none of the apps(background) crashing or being killed.
I believe custom roms try to enhance the performance by limiting the minimum
memory balance before which background inactive apps are killed by android.
Might be the cause but not quite sure.
So thats that, worth a try. Go to [Apps-->Running] and check if some app is disappearing and reappearing
on its own. Force stop it. Reboot the phone. Avoid any memory tweaking and task killer,
android is smart enough to know when to kill and when to keep apps.
Note: I am running a stock 4.0.3(1.29), no unlock,rooting etc...
Good luck
Rowlf said:
Had happened to me last evening. Random auto wakeup, first the touch buttons lightup and then
the screen. Then it goes to sleep on its own and then wakeup again. At first I thought it was related
to motion sensor because it always managed to coincide when I started typing in my laptop. But later
I noticed it wasn't the case as I was away from the table when it reached a very fast frequency
similar to notification LED,flashing sleeping flashing sleeping.... then complete sleep.
Went in task manager in search of rouge app, found "HTC Hub","Google Search","Google Play"
and a few other were constantly being slaughtered by the "Android Task Killer Free".
Exited the "Android Task Manager Free" and the auto wakeup has completely disappeared since then.
I also closed smart stay EX, which might have been the culprit as well since I have got dust in my front
camera and those might be recognized as faces or eyes?
I suggest you check for stray apps or task killers.
Make sure that none of the apps(background) crashing or being killed.
I believe custom roms try to enhance the performance by limiting the minimum
memory balance before which background inactive apps are killed by android.
Might be the cause but not quite sure.
So thats that, worth a try. Go to [Apps-->Running] and check if some app is disappearing and reappearing
on its own. Force stop it. Reboot the phone. Avoid any memory tweaking and task killer,
android is smart enough to know when to kill and when to keep apps.
Note: I am running a stock 4.0.3(1.29), no unlock,rooting etc...
Good luck
Click to expand...
Click to collapse
That worked !! but in a different way, i have no task killers and the ROM did not kill apps before because it didnt use to happen until recently, but i tried to clean up my phone and uninstalled some apps and it stopped since then, problem is i uninstalled them all at once so i dont know which app exactly was the cause but sure it was one of 'em.. maybe it got corrupted and started crashing in the background or something because i didnt install any apps recently... this didnt happen not even once since i cleaned up those apps.. thanx a lot for helping
So the root cause could be thee Apps that has permissions to wack/prevent (android.permission.WAKE_LOCK) your devices from sleeping..
I experienced it occasionally while 'smart stay EX' was on beta time..
HebeGuess said:
So the root cause could be thee Apps that has permissions to wack/prevent (android.permission.WAKE_LOCK) your devices from sleeping..
I experienced it occasionally while 'smart stay EX' was on beta time..
Click to expand...
Click to collapse
I recommend installing "Wakelock detector" which shows statistics of WAKE_LOCK usage !!