Shutting down when screen is off - G2 and Desire Z Q&A, Help & Troubleshooting

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

Related

[Q] SetCPU Superuser Permissions

So I'm on a visionary temp root, overclocked with setcpu. Ive set up several different profiles but I've noticed that my battery life with the profiles isnt as good as other users have claimed.
I have noticed that when i open setcpu sometimes a little message will flash up saying that setcpu has been given superuser permissions. Does this mean that prior to opening the program, it didnt have permissions? If it in fact did not have superuser permissions, could that be why my battery life is less than expected? (i.e. The program didnt have permissions and thus couldnt use the profiles to slow down cpu speed upon screen off, etc.) The message does not come up every time I open setcpu, but it seems to come up when I havent opened the app recently.
Any ideas?
cmccollough said:
So I'm on a visionary temp root, overclocked with setcpu. Ive set up several different profiles but I've noticed that my battery life with the profiles isnt as good as other users have claimed.
I have noticed that when i open setcpu sometimes a little message will flash up saying that setcpu has been given superuser permissions. Does this mean that prior to opening the program, it didnt have permissions? If it in fact did not have superuser permissions, could that be why my battery life is less than expected? (i.e. The program didnt have permissions and thus couldnt use the profiles to slow down cpu speed upon screen off, etc.) The message does not come up every time I open setcpu, but it seems to come up when I havent opened the app recently.
Any ideas?
Click to expand...
Click to collapse
From my understanding, you only set it once. i had set a widget because i thought set cpu had to be running. But i deleted it because if you think about it....superuser app already has the permissions set, and when you open setcpu it shows the current speed.....if it wasnt working it would show 800mhz then KICK into 1 ghz?....thats what i think. You shouldnt need to worry.
Great, thanks for the response.
Sent from my HTC Vision using XDA App
same here. from time to time this popup comes.
anyway i cannot see any benefit from running setcpu as the profiles are not working for me.
i tried setting up screen off profile. this never triggers.
i leave setcpu deinstalled now. battery life is good so far
snudel said:
i tried setting up screen off profile. this never triggers.
Click to expand...
Click to collapse
How can you tell if it triggers or not?
cmccollough said:
How can you tell if it triggers or not?
Click to expand...
Click to collapse
Good question. Can't find anything in logcat.
set notifications.
on the magic you could see him switching profiles right after turning on the screen
you wont see it on the g2
I agree, something is fishy with this. EVERY time I open setcpu it gives me the su permissions granted window like its not being saved in memory
Sent from my HTC Vision using XDA App
EDIT: After shopping around on the market I came across an app called "CPU Tuner". The UI is nice and has roughly the same customization as setcpu if not more. It does take a bit of getting used too but i'm more than willing since the profile notification actually cycles with this app vs. setcpu. I'll give it a shakedown tomorrow as it's getting too late here to test.
cpu tuner doesn't work for me.
in profiles, it just shows 700mhz to 800mhz, which makes it useless as i want to underclock to 200 when screen is off.
That toast pop-up is nothing to worry about, its just something that has featured in the last couple of SU builds, it doesn't mean your app is not working.
I just turn the notification off in the SU settings.
I can now confirm that the screen off profile is not working correctly. Before going to sleep last night, my phone had a charge of 99%. I did not have anything running (no wifi, bluetooth, sync, etc.) and I woke up to 81% battery. It never killed that much overnight before overclocking. We gotta get this fixed.
Sent from my HTC Vision using XDA App
cmccollough said:
I can now confirm that the screen off profile is not working correctly. Before going to sleep last night, my phone had a charge of 99%. I did not have anything running (no wifi, bluetooth, sync, etc.) and I woke up to 81% battery. It never killed that much overnight before overclocking. We gotta get this fixed.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i have mine set to 1ghz max 245 min profile screen off 245/245 priority--100..and put a widget on my main screen. My phone has been on screen off for the pat 5 hours....and drained only 2% battery life.....i dont understand why it doesnt work with some peoples phones??!!. is it different cause im using a desire z and yours a g2?...i HARDLY doubt that would be a problem :S..
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
jark99 said:
i have mine set to 1ghz max 245 min profile screen off 245/245 priority--100..and put a widget on my main screen. My phone has been on screen off for the pat 5 hours....and drained only 2% battery life.....i dont understand why it doesnt work with some peoples phones??!!. is it different cause im using a desire z and yours a g2?...i HARDLY doubt that would be a problem :S..
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
Click to expand...
Click to collapse
Running the setcpu widget on my phone caused instability issues at higher clocks (feeling ballzy w/ flippy's 1.8 kernel). After removing the widget my profiles were hit and miss for some reason.
As far as the battery issue goes, anyone running CM RC2 and earlier might want to check out nightly 36, apparently there was a memory leak causing battery drainage ( I don't know anything about what it means but common sense leads me to believe a leak is bad lol). If anyone is still not satisfied with setcpu I highly recommend CPU tuner.
jark99 said:
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
Click to expand...
Click to collapse
Yes I have the widget on my homescreen. Weird that so many people get different results
Could the scaling be giving people varying results? I don't even really know what they do, I have mine set on ondemand. Would someone mind sharing what exactly the different scalings do?
cmccollough said:
Could the scaling be giving people varying results? I don't even really know what they do, I have mine set on ondemand. Would someone mind sharing what exactly the different scalings do?
Click to expand...
Click to collapse
http://www.droidforums.net/forum/rescue-squad-guides/47871-overclocking-101-a.html
Centered around the OG Droid but basic concepts still stand.
- Just picked up an app called SuperPower, had it a while back and had issues..but it's been update a lot since then. Looks like it's an all purpose battery management app that has the ability to govern cpu speed also. I'll test drive it and see how it works.
My battery life has improved markedly since installing CM nightly #36 and Pershoot's latest kernel. I've been using my phone pretty heavily over the last 8hours and still have over 50% left. Lots of texts, emails and websurfing etc.

Sleep of death

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.

ROM/kernel Not Playing Nicely- No "Deep sleep" & "Titanium Backup" & More

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

[Q] CPU not using any speed other than max.

I have looked around and completed a few searches but cannot find any direct answers to this.
I have CPU Spy installed and have been checking it off and on since I got the phone. I have noticed that my phone does not run at any speed other than the absolute max. The phone does go into Deep Sleep without issue, but the only CPU speed it uses is 1728. I have tried a few ROMS without any change.
Currently running Juggernaut 5.0 with Darky's Kernal.
I have tried different Governers. I have tried Antutu's CPU Master, SetCPU and No-Frills. I just cannot get this phone to run anything other than MAX speed. Since I am constantly having things run in the background like music, this is effecting my battery life.
Anyone have any input, ideas or suggestions? Other than running stock.
Turn down your minimum CPU settings in set CPU and check set on boot?
Sent from my SGH-T989 using Tapatalk
You've done just about everything possible. Only option left it to Odin back to stock, root it and check cpu Spy to see if it is acting normal. If it is back to normal flash back to your favorite distro!
Perhaps something got messed up along the way of flashing all those roms? Shouldn't, but you never know.
da_dragon2k3 said:
You've done just about everything possible. Only option left it to Odin back to stock, root it and check cpu Spy to see if it is acting normal. If it is back to normal flash back to your favorite distro!
Perhaps something got messed up along the way of flashing all those roms? Shouldn't, but you never know.
Click to expand...
Click to collapse
I was really hoping it would not come to this :'(
*update....
I re-flashed Darky's Kernal and removed all OC apps and now I am showing full utilization of the different seed steps.
Quite glad it did not result in me having to start over again.

Little cores running at 1440 all the time

Hey guys, need some help. I have an AT&T H810 rooted 10o. My little cores seem to be running full out at 1440mhz even though my governor is set to Interactive. This is causing it to heat up incredible, to 70c+, and is draining the battery quickly. It seems to have only started occurring in the last few days! I can run it in powersave governor which fixes it to 384mhz, and it fixes the problem, but I don't understand why it is running at full speed under interactive now. The big cores do NOT have this problem AT ALL.
I've removed any apps I installed during that time, cleared my phones cache, cleared the memory, I have tried running it in airplane mode, I've looked into what apps were running and it seems to be very few. Turned location off. I've tried freezing the play services because I have been getting a very intermittent force close. I have also tried to disable all xposed modules, and used avg to scan for any malware. Possibly init.d? Possibly the new xposed v79? I'm at a loss as to what is causing this!
Does anyone have any other ideas as to what could be happening?
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
spartan268 said:
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
Click to expand...
Click to collapse
Battery usage Android OS is highest at 33, followed by screen at 16%.
Wakelocks, I seem to have them under control with amplify, and I don't see any new ones.
Question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
elementalfusion said:
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
Click to expand...
Click to collapse
Doesn't solve why it's running at full speed, but I'll keep that in mind.
question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.
Personally I never done a factory reset myself yet so i cannot comment.
For the most part it does look like you have something to work with seeing Android OS is taking up the most battery. The hard part is tracking down which process. I'm not the best at this so maybe someone else can chime in. Try taking a look at your currently running processes and see if there's anything odd
Well, after a few factory resets which did not affect xposed, I was able to resolve it to where the cores now return to 384mhz idle. It was something that was installed, and it took 3 or 4 resets after restoring my app backups, and I'm still not sure which app was the culprit. I'm possibly wondering if it was the Amplify module
Sorry for bumping this. I just suffered from this problem and it seems for me it was antutu. For some reasons it was running the background keeping the 4 small cores at 1,2-1,4 cuz constantly. I stopped it and now it's back to normal. Just wondering why it started itself in the first place.
Sent from my LG-H815 using XDA-Developers mobile app

Categories

Resources