I'll wake up in the morning to find my phone off and extremely hot. It will also randomly reboot throughout the day and won't stop until I remove the battery. Any ideas on whats going on and what I could possibly do to fix it?
Sounds like either the screen is staying on....or its overclocked waaay to much... A voltage setting.... Or simply just some app or widget running 24/7
Causing the phone to get hot....make sure tethering and wifi are off at night while your sleeping... Kill the GPS if your passed out too...
Sent from my SPH-D710 using XDA App
Wifi may be the culprit for the overheating issue, but throughout the day wifi and 3g are barely on unless I need internet. Kinda frustrating when you're in the middle of something and your phone randomly reboots and doesn't stop rebooting until you pull the battery. lol I was also thinking it could be the rom im on (always used blazer) but no one else is having the issue therefore it's probably not the rom.
A lot of times an out of control process will cause that too. I don't know and I doubt this phone would power down if it got too hot. Rebooting seems like a no go also since that's not going to help cool it down, if anything it would heat it up. If it powered down and stayed off or shut down as soon as it started to boot - now that would make sense.
Get something like Watchdog or OS Monitor - use it to watch your processes. When it starts getting hot for no reason, check them to see if anything is running. You can set Watchdog to alert you if anything stays over xx% of cpu usage for a specific amount of time.
Do you notice any lag before this happens?
I had the problem with the overheating at night and not charging. I tracked it down to set cpu and the over clocking profile. I use my phone at night as a clock with the clock widget and found that the default over overclock profile I was using for the screen on was in effect even tho I had another profile for charging so what I did was set a profile for 100 priority to under clock to 800 starting at 9:00 PM becuase I go to bed at 10 when I have to work the next day and have had no problems since. Also I did hav some problem's with instability and rebootting at 16oo so I clocked mine to 1400 still fast but doesn't heat up the phone or cause reboots.
KCRic said:
A lot of times an out of control process will cause that too. I don't know and I doubt this phone would power down if it got too hot. Rebooting seems like a no go also since that's not going to help cool it down, if anything it would heat it up. If it powered down and stayed off or shut down as soon as it started to boot - now that would make sense.
Get something like Watchdog or OS Monitor - use it to watch your processes. When it starts getting hot for no reason, check them to see if anything is running. You can set Watchdog to alert you if anything stays over xx% of cpu usage for a specific amount of time.
Do you notice any lag before this happens?
Click to expand...
Click to collapse
The phone will lock up right before it reboots over and over. When the phone starts up it'll stay on for a couple minutes and then restart. It will keep doing so until I pull the battery.
I'll download one of those apps and see what I can find.
arsmithsr said:
I had the problem with the overheating at night and not charging. I tracked it down to set cpu and the over clocking profile. I use my phone at night as a clock with the clock widget and found that the default over overclock profile I was using for the screen on was in effect even tho I had another profile for charging so what I did was set a profile for 100 priority to under clock to 800 starting at 9:00 PM becuase I go to bed at 10 when I have to work the next day and have had no problems since. Also I did hav some problem's with instability and rebootting at 16oo so I clocked mine to 1400 still fast but doesn't heat up the phone or cause reboots.
Click to expand...
Click to collapse
I haven't used setcpu on this phone yet, so maybe the rom i'm using is overclocking the phone. This morning when I woke up around 9 it was off and very hot and did not charge, even though it was plugged in. When I turned it on, it was only at 62%. I know it was on and was working around 430 or so when I woke up in the middle of the night. I don't know if it was charging at that time or not though.
adima said:
I haven't used setcpu on this phone yet, so maybe the rom i'm using is overclocking the phone. This morning when I woke up around 9 it was off and very hot and did not charge, even though it was plugged in. When I turned it on, it was only at 62%. I know it was on and was working around 430 or so when I woke up in the middle of the night. I don't know if it was charging at that time or not though.
Click to expand...
Click to collapse
A ROM won't overclock your phone. It may have a built in overclock option but that's user defined. I had this issue also but I noticed that I would have it laying on top of a shirt or under a pillow (very dumb).
I can replicate the issue if I charge the phone and place it under my pillow. The phone will overheat and shut off. If I pop out the battery it's super hot and I have to blow on it to cool it down. I stopped doing that and just set it on the floor and charge it if need be.
I charge my phone in the daytime and leave it off the charger at night. It's safer and you never know if it can catch fire while you're sleeping.
Android300ZX said:
A ROM won't overclock your phone. It may have a built in overclock option but that's user defined. I had this issue also but I noticed that I would have it laying on top of a shirt or under a pillow (very dumb).
I can replicate the issue if I charge the phone and place it under my pillow. The phone will overheat and shut off. If I pop out the battery it's super hot and I have to blow on it to cool it down. I stopped doing that and just set it on the floor and charge it if need be.
I charge my phone in the daytime and leave it off the charger at night. It's safer and you never know if it can catch fire while you're sleeping.
Click to expand...
Click to collapse
At night I set it on my nightstand and there is nothing by it, and it only does it about once a week i'd say. Kinda frustrating when you set an alarm to get up at a certain time and it doesnt go off cuz the phones off. I do have a real alarm clock, but I know how to turn it off in my sleep. Using my phone allows me to have to answer an equation to turn the alarm off. It's no big deal if I don't get up with an alarm during the wk, but it is nice to get up early and get a head start on the day. Now that I think about it, maybe the alarm clock app i'm using is causing the phone to overheat at times...
Drat!
I was hoping someone was able to diagnose and solve this issue. I've had this same problem/behavior for the last month now. And it's only getting worse :\ Also worth noting is that when the battery overheats, it smells like dill+mint (very weird) ... so it may be a bad battery. When I get a sec, I'll run to the sprint store and pick up a new one and test that out for a while.
Take the battery out and try to spin it on a flat surface... does it spin freely? If so its bad
Sent from my SPH-D710 using Tapatalk 2
I have had this problem a couple times before but it stopped for a long while. Then last night when I was charging, it overheated and shut off but this time it won't charge again, won't turn on at all and when it's plugged in there is a very dim blue light that flashes where the notification/charging LED is. I can barely see the light flashing but it is there. When I first plug in the charger I do see the battery with the loading animation and the battery is empty but then the screen goes black after a second or less and the dim blue LED starts flashing.
I let the phone and battery cool down for a long while, took it out and set it out for a while and it still won't charge at all. This really sucks because I have a 3-day weekend and I can only play Guild Wars 2 on the hotspot on my phone that won't turn on
I am using Mijjz Blend The Goodness with Sleshepics the governers 1.2.3 kernel that was flashed through the ROM updater, it's been working fine for the past couple weeks. I am not using any overclocking/undervolting profiles or anything like that besides what was put into the kernel already.
Please help D: I really want to play Guild Wars.... Q,Q
hope this helps,
i also have setcpu install in a stock rom with overclock and underclock enable
here is the profile settings in my setcpu that might help you solve your problem
profile1.screen off => cpu speed is set 500mhz(high) to 200mhz(low) in governor.conservative mode
profile2.in call => cpu speed is set 500mhz to 200mhz in gov.ondemand mode
profile3.battery temperature is greater than 44c(111f) degree => cpu speed is set 500 to 200 conservative
profile4.11pm to 7am(sleep time) => cpu speed is set 500 to 200 conservative
profile5.battery percentages drop less than 50% => cpu speed is set 1000mhz to 200mhz in ondemand mode
whenever those conditions hits when the phone is on, setcpu will lower the speed for me and consequently reduce the heat issues for me
because i run my phone in 1.7ghz ondemand mode all the time. my phone is the white version which have a newer cpu and i know for a fact
that the older black version epic4g-touch can only go as high as 1.5ghz before problems arise such as kernel panic and overheat
good luck
I had this issue. Man, after a month of looking for a solution, i think I found a solution, at least for my issue. My phone would reboot at least 5 times in a row, and get very hot. This is what worked for me; when the phone reboots, take the battery out, wait 5 seconds, hold power button and volume down to get to reboot into recovery, wipe out Dalvik cache, and then fix permission and reboot.... Hope this works for you too.
Sent from my Samsung S2 ET4G using Tapatalk
Related
I've heard that having your screen off setting to 128mhz that it drains more battery than 284mhz and does not let the evo perform correctly. Is this true?
I have mine to 128mhz atm and dont seem to notice qany diffrence in battery loss to when it was at 284. I have only had it this way about 24 hours but so far not a big diffrence one way or the other
Haven't noticed any extra power drawn, only thing I noticed and hate is that when you wake up it can lag bad, until the profile changes to a higher clock
Sent from my PC36100 using XDA App
Im interested in this also. I saw some people say 128 drains more battery but nothing to actually show it. I am running some tests of my own currently. Im sure it will be hard to see a difference unless there is something crazy going on.
It must have been me who posted about the 128Mhz bug first.
I'm running latest ota stock rooted, latest ota radio/wimax with Netarchy's 3.0 or 3.7.3c kernel.
I noticed that when I had 128-998 set on boot, the phone wouldn't sleep properly, and the battery drain in standby mode was ~3x what it normally was.
The normal battery drain for my configuration is about 1% an hour in standby.
If you are running a different rom/kernel, I suppose, it's entirely possible not to see this problem. Test it yourself and find out.
I have had my Evo clocked at 128 for Min and Max for about a day. I initially thought the reports of uneven performance were wrong, but a few runs of Pandora during "Screen Off" did cause some long pauses and some FCs on a couple of occasions. I suspect this is why many recommend increasing the clock to 245, especially when you have process heavy apps running.
I personally don't think the difference in such low clocks will have a significant impact on battery life, but for those of you who get the warm and fuzzies from the absolute lowest setting, I have been playing with my Min @ 128 and Max increased to 245 for a couple of hours. It's jumping out of the low clock much smoother (I can immediately drag the lock bar down) and I haven't gotten any FCs while using Pandora with the screen off. I have ran Pandora with the Screen Off and the "adb shell powertop -d" from my terminal. It is reporting that my Evo is staying in the 128 clock, but, like I said, it's transitioning to higher clocks without a hitch when I turn it on.
Hope that helps.
I've also found that 128 is just too low for things to work properly. It stutters a lot when the screen comes on and things like music also stutter.
Having tested this for a little over 24 hours in response to the increased battery drain, I could not tell any additional battery drain still after 24 hours. On the flip side i could not tell of any additional battery saving either. At the end of the day i was in my normal range.
I do not use the Stock rom but do use Netarchy's latest kernel. So ti may just be a stock rom thing. I will agree that the screen comes on sluggishly and music will skip if you have it playing with the screen off. Since i was unable to tell any significant benefit from lowering it i will be stick to 284.
I prefer screen off profile to scale down to 285mhz as opposed to 128mhz. I know the clock differences are minute, but the phone feels more responsive and ready for action when woken up at 285mhz. You can feel the 128mhz drag.
Due to some of the instability I've gotten, I've decided to bump up the Min to 245. It runs much smoother and I cannot see a difference in battery life. I think the occasional lag and FCs that 128 might cause will hurt your battery life before the increase in clock will. I'm now with the "128 is not an option" camp.
scriptx said:
I prefer screen off profile to scale down to 285mhz as opposed to 128mhz. I know the clock differences are minute, but the phone feels more responsive and ready for action when woken up at 285mhz. You can feel the 128mhz drag.
Click to expand...
Click to collapse
What is your screen off profile, min/max? Obviously 285 is min, but what is your max? What about when the screen is on?
I have my screen off setting for 245 min & max. I get no stuttering pandora and it doesn't **** itself when I turn the screen on. The transition to normal is smooth.
I am getting over 40 hours on battery....
with the set-up in my signature below.......
I have Set CPU set to 245/128 with screen off. I get almost no drain with phone resting. Went to be last night and when I picked up my phone this AM, it was still on the same %. This has been consistent for the last 3 nights.
If you go to the baked snack rom thread, towards the last two pages as of today....I discuss my set up. Others are experiencing the same kind of battery results.
I get no hiccups from resting to on. Pandora plays fine. If it needs the 245 for Pandora or such, it's there. If not, it goes down to 125 and uses almost no battery over an extended period of time.
I just tried setting 128 as min and 245 as max for screen off and my phone got stuck in a boot loop. After sitting idle for a few minutes it started rebooting on its own.
I had to remove the battery and was then able to get into the OS. I have since set my phone back to 245 . I will update if I find out this was happening for another reason or if I try 120 again.
I know it ibeta before you all start on me, however 15 minutes of web browsing = 10% loss of battery. At that rate my phone will be dead an hour and half of web browsing
When the phone is just on stand by battery life is fine
Hope they fix this when the "official" release comes out
Wow where did you learn maths?
BETA Roms effect the mind.
Jamiec902 said:
I know it ibeta before you all start on me, however 15 minutes of web browsing = 10% loss of battery. At that rate my phone will be dead an hour and half of web browsing
When the phone is just on stand by battery life is fine
Hope they fix this when the "official" release comes out
Click to expand...
Click to collapse
i think it will be 150 minutes and that's not 1,5h
btw
my phone: few calls, some games - 1,5 day and still 27% of battery
icemac said:
i think it will be 150 minutes and that's not 1,5h
btw
my phone: few calls, some games - 1,5 day and still 27% of battery
Click to expand...
Click to collapse
My phone: lots of calls, few minutes wireless =1 day and still 70%. No web browsing.
Agreed 150 mind isn't 1.5hrs. But still bad!
Jamiec902 said:
Agreed 150 mind isn't 1.5hrs. But still bad!
Click to expand...
Click to collapse
the screen needs lots of power, processor needs to,
everything needs the power
look it is same like brand new commputer (whit very good graphic card, processor, memory, MB) - you need good and strong power supply without it is crap ...
if you need good long working phone buy something else like :hmm: i dont know what maybe NOKIA with small BW display
no offence
I noticed on the JPC the battery drains soooo fast!
did a full charge while the phone was off today and also deleted the battery stats.. lets see if it improves
icemac said:
the screen needs lots of power, processor needs to,
everything needs the power
look it is same like brand new commputer (whit very good graphic card, processor, memory, MB) - you need good and strong power supply without it is crap ...
if you need good long working phone buy something else like :hmm: i dont know what maybe NOKIA with small BW display
no offence
Click to expand...
Click to collapse
I love my SGS and will not being going back to Nokia, also love andriod - just hoping the official release will let me have use for one full day - not too much to ask I dont think
I get 2 days of moderate to high usage with JPC. I think it uses less battery because the GSM signal is better, but the screen uses more power, is always over 90% in battery stats.
Sent from my GT-I9000 using XDA App
For me it all comes down "display on" time.
if using 3G/edge i get 4,5h
if wifi then 5,5h (no difference if im using it during 1 day or 4 days)
JPC is same as JP3 or JMx
Screen brightness
Just thought I'd say, incase you didn't know, the web browser has it's own brightness setting. That could be killing the battery.
I, for one, already set the brightness to the first level for all aplications that have brightness setting, and still the display sucks the battey like crazy, at list with JPC. With other FW it drops even to 40%.
Sent from my GT-I9000 using XDA App
speaking of GSM, w/c one is 2G mode for the Galaxy S.. GSM or WCDMA ?
earlz said:
speaking of gsm, w/c one is 2g mode for the galaxy s.. Gsm or wcdma ?
Click to expand...
Click to collapse
gsm = 2g
wcdma = 3g
Battery drain was ridiculous with me. The first night I went to sleep I remember my phone was nearly fully charged, when I woke up at morning it had used around 50%... that is, 50% of the battery for around 6 or 7h just sitting in IDLE! When I actually USED the phone it could barely handle 10h with a full charge, and that's with very moderate usage. I had to leave the phone charing all the time to survive a day with it (charging in my car, charging every time I stopped near an AC outlet, etc). And yeah, the funny thing was noticing how exaggeratedly high the screen battery drain was, even though I wasn't using the screen all that much...
Some other symptoms of the high battery drain:
-Charging the phone took FOREVER with the phone being used, took a LOT of time with the phone sitting Idle, but if I turned the off the battery would actually charge very fast... that proved that the phone was draining so much energy even the AC charger (or USB outlet) couldn't effectively charge the battery while supplying power to the phone...
-The phone got HOT very easily...
How did I solve it?
Well, yesterday I decided I would reflash my device. I did a full reflash (as I always do) including a re-repartion. Now the funny thing that I noticed was that my phone actually wouldn't flash! It would always crash at the Galaxy S welcome screen... I have never flashed it using my notebook (since I'm traveling), but I used the exact same procedure I always use with my desktop back home, for some reason it wasn't working. Maybe some corrupt file? I re-downloaded ALL files (that is, Odin with the 803 pit file, and the JPC files)...
For my surprise, this time my phone hanged in a green screen, and it was really scary. I even thought perhaps the Nokia USB cable I was using was causing some kind of incompatibility problem, but that would make no sense at all... so I entered the recovery menu in my phone and reset EVERYTHING, and tried flashing it one LAST time (this time closing ALL background apps in my notebook, to avoid any problems)... and there it went, a perfect flash, as easy as they go with my desktop PC back home.
1st thing I did was a hardreset, and then I reflashed it again with Doc's RomMod V2 (was using V1 the day before), and new hardreset in the sequence. Then I changed as little as possible in the phone configurations, I just turned everything off (GPS, wifi, and even the data connection through the power button shortcut), and went to sleep...
For my surprise, the next day I checked the phone's battery use, it had drained only ~4-5% for more then 10hours, this means it would, at least in theory, be able to last for days and days in this setup...
So I installed my apps again (not that I have many), did lagfix, turned widgets and network connection back on... and it has been working like a breeze, although battery drain can still be considered high, it's nowhere close to being as bad as it was before I flashed it, now at least the battery will last a full day with a charge @ my standards of usage, that's good enough for me...
One thing I did change, I remember my screen setup was always at 10/30min for shutdown, I left it like that because I'm always using the phone in situations where the screen will constantly shut down at my face, and that annoyed me... well, this time I actally left the stock 30 seconds for screen shutdown, not sure if it has anything related, but one of the things I noticed before was that my IDLE battery-drain was as high as you'd expect from a phone that had it's screen on all the time... maybe some bug makes the phone drain screen power even with the screen turn off, let's say if you have the 30min turn-off config, your screen will continue to drain power for 30min (and there you have the reason for so much screen draw in the stats), even though the screen is turned off... despite my hardware knowledge telling me that a black screen should NOT be draining power from your phone battery, you never know how far a software bug can fck things up hardware-wise, so I wouldn't be surprise if that actually DID happen...
I could even try setting my screen back to 30min-turnoff just to check if the battery drain will go back to insane levels.. but the fact is that I'm scared of messing it up again, it's working fine the way it is, why mess it up? I figured out some things that get messed up with this phone appear to only get fixed with a new firmware flash, and I really don't feel like having to flash my phone every two days...
Either way, I hope others here can fix their battery drain... it's just my tip: try reflashing, leave everything as stock as you can (only thing I did was Doc's RomMod v2, and later Ryan ZA's lagfix, none of them seem to be related to JPC's battery drain), and see if it helps...
wth I can only get 3.5 hours max
Sent from my phone so excuse the spelling errors
After a week of using JPC I don't see any real difference in battery usage from the original stock rom and JP3, I charge the phone every second night ( battery is usually around 25% at this point).
My usage isn't that high, I have a couple of notifications running and a weather widget that updates hourly, its my alarm clock, my mp3 player to and from work (about 90 minutes a day), I make and receive 4-5 calls a day and send and receive a dozen texts a day, I check face book 3-4 times a day and on a daily basis someone gets a 10-15 minute demonstration of the beauty of this phone(note: don't let a taxi driver play with your phone whilst in heavy traffic, even if it gets a confession that it makes his iphone look like a piece of crap).
As far as screen time outs are concerned, I set mine at 1 minute but always turn the display off manually when I finish doing something with it including after I have started the music player (btw I use bluetooth headset to listen to music but not for phone conversations).
The highest display percentage I have seen is about 85% but the is usually tied in with using gps or browsing, on a day I don't use gps or browsing display is much lower, on a day that the display is pretty much off it drops to about 10-15% usage.
This phone is the first, of the several pda/smart phones I have owned over the years, that I haven't had to charge every day.
Id battery usage is not a problem for me on JPC, 8hrs idle ( sleeping ) and I still got 100% started to use the phone and it rapidly dropped.. now im playing a 2hr movie and see if i can get it to loop for 2-3 times before it shuts off.. if it reaches 6hrs then i would consider the battery usage the same.
Please turn off the GPS and a-GPS....
You will get a much better battery life.....
So I was wondering what temps you guys are seeing when your phone overheats.
My phone reboots when it hits 37 C, which seems awful low. Anyone else seeing such low reboot temps?
gmichaelow said:
So I was wondering what temps you guys are seeing when your phone overheats.
My phone reboots when it hits 37 C, which seems awful low. Anyone else seeing such low reboot temps?
Click to expand...
Click to collapse
Mine doesn't reboot that low, the highest I have seen it go was like 43.7 or something
I've never had my phone reboot due to overheating even at 42°C. Running CM6.01
Sent from my Incredible using XDA App
Hmm, this is getting frustrating. I've begun to reboot at around 37 C. Is there any way to change that number? Anything to reset?
Is that CPU or battery temperature? If battery then the CPU would be much hotter.
Sent from my Droid using XDA App
Battery... but it's weird. The battery temperature gets to 37 C, and then reboot. When I very distinctly remember it before going 45+ C without a problem.
And now I'm bootlooping. Seems to start up, and is still too hot, then reboots again. Anyone have this happen to them? Lower temp reboots?
Sounds like you may have permanently damaged your device, if your battery temp were 40+ degree celsius your CPU temp would be a sustained 15+ degrees hotter. Running your device this hot often certainly could damage it over time.
Sent from my Droid using XDA App
Try a standard or increasing voltage kernel if possible.
Sent from my Droid using XDA App
fivefour said:
Sounds like you may have permanently damaged your device, if your battery temp were 40+ degree celsius your CPU temp would be a sustained 15+ degrees hotter. Running your device this hot often certainly could damage it over time.
Sent from my Droid using XDA App
Click to expand...
Click to collapse
No no, my battery isn't that hot for long amounts of time, just, like when I'm surfing for a long time or something. Trying an undervolted kernel now.
Do you have a backup battery that you can try - see if you get the same results? Batteries do occassionally stop working properly.
My phone would reboot when using GPS in the car if it was on the dashboard or mounted - I checked the temperature when it booted and didn't get stuck in a boot loop and it was around 45c.....
I returned the phone to stock and brought it back to vzw, they gave me a new battery, phone still runs somewhat hot even stock.
jp43 said:
My phone would reboot when using GPS in the car if it was on the dashboard or mounted - I checked the temperature when it booted and didn't get stuck in a boot loop and it was around 45c.....
I returned the phone to stock and brought it back to vzw, they gave me a new battery, phone still runs somewhat hot even stock.
Click to expand...
Click to collapse
But mine is rebooting at 37-38 C. Which is awfully low. I'm RUU'd, S-oned, and factory-resetted and STILL it happens. So it's a hardware problem.
Gonna take it into a Verizon store and demand a replacement on the spot x]
I can advisr from personal experience on your symptoms that you have one choice ... Return to verizon for a refurb. This is what happens when you have an early incredible with a faulty hardware radio. It gets to the point where it starts trying to compensate and super heats. You must return.
Every other suggestion would be a mask to an existing well known hardware problem.
I once left my phone in a black bag on a hot summer day. It went up to 50 C with no problems. It didn't reboot or anything.
I have one of the original Incredible's from launch day, it is usually around 43-45. Sometimes it gets warmer than that playing games. Never actually had any problems. The hottest it ever gets is on Z rom's. Those things have gotten it to 50 .
I'm on CM7 W/Slayher's 2.6.37 kernel, and it's at 42 just on the home screen. Mind you this is all on stock speeds. My phone doesn't like to overclock. Regardless of kernel. It can go to 1.113 sometimes, but any more = reboot.
On the HTC Incredible site, there is a FAQ which states the maximum recommended operating temp is ~60C.
I'm relatively sure there is no problem with the battery or the CPU doing up to ~90 for awhile because that's a fairly common temp for CPUs and Batteries to withstand. I'm sure that like most batteries , at >~50C it is less efficient, but I doubt the CPU is presented with any problems in that range.
Phones present a unique set of high-temp problems. Cooling sucks in those little enclosed boxes, and manufacturers definitely don't want your hand or ear burned, and are terrified of having a battery burn up in your hand or pocket, so that is probably why 60 is said to be max. I don't like picking up my phone when it's at all hot (~40C or more) but while experimenting with my own kernels and voltages and overclocking, I've had it reboot somewhere around 60C. Was it the temp, or was it overclocked too far? I have no idea, but I lowered both and stopped taking stupid chances with it.
This thing of rebooting at 37C seems nuts, inappropriate, and most likely a defective part, or one of the many services or apps that perhaps does the wrong thing (accesses verbotten memory, bad ptr, etc..)
A bad example for sure, but at work, many of our HP or Dell Racked servers (DL380's etc), are too hot to touch while running. They have enough fans to power a 747, and it just makes it pretty clear that in some cases, processors and other components can run at amazing temps.
--
Hi there! I had this problem with my Nexus twice now, that's why I'm bothering you.
Long story short - I plugged my phone to charge in the evening, woke up in the morning to find that the phone is VERY hot(area around the camera on the back) and switched off, and won't turn on. After doing a battery pull the phone switched on, the battery was full and the temperature was at 46C. It happened to me on the Monday night but I thought it is just something silly, but it happened to me today again. I was not using any hardware intensive application before I went to bed, just writing emails with my GF.
Any ideas?
ive left mine on overnight every night since saturday and its not overheating
Leave it in a chocolate tin to keep it cold, with ice below it, charge it in the morning and see if its a app
Sent from my HTC Vision using XDA App
I'd do a factory reset and see if it does the same after another night of charging with no apps on it.
If it does the same, the phones probably defective.
mintaeroboy said:
Leave it in a chocolate tin to keep it cold, with ice below it, charge it in the morning and see if its a app
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
A chocolate tin with ice under it?? REALLY?
gambiting said:
Hi there! I had this problem with my Nexus twice now, that's why I'm bothering you.
Long story short - I plugged my phone to charge in the evening, wake up in the morning to find that the phone is VERY hot(area around the camera on the back) and switched off, and won't turn on. After doing a battery pull the phone switched on, the battery was full and the temperature was at 46C. It happened to me on the Monday night but I thought it is just something silly, but it happened to me today again. I was not using any hardware intensive application before I went to bed, just writing emails with my GF.
Any ideas?
Click to expand...
Click to collapse
Have you modded the phone since you got it? Like rooting or installing any mods.
How many apps have you installed on it? Any that may keep running in the background?
If it does it again then I would advise going into Settings, Backup & Reset and restore the phone to factory settings. Then put the phone back on charge for about 8 hours and sede if the temperature goes up again. As mentioned it may just be an app thats making the phone go hot but if it goes hot after a factory reset then you will need to send it back for replacement.
Mark.
The first thing to go from heat damage is the battery. 50 degrees celcius and up is in the battery killing temperature range.
As long as it's under warranty I guess do what you want. But I'd highly recommend setting up an app like setcpu to force a lower clock speed when temp>44 celcius, just to be safe. No sense in killing a battery while trying to fix the problem.
Sent from my SAMSUNG-SGH-I777 using XDA App
I leave mine on charge overnight, and it doesn't do this... so I'd agree with others in that it's either a rogue app or a duff handset.
Didn't they say that one of the CyanogenMod devs was working with Samsung on the Nexus? Maybe he implemented "sleep of death" as a feature
Sent from my GT-I9000 using XDA App
The phone is not rooted, it's not running any mods. The only two applications that run constantly in the background are the DoubleTwist AirSync module and Llama profile manager(and the default weather+news widget). As both have not been tested with Android 4.0 it may be it. Is there any good app to display the current CPU usage by a process? Just like "top" in the console.
Don't know about it being hot but mine was on charge last night and died.Making me 2 hours late for work . Pulled the battery out and put back in and its fully charged ????
Sent from my Galaxy Nexus using XDA Premium App
cja1972 said:
Don't know about it being hot but mine was on charge last night and died.Making me 2 hours late for work . Pulled the battery out and put back in and its fully charged ????
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
That's pretty much the same thing that happened to me. Except that being hot explains the issue at least partially,as the phone will switch off when overheating.
Same here, no issues with mine. Maybe do an exchange?
coleburns said:
Same here, no issues with mine. Maybe do an exchange?
Click to expand...
Click to collapse
I'll try it for one more charge after a factory restore. If it doesn't help then I'll get it exchanged.
cja1972 said:
Don't know about it being hot but mine was on charge last night and died.Making me 2 hours late for work . Pulled the battery out and put back in and its fully charged ????
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Mine was on charge last night and showing 28% on screen. I rebooted the phone and when it came back on, it was suddenly showing as 48%.
I think the battery reporting may be slightly borked, but this could just be down to the battery being run in. I'm just going to keep an eye on it for now.
gambiting said:
Is there any good app to display the current CPU usage by a process? Just like "top" in the console.
Click to expand...
Click to collapse
Free and simple:
https://market.android.com/details?id=com.houmiak.taskmanager
djmcnz said:
Free and simple:
https://market.android.com/details?id=com.houmiak.taskmanager
Click to expand...
Click to collapse
Thank you, I have used different task managers but none of them displayed CPU usage.
I have discharged my battery pretty much completely, and now I'm charging the phone again, with my battery monitoring app running - at 50% capacity now the temperature is 42C. Can it be normal? The task manager shows that no process is using any CPU time.
That is hot but not that bad. Upper 40's celcius (47-49) is not good. And 50 is critical. Download setcpu and downclock the cpu to 500mhz while charging to help keep the temperature low in case an app spikes cpu usage that doesn't show up in task manager.
Sometimes just flipping the phone so the back is exposed is enough to cool down a phone.
Keep in mind most electronics have solder that will melt between 120 to 180 degrees celcius (248 - 356 farenheit!). While your phone should never ever get close to that, 50 degrees celcius pales in comparison. But it can kill the battery.
Seems most people who have had the problem of their phone spiking in temperature only have it happen a couple times and that's it.
I really recommend setcpu as you can have it run your phone slower when it hits a certain temperature to help keep it cool. As well as sound a notification that it has past that temperature.
It will prevent damage while you try and find out what may be causing the spike.
Though 42 degrees celcius is relatively normal for charging temperatures.
For my phone I have it set at 44 degrees celcius. I'd rather catch it before it gets even close to bad.
Sent from my SAMSUNG-SGH-I777 using XDA App
gr8hairy1 said:
That is hot but not that bad. Upper 40's celcius (47-49) is not good. And 50 is critical. Download setcpu and downclock the cpu to 500mhz while charging to help keep the temperature low in case an app spikes cpu usage that doesn't show up in task manager.
Sometimes just flipping the phone so the back is exposed is enough to cool down a phone.
Keep in mind most electronics have solder that will melt between 120 to 180 degrees celcius (248 - 356 farenheit!). While your phone should never ever get close to that, 50 degrees celcius pales in comparison. But it can kill the battery.
Seems most people who have had the problem of their phone spiking in temperature only have it happen a couple times and that's it.
I really recommend setcpu as you can have it run your phone slower when it hits a certain temperature to help keep it cool. As well as sound a notification that it has past that temperature.
It will prevent damage while you try and find out what may be causing the spike.
Though 42 degrees celcius is relatively normal for charging temperatures.
For my phone I have it set at 44 degrees celcius. I'd rather catch it before it gets even close to bad.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Thank you for your detailed explanation. Actually the temperature dropped later, averaging 35-36C between 80-100%. So the temps look good for now, but I still have no idea what caused the sleep of death issue....
Yeah,ive had this two nights in a row.i deliberately rebooted my phone and put it on charge last night to eliminate an app being the cause.
This pretty much makes the phone useless as an alarm.
I charge my DHD every night over night, to make sure it has a full charge at the start of everyday. I've had my DHD for 16 months and I have had no problems with it ever. I've run many ROMS and kernels and its been rooted since the first week I got it. However it now overheats when I put it on charge almost every night.
I plug it in and the temperature will steadily rise from about 29 - 32C (which is what it runs at throughout the day) to over 40C, I've never seen what it actually reaches because since its over night I haven't monitored it that much. The highest I've seen it is 47C. After the first few occurrences of this I set a profile in setcpu to set the phone to 800Mhz when temperatures go over 38C. However this was to no avail. I then set it to underclock all the way down to 230Mhz when it goes over just 35C. But yet it still overheats when on charge so I don't think it has anything to do with my CPU? I changed kernels too but it still didn't help. The only reason this really annoys me is when it does over heat (lets say 1 in every 3 nights) I wake up and its just boot looping over and over until I do a battery pull. Which means my alarm hasn't been going off so I've had to dig out the old G1 the past two weeks just for it to act as an emergency alarm in case the DHD overheats.
I'm not sure what my problem is here, any insight?
Might want to try replacing the battery. Is it a third party bettery, those cheap "Gold 2000ma" batteries are notorious for overheating and being a bit rubbish. The other thing that might have happened is there is a short in the charging circuit which is causing the overheating.
I would say it's a 80% chance of it being a hardware problem. Try a different ROM if you are unsure.
If you have an o/c tool like no frills cpu control or anything like that, then that could be your issue too. Running high on cpu can cause overheat even when the phone is in sleep mode.
Sent from my HTC Desire HD using XDA App
Thanks for the replies.
I have my cpu overclocked during the day but I have a profile in setcpu which underclocks it to 230Mhz when the phone goes over 35C. I've seen this in affect and the cpu does downclock as expected yet my phone is still overheating.
I am using the stock HTC battery still and have had no issues with it before. I will try another ROM/kernel combo and see if it that resolves my issue just in case. Otherwise I might have to S-ON my phone again, put it back to stock and send it to HTC...
didge3 said:
Thanks for the replies.
I have my cpu overclocked during the day but I have a profile in setcpu which underclocks it to 230Mhz when the phone goes over 35C. I've seen this in affect and the cpu does downclock as expected yet my phone is still overheating.
I am using the stock HTC battery still and have had no issues with it before. I will try another ROM/kernel combo and see if it that resolves my issue just in case. Otherwise I might have to S-ON my phone again, put it back to stock and send it to HTC...
Click to expand...
Click to collapse
I had this same problem it was the setcpu app or no frills create another profile and put the setting on charging and turn setting down or add profile when screens off 122-245 set priorities to high hope this helps
If it's not a software issue, your battery might be faulty and you should switch it as soon as you can.
starkilling said:
If it's not a software issue, your battery might be faulty and you should switch it as soon as you can.
Click to expand...
Click to collapse
My Desire HD is fitted withe the original battery and its also getting hot during charging.
I've been monitoring my battery with 'Battery Monitor Widget' from the market, the recordings show that throughout the day my battery fluctuates between 20 - 30C depending on my usage. As soon as I plug it in however the battery immediately starts creeping up from low 30's to around 47C, this is where the monitoring stopped and has a huge gap until morning when I boot my phone again.
I applied a new profile in setcpu as suggested for charging instead of temperature and tested again last night, I set the charging profile to 230/384 min/max. The monitoring from last night shows the phone reached 40C by the time it'd charged to 100% and steadily started to cool back towards 30C, my phone was on when I woke up and functional so hopefully this is a temporary fix until I eventually have to get a new battery because I'm pretty certain its a hardware fault.
How long is the standard warranty for a Desire HD? If its 1 year then I'm out of luck and will have to buy a replacement...
didge3 said:
I've been monitoring my battery with 'Battery Monitor Widget' from the market, the recordings show that throughout the day my battery fluctuates between 20 - 30C depending on my usage. As soon as I plug it in however the battery immediately starts creeping up from low 30's to around 47C, this is where the monitoring stopped and has a huge gap until morning when I boot my phone again.
I applied a new profile in setcpu as suggested for charging instead of temperature and tested again last night, I set the charging profile to 230/384 min/max. The monitoring from last night shows the phone reached 40C by the time it'd charged to 100% and steadily started to cool back towards 30C, my phone was on when I woke up and functional so hopefully this is a temporary fix until I eventually have to get a new battery because I'm pretty certain its a hardware fault.
How long is the standard warranty for a Desire HD? If its 1 year then I'm out of luck and will have to buy a replacement...
Click to expand...
Click to collapse
Did you ever try uninstalling the setcpu app or any cpu controller and try that.. another thing what Rom are you using . Did you try wiping the battery stats in recovery
hopesfall190 said:
Did you ever try uninstalling the setcpu app or any cpu controller and try that.. another thing what Rom are you using . Did you try wiping the battery stats in recovery
Click to expand...
Click to collapse
Worth a try, Im using Virtuous Quattro RC3 at the moment. Although the ROM development seems to have died so I might try the other stock ICS ROM I see floating around for the DHD.
I've been told to dump setcpu about 948 times before due to performance issues it supposedly brings or other faults and I just cant tear myself away from it, I've had the widget on my home screen in the same place set up the same way for about 3 years across 2 different phones and about 20 different ROM's, I just cant seem to force myself to get rid of it.
Wiping my battery stats seems like a good idea and I'll make sure to do that tomorrow morning when my phone will be fully charged. I'll also change my ROM later this week and if I'm still getting issues I will TRY to ditch setcpu for a while. If I still have issues then I will have narrowed it down to some sort of hardware fault.