I have a fascinate currently running HellyBean 4.03 and I have an anker 1800mah battery, I have the kernal running smartassv2 and sio with max cpu set to 1200. I used gmaps with navigation (gps plus cell data) last night for about 30 minutes and when I picked my phone up again it was hot. After turning everything off the phone cooled down again but I am curious what would have caused this? Rom? Kernal? Battery? Anyone else experiencing any overheating issues?
I would test the battery myself but unfortunately I cannot get to my original battery until this weekend.
Yeah, that always happens when it has to run at max or near-max clock frequency for a long period of time. As long as it isn't give-you-a-burn hot, nothing is wrong.
Posted from my Galaxy Tab 2 with CM10.1
MultipleMonomials said:
Yeah, that always happens when it has to run at max or near-max clock frequency for a long period of time. As long as it isn't give-you-a-burn hot, nothing is wrong.
Posted from my Galaxy Tab 2 with CM10.1
Click to expand...
Click to collapse
If this is normal then is there anything I could do to reduce the temperature? Maybe set max cpu back to 1000? I only ask because I am concerned if I tried to use navigation for a longer period of time the heat would end up causing some damage to the phone.
ulnevrwalkalone said:
If this is normal then is there anything I could do to reduce the temperature? Maybe set max cpu back to 1000? I only ask because I am concerned if I tried to use navigation for a longer period of time the heat would end up causing some damage to the phone.
Click to expand...
Click to collapse
No its fine these phones are known for getting a little warm I have mine set to 1.4ghz 24/7 and its fine . back in the days when you could over clock your phone to 1.7ghz LOL I had my over clocked to 1.6ghz and it got so hot it would turn on and off it never hurt it lol
Sent from my SCH-I500 using Tapatalk 2
Related
Hello,
Im experiencing some lockscreen delay when i try to wake up the phone. I have rooted and flashed the original kernel back. When phone is connected to PC or charging its very responsive. Is there anyway to fix this? How do you do a factory reset?
Would be interested in an answer for this as well. I have the same situation, fast response to lock-button press when charging, few (2 +-1) seconds delay when not charging. I haven't rooted yet and have 2 pages of homescreen which have 5 widgets and 10 shortcuts/apps.
Is this normal behaviour, because the phone wakes up from a deep sleep state?
I think this is because of the phone being in sleep mode. It takes a second to wake up and increase the CPU speed and such... If you were to disable this, your phone would probably consume a LOT more battery. =/ But, heck, if it's only one second, it's worth waiting for, given that it's the most awesome phone you'll see until SGS3!
This used to happen all the time on JVK on SGS1.
This also happens to me and I just can not figure out what causes this? When the phone is on the charger it mostly doesn't happen. When I switch from Wifi to 3G, for a few seconds it doesn't happen... I cant figure it out what it is!
Same here, doesn't bother me that much though. What does bother me is, I first see the normal screen for just a moment and then the lockscreen. Anyone else got this to?
Sent from my GT-I9100 using XDA Premium App
It's because when the phone is uplugged and has been locked for awhile, the CPU downclocks to conserve energy. And when you wake the device up, it takes awhile to get the display going and bump the CPU speed back up.
This happened with my old HTC Desire with battery optimizations. When the custom roms start rolling in for the G S2, I guarentee there will be a 'fix' for this at the expense of battery life.
FYI, the delay isn't there when the phone is on charge/plugged in as the CPU doesn't downclock as drastically.
*EDIT*
TheGhost1233 said:
Same here, doesn't bother me that much though. What does bother me is, I first see the normal screen for just a moment and then the lockscreen. Anyone else got this to?
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Yep, I've got that, as does the other 4 Galaxy S2's that have passed through my ownership due to replacements. It's completely normal don't worry.
drm111 said:
It's because when the phone is uplugged and has been locked for awhile, the CPU downclocks to conserve energy. And when you wake the device up, it takes awhile to get the display going and bump the CPU speed back up.
This happened with my old HTC Desire with battery optimizations. When the custom roms start rolling in for the G S2, I guarentee there will be a 'fix' for this at the expense of battery life.
FYI, the delay isn't there when the phone is on charge/plugged in as the CPU doesn't downclock as drastically.
*EDIT*
Yep, I've got that, as does the other 4 Galaxy S2's that have passed through my ownership due to replacements. It's completely normal don't worry.
Click to expand...
Click to collapse
I use Widgetlocker great lockscreen mod and the normal screen does not come up first.
I understand your explanation but this did not happen to my desire and it doesn't happen all the time (switch from wifi to 3g and stuff). I can get used to it but it would be nice if it would be instant!
DHel01 said:
I use Widgetlocker great lockscreen mod and the normal screen does not come up first.
I understand your explanation but this did not happen to my desire and it doesn't happen all the time (switch from wifi to 3g and stuff). I can get used to it but it would be nice if it would be instant!
Click to expand...
Click to collapse
It happens rarely, but I've used both widget locker and the stock lockscreen on this phone and it happens on both.
And no, it didn't happen on the stock desire, it only happened on my desire with the battery optimizations which downclocked the CPU to 133mhz i believe, so the G SII must be downclocking to around that speed when not plugged in.
drm111 said:
It happens rarely, but I've used both widget locker and the stock lockscreen on this phone and it happens on both.
And no, it didn't happen on the stock desire, it only happened on my desire with the battery optimizations which downclocked the CPU to 133mhz i believe, so the G SII must be downclocking to around that speed when not plugged in.
Click to expand...
Click to collapse
I think you are right about the downclocking because when I wake my SGSII RIGHT after a whatsapp message or something it works instantly. That means that the CPU is also awake to for a moment. Strangely, Setcpu doesnt affect this when I set 1200mhz on sleep. Oh well, lets await the custom roms!
I left my TP on and booted into Android last night as it was charging. When I picked it up this morning it was really HOT and overheated, so I'm thinking either turn it off when charging or boot into WebOS before while charging. It seems like its not shutting off the charger when it reaches 100%.
Good to know. Do you know if the developers know about this as a known bug? Please check the rootzwiki thread here:
http://code.google.com/p/cmtouchpad/issues/list
open issues here:
http://code.google.com/p/cmtouchpad/issues/list
Left mine plugged in repeatedly w/out issue the last two nights w/out any heat issues. I had my screen off profile in SetCPU set to 1080 max CPU speed.
Redflea said:
Left mine plugged in repeatedly w/out issue the last two nights w/out any heat issues. I had my screen off profile in SetCPU set to 1080 max CPU speed.
Click to expand...
Click to collapse
I've got a case on mine so I might have not noticed if it was hot.
I've set the CPU to 1080 max aswell but can't overcome the sleep bug.
I'll take the case off tonight n test this.
Sent from my CM7 Atrix!
jackdonogy said:
I've got a case on mine so I might have not noticed if it was hot.
I've set the CPU to 1080 max aswell but can't overcome the sleep bug.
I'll take the case off tonight n test this.
Sent from my CM7 Atrix!
Click to expand...
Click to collapse
I was hoping upping the minimum CPU setting to 384mhz would have helped the sleep bug, but it hasn't. That and the wifi bug are the only 2 annoyances, but considering the alpha state, its stellar. Doesn't even really bother me
Sleep bug only effects me when Touchpad is asleep with charger plugged in. When unplugged and left alone It always turns on fine. I tested it to make sure too. Im also Overclocking to 1.5 ghz with set cpu and minimum 384 mhz using OnDemand.
Background: cm7 nightly (6 when this happened)
So last night before I went to bed, my phone was really hot and according to z-device test, my phone was 36°C. Then in the morning, it took nearly a minute for my screen to turn on so i could stop my alarm and it was even hotter. Z-device test now said it was 50°C. Idk if that's accurate but it definitely felt well over 100° Fahrenheit. I put the screen on my face and it was almost unbearably hot. The I turned it off until it cooled off and it seemed okay the rest of the day. What could the problem be?
--
Sent from my Samsung Galaxy S II using XDA App
was the phone plugged into the charger? were you using it intensively on the charger right before you went to bed? do you have any profiles set (with setcpu or another program) that is forcing your phone to stay on high frequencies?
if it is fine now, then i wouldn't worry about it... chances are some app just caused you to use a lot of CPU, thereby making the phone hot. if it happens again, and you can't pinpoint a particular app as the culprit, i would try a battery pull, and if that doesn't work, maybe try a re-flash of CM7.
It was plugged in. And I had setcpu at 800-1200 because I heard that if the cup gets too low, the screen won't turn on... Also it was plugged into my Touchpad charger, and and since the Touchpad charger is like higher voltage or whatever, could that have affected it?
Btw, i uninstalled SetCPU since then.
--
Sent from my Samsung Galaxy S II using XDA App
yes, that is what is causing your heat issue. you should not do extremely intensive tasks (like game playing) while your phone is on the charger - your phone is receiving a lot of juice, and you are exerting a lot of juice at the same time - ends up in a bad (and hot) combination.
especially with the setcpu charging profile that you have set up... you aren't allowing your phone to get below 800 mhz while it is on the charger, so of course it is going to be excessively hot when charging, for the reason mentioned above. if you got rid of that profile (don't have to get rid of setcpu completely), and let the phone dictate the frequency it charges at (most likely 200 mhz, or even deep sleep), then your heat issues will be solved.
glad i could help.
Ferrari353 said:
It was plugged in. And I had setcpu at 800-1200 because I heard that if the cup gets too low, the screen won't turn on... Also it was plugged into my Touchpad charger, and and since the Touchpad charger is like higher voltage or whatever, could that have affected it?
Btw, i uninstalled SetCPU since then.
--
Sent from my Samsung Galaxy S II using XDA App
Click to expand...
Click to collapse
If you limit max frequency to less than 800 on a stock kernel - you'll encounter SoD issues.
With a custom kernel that includes the SoD fix (nearly any custom kernel does), you're fine. I wouldn't set a limit to 200 max and do NOT use "Powersave" for screen off.
Which custom kernel? Ive never flashed kernels before... Do kernels come with Roms? Because I have cm7 nightly...
--
Sent from my Samsung Galaxy S II using XDA App
I am no my second GS2 and the issue persists.
Issue:
When charging overnight, the battery gets extremely hot. So much it warps the sim card. The first phone overheated until it died. Last night the second phone overheated until the warning message “charging paused due to temp” came up. I do use a CPU intensive app that uploads files to my server when plugged in. (so it doesn’t drain the battery). I have used all these apps on my old captivate with no issues with overheating.
I have tried Unnamed 2.2.1 and ICSreweD 1.6.1 roms, but the battery still overheats. Unless this might be a faulty batch from the store, what areas should I look into? At the end of the day, I would really like to continue to allow the app to run while charging. Especially since I have used it with less powerful phones prior. I have read others have this same issue with the GS2 but no solutions as of yet. Is there a different ATT phone that does not have this issue?
Silly question, but I know many who do this...
Do you place your phone under your pillow overnight while charging?
When charging and running a app that requires high cpu usage will overheat the battery. So close it at night while charging.
Damn warping the card. **** that's bad.
One time at football camp i put my shoulder pads in my ass
If you need to keep the app running while plugged in all night, what about using a plugged in profile in set CPU to throttle to 800 mhz Max or something...
Sent from my SGH-I777 using XDA App
dandrumheller said:
If you need to keep the app running while plugged in all night, what about using a plugged in profile in set CPU to throttle to 800 mhz Max or something...
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Is there a specific app you recommend? Also, is there an app to limit the cpu useage of a service/app?
quy said:
Is there a specific app you recommend? Also, is there an app to limit the cpu useage of a service/app?
Click to expand...
Click to collapse
Set it with setcpu or tasker. It's likely running at 1200 mhz all night right now. (assuming you don't OC). Try throttling it down to 500 or 800 mhz, it should help. Not sure if there's anything that limits specific apps though.
Sent from my SGH-I777 using Tapatalk
Try the lulzactive CPU Governor.
Sets max CPU clock to 200mHz while phones asleep.
Also great for battery life
twiggums said:
Set it with setcpu or tasker.
Click to expand...
Click to collapse
If you absolutely have to leave your phone performing such intensive tasks all night, this is what I would try.
As twiggums said, it is probably running at 1200 all night and just melting itself. Unlike most computers, everything in our phones is passively cooled. Something else you might try is removing the battery cover (and any phone case) and placing a fan blowing directly on it. I know that is extreme, but so is what is happening to your phone.
Hope this helps.
I have also experienced this and it's really annoying. I couldn't love a human child as much as I love this phone but the overheating is not cool. I was using my phone to navigate while charging and once it got so hot that it locked up and another time it paused the charging due to thermal issues.
Sent from my SGH-I777 using XDA App
MonFrayr said:
Something else you might try is removing the battery cover and placing a fan blowing directly on it. I know that is extreme, but so is what is happening to your phone.
Hope this helps.
Click to expand...
Click to collapse
I had to do that sometimes when downloading some big files and tethering. Lol
Since my PC is caseless it wasn't that hard pointing a 120mm fan to it.
And yes it did work.
DJSLINKARD said:
I have also experienced this and it's really annoying. I couldn't love a human child as much as I love this phone but the overheating is not cool. I was using my phone to navigate while charging and once it got so hot that it locked up and another time it paused the charging due to thermal issues.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
IIRC entropy mentioned some time ago that he throttles CPU to 800 mhz when using nav and charging...keeps it cooler and allows for slight charge rather than drain...
Sent from my SGH-I777 using XDA App
Yeah I'd suggest possibly throttling the CPU. I charge my phone while driving and stream Pandora and use navigation. I've got mine set to Max out at 500 while screen off and it works fine.
Ideally our phones should be able to handle sustained 1200 mhz. But then when you add a case and the heat generated while charging I guess it's too much for some. Guess it's the price we pay to have a beast of a CPU
Sent from my SGH-I777 using Tapatalk
thanks for the tips on throttling the cpu. i had thought about that and will probably do it but i still thinks its really lame that we have to do this. i dont even have a case on my phone. what are people who arent rooted and cant underclock their cpus supposed to do? oh well i guess
I have started to notice this on my phone. it happens when I'm in the car only though. Here's the situation.
It seems anytime I run Navigation my phone cranks up in heat to the point that I can't touch it. Is this a ROM/Kernel issue, or a problem in the phone itself?
stalked_r/t said:
I have started to notice this on my phone. it happens when I'm in the car only though. Here's the situation.
It seems anytime I run Navigation my phone cranks up in heat to the point that I can't touch it. Is this a ROM/Kernel issue, or a problem in the phone itself?
Click to expand...
Click to collapse
Well if your sig is correct and you're running at 1600 MHZ, I'd say that's probably why. Running at that speed for prolonged periods is likely to generate some heat.
twiggums said:
Well if your sig is correct and you're running at 1600 MHZ, I'd say that's probably why. Running at that speed for prolonged periods is likely to generate some heat.
Click to expand...
Click to collapse
I run Set CPU and my sig isn't correct. Well, the 1600 mhz isn't at least. I have it capped at 1000. It's just odd that I can multi task any number of applications without a problem. I use navigation and instantly, the only application I can use is that one. Running Pandora or the phone or the phone interrupts pandora or the phone interrupts navigation and I get this error and the screen gets untouchable.
stalked_r/t said:
I run Set CPU and my sig isn't correct. Well, the 1600 mhz isn't at least. I have it capped at 1000. It's just odd that I can multi task any number of applications without a problem. I use navigation and instantly, the only application I can use is that one. Running Pandora or the phone or the phone interrupts pandora or the phone interrupts navigation and I get this error and the screen gets untouchable.
Click to expand...
Click to collapse
Hmm possibly reflash your ROM. I can run nav and Pandora fine, and my phone limits my CPU to 500mhz while screen is off. Or at least try reinstallin maps/nav, sounds like its gobbling up way too much CPU for some reason.
twiggums said:
Hmm possibly reflash your ROM. I can run nav and Pandora fine, and my phone limits my CPU to 500mhz while screen is off. Or at least try reinstallin maps/nav, sounds like its gobbling up way too much CPU for some reason.
Click to expand...
Click to collapse
I told Pandora to not turn off the screen. I would think that Nav would do that natively or else it would negate the purpose of it. I wonder if maybe telling Pandora to keep the screen on and Nav keeping it on natively makes it think really hard and heat up.
stalked_r/t said:
I told Pandora to not turn off the screen. I would think that Nav would do that natively or else it would negate the purpose of it. I wonder if maybe telling Pandora to keep the screen on and Nav keeping it on natively makes it think really hard and heat up.
Click to expand...
Click to collapse
That's probably why
Sent from my SGH-I777 using Tapatalk 2 Beta-5
My P760 is heating in the sim card area with almost no use, the battery doesn't get hotter then 38C.
Is this normal?
Can a sim card cause heat?
albwh said:
My P760 is heating in the sim card area with almost no use, the battery doesn't get hotter then 38C.
Is this normal?
Can a sim card cause heat?
Click to expand...
Click to collapse
No, as far as I know there is CPU somewhere nearby and that causes heat. What CPU governon you have? If "performance" you should change it. Also maybe some apps working cause high use of CPU? There can be a lot of reasons. You have to tell us more details such as ROM which you use, if this thing happened from the start etc. For start you can try hard reset and see how it will work.
anirion said:
No, as far as I know there is CPU somewhere nearby and that causes heat. What CPU governon you have? If "performance" you should change it. Also maybe some apps working cause high use of CPU? There can be a lot of reasons. You have to tell us more details such as ROM which you use, if this thing happened from the start etc. For start you can try hard reset and see how it will work.
Click to expand...
Click to collapse
I have just got it yesterday. I have stock v20h for Europe rooted. My governor is set to interactive.
And if I integrated some app updates into rom, can I use hard reset?
fieldien their
So can I hard reset if I integrated apps into rom?
You can but you will lose them. You will need reinstall them.
Sent from my LG-P760 using Tapatalk 2
I did the hard reset but the problem is still there. Any other ideas?
Install cpu spy from playstore and see speed your CPU works for few hours.
Sent from my LG-P760 using Tapatalk 2
I already have battery stats plus and it says that the cpu stays at 600-1000mhz when the screen is on and in deep sleep when the screen is off.
albwh said:
I already have battery stats plus and it says that the cpu stays at 600-1000mhz when the screen is on and in deep sleep when the screen is off.
Click to expand...
Click to collapse
So how long it stays in 1000 Mhz? Did you try different governon?
8 hours on battery. 37% battery. 37 min at 300mhz. 1h at 600mhz. 9min at 800mhz. 32min at 1ghz. 5h 34min deep sleep. All of these with hotplug governer.
albwh said:
8 hours on battery. 37% battery. 37 min at 300mhz. 1h at 600mhz. 9min at 800mhz. 32min at 1ghz. 5h 34min deep sleep. All of these with hotplug governer.
Click to expand...
Click to collapse
It look everything is fine. Well the last resort is to give your phone to LG service if noone else will write something but I wouldn't bother if it's only heat. My phone sometimes heats up if I watch a lot of videos or something but not in normal use as listening music or surfing in the net so it's still strange.
It start warming fast and it fills like a cold spot. Warm middle cold outise. Also if I tap the back of the phone I can hear a sound like a jingle or a spring.
I have changed my device and this one has the same symptoms. I think that this is a fabrication issue. It is happening also for Nexus 4 (made by LG too). http://code.google.com/p/android/issues/detail?id=40334