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.
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.
My tablet has been getting really hot lately. So far I can't tell if it's a specific app running in the background making it hot or if it's from continued use but it has never felt this hot before until recently. Does our tablet have that feature that tells you if it's too hot and turns it off if it's at a dangerous temperature? I read that 85°F is average for a different tablet but I don't know if it's different for different devices and how hot is considered to be a dangerous temperature? I've been thinking if it was getting too hot it would notify me like my phone did before, but now I'm wondering if I shouldn't depend on that.
Sent from my GT-P6210 using Tapatalk 4 Beta
kcerica said:
My tablet has been getting really hot lately. So far I can't tell if it's a specific app running in the background making it hot or if it's from continued use but it has never felt this hot before until recently. Does our tablet have that feature that tells you if it's too hot and turns it off if it's at a dangerous temperature? I read that 85°F is average for a different tablet but I don't know if it's different for different devices and how hot is considered to be a dangerous temperature? I've been thinking if it was getting too hot it would notify me like my phone did before, but now I'm wondering if I shouldn't depend on that.
Sent from my GT-P6210 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's(P6200) been getting hot for me too but only when using intense graphic processing apps like heavy gameloft game's, sometimes extended use of certain apps also does that but the heat will be very low.(as opposed to HC I didn't have any heating issues at all in any situation)
Sent from my GT-I9100 using xda app-developers app
I had a N9. It died catastrophically and I suspect due to overheating. Does the Shield Tablet have a heating problem like the N9 does or does the passive cooling keep it under control? I want to try to avoid this problem with whatever I end up replacing the N9 with.
nimdae said:
I had a N9. It died catastrophically and I suspect due to overheating. Does the Shield Tablet have a heating problem like the N9 does or does the passive cooling keep it under control? I want to try to avoid this problem with whatever I end up replacing the N9 with.
Click to expand...
Click to collapse
I haven't seen that issue yet even when gaming for 2-3 hours on end.
I should note that when I killed my N9 I was running Antutu. I completed one run and it died on the second. I had done a bit of gaming on it without issue, but benchmarks can push the hardware to the limits, including thermal design limits.
Anecdotal evidence suggests the shield is cooled more efficiently than the N9. Though it is possible the Denver cores just generate more heat, too. Noons has reported a heatstroke on the shield so far though.
why isnt the company doing something about the overheating issue? is there any solution for this? Just bought my one plus one and this overheating issue is such a let down.
From what I can see the reason the charger "overheats" is because of the speed in which it charges the phone. A way to fix this is to root the phone and install an app that can slow down the amount of power the phone takes in during charging. Ofcourse this means longer charging times but it will help with the heat issue.
With regards to the phone, unlock the developer options and underclock the phone. Obvious advantage of longer battery life and less heat but with the trade off of performance. I would reccomend only underclocking it a little but as you will get lag because of the restricting of power to the CPU. Changing the cpu governer etc. to save battery will help with heat as they just slow down the ram and CPU.
My appologies if you have done all of these and are still experiencing these issue, i do know where you are coming from but they are trivial issues and depend on how you as the user do use the phone. Have a browse around forums etc. to find tips on slowing things down a little and things will cool down for your phone.
I hope i have helped even a little bit
How do you define overheating on the phone? What temperature?
Transmitted via Bacon
No overheating here. What do you mean? The phone gets hot and turns off?
overheating
baratv said:
why isnt the company doing something about the overheating issue? is there any solution for this? Just bought my one plus one and this overheating issue is such a let down.
Click to expand...
Click to collapse
This phone is not known for overheating any more than any other phone that will heat up when driven to its max for example in heavy 3D gaming. There is a difference between heating up and overheating
First, run stock without any extra installed apps, and NO running apps or network connections or anything and see if it's overheating.
Do not use an aftermarket charger--they could be rated for different amps and overheat or damage themselves or the battery.
Phone brand new?--simple--ask OnePlus to replace it.
Phone used?--probably been abused--get your money back and get another one.
pbergonzi said:
There is a difference between heating up and overheating
Click to expand...
Click to collapse
This. Far too many people mistake a device heating up for a device overheating. All phones heat up, they have no active cooling. If the phone was actually overheating the thermal cutoff would kick in and the phone would shut down.
Transmitted via Bacon
No overheating issue here, you may want to try different - weaker charger like stock Samsung or Sony one with output current ~700mA-1A and see how it performs.
Sent from my Bacon