so i got a warranty replacement T-mobile g2. i rooted it using gfree method. loaded cm7 nightly...206 i think was the latest. the next day i pulled my phone from my pocket to find it had shut off. i had to pull the battery before it would power up. it did this once a day at different times. i pulled back the overclocking to 806mhz from 1113mhz. no change. i wiped and reinstalled cm7. no change. i reverted to stock. no problems for two weeks. then i thought maybe i had done something wrong during the rooting process or had a bad nightly, so i rooted again. i installed cm7 nightly 216 last night. My phone shut off again today and i had to pull the battery. my searches have revealed that this problem is fairly common, but why only when rooted? any ideas?
spudkinks said:
so i got a warranty replacement T-mobile g2. i rooted it using gfree method. loaded cm7 nightly...206 i think was the latest. the next day i pulled my phone from my pocket to find it had shut off. i had to pull the battery before it would power up. it did this once a day at different times. i pulled back the overclocking to 806mhz from 1113mhz. no change. i wiped and reinstalled cm7. no change. i reverted to stock. no problems for two weeks. then i thought maybe i had done something wrong during the rooting process or had a bad nightly, so i rooted again. i installed cm7 nightly 216 last night. My phone shut off again today and i had to pull the battery. my searches have revealed that this problem is fairly common, but why only when rooted? any ideas?
Click to expand...
Click to collapse
If you're running anything like SetCPU, you might have your min speed/screen off profile set too low.
Pull the /proc/last_kmsg next time it happens; if it is actually powering off (as opposed to just not having the clock speed to wake up), that's where you'll need to look to see what happened.
Sent from my T-Mobile G2 using XDA App
Thanks..that makes sense...I use the cm CPU settings had minimum set to 245mhz...I bumped it
up top 368...I forgot that every processor is different
Sent from my HTC Vision using xda premium
spudkinks said:
so i got a warranty replacement T-mobile g2. i rooted it using gfree method. loaded cm7 nightly...206 i think was the latest. the next day i pulled my phone from my pocket to find it had shut off. i had to pull the battery before it would power up. it did this once a day at different times. i pulled back the overclocking to 806mhz from 1113mhz. no change. i wiped and reinstalled cm7. no change. i reverted to stock. no problems for two weeks. then i thought maybe i had done something wrong during the rooting process or had a bad nightly, so i rooted again. i installed cm7 nightly 216 last night. My phone shut off again today and i had to pull the battery. my searches have revealed that this problem is fairly common, but why only when rooted? any ideas?
Click to expand...
Click to collapse
Could be the battery moving ever so slightly... check out this post: http://forum.xda-developers.com/showpost.php?p=17876904&postcount=276
I've seen similar posts/threads...I'll keep it in mind...I tried the "tape over the sdcard method" to no avail...this is just as easy I'll give it a couple days to see if the min CPU speed is my prob
Sent from my HTC Vision using xda premium
spudkinks said:
Thanks..that makes sense...I use the cm CPU settings had minimum set to 245mhz...I bumped it
up top 368...I forgot that every processor is different
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ouch, that's probably the problem; when I was using SetCPU I have mine at 386 without any issues, when I had it lower I was running into the same problem as you.
Sent from my T-Mobile G2 using XDA App
I hope that's it...my first G2 had no issues with 245 min setting. I guess this one is just more finicky
Sent from my HTC Vision using xda premium
Well...it went 36 hours, but it did it again. I've also had one random reboot today and massive force close. By that I mean my browser, swype, and adw all force closed at the same time. Maybe my warranty replacement is someone elses unfixed warranteed phone...
Sent from my HTC Vision using xda premium
Related
I have had this phone going on a month now I would say this problem started about a week ago. The phone (not on the charger) just gets hot and the battery life dips tremendously. (The phone is stock unrooted) I used to be able to get at least 14 hours out of the phone with normal use and 3g on, now i get about 7 hours before i have to plug it up again. The phone can be in my pocket idle and I can feel it heating up, I have never had a device do this I am at a loss right now because the main reason I sold my evo was because of the rave reviews of the phones battery life and all of a sudden that is just gone. I tried searching the forum before posting and found nothing with regards to this problem, If there is another thread like this I do apologize it was simply overlooked.
Any suggestions??? Thanks in Advance.
Could just be a Los, try sending a text or making a phone call the next time it happens...
Usually when I have a ghost Los, my phone will heat up and the battery drops. If you can't send a text, go to your task manager and go to the RAM tab and clear memory. That usually helps, but if it doesn't work, just reboot.
Sent from my SPH-D710 using XDA App
Usually when you have this problem, for me it's always been a program pegging the CPU usage. download system panel to see what's up
.: sent from my Samsung Galaxy S II Epic 4G Touch :.
Thanks I will give both a try.... The los happens but its rare. I'm thinking of resetting the phone or returning it.
Sent from my SPH-D710 using XDA App
I've had it happen to me once, I woke up one morning and it was hot and battery drained. I noticed it had the LOS circle up top so I attributed it to that..........It's only happen once thus far.
It's not LOS I have service I can call and send texts but the phone just gets hot as he'll and battery life gets destroyed. The thing is this started about a week ago and I have not installed anything new on the phone it just started doing this on it's own.
I would not say my phone gets "hot" but noticeably warmer especially when playing some games. To help with the battery drain I have underclocked and undervolted -25.
The Facebook app didn't seem to like my phone very much. After downloading it and going to bed I woke up with a hot phone. Uninstalled soon after and works fine now =]
Sent from my SPH-D710 using xda premium
I started to have this problem after flashing "Rogue" kernel with CWM
It was Fancy Widget (HTC style clock) I don't know why the conflict started in the past week because I've had fancy Widget since the day I got the phone. Thanks for the help guys really appreciated.
Sent from my SPH-D710 using XDA App
Greetings All!
This happened to me once. While phone was in pocket battery life nosedived and temperature skyrocketed. Wasn't LoS. Looked at running apps/services and saw that AP Mobile was running out of control. Which surprised me since I wasn't using the widget. So I froze it and the problem has not reoccurred. It was probably just a fluke but since I wasn't using it anyway it seemed like a no-brainer to hide it.
Cheers, Henri
I had this issue once and found that it was the enhanced email app. Installed and good to go.
Sent from my SPH-D710 using XDA App
I have this problem about once a week. I'm pretty sure it's my pulse app, it happens when I recently opened that app
Sent from my SPH-D710 using XDA App
I was going to say check for a rogue app that may be opening and running on its own. I deleted Maps, Google+,etc and install when I need them.
Sent from my SPH-D710 using xda premium
Happened to me for the first time yesterday. I was at 77% and my phone froze. It was extremely hot so I pulled the battery and rebooted. It cooled down but now my battery was at 20%.
Sent from my SPH-D710 using XDA App
i have the same problem use to get excellent battery life then all of a sudden phone last 7 hours i noticed on the status that the up time was 100%. it seems like it doesn't sleep anymore.please help
Something that I have noticed is that every time I pull the battery for this problem when I restart the phone the keyboard is reverting from the Smart Keyboard Pro back to the standard Samsung keyboard. Is anyone else seeing this? Could this be related?
It has to be an app that's killing the cpu look on the first page under my original post Hyabusa1300 (thanks) gave me the advice that worked. Figure out which app is causing the issue and uninstall it.
Sent from my SPH-D710 using XDA App
hot phone
JohnCorleone said:
I was going to say check for a rogue app that may be opening and running on its own. I deleted Maps, Google+,etc and install when I need them.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Almost always a hot phone means it is doing something in the background. Defiantly check battery stats and see what is running
Alright I have only had my white DInc2 for a week and I have noticed this since day one, certainly on CM7 (with and without custom kernels) and possibly on sense too (I'm not positive since I flash constantly but I deffinitely use CM7 more). Basically when I hit the power button to shut the screen off, and then almost immediately hit it again turn it back on, the phone will hang and the screen may not come on for 30 - 60 seconds. It doesn't matter how many times I hit the button. This happened almost right after I bought the phone, running cm7 but at stock speeds and overclocked. As I said above it's happened on at least a few different kernels. So what could be the issue? I've seen something similar on the Eris back in the day and that was caused by the minimum voltage being to low on screen off. But like I said its done this even at stock speeds. I still have a little time left to return this phone if need be, or I have insurance that covers everything (including water damage) so I can always get another phone if need be. And the insurance has no deductible, so that's a plus.
If anyone can help me out here, it would be much appreciated.
Thanks
Sent from my Incredible 2 using Tapatalk
n0yd said:
Alright I have only had my white DInc2 for a week and I have noticed this since day one, certainly on CM7 (with and without custom kernels) and possibly on sense too (I'm not positive since I flash constantly but I deffinitely use CM7 more). Basically when I hit the power button to shut the screen off, and then almost immediately hit it again turn it back on, the phone will hang and the screen may not come on for 30 - 60 seconds. It doesn't matter how many times I hit the button. This happened almost right after I bought the phone, running cm7 but at stock speeds and overclocked. As I said above it's happened on at least a few different kernels. So what could be the issue? I've seen something similar on the Eris back in the day and that was caused by the minimum voltage being to low on screen off. But like I said its done this even at stock speeds. I still have a little time left to return this phone if need be, or I have insurance that covers everything (including water damage) so I can always get another phone if need be. And the insurance has no deductible, so that's a plus.
If anyone can help me out here, it would be much appreciated.
Thanks
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
What are your screen off clock speeds.
Sent from my HTC Incredible 2 using xda premium
245, though on a sense Rom I had it lower and didn't have a problem.
Sent from my ADR6350 using Tapatalk
n0yd said:
245, though on a sense Rom I had it lower and didn't have a problem.
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
Try upping it.
Sent from my HTC Incredible 2 using xda premium
knipp21 said:
Try upping it.
Sent from my HTC Incredible 2 using xda premium
Click to expand...
Click to collapse
I'll try it but its so random, its very odd. It happened quite a bit when I first got the phone, then it didn't happen at all for a good 4 or 5 days. Also it only seems to happen when I switch off and back on right away, if I switch off and come back to the phone 15min later it comes right on at the press of a button.
Sent from my ADR6350 using Tapatalk
A little update. Running a sense 3.5 rom I had my screen off set to 245 min AND max. I haven't had any problems. So that's more evidence leaning towards it not being a minimum voltage problem. But the problem is so damn intermittent, I'm really not sure what to think of it. I did see on another forum someone else had the same problem but they didn't go into detail.
Well if anyone else has ideas, shoot them my way. Thanks
Sent from my Incredible 2 using Tapatalk
I had similar problems on my eris and it was related to the governor settings (my eris hated smartass in particular.) The min clock speed affected it as well but not as much. I would try a different governor.
Sent from my Incredible 2 HD using XDA App
So I have rooted and installed CM7 onto my kindle fire. last night while i was at a party i came out to my truck and tried to unlock the fire. nothing happened. i press again. nothing. finally I had to hold it down for quite a while before it rebooted. This morning when I woke up it had done the same thing to me. It seems if i let it sit for several hours it will do this. Any clues?
Sounds like you spilled beer on it. But seriously same thing happened to me and i just waited for it to die, then plugged it in and it came up fine.
Sent from my DROIDX using XDA App
This is the sleep of death everyone is dealing with on cm 7 and cm 9
Sent from my Amazon Kindle Fire using xda premium
hmm anyone have a link to the latest modaco they can share? the one posted in the main thread isnt working. filesonic is messed up right now.
I do have it on my Kindle still, which surprised me. I'll get it up on hotfile and post a link shortly.
DeerSteak said:
This is the sleep of death everyone is dealing with on cm 7 and cm 9
Click to expand...
Click to collapse
I've had this happen on my stock rooted rom as well. doesn't do it very often, and I've not found a reason why.
Just hold the power button for 20secs and it restarts without any problems.
I had read on some forums for the stock fire that people were returning them for new ones due to this issue. think i should return it? i got it yesterday...
krelvinaz said:
I've had this happen on my stock rooted rom as well. doesn't do it very often, and I've not found a reason why.
Just hold the power button for 20secs and it restarts without any problems.
Click to expand...
Click to collapse
Try this link I uploaded it to: http://filesmelt.com/dl/Gr5-update-modacocustomrom-kindlefire.zip
Bizzle58 said:
I had read on some forums for the stock fire that people were returning them for new ones due to this issue. think i should return it? i got it yesterday...
Click to expand...
Click to collapse
I've had it happen 4 or 5 times since I got my Fire which was on the 19th of Nov. Inconvenience a few times, not a big deal.
I wouldn't return mine for that.
awesome, file download link worked!! you are a savior. md5 sums check out. im flashing it now.
http://hotfile.com/dl/143286969/f3376e7/Gr5-update-modacocustomrom-kindlefire.zip.html
edit: holy **** i'm slow...
DeerSteak said:
http://hotfile.com/dl/143286969/f3376e7/Gr5-update-modacocustomrom-kindlefire.zip.html
edit: holy **** i'm slow...
Click to expand...
Click to collapse
No worries. Not to change the topic of this post, but since Im now on modaco, are you guys only able to run go launcher with this as well? every other launcher crashes on me
You need to move the launcher to the /system/app directory.
Damian
Sent from my GT-I9100 using XDA Premium App
I've come across this problem on other devices running custom ROMs and this one is no exception, at least so far.
What's happening is chances are because you're on a custom ROM, you're probably running a custom kernel, or at least using a governor for your CPU speeds. Most of us probably have SetCPU running and have it to where your CPU clock is lowered when you're not doing anything. So when the screen is off, your CPU is lower. But the problem is that sometimes the clock speed goes TOO low and your device doesn't have the processing power to wake up. The solution is simple, go to SetCPU and raise your minimum clock speed. I did that as soon as I got the "deep sleep" problem and it hasn't done it since.
TL;DR
You probably have SetCPU running your clock speeds at a minimum that's too low. Raise it.
adamantypants said:
I've come across this problem on other devices running custom ROMs and this one is no exception, at least so far.
What's happening is chances are because you're on a custom ROM, you're probably running a custom kernel, or at least using a governor for your CPU speeds. Most of us probably have SetCPU running and have it to where your CPU clock is lowered when you're not doing anything. So when the screen is off, your CPU is lower. But the problem is that sometimes the clock speed goes TOO low and your device doesn't have the processing power to wake up. The solution is simple, go to SetCPU and raise your minimum clock speed. I did that as soon as I got the "deep sleep" problem and it hasn't done it since.
TL;DR
You probably have SetCPU running your clock speeds at a minimum that's too low. Raise it.
Click to expand...
Click to collapse
I raised my min CPU to 600 mhz about a week ago and have not had any SOD problems at all and the battery life is about the same.
i haven't read every post on here but this is a common problem for kindle rooted or not. when this happens hold the power button for 20 seconds let go push the power button and it should turn on.
Sent from my Kindle Fire using xda premium
I have pre-rooted stock and the problem occurs ever few days or so, power cycle it will turn it back on ... but it's kinda annoying
been running cm7 for a few weeks and this just happened to me tonight, scared the hell outta me.
bal1985 said:
been running cm7 for a few weeks and this just happened to me tonight, scared the hell outta me.
Click to expand...
Click to collapse
I think we have all felt that quick rush of panic.
Sent from my Kindle Fire using xda premium
Same Here!
asb2164 said:
I raised my min CPU to 600 mhz about a week ago and have not had any SOD problems at all and the battery life is about the same.
Click to expand...
Click to collapse
This worked great.
Over the past couple weeks my sons phone started to have a couple issues. These are the first issues we've experienced since we got the phone when it was first released. The first two problems were that it started dying real fast and I mean in a couple hours with zero usage. Before the problem started we were getting 15-20 hours with moderate usage. The second issue was that at any point in time it would shut down and it would take a charger to be plugged in to restart it (even though it wasn't dying).
When this started it was completely stock. Since then here are the steps I've taken...
1) checked battery stats, Android OS was always on top at around 70%. No rogue apps
2) loaded CPU Spy, the phone seemed to be sleeping normally
3) remove sd card
4) shut off wifi
5) factory reset (didn't stop the issues)
6) went into the stock recovery and wiped data and cache (I've since heard this may cause an issue in the stock build)
7) loaded a custom recovery (Agat)
8) loaded CM10 (this seems to have fixed the problem with it dying quickly)
And it just shut off out of no where. Is there something else I can try?
wburbage said:
Over the past couple weeks my sons phone started to have a couple issues. These are the first issues we've experienced since we got the phone when it was first released. The first two problems were that it started dying real fast and I mean in a couple hours with zero usage. Before the problem started we were getting 15-20 hours with moderate usage. The second issue was that at any point in time it would shut down and it would take a charger to be plugged in to restart it (even though it wasn't dying).
When this started it was completely stock. Since then here are the steps I've taken...
1) checked battery stats, Android OS was always on top at around 70%. No rogue apps
2) loaded CPU Spy, the phone seemed to be sleeping normally
3) remove sd card
4) shut off wifi
5) factory reset (didn't stop the issues)
6) went into the stock recovery and wiped data and cache (I've since heard this may cause an issue in the stock build)
7) loaded a custom recovery (Agat)
8) loaded CM10 (this seems to have fixed the problem with it dying quickly)
And it just shut off out of no where. Is there something else I can try?
Click to expand...
Click to collapse
Have you checked the battery. Take it out and place on flat surface and spin it if it spins get a new battery.
Sent from my SPH-D710 using Tapatalk 2
Lol, embarrassingly that's the one thing I haven't done.
Sent from my Nexus 7 using Tapatalk 2
Maybe I'm wrong but I read that he flashed Agats kernel then flashed CM 10. I believe you can't use a TW based Kernel on CM builds? That may cause serious problems.
Sent from my SPH-D710 using xda premium
He was having issues on stock. Then he loaded up custom roms.
But yeah check the battery that's what the quick dying might be.
Mines started dying even tho it said it had 70-80% battery left. Bought a new battery problem solved.
Sent from my SPH-D710 using xda app-developers app
BIGSAMDA1ST said:
Maybe I'm wrong but I read that he flashed Agats kernel then flashed CM 10. I believe you can't use a TW based Kernel on CM builds? That may cause serious problems.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I'm going to head out and pick up a new battery once the Sprint store open this morning. Then I'm planning on bringing it completely back to stock and hopefully that takes care of it.
My wife is threatening me that if we need to get him a new phone that she'll give him her iphone 4 and buy an iphone 5 for herself. I need to make sure I get this phone back up and running properly so that doesn't happen. lol
I went to the Sprint store this morning and he didn't even have to test the battery to know it's defective. I guess batteries get swollen at a certain point and from that point on it will hold less and less of a charge and start shutting down spontaneously as it gets worse. Needless to say I have another Samsung battery on order and will be getting this back to as stock as I can.
Thanks for your help and the headslap!
wburbage said:
I went to the Sprint store this morning and he didn't even have to test the battery to know it's defective. I guess batteries get swollen at a certain point and from that point on it will hold less and less of a charge and start shutting down spontaneously as it gets worse. Needless to say I have another Samsung battery on order and will be getting this back to as stock as I can.
Thanks for your help and the headslap!
Click to expand...
Click to collapse
You know you can hit the thanks button they are there for a reason
Sent from my SPH-D710 using Tapatalk 2
I've searched and haven't found an answer, just in the past few days my phone has started getting very hot with just average use. I am using a 4.1.2 TW rom, I have an aftermarket eBay battery, a lifeproof nuud case, and I'm using ktoonz kernel under locked a little. Which of those variables would most likely be the cause of this heat issue? By hot I mean battery temps of 100F, at least according to CPUZ app.
Its probably either your battery or your baseband. Flash a different modem and see if it helps.
Sent from my SGH-T999 using xda premium
100°f isn't that hot. I live in AZ and sometimes take public transportation which leads to being outside for 15-30 minutes at times and 115° weather, my phone has reached 120°. Not good but nothing putting my water bottle didn't fix lol. I wouldn't be stressing about it getting to 100° it could also be an app running in the background causing things like GPS to run. We need more info to help what you gave leaves way too many variables. Good luck.
Sent from my SGH-T999 using xda premium
you're aftermarket battery could very well be the problem. is you're going this route there is only 2 brands I trust and that would be Anker and Zero Lemon.
also, are you running ktoonservative without renaming qosmgr in system/bin?
Danvdh said:
you're aftermarket battery could very well be the problem. is you're going this route there is only 2 brands I trust and that would be Anker and Zero Lemon.
also, are you running ktoonservative without renaming qosmgr in system/bin?
Click to expand...
Click to collapse
I did order a zerolemon so that will go in next week when its delivered. I didn't rename that file, I did with the last rom but I completely forgot to do it when I flashed the 4.1.2 rom I'm on now. I don't think it's an app as I haven't added anything new and its not staying awake when it shouldn't. I'll also try the suggestion to change the baseband but I've been on md5 for weeks now and no issues until now.
It's good to know that 100f isn't too hot, I just never saw temps like that before. When do I need to worry about heat damage? I'm assuming the s3 has a self preservation mode and would shut down?
Try a different kernal. All phones are different. Try to flash back to a stock kernal first and see if it fixes the problem.
Sent from my SGH-T999 using Tapatalk 4 Beta
Not sure at all what happened, the phone continued to getting weirder and weirder, it started not sleeping and then just randomly shutdown. I went back and restored an older backup of a 4.1.1 rom and its working perfectly now. I have no idea why it didn't like the 4.1.2 rom but seems like that was the problem.
When you updated did you have a lot of apps and data from your previous setup? As in, did you wipe before flash? Restore any backups?
Sent from my SGH-T999 using xda premium
Android is very complicated and needy, sometimes you really need to watch all that you download and maintain apps that run in the background. Little things like keeping sync off, apps updating every few hours that keep your phone from `sleeping `. also your environment, temperature, using your phone while charging can affect your phones temperature
Sent from my SGH-T999 using xda app-developers app