Related
What might be the possible causes to the T-Mobile G2x randomly shutting off by itself?
POS
Mine crashes every night and needs booted in the morning.
It's the best phone ever and the worst phone ever.
FatalityBoyZahy said:
What might be the possible causes to the T-Mobile G2x randomly shutting off by itself?
Click to expand...
Click to collapse
I think it's caused by loading giant signatures at the bottom of forum posts.
lannister80 said:
I think it's caused by loading giant signatures at the bottom of forum posts.
Click to expand...
Click to collapse
Donate to the op for your troubles.lol
Mine does it randomly. I had it since April 20, and it has shutdown 3 or 4 times. Still don't know the cause of it.
Sent from my LG-P999 using XDA App
Funny no one is stating their OS they are running?
The only time my phone randomly SHUT DOWN was running the leaked Gingerbread rom from LG. Stock was fine as were CM7.
Of all the roms I've tried, I've never had reboot problems or finding the phone off outside of the leaked GB.
This happened to me all the time with the stock FroYo ROM. I think it is caused when the phone runs out of free RAM (due to playing a game or running lots of widgets) I flashed CM7 with the ext4 Trinity maxmem firmware and it fixed all of these types of problems. Also, the stock battery seems to have major issues because when I replaced the battery with a third party one it fixed lots of problems with battery life and also the HDMI instantly drain the battery.
I still believe it could be a combo of questionable batteries and chargers. Purchased two the first week out. Mine started the reboot dance the first night. My wifes phone has had zero issues as has my replacement.
Probable fix
Hello,
So we’ve been working on this issue for quite a while. And have come up with a semi-practical solution. This might interest some of you, who have this issue.
Issue:
Both I and my friend opted out to purchase the new and wonderful LG g2x phone. After receiving the phones we came against a very similar issue. The cellphone unit would shutdown/turnoff during the charge [car or wall]. The shutdown would occur around 95% of battery charge. In addition the phone would get hot. After the shutdown to start the phone would require pulling the battery out of the unit and reconnecting it again, otherwise known as: Perform a battery pull.
Trials:
So after doing some research and funding out that LG is literally doing nothing about this issue, [great testament to their corporate integrity] we decided to take on this issue. At first we also believed that it is, indeed, the battery that gets heated and goes offline after reaching some temperature. After recognizing the poor quality of the battery, I’ve decided to purchase a better quality one online. No surprise really the phone would still lockup at 95% charge.
At this point I took it upon myself to resolve this issue with what resources I have available. I am an MIT student and have a high tech engineering lab available at my disposal, in addition to some free time with a winter break and all. Anyways, I pulled the phone apart and this is what I’ve discovered…
Discovery:
So inside the phone right next to the 4 connecting diodes that connect the battery to the cellphone unit are 2 semis [semiconductor hubs] that are responsible for providing battery charge information to the cellphones cpu [central processing unit] in addition theres also a line running to those semis that probably carries some sort of information [current] that the semis are also responsible for.
The first approach that we took was through the hardware, and killed that additional line and allowed the semis to only be responsible for the battery charge. The results were somewhat positive. Although the phone would freeze and glitch like crazy it would not shutdown with a subsequent necessity of pulling the battery.
We also noticed that it was the two semis that would get hot actually and lockup shutting the phone up and requiring a battery pull. The reason you need to pull the battery is because the iodes would overheat and completely glitch out, also even though the phone was now powered off there still was a current running between the battery and the phone. Only the battery pull would allow the diodes to drop the charge and reset to the position for the phone to be functional again and able to power up.
Solution:
So the idea was to find a software solution, which would free up this one line running into semis and allow them only to carry the responsibility for reporting the battery charge to the cpu. Believe it or not the first thing that came to my mind was the solution.
The app called Advance Task Killer (ATK) [available free on the market] proved to be useful. I do understand that this program is not very effective and only kills running progs in the foreground. However, that single line is also not very important to information transfer and becomes useless after you clear the cellphone’s foreground information transfer.
Basically when you run atk the line becomes inactive and you can charge the phone without any lockups. I’ve been doing that for about 10 days now. Discharging the battery to about 17% and charging it all the way up again and the phone has not yet turned off once and required a battery pull, nor has it been getting hot.
The idea is to clear the line prior to putting the phone on charge [car or wall]. So what you do is run atk few times [twice at least] then plug the phone in. this worked for both me and my boi here @ mit. After a week plus of testing we decided to release this onto the public.
We both a running stock lg g2x gingerbreads and have not tested it on any other roms, however, I suspect that it will have a similar effect on more leaner and cleaner roms like CS7.
Hope this helps those who are still struggling with this issue.
P.S.
In addition I would like to add that we did pull the battery apart in the lab and found that the stock battery was complete SHAYT! Some of the cells were cracked and overall it was just poorly manufactures. Cracked cells inside the power unit diminish its capacity to carry charge by a factor razed to n^power. Also may cause the battery to heat up during the final stages of its charge process [around 95%] due to the fact that to go the last 5% it will require higher resistance also in n^power. I suspect that in this great economy LG is cutting corners whatever place it can so there’s prolly very minimal quality control in power unit production. To those who think that they lose charge too quickly, that the battery gets too hot during charges, and possibly causing the phone to lock up: If you are using the stock battery, you may want to consider replacing it.
P.P.S.
Overall it is a hardware issue, in our opinion, that could be fixed with the use of the software, by rendering that extra line inactive for example. However, I would like to NOT compliment LG as a corporation and organization in general on their moral standing and responsibility that they carry to their customer base by doing completely nothing about this issue!
Thank You LG, I am no longer your customer.
“Making the world a better place, one action at a time.”
Mine used to only shut down during phone calls. This only happened about 4 or 5 times and it got very annoying but eventually it just stopped and hasn't happened since.
Sent from my LG-P999 using xda premium
e4e5nf3nc6 said:
Mine used to only shut down during phone calls. This only happened about 4 or 5 times and it got very annoying but eventually it just stopped and hasn't happened since.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I had my phone reboot during calls a few times a day after I got it. I OC'd my phone with Setcpu and was running Juicedefender. Ever since I clocked it back down and uninstalled those two apps (mind you I just got rid of them without doing any research if it was a problem really either of them cause). I'm going to get replacement batteries soon in hopes to help but it's good know a technique finally so my phone wont crap out during the night.
Seperate story kinda, I once put my phone on the charger. I placed the phone on my bed but with proper air circulation. It sat there for an hour or so. I walked over to use it and the thing was extremely hot. I pulled the battery and checked the phone. The battery was hotter then the phone so you could tell it was the thing over heating and not the phone. I put the battery back in the phone and booted and went straight to spare part's battery stats. It said the battery was overheating. So I pulled the battery and held it and the phone in front of a fan. 5 minutes later it was running cooler then any other time I looked at the battery readings (about 28c) and my phone charged fine for the rest of the night. Also yes when it did over heat the phone wouldn't turn on the first time I got to it.
Hey guys,
This last week has been absolutely brutal in the northeast us. We've had high 90s pretty much everyday. [Especially in the car] my g2x has been suffering from "random reboots" running fauxs 1.2.8 and kernel 0.3.2. It was a new phenomenon, I thought it was the DS kernel I had rather than CM7, but all that did was affect battery life.
I finally was using my device when it decided to "turn off" and the screen just kept turning off ( less and less time being on, fractions of seconds.) Then it just stays off and the battery temp reads 100+° at turn offs.
It requires a battery pull to turn back on ( and I guess turn off) but the heat doesn't seem to come from the battery, but behind the camera, im thinking processor.
Could it be from the OC/UV kernel. I had on? It's on standard now.
Sent from my LG-P999 using XDA App
OC'ing can easily overheat/fry the processor (hence why there's always large warnings around it), especially if the kernel hits a race condition or similar.
The phones are passively cooled. and the radios in the phone heat up the phone when used heavily. I have not had anyphone that didnt get extrememly hot while it is using the radio when its in above 80 degrees ambient temperature and overclocking would just add to this. luckily most have a feature ot turn off the phone at a certain temp to protect the hardware. But I dont think this is a specific g2x problme my old droid does the same thing.
I took mine to a pool in Vegas. It was probably about 90 degrees. I had it under my lounge chair shaded listening to music. It had a heat stroke after about an hour.
I understand why/how overheating can be caused by oc but honestly if its not running at stock (or benchmarking) I have it set to 800mhz by default- its still fast as hell. It hasn't overheated in the last few days, but the problem was that even if I don't use it, it'll overheat.
I use juice defender to keep my radio off when the screens off, so I can't even lay blame to that.
I haven't really dove into undervolting, but in theory wouldn't lower voltage equate to less residual heating?
Sent from my LG-P999 using XDA App
mine does this running stock. Mostly when I have the charger plugged in and am still doing something. It will be taking a charge but the batery level will still slowly fall, once it gets below a certain point it gets really hot behind the camera and the screen starts locking and unlocking. faster and faster until you finally have to pull the battery and let it cool down a while.
YES!!!! I have 2 G2x that do this, and a guy at work has one. All stock phones, and can be doing NOTHING - gets hot near the camera lens, and LOCKS!!!! Have to pull the battery. I pull the battery for 1 second, re-install, and G2x works fine. I know of 3 G2x, and all do this. I can't believe I don't see more of this on this forum. T-Mobile has a "discussion number" on this: 265747. LG claims ignorance. I'd love to know how to "fix" this. I'd also like to know if GB fixes this.
The occasional re-boots are live-able - this lock up is NOT.
namklak said:
YES!!!! I have 2 G2x that do this, and a guy at work has one. All stock phones, and can be doing NOTHING - gets hot near the camera lens, and LOCKS!!!! Have to pull the battery. I pull the battery for 1 second, re-install, and G2x works fine. I know of 3 G2x, and all do this. I can't believe I don't see more of this on this forum. T-Mobile has a "discussion number" on this: 265747. LG claims ignorance. I'd love to know how to "fix" this. I'd also like to know if GB fixes this.
The occasional re-boots are live-able - this lock up is NOT.
Click to expand...
Click to collapse
I can verify this is an issue with my phone as well! It was happening all the damn time in both stock Froyo and EaglesBlood Froyo, but as soon as I went to CyanogenMod 7 RC1, I haven't had it happen once.
And to those of you who haven't had this happen, it's like the Sleep of Death + your phone gets REALLY hot by the camera lens and it keeps draining the battery and putting out TONS of heat until you do a battery pull. It brought my battery from 100% to 25% in like 30 minutes of doing this.
But CM7 seemed to solve the issue. No more SOD+heat!
This problem has been driving me absolutely insane. My wife and I both got g2x's at the dame time (new from tmobile), and hers rarely does this, while mine does it continually. I was wondering if it was related to the case we have - but we both have the same case - the speck one sold at tmobile.
My wife and I both have the little rubber buggy baby bumper condom case thing that does cover the back - that would reduce heat dissipation. I often carry mine in a belt case that came with the phone from CostCo - she almost never uses that case.
This happens sometimes... For example, I usually leave my phone on airplane mode during the night while I'm sleeping, but when I wake up sometimes I seem to have one more percent than I had before going to bed.
And it also happened just now, I checked my battery about an hour ago which was at 60%, and when I got home it was at 61%.
What gives?
Are you living under a huge power line?
Just joking... but really, low temperatures can decrease battery voltage.
Do you live in an area that's cold outside right now?
I guess Android is starting developing its own consciousness, and found a way to violate thermodynamics laws. You should destroy it before we get dominated by machines!!!!
Lol, I was expecting serious answers haha.
But anyways, it's cold outside now, but this also happened when it was hot too. So it has nothing to do with that...
I think I've heard of there being a file on the phone that takes care of the battery stats or something like that... Maybe it needs to be reset? I'm on an unrooted Nexus S so I'll likely have to factory reset for that...
it is not a big problem, if you want,you can do a calibration to fix it. There's software in market
i've seen this happen after my phone crashes, usually from tinkering with voltages. but the change is usually rather significant, ~10-20%. very odd
It must be that Android's latest update installed a bunch of neutrinos into the core time clock and because of neutrino's faster than light speed your phone itself is experiencing spacetime shift and going back in time.
So I did a fairly generic search trying to find out tips on storing batteries since I plan to get backup batteries for my phone, one of which will remain in storage for a while and I read that apparently under best charging practices it's actually considered to be high voltage for it to go to 4.1V and shouldn't go above 4.2V. Well, according to Android Assistant my battery charges up to around 4.33 to 4.34 or so (there seems to be some variance within that range.) Even allowing for the possibility that it's not 100% accurate this sounds like it's absolute torture on the battery. At the same time, it's also best to keep the battery charges short and small rather than letting it just sit and largely discharge frequently (and if I could help it I'd rather keep it plugged in and run as little from the battery as possible when I'm actually at home.)
EDIT: Sorry, I forgot. I was meaning to link to the original article and somehow didn't paste the link: http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
So what I'm wondering is if there might be some way to trick it into deciding that a full battery charge is, say, 4.1V or even 4V? (From what I can tell by that article, 4V sounds like it would be pretty close to ideal since it's still more than 90% of the current full charge so still has a lot of capacity, but should considerably increase the battery's total lifetime. Even so, 4.1V would be considered "nominal voltage" and still a much better overall lifetime compared to the 4.33-4.34V range I'm seeing now. Heck, even 4.2V should be safer than that...) The phone is rooted and I plan to keep it that way -- I'm not in any rush to update to Jelly Bean or anything so won't be doing any updates or anything until I'm absolutely sure I can root once I do -- so even if it's something that requires root access it would be fine. I see at least one tool to force the system to recalibrate by basically just deleting the current calibration info, but that only really ultimately affects the level indicator and any software that relies on it, not the actual charging. I'm not sure if ANYTHING can really change the actual charging mechanism since it sounds like that is done more via hardware than software, but smartphones are a heck of a lot smarter than, say, a stand-alone battery charger, so perhaps it is still possible?
*Bump* I guess. Hate to do it, but I'm really curious. It may be built into the battery, not the firmware or whatever now that I really think of it, but I'd like to at least ask and see rather than never knowing. I'm kind of concerned because I think one of my batteries is already getting worn out. I've gone out of my way to increase battery life -- even using apps like Greenify (kind of a smarter way of killing apps, it doesn't actually keep just killing stuff, but actually disables their autostarts along the way and it's smart enough to not kill whatever is currently active and to give them a few minutes before it does kill) and I've used another more advanced app to disable a lot of the autostarts of a lot of other apps (including a couple of system apps.) I also have SetCPU doing stuff like lowering the CPU nearly to the minimum (it struggles to even turn on the screen if it's at the minimum, so I believe I put the maximum on 512 or whatever) with the powersave and even the noop scheduler (it doesn't get any more power saving than that!) Data is off, though I have to keep wifi on (but again, minimal apps running so just about the only thing ever using WiFi at all is e-mail syncing since I need to not miss certain things) and GPS is off. I've tried to keep it from ever running terribly hot with only a minimal plastic (not silicone and I've eliminated the horrible Otterbox case I used to have that had so much insulation that the only heat escaping had to go out the glass which is already pretty high on the insulation scale) grip and I don't really do an excess amount of gaming (well, I'll admit to a ScummVM session or two, but for the most part I'd rather use my 3DS or something else) so while I won't claim the battery has never been hot, I think it has generally stayed at least very reasonable and far better than most, so I don't think temperature is responsible for the battery life decreasing. On the other hand, if I look at that information it kind of implies to me that the extreme overcharging probably reduces the lifetime of batteries that should make it to 1000+ charges down to around 250 or something ridiculous like that (well, I'm not doing the math on it, but you get the idea.)
Is there anything else to be done, or is it pretty much just all in the battery itself? I'm really kind of planning on making this phone last for years if I can (well, I am kind of wondering if I should consider something just a little bit smaller -- maybe 4.3" instead -- but at the same time I need something that can do some of the stuff this one can like the actually surprisingly good sound quality despite being the US model without the Wolfsen DAC, so I'm not really planning on getting rid of this phone any time soon. With its excellent hardware for the time and wonderful support from CyanogenMod, it should last for basically every bit as long as I want it to within reason.)
Many complain that the Pixel 6a gets hot or overheats. I have also seen videos were people claim it's only in the beginning while the phone "learns" your usage habits and how to optimize itself accordingly. But later on it doesn't need to run all of its processes like in the beginning once it figured you out, so to speak. (The exception being when you record a 1080 video at 60 frames, which even later on can get problematic.)
Can Pixel 6a users chime in here and recount their experiences? Does the overheating last past the first few weeks after purchasing it?
Bonus question: are the signal issues some complain of widespread, or not?
-----
I really want to get this phone, but I hesitate due to these two issues.
I didn't have overheating issues since I bought the phone 3 months ago.
dudaka said:
I didn't have overheating issues since I bought the phone 3 months ago.
Click to expand...
Click to collapse
Even from day one?
xda-eh said:
Even from day one?
Click to expand...
Click to collapse
Yup
I have my 6a 2 weeks and I don't have any issues with overheating or bad signal.
Thanks.
Anyone else?
Overheating in the sense that it shuts down with a warning? No, never. But the phone does get annoyingly hot, especially when charging even if I'm not using it at all. That's the phone plus the weather in my country isn't helping. Phone regularly touches 40° according to battery guru, when charging can go up to 43°.
On WiFi things are very normal. Mobile data however is a very different animal. It you have poor signal especially expect this to get pretty hot. Like stated above though, not shut down hot just hotter than what I consider normal. 35-40c battery temps on stock with those conditions isn't unusual.
Initial setup for sure gets toasty as well.
For whatever reason (latest updates maybe?), I've noticed recently that not only does my 6a not overheat, but the battery consumption has dropped significantly. At my admittedly low level of active usage I can easily go two days and still be over 50%. I might try for three full days soon.
I dont have any problems with overhiting , i have phone about 30 days. Playing games recording at 4k no heat problems at all.
Damn bruh...another 'overheating' thread?
Yes. The 6a may get fairly warm in some specific use cases, but it doesn't actually overheat as in start throwin' out warning messages and start throttling or worse, crash/reboot that I've ever witnessed. Actually mine seems to run slightly 'less warm' since A13's beta 2 & 3...just before I flashed a custom kernel. A few things to consider besides differing usage scenarios. If you're using a case, it may not only hinder cooling a little but probably 'feels' less warm due to the insulating properties as well. I try to go with a minimalistic case...it may not provide a lotta cushion if dropped but I'm hoping the improved grip offsets that point. And ofc the thinner the skin to less it retains heat. I went with a grippy Spigen Liquid Air or something like that.
Above all, I keep in mind that the 6a has the same processor as the [email protected] P6 PRO and that also helps me to forgive n forget that it can get toasty at times...plus thst resulting Tensor 'grin-factor' tho...
...just my 2 centz ofc
If you're using mobile data or using the phone as a hotspot thing gets very warm.
Normally, I've only experienced the phone getting very warm when I'm playing a game and charging the phone at the same time. However, on a recent trip to a foreign country, my phone (and its camera) stopped working because it was hot outdoors (around 80°F) and I was outside for 30min or longer. My friends' iphones didn't overheat though.
I haven't experienced any signal problems.
Mine never overheats. Its just warm enough to be a hand warmer, but not enough to damage anything
neo_lithic3K said:
Normally, I've only experienced the phone getting very warm when I'm playing a game and charging the phone at the same time. However, on a recent trip to a foreign country, my phone (and its camera) stopped working because it was hot outdoors (around 80°F) and I was outside for 30min or longer. My friends' iphones didn't overheat though.
I haven't experienced any signal problems.
Click to expand...
Click to collapse
...and it displayed an overheat popup warning? 'cuz it was 80F outside? I've been out with my 6a dozens of times in 80F+ weather and NEVER had my phone throw an overheat warning much less shutdown or lock up. You might have something wrong with ur phone if a warm day kills ur phone...js
Zaxx32 said:
...and it displayed an overheat popup warning? 'cuz it was 80F outside? I've been out with my 6a dozens of times in 80F+ weather and NEVER had my phone throw an overheat warning much less shutdown or lock up. You might have something wrong with ur phone if a warm day kills ur phone...js
Click to expand...
Click to collapse
No overheat warning. Phone felt very warm, froze up and apps would barely respond or it would keep on rebooting. Tried a few times to power off, wait a minute, and then power on to get that last photo, but didn't work. After I got out of the heat for a short time, phone went back to normal. Felt hotter like 95 degrees, but weather report said 80s.
Nothing wrong with my phone per se. My guess is that my phone was in direct sunlight for 30 min. I myself was dying from the heat. And before that, I was already taking pictures on and off for an hour (in the heat but not direct sunlight). I've used the phone before in hot weather without issue, but this time around, it was continued use and in direct sunlight.
My 6a definitely overheats and shuts down sometimes without warning. This has happened numerous times even when the phone is having light use (chrome or connected to android auto). I would say there are 2 factors. When the outside temperature is hot (35c or hotter - which currently in Australia is a daily occurance) and when the signal is not strong (also a very common occurrance here) - when this happens the phone can overheat and shutdown within minutes even with little use.
From my exp. signal strength seems to be the biggest issue. The pixel seems to literally burn through the power when signal is weak and get hot.
Generally I have had a 50% chance of getting a 'Your phone is hot' warning - other times it just turns off.
savanne said:
My 6a definitely overheats and shuts down sometimes without warning. This has happened numerous times even when the phone is having light use (chrome or connected to android auto). I would say there are 2 factors. When the outside temperature is hot (35c or hotter - which currently in Australia is a daily occurance) and when the signal is not strong (also a very common occurrance here) - when this happens the phone can overheat and shutdown within minutes even with little use.
From my exp. signal strength seems to be the biggest issue. The pixel seems to literally burn through the power when signal is weak and get hot.
Generally I have had a 50% chance of getting a 'Your phone is hot' warning - other times it just turns off.
Click to expand...
Click to collapse
You should RMA the phone. Sounds like a faulty device to me.
Also, just hot ambient temp does nothing to a phone. If it gets direct sunlight, thats unsafe for the device because of how hot it can get (if you measure temp in your car, it gets up to 60-70C+ easily.) If I use my car in hot sun, I aim an AC vent to its back and then the phone is super chill all through the ride.
h8Aramex said:
You should RMA the phone. Sounds like a faulty device to me.
Also, just hot ambient temp does nothing to a phone. If it gets direct sunlight, thats unsafe for the device because of how hot it can get (if you measure temp in your car, it gets up to 60-70C+ easily.) If I use my car in hot sun, I aim an AC vent to its back and then the phone is super chill all through the ride.
Click to expand...
Click to collapse
Yes, I think I will RMA it. - I don't agree re ambient temp. My phone certainly seems to shut down more often when the ambient is hotter. Also, re the car. I had the phone in the glove box which is separately cooled to 21c and even then it would overheat, - I suspect related to poor signal. But yes - will RMA it.
Try safe mode first. You may have an app which is misbehaving. I've never had my 6a overheat, it will sometimes get a bit warm when charging, but that's it.