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
Related
Anyone experiencing a delay when pushing the power to wake after a few min of being idle? It always runs perfectly when plugged in, but when not, there's always like a 2-3 second delay??? (running stock)
Yep, I've noticed this as well. The wakelag is extremely annoying.
I know man, this used to happen on my evo, needless to say I wasn't expecting this from the epic lol
edoso1810 said:
Anyone experiencing a delay when pushing the power to wake after a few min of being idle? It always runs perfectly when plugged in, but when not, there's always like a 2-3 second delay??? (running stock)
Click to expand...
Click to collapse
There are already several threads on this please use the search feature. However if you remove your sdcard the delay goes away.
Sent from my SPH-D710 using Tapatalk
Khilbron said:
However if you remove your sdcard the delay goes away.
Click to expand...
Click to collapse
I tested this, and it was just as lagged with or without a SD card. Maybe a tiny bit faster without. But still lagged.
I installed Tegrak Overclock and it seems to fixed this issue.
As bonus got 4600 on Quadrant with stock rooted kernel. I have a 32gb class 2 microsd card also
removed my sdcard and tried this huge increase in wake time. But even with the little lag with the sdcard in it's nothing that's going to turn me off of the phone.
It appears samsung is underclocking to conserve battery in sleep
Sent from my SPH-D710 using Tapatalk
which of course is a good thing...
Bump bump. Idk if anyone found this out or not, but spare parts will get rid of the delay on lockscreen. Set transitions and animations to fast and the delay disappears even with SD card in
Sent from my SPH-D710 using xda premium
kingsway8605 said:
It appears samsung is underclocking to conserve battery in sleep
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Most android phones underclock when the phone is sleeping to conserve battery. I know for a fact the Evo 3D does it, and that phone had no lag on wake. I think it's annoying, but I wouldn't give up the phone because of it. I hope IF and when Samsung comes out with an update for all the bugs, they fix this bug too.
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
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.
Hello there xda. I bought my first SGH-i747m(Canada Bell version) and it had a pretty serious heat problem when I did use my cellphone doing anything for more than 5 minutes. After 15 minutes it usually bothers me too much so I just stop using my device.
I didn't try anything to fix it yet other than using a JB rom(ParanoidAndroid) on both my first device, and now my second device. They both do the absolute same thing. The bottom half gets really hot while the top half stays really cool.
Is that a common thing? If so, is there any fixes? It's really horrible to use a half hot/cold device, even worse than using a fully hot device.
Nah
Try turning Powersave On.
I had issues with overheating too.
Now they are all gone.
I'm running Nostalgia 7.5
It gets hot at the bottom because that's where the CPU and all that good stuff are, and that good stuff gets hot. Mine doesn't get crazy hot down there but it is definitely warmer down there then the top, that much is normal. Yours may be to hot down there however... Idk. But I've seen others with this issue cool the phone down with custom kernels. I've also seen people say custom kernels make there phone hotter.. Try it out.
Sent from my SGH-I747M using Tapatalk 2
bravomail said:
Try turning Powersave On.
I had issues with overheating too.
Now they are all gone.
I'm running Nostalgia 7.5
Click to expand...
Click to collapse
I'm on custom JB, so there' no "powersave".
I guess I'll try different kernels etc. I'm quite close to actually selling the device, overheating is one of my pet peeves.
Are you sure its overheating?
Like the gentleman a few posts up said. Depending on how you use it. The phone will get warm.
It should never be actually hot, to the point where it will harm you if you pick it up.
Sent from my SAMSUNG-SGH-I747 using xda premium
try going back to stock, all of a sudden the phone doesnt get as hot.
or try underclocking your kernel on custom. AOKP and CM both have an out of the box clock of 1.8 Ghz.
tune it down to 1.3 or 1.1. issue gone.
ThatJawn said:
Are you sure its overheating?
Like the gentleman a few posts up said. Depending on how you use it. The phone will get warm.
It should never be actually hot, to the point where it will harm you if you pick it up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I feel like I shouldn't be complaining, and that it's not "overheating" but it's getting warm. I'm used to my SGS1 which runs ice cold whatever I do.
I just underclocked it, but I don't even feel the difference. I'm now running the new ParanoidAndroid with the custom kernel recommended in here. It has all the tweaking tools necessary.
Happened even on stock ROM
Mine runs a bit warm too. It is warm to the point where is gets uncomfortable to keep in my pocket at times and as far as I know it is doing "nothing". It will be fine, then I check an email or G+ notification then it goes crazy.
One commenter suggested going back to stock but mine has been doing the same thing since then, it just seem a bit more regular for the last few days. I am now in KyanROM 1.3. I am going to give that po.wer save thing a shot over the next day or so and let you guys know how that goes.
Use setcpu load up the setcpu widget and tell up what tempature your phone is
Sent from my SAMSUNG-SGH-I747
I notcied it is overheating when it's on LTE and the battery drain fast. I turned LTE off and I am using 4g or wifi and i don't have this problem
I noticed my phone started connecting to LTE since this week too but my overheating problem started long before that. What I noticed though is that the battery also started to drain a lot faster when it started. For the battery drain, I am thinking it is either that LTE thing or a rouge app trying access my GPS a lot since the icon keeps popping up more and more in the notification bar "searching". For now I have disabled LTE and GPS until I have time to investigate them.
By the way, I tried using PowerSave, as someone suggested to help with the overheating, but it screwed up how some of my emails are displayed so I turned it off.
I'm having a huge problem with my S3 heating up at the bottom of the phone, right around the sim card slot. I've tried CM10.1 and other similar ROMs and TW ROMs and I'm still getting this problem. My phone hasn't been through any trauma at all and this just happened from one day to another and I find that extremely strange.
Also kind of worried about things melting down on the inside, even tho I know it might not happen.
Can anyone out there help or point me to the right direction.
Sent from my SGH-T999 using Tapatalk 4 Beta
Are you using your phone and charging it constantly while this occurs? If it is happening while dormant on all roms, might be a specific app or the phone itself is giving up? Not too sure to be honest without more info.
130 degrees?! Where are you getting this info from? I can't even TOUCH mine when it hits 105 and it has an Incipio case on it! At 130 I'd be worried about the battery exploding to be honest.
Have you tried running an "empty" ROM on it? Just a basic ROM with nothing installed?
mt3g said:
Are you using your phone and charging it constantly while this occurs? If it is happening while dormant on all roms, might be a specific app or the phone itself is giving up? Not too sure to be honest without more info.
Click to expand...
Click to collapse
I tend to charge my phone about twice a day. if you need anymore info just let me know. Now the crazy part is that I would have torrents downloading and it would get hot just slightly warm, till I turned on the screen and the heat spiked
EtherealRemnant said:
130 degrees?! Where are you getting this info from? I can't even TOUCH mine when it hits 105 and it has an Incipio case on it! At 130 I'd be worried about the battery exploding to be honest.
Have you tried running an "empty" ROM on it? Just a basic ROM with nothing installed?
Click to expand...
Click to collapse
Crazy part is that it's not the battery that's getting hot. Its that plastic cover right under where the SD card and sim sit. I used a friends infrared thermometer and the highest is 132 but it averages 120-125. And today I used a "empty" ROM and just ran the browser for instagram and some Facebook, about 15 minutes in it got extremely hot. Also tried TW ROM "empty"
Sent from my SGH-T999 using Tapatalk 4 Beta
itzsmokey said:
Crazy part is that it's not the battery that's getting hot. Its that plastic cover right under where the SD card and sim sit. I used a friends infrared thermometer and the highest is 132 but it averages 120-125. And today I used a "empty" ROM and just ran the browser for instagram and some Facebook, about 15 minutes in it got extremely hot. Also tried TW ROM "empty"
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sounds like a phone on the way out... Although I've never used an infrared thermometer on my phone I'm sure its not heating up to those crazy temperatures. When I use it heavily it gets warm but doesn't really ever get too hot unless I turn the screen brightness all the way up, then the screen gets hot.
I know of the area that you're speaking of - I'd consider replacing the device.
itzsmokey said:
I tend to charge my phone about twice a day. if you need anymore info just let me know. Now the crazy part is that I would have torrents downloading and it would get hot just slightly warm, till I turned on the screen and the heat spiked
Crazy part is that it's not the battery that's getting hot. Its that plastic cover right under where the SD card and sim sit. I used a friends infrared thermometer and the highest is 132 but it averages 120-125. And today I used a "empty" ROM and just ran the browser for instagram and some Facebook, about 15 minutes in it got extremely hot. Also tried TW ROM "empty"
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
wow! this was happening to my phone during the first month after purchased. It was completely stock. i would get a message saying my phone was in critical temp levels. all i did was wiped it clean and started fresh. after that everything was fine.
seems like your problem is much worse. return your phone back to stock and tell samsung to give you a new one. this is very dangerous. especially if it sits next to your leg all day!
@mt3g @EtherealRemnant do you think it could be the radio working harder than it should?
Sent from my SGH-T999 using Tapatalk 4 Beta
itzsmokey said:
@mt3g @EtherealRemnant do you think it could be the radio working harder than it should?
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Put it in airplane mode and see what happens. Anything is possible but if it's the radio causing the issue you need a new phone
Sent from my SGH-T999 using Tapatalk 4 Beta
EtherealRemnant said:
Put it in airplane mode and see what happens. Anything is possible but if it's the radio causing the issue you need a new phone
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Crap now that I think about it, that won't help since the phone gets cool when not in use, and the phone is basically useless when without data
Sent from my SGH-T999 using Tapatalk 4 Beta
itzsmokey said:
Crap now that I think about it, that won't help since the phone gets cool when not in use, and the phone is basically useless when without data
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Get an offline game that you can play for 30 or 40 minutes... Anything to get the processor up with the radio off.
Sent from my SGH-T999 using Tapatalk 4 Beta
@EtherealRemnant so I tried it for a few hours and phone didn't heat up at all. I ended up going back to complete stock for an hour with use. Then rooted and flashed CM10.1 and now phone temp is back to normal. Thanks for the help, at least I now know it was a radio problem.
Sent from my SGH-T999 using Tapatalk 4 Beta
itzsmokey said:
@EtherealRemnant so I tried it for a few hours and phone didn't heat up at all. I ended up going back to complete stock for an hour with use. Then rooted and flashed CM10.1 and now phone temp is back to normal. Thanks for the help, at least I now know it was a radio problem.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Glad you got it fixed and you're welcome! :good:
itzsmokey said:
@EtherealRemnant so I tried it for a few hours and phone didn't heat up at all. I ended up going back to complete stock for an hour with use. Then rooted and flashed CM10.1 and now phone temp is back to normal. Thanks for the help, at least I now know it was a radio problem.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've run CM10.1 RC4,5, and Many Nightlies, as well as Stock Deodexed and whatnot, with many different kernels (Ktoonz, Stock CM, etc), and I have an Otterbox Defender (And tonight will be an Otterbox Armor). I live in Utah, so we get some fairly warm temperatures and whatnot. My phone never heats up above about 50-60 degrees. I mean i never expose it to heat or sunlight that much, but I cant see a phone getting 130 degrees.
Purple Ferret said:
I've run CM10.1 RC4,5, and Many Nightlies, as well as Stock Deodexed and whatnot, with many different kernels (Ktoonz, Stock CM, etc), and I have an Otterbox Defender (And tonight will be an Otterbox Armor). I live in Utah, so we get some fairly warm temperatures and whatnot. My phone never heats up above about 50-60 degrees. I mean i never expose it to heat or sunlight that much, but I cant see a phone getting 130 degrees.
Click to expand...
Click to collapse
Yea it was pretty crazy how hot it was getting....I actually ended up finding out it had something to do with the MD5 firmware. Now I'm running the old LJC firmware and everything is back to normal.
Sent from my SGH-T999 using Tapatalk 4 Beta