MIT student proves by A + B that T-Mobile G2x has hardware issues related to overheating / shutdown / battery
http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
Let's share this and be social.
Here are some other references for this same post.
#OccupyLg
LG: http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
XDA-Developers: http://forum.xda-developers.com/showthread.php?t=1433445
T-Mobile: http://support.t-mobile.com/thread/16431
I would assume a hot reboot would work as well if you don't want to install an app killer
Sent from my LG-P999 using xda premium
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
jcbofkc said:
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
Click to expand...
Click to collapse
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
psychoace said:
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
Click to expand...
Click to collapse
If (big if) the overheating observed is due to heat from the battery charging leaching into the phone, wouldn't a quick and easy fix/test be a piece of aluminum foil between the battery and the phone?
Sent from my LG-P999 using Tapatalk
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Prod1702 said:
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Click to expand...
Click to collapse
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
FYI if it does it on all roms then its a hardware issue and software change wont fix it...
Sent from my LG-P999 using xda premium
I also had the dreaded sod at least once every couple of days.
However, after I installed eb kang with faux oc/uv profile with set cpu, I have had no problems since.
I guess its ymmv...
Sent from my LG-P999 using XDA App
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
gggirlgeek said:
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
Click to expand...
Click to collapse
I don't think anyone is saying this problem effects everyone. It's just with all the bad units out there with this problem, this is probably why it's happening. Right now I'm trying to run some profiles in setcpu to see if it improves my phones sleep. It's only been one day so I will see by the end of the week how this fares
Sent from my LG-P999 using xda premium
Cm7, morfic Trinity kernel, go launcher ex oc'ed to 1.4 ghz. Perfect! No issues!
Sent from my LG-P999 using xda premium
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
Posts like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Prod1702 said:
Things like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Click to expand...
Click to collapse
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
mt3g said:
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I think the term overheating is thrown around too loosely here without more of a description. There's the type of overheating that causes our phones to shut off and stay off until the battery is pulled. There is also the type of overheating that occurs when you plug in an HDMI cable, which may or may not cause your device to die.
I'd assume those two types of overheating are the same, as they result in the same thing: dead device that won't turn on without a battery pull. And the phone gets hot as fsck. Hot as in you'd be scared to keep it in your pocket because (1) it'll burn your leg and (2) you are scared the battery will explode.
Those two types are overheating are different from your phone merely heating up upon use. I'm talking about charging the phone while navigating via GPS at full brightness or playing a graphically intense gaming. That magnitude of that heat is normal. And I'm guessing that's what all your devices have experienced.
And as all the devices get thinner, that battery's going to sit closer and closer to your hand, which equals more heat. And as the glass technology gets thinner (gorilla glass 2.0), your face will probably feel the heat to a greater degree as well.
---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
It's true, it's not android, it's LG.
And to all the people thinking that undervolting and underclocking your phone will fix everything, it won't. Android already underclocks the CPU when it's not in use. SetCPU does nothing in this instance. The only instance they'll see a difference is if they have some sort of rogue app that's maintaining a wake lock. You just can't beat terrible design (referring to the MIT guy's findings). Sometimes it'll work, sometimes you just lose.
LG majorly screwed up with this and I hope that their mobile efforts in the future fail for their lack of follow through.
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Just wanted to say that this thread has been really helpful to me. Every time I've flashed a custom kernel, my phone has always, within the first 2 nights of installation, turned off in the middle of the night while on the charger. So I've always been stuck with the stock kernel. But then the suggestion to use SetCPU to lower the speed while the screen is turned off worked for me. So far no SOD and my phone has survived Faux's kernel and charging overnight without a battery pull and without overheating.
Now I can try out custom kernels and find all new ways to destroy my battery by doing things I'm not knowledgable enough to be doing!
lotherius said:
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Click to expand...
Click to collapse
hmm.. I dont doubt you, but I think doing that would not be any different.
BECAUSE, the charger is not constantly charging at 1A rate. If you notice, the phones ramps down the input current after a certain percentage ~90%, and trickles it up to 100. Once at 100, the charging is supposed to be stopped. I've charged mine with my bluetooth 500ma charger, and I didnt see a difference in heat temps; only charging time took longer.
As far as heat, Lion batteries should be able to handle 1C charge (1 x charge capacity) with no problems in heat. That means even at 1.5A charge, it should be OK.
Regarding overclocking, undervolting and overheating. There is a variation of parameters across every silicon wafer; among the 25 or so wafers in a wafer lot; and from wafer lot to wafer lot. This is referred to as the "spread" and parts at the extremes are called "corner parts". Most parts should be in the middle of things, not all. With newer parts and small silicon process geometries, the margins are typically smaller - hopefully improving as the fab gets experience with the new process.
A hardware developer should get corner parts to check their PCBA layout and FW, to see if they have design margin. In the case of DDR (RAM), the voltage, circuit layout and DDR interface timing (from Tegra, in this case) should be checked across some tolerance and with the corner parts. "Fast" parts can draw more current during operation that nominal parts, possible heating up the voltage regulators nearby.
In a good hardware design, everything should work across part variation and the specified operating temperature for the system. When we start playing with the clocking frequency and voltages, there is the risk of FW crashing and HW flipping out. The symptoms can include system shut down (lost), resets, heating, bad effects on other systems (battery, voltage regulator circuits, etc.).
This is why some of us (like me) have little luck Set CPU and others can change it to extreme. What none of us know is how close to the design limits the G2X is - the system and the components like Tegra, the FW control. If due design diligence was not done, the sensitivity to part variation and our hacking is greater than normal.
Related
Not all phones can be overclocked safely. Not all CPUs can handle overclocking. If you've ever overclocked a computer CPU, you'd know that no two CPUs are exactly the same.
Well, my Captivate heats up a lot, quickly. It heats up so much that the screen literally CRACKED. After using Screencast w/ Droid VNC, I've managed to backup with Titanium Backup and I'm ODIN flashing back to stock.
I'm trying to get it fixed by Samsung...
We'll see if I can say it's because of the phone overheating that I can get it covered (I didn't drop it for it to crack like that).
I know I'm warning overclockers, but the funny thing is, I didn't use an overclocked kernel (Cognition 3.04). This happened with stock speed!
CLShortFuse said:
Not all phones can be overclocked safely. Not all CPUs can handle overclocking. If you've ever overclocked a computer CPU, you'd know that no two CPUs are exactly the same.
Well, my Captivate heats up a lot, quickly. It heats up so much that the screen literally CRACKED. After using Screencast w/ Droid VNC, I've managed to backup with Titanium Backup and I'm ODIN flashing back to stock.
I'm trying to get it fixed by Samsung...
We'll see if I can say it's because of the phone overheating that I can get it covered (I didn't drop it for it to crack like that).
I know I'm warning overclockers, but the funny thing is, I didn't use an overclocked kernel (Cognition 3.04). This happened with stock speed!
Click to expand...
Click to collapse
First off wrong forum... Second off their is no way the phone could get hot enough to crack this glass unless it had defective regulation or the glass was damaged.
Gorilla glass is tempered in a special way, it is tougher then pyrex, thermal shock would not crack this glass.
slayp00n said:
First off wrong forum... Second off their is no way the phone could get hot enough to crack this glass unless it had defective regulation or the glass was damaged.
Gorilla glass is tempered in a special way, it is tougher then pyrex, thermal shock would not crack this glass.
Click to expand...
Click to collapse
"No way"?
It's not the gorilla glass. The glass is in fine condition. It's the digitizer/amoled screen under the glass. The heat comes from the CPU.
Plus, I'm not the first one:
http://forum.vodafone.co.uk/t5/Galaxy-S/Overheating-caused-Galaxy-s-screen-to-crack/m-p/643601
CLShortFuse said:
"No way"?
It's not the gorilla glass. The glass is in fine condition. It's the digitizer/amoled screen under the glass. The heat comes from the CPU.
Plus, I'm not the first one:
http://forum.vodafone.co.uk/t5/Galaxy-S/Overheating-caused-Galaxy-s-screen-to-crack/m-p/643601
Click to expand...
Click to collapse
Something is seriously wrong with any phone that could get that hot, My phone never breaks the mid forties, even while charging and tethering.
slayp00n said:
Something is seriously wrong with any phone that could get that hot, My phone never breaks the mid forties, even while charging and tethering.
Click to expand...
Click to collapse
Hottest I ever gotten was 114°F. And im at 1.4. Its gotten worst but that was at 1.6 and I let it freeze so I can drain the battery, but damb was ut hot
Sent from my GT-I9000 using XDA App
As I said, not everyone's phone is the same. Yes, there is something wrong with my phone. That's why I'm sending it in.
If my phone was this bad without overclocking, other people may have not-as-bad phones where overclocking pushes it past its limit.
goob1284 said:
Hottest I ever gotten was 114°F. And im at 1.4. Its gotten worst but that was at 1.6 and I let it freeze so I can drain the battery, but damb was ut hot
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
thats 45C so about the same as mine.
I don't remember what cognition version I was on when it happened, but I was tethering and fell asleep. Woke up when I rolled over onto my phone which was extremely hot. I know my heat safety control is working, shuts down normally about 115 F. But for some reason this time it didn't. I quickly opened it up, popped the battery out and started blowing in it. I couldn't even touch the battery at first it was so hot. So I can testify that sometimes craziness happens and can jack up your phone.
This is a fairly common problem with blackberrys I have heard stories about the phones getting insanely got and just frying the whole phone. My personal bet is on a problem with the cpu temperature regulation or something funny going on with the battery.
Sent from my SAMSUNG-SGH-I897 using XDA App
Besides the unusual problem mentioned above, what other issues overclocking could cause to my captivate? Force closes? Freezes? Charge Deaths? Anything else? Anything REAL bad?
sorry for the newbie question...
ddoubt said:
Besides the unusual problem mentioned above, what other issues overclocking could cause to my captivate? Force closes? Freezes? Charge Deaths? Anything else? Anything REAL bad?
sorry for the newbie question...
Click to expand...
Click to collapse
Cpu failure, true bricks.
Not really a need to oc right now, not worth the risk for me. Just bragging rights imo.
boborone said:
I don't remember what cognition version I was on when it happened, but I was tethering and fell asleep. Woke up when I rolled over onto my phone which was extremely hot. I know my heat safety control is working, shuts down normally about 115 F. But for some reason this time it didn't. I quickly opened it up, popped the battery out and started blowing in it. I couldn't even touch the battery at first it was so hot. So I can testify that sometimes craziness happens and can jack up your phone.
Click to expand...
Click to collapse
Tethering was the culprit here. It seems Samsung's (and many mfr.) engineers didn't anticipate anyone would want to run the 3G and WiFi radios simultaneously as wireless tethering wasn't included in Android at the time. It produces tons of heat and uses battery by the gallon. The old open-source wireless tethering app needed for 2.1 had a battery temp indicator for this reason.
Overclocking is considerably less risky. If anything it will simply cut power to the unit at a threshold temperature before damage is incurred. The real risk of soft-bricking while overclocking comes from if an overaggressive clock setting is permanently saved before a crash, which is easily avoided with reasonable care.
Using an overclocking kernel (Suckerpunch ftw!) that also allows for undervolting helps diminish excess heat somewhat. I've run Stability Test and Neocore stress-tests for an hour each at 1.4GHz undervolted, reaching 45 degrees C with no issues. My typical use patterns seldom put that much load on the phone though, so I'm not worried.
slayp00n said:
thats 45C so about the same as mine.
Click to expand...
Click to collapse
i remember mine going upto 48 C.
diablo009 said:
i remember mine going upto 48 C.
Click to expand...
Click to collapse
That's why we like to overclock our phones here in Winnipeg- helps keep us warm at night
You probably got drunk and dropped your phone
Sent from my SAMSUNG-SGH-I897 using XDA App
I thought you bailed on the captivate cl?
Sent from my SGH-T959 using XDA App
Wow that's serious; mine never really gets that hot though, even when I'm charging and using a lot of applications at the same time. It gets to around 44C max; ruccintg 1.2ghz.
But yea I think something might have been wrong with the phone; of course undervolting helps as well and Im' sure that's attributing to my phone staying cool 80 percent of the time.
I think it's more to so with the radios. My phone isn't very overclockable and it freezes long before the chip puts off heat. My phone gets hot running navigation and charging at the same time. it also has gotten hot with roms that suffer from battery drain. I doubt that the battery drain is ever cpu related.
Sent from my SGH-I897 using Tapatalk
The phone would have froze up and crashed before hot enough to crack screen.
:
clemmie said:
That's why we like to overclock our phones here in Winnipeg- helps keep us warm at night
Click to expand...
Click to collapse
LOL......probably need all the heat you can get this winter my Canadian friend....stay warm!
This is my first Android phone (2nd device overall), I love it, it was my free upgrade option from AT&T, on number 2, the first, I completely bricked trying to upgrade to GB stock..... After I got the taste of flashing ROM's, thanks to TRusselo and his ninja skill, I find myself oriented towards the leaner ones because of memory issues, I run V6 Supercharger , SlimICS :victory:, with JRummy's ROM Toolbox Pro :good: (gotta support the kicka$$ apps), TB, blah blah blah.
My major complaint is that my Cap runs hot, I have OS Monitor on it because I got tired of not knowing the threshold. It bothers me that my phone gets over 110 degrees Fahrenheit , I've even had a brief history of random reboots I attribute to heat when I ran the ICSSGS 4.0.3 ROM (Awesome stuff, but once I bit into Slim, it was over). Is there a way to manage the heat or get a case for the phone that helps to manage the temperature? Or am I S.O.L unless I keep a frozen gel pack nearby?
BTW, first post, I surf the posts often and since I didn't see any questions about overheating for this particular Samsung model thought I'd give this a shot
My gets hot to I think it has to do with the kernel
Sent from my SGH-I897 using xda app-developers app
Mine runs really hot too, mine gf has a cappy and they run the same everything most of the time, but mine is the only one that gets stupid hot. Would love it to be fixed but I think its probably a manufacturing issue. Problem is it wears on the battery. 10-20 of use and you will burn your ear if you want to talk on the phone . The metal back certainly doesn't help either.
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
takeoutttt said:
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
Click to expand...
Click to collapse
I have the max set at 1Ghz, min 600Mhz, Performance, SIO, I'm sure the fact that the temperature outside being over 100 F doesn't help at al. I have overclocked it before and it started smoldering, not literally, just felt like it.
I've literally taken damp cloth's and set them underneath the phone on occasion to see if that will help, it definitely does, so does setting the gel ice pack under it, so I have found ways around it. I would probably only trade this phone for one of the S3's, but this phone has definitely earned the top place among my favorite devices all time. It's just as tough as a Blackberry, and easier to use than an iPhone.
That's why LOL, 600MHz minimum and 1000MHz max, with performance gov, that keeps it at max clock all the time XD take that off OMG...
b-eock said:
That's why LOL, 600MHz minimum and 1000MHz max, with performance gov, that keeps it at max clock all the time XD take that off OMG...
Click to expand...
Click to collapse
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
takeoutttt said:
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
Click to expand...
Click to collapse
I have never knowingly oc my phone, it would get hot on GB even before I rooted and went to cm. 10-20 mins of web browsing brings my temps up to about 41 C (106 f) I am pretty new to this, where to I check my clock settings?
I'm running helly bean nightly s
I have switched batteries with my gf cappy so I'm pretty sure its not a battery issue
Maybe a bad/defective battery is the cause of the problem since there is no overclockin...???
Sent from my SAMSUNG-SGH-I777 using xda premium
master2828 said:
I have never knowingly oc my phone, it would get hot on GB even before I rooted and went to cm. 10-20 mins of web browsing brings my temps up to about 41 C (106 f) I am pretty new to this, where to I check my clock settings?
I'm running helly bean nightly s
I have switched batteries with my gf cappy so I'm pretty sure its not a battery issue
Click to expand...
Click to collapse
With a metal back of cappy, it will easily heat up because it conducts heat in the metal. Based on my experience it is cause by the user usage depending on how high is the voltage/clock require of each app used to maintain it's smoothness and reached it's maximum clock. You can see your usage at Settings>Battery.
You can use CPU Spy or Voltage Control to see your OC and adjust it. You can check also in Settings> Performance >Processor.
---------- Post added at 02:36 AM ---------- Previous post was at 02:28 AM ----------
brttwilliams said:
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
Click to expand...
Click to collapse
Yeah, you'll learn in time, just try to search and read throughout the forums. I suggest that you lower your min to 100/200 and max to 1000/1200,
use smartassv2 and sio governor. This settings saves me some battery and to extent that still smooth, slick and good ui/gaming/app performance.
If you're on DEVIL KERNEL, go to recovery>devil>governor profile> tick SMOOTH.
brttwilliams said:
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
Click to expand...
Click to collapse
Wasn't doggin' you dude, Just letting you know that could be the cause of your problem. Awhile ago I might have flamed you, I have matured and get that not everyone reads (not this situation), and I have to get used to that. People make mistakes, I know I do even if I wanna act like I don't. I am just helping around here now since I have gotten as much knowledge as the some of the users that joined XDA and other hacking forums in the beginning because I was always searching to find out ways to do it on my own, asking for help with stuff that no one talked about. So I am glad that I was able to help you in a way, sorta.
b-eock said:
Wasn't doggin' you dude, Just letting you know that could be the cause of your problem. Awhile ago I might have flamed you, I have matured and get that not everyone reads (not this situation), and I have to get used to that. People make mistakes, I know I do even if I wanna act like I don't. I am just helping around here now since I have gotten as much knowledge as the some of the users that joined XDA and other hacking forums in the beginning because I was always searching to find out ways to do it on my own, asking for help with stuff that no one talked about. So I am glad that I was able to help you in a way, sorta.
Click to expand...
Click to collapse
Thank you both, b and takeout.... I know neither of you were doggin me, b-eock. I've been one of the behind the scenes types but I've seen a few of your posts, I know you know what you're talking about, I definitely appreciate the guidance. Truth be told, I know I'm still a nub here, but I know my way well enough, after you break something a few times, its only natural to pick up a few tricks along the way.
Yeah you'll learn something here just have the patience, experiment, test things out yourself to conclude and rather soon it'll be your hobby reading
And also help others out too.
Sent from my SGH-I897 using xda premium
my gets hot sometimes too. im on helly bean latest 08/08/12 version, also battery gets sucked down quick, barely get 8 hrs and i do virtually nothing. ics cm9 was great on battery.
VashTS said:
my gets hot sometimes too. im on helly bean latest 08/08/12 version, also battery gets sucked down quick, barely get 8 hrs and i do virtually nothing. ics cm9 was great on battery.
Click to expand...
Click to collapse
I know my battery is going quick on the SlimBean 2.0 ROM, but the heat issue still happens, I have noticed with my OS monitoring tool that it gets hotter if you have programs running constantly in background using up high CPU %. I was able to isolate a few of the programs as things I could remove, overall it does still run hot, but it's not as bad.
I use the free version of the OS Monitor on Play Store, you can set it to run under root and to autostart when the device is turned on.
Picked up an 1800 mah battery and my batty life is great! Going to bed with 40ish percent left
Haha, well let me know where you snagged that from
Sent from my SGH-I897 using xda premium
try Smartassv2 gov and change your min from 600 to 100, then note the temps, or run a log of them.
typically my phone runs about 35° C (95° F) and that is with an otterbox commuter case on the phone. When the gps is on in the car, I use a vent mount to keep it at 40° or less, and never have to take the case off.
I read that higher temps, example 45°, really shorten battery life, and you wiil only get 200 charge cycles instead of 500 from the battery.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
brttwilliams said:
Haha, well let me know where you snagged that from
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Amazon, was a great purchase, got an oem battery, there is a huge thread in the accessories section about the 1800 mah epic 4G battery that fits in the cappy
Anyone else having their phone over heat ?
Tomorrow will be my 3rd phone beacuse of overheating and i have one more replacement before i have to switch to a different phone.
What do you consider overheating and how are you measuring its temperature?
- ooofest
CovXX said:
Anyone else having their phone over heat ?
Tomorrow will be my 3rd phone beacuse of overheating and i have one more replacement before i have to switch to a different phone.
Click to expand...
Click to collapse
NOT a known issue. The S III might get warm under a heavy load or charging a very low battery, but overheating? I'd look at the mods you've done to the phone. The ROM you flashed, the apps you're running... this sounds like a user error.
Roms?
I have cyanogenmod 10 nightly with jellybean 4.1.1 and I've been getting temperatures around 95-101 fahrenheit under pretty heavy use. From what I've found out, it seems normal.
If your in the 140 degree area, start investigating, if your 150+ start worrying. Other than that, don't worry about it.
Sent from my SCH-I535 using xda premium
No over heating what so ever. On my s3. But I have seen one s3 b4. I from Sprint though. It was over heating from just talking on the phone.
U got any temp. Measurements?
Sent from Land Line using pay phone
Do you know that these phones have CPU's that given certain stresses, will heat up quite a bit? That's why they are installed on metal frames and with thermal paste, so the phone can dissipate heat..
These aren't your ordinary dumb phones, these are portable computing devices too..
Sent from my Commodore 64..
READY.
load"*", 8,1
My original S3 was getting a bit too hot to hold with a 2 bar 4G connection, surfing the web. Exchanged the phone using the 14 day return policy at the local verizon, and my new phone has no issues.
i mean like 120 + With little use. Im also using reborn battery widget to get the cpus temp. And my pc doesn't even get past 101 and that has 6 cores.
CovXX said:
i mean like 120 + With little use. Im also using reborn battery widget to get the cpus temp. And my pc doesn't even get past 101 and that has 6 cores.
Click to expand...
Click to collapse
You realize that your PC likely has rather decent ventilation and actively controlled fans, yes?
120 F isn't really a cause for concern, IMHO. Above 140F consistently might be, though - could be the battery, actually.
- ooofest
No over heating here
I'm currently on CM10 nightly 9/18. No over heating here. Ever. I've had the phone since it was put on shelf.
Hey guys,
I am calibrating my battery atm and as you may know you have to discharge your device fully to calibrate the battery properly. To speed up the process I decided to install a stresstest app to my phone and guess what: the phone gets insanely hot, I can't even hold it in my hand longer then 5-10 seconds. Kernel tuner displays me temperatures between 78 and 82°C.
But this overheating problem not only happens with the stresstest. When I start watching videos on youtube or start using my phone for maps it gets hot too (about 60-70°C). It starts to bug me.
What do you guys think I should do to fix this? I already thought about applying some thermal compound between the CPU and the metal shield around it. But I'm not quite sure if it's a good idea. I already have a new phone but I still need two phones because I have to travel between Germany and Switzerland all the time. And this issue starts to make my Sensation unusable.
Send from my flying Note 2
I would suggest an anker battery. It has a greater capacity and it keeps the battery very cool.
Sent from my Ouya
did you try different kernels?
AndroidSupporter318 said:
I would suggest an anker battery. It has a greater capacity and it keeps the battery very cool.
Sent from my Ouya
Click to expand...
Click to collapse
Already using it and I'm talking about the CPU temperatures and not the battery's temperature.
And sure I did try different kernels. Even at stock kernel setting this thing gets hot as f***!
Send from my hovering Note 2
So I just decided to disassemble my Sensation and put some thermal compound on the processor chip. Now I'm not getting over 70°C at full load, 1,56GHz. Pretty good outcome. And under normal use it doesn't heat up over 45°C.
I really have to recommend you this method!
Just wanna ask around to check if I'm the only one who feels my phone is a tad bit too hot?
Usually when not charging , the batt temps are around 34-38°C, with the CPU in the range of 38-45°C
When charging the batt goes up to 38°C - 44.7°C or even overheating in the 45-50°C range( ok this would be my fault in using heavier apps)
And the CPU would stay in the range of 40°C - 55°C even without use sometimes
Those temperatures aren't out of the ordinary for this device, that's pretty normal actually. I've had my battery temperature go between 50-55°C fairly regularly, and even as high as 66°C without the phone shutting down (I did cool it down very quickly upon seeing how hot it was though).
Sent from my Evita
timmaaa said:
Those temperatures aren't out of the ordinary for this device, that's pretty normal actually. I've had my battery temperature go between 50-55°C fairly regularly, and even as high as 66°C without the phone shutting down (I did cool it down very quickly upon seeing how hot it was though).
Sent from my Evita
Click to expand...
Click to collapse
Thanks timmaaa, for a moment I thought I was the only one.
I use Battery Mix to record my temperature vs. Battery % over time (use the JB feature to disable its persistent notification): https://play.google.com/store/apps/details?id=jp.smapho.battery_mix&hl=en
One thing I've noticed is that when it hits 40C+, the space below the camera becomes extraordinarily hot! This happens at least once during a work day, especially happens when I don't touch the device.
When this happens, the drain rate just plummets (when I refer to the battery level slope vs. the phone temperature). However, a reboot fixes the heat (and as a result, the drain rate) over a lengthy amount of time.
I've heard of this, but haven't gotten around to trying it successfully:
http://forums.androidcentral.com/ht...g-red-while-charging-rapid-battery-drain.html
That shouldn't happen while you're not using the phone. Have you used an app like BetterBatteryStats to identify what's draining your battery?
Sent from my Evita
well this was previously answered by timmaa i had a similar concern cause none of my earlier phone actually felt that warm...
but when i got a green signal that these are normal temperatures, i tried gaming for almost an hour turns out the phone was hot indeed the battery was around 50+ but still the phone dint shut down itself or showed any inconsistency in its functions!
moral of the story.. it happens with everyone.. my friend has a endeavor it also suffers from heating... its so normal that if u search it in google that "why does ht one x get..... "it automatically completes it in with " get hot"(also for the new One).
if you want to cool it down get SET CPU and create a profile in which select battery temperature/cpu temperature at a certain temperature you don't want your phone to exceed and then set the cpu to a lower speed typically till 1026 or 1134...
but again if u feel its necessary cause doing so will obliviously slow down the device.:angel:
Sonone said:
moral of the story.. it happens with everyone.. my friend has a endeavor it also suffers from heating... its so normal
Click to expand...
Click to collapse
Of course its normal. All computers generate heat as power is discharged. Manufacturers are also packing more and more computing power into these small devices, and in general that means more heat (although there are other variables). And every smartphone is designed to deal with the heat differently, so those might be some reasons why your previous phones did not feel as warm.
redpoint73 said:
Of course its normal. All computers generate heat as power is discharged. Manufacturers are also packing more and more computing power into these small devices, and in general that means more heat (although there are other variables). And every smartphone is designed to deal with the heat differently, so those might be some reasons why your previous phones did not feel as warm.
Click to expand...
Click to collapse
true that!!
even i was actually worried before hearing about it being normal from u and timma as well!
its probably htc one x is build that way.
BTW sorry a little off topic since this issue has already been resolved has anyone heard a little rattling sound near the camera region only when the phone is sharked up and down (from screen to back)
this also is a build issue!
Sonone said:
BTW sorry a little off topic since this issue has already been resolved has anyone heard a little rattling sound near the camera region only when the phone is sharked up and down (from screen to back)
this also is a build issue!
Click to expand...
Click to collapse
Totally normal. Just a moving part in the camera module. Likely related to autofocus as you can sometimes hear a sound when focusing the image.
Sent from my HTC One XL using xda app-developers app