• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help mysterious overheating phone - detailed case study

electricpete

Android Expert
Historical phone performance:
Battery usage (slide 1) – phone uses up 21% in 9 hrs incl 1hr screen-on time and 23 minutes talk-time.
Charging (slide 2) - phone reaches peak battery temperature 105F as voltage increases past 70%, then battery temperature lowers. Max charging current 1500 – 2000 millamps, decreases back to zero causing the temperature to falls. Max voltage 3,450 millivolts.
Phone is rooted and generally operates great with very few problems.


The overheating event (slide 3)
9:50pm – placed phone on charger, using phone screen
10:30pm – stopped using phone, left phone on charger (normal routine)
11:20pm – batter reaches peak temperature of 110F as voltage increases past 70% and then battery temperature starts decreasing. Everythign seems normal at this point.
1:45am – battery temperature starts increasing again and increases to peak of 145F battery temp at 2AM. Bounces around in the 140-145F range for the next 3 hours

NOTE – Even though at first glance it seems like a battery/charging problem, the current and voltage behave very similar to the previous normal charge. This seems to rule out battery/charging problem (?)

4:40AM – alarm goes off and I awake and find hot phone and unplug it from charger immediately. Took screenshot (slide 7) showing battery temp 135F and cpu temp 174F. (by the way in other screenshots, cpu temp is on the far right of my notification bar, battery level is on far left of notification bar, and battery temp is 2nd from left on notification bar... the battery temp showing on the notification bar in this particular screenshot is not updated yet because I just turned the phone screen on).

From this point on battery temperature drops significantly (in response to unplugging presumably). Note that GSAM battery monitor battery stats are wiped by unplugging charger, can’t retrieve what they were before.

04:52 – took GSAM battery stats approx. 12 minutes after unplugged. (slide 4) - Battery is down to 95% already and 56% used by apps (even though I have had screen on continuously). The two apps sucking up all the juice are Lookout and Mapquest. Lookout has been on for 13 minutes which is the entire time since the stats were reset when the phone was unplugged. Mapquest only shows as being on 10 minutes at this point. I checked GPS at this point and it was definitely enabled (I normally leave it enabled without any problem). I am not positive whether I disabled GPS at this point or not. I didn’t stop the apps… curious to see how they would behave. Turned off phone screen and left it alone approx. 05:05 until..

05:40 – took GSAM battery stats approx. 1 hour after unplugged. (slide 5) Battery is down to 79% (huge drain… I normally get 9hours plus before I get to 79%). Biggest users are again Lookout and Mapquest. Battery temp is 95F (in an ambient temperature around 70F) which is high considering the phone was not being used and not being charged.

05:45 - Uninstall lookout. I may have turned GPS off at this time (if I hadn't already done it at 04:52... not sure). Reboot. After reboot I did note GPS was disabled and Mapquest was not running.

Phone has operated normally since (normal battery drain, normal temperatures). Charged overnight and everything was normal, just like slide 2.

Hypothesis – Rogue apps Lookout and Mapquest? But they didn't overheat much after battery was removed from charger (even though they continued to use abnormal battery). Maybe it only overheats with the combination of both the rogue apps plus the charging?
Also, would seem too coincidentl to have two different rogue apps show up at the exact same time. Maybe at least one of the rogue apps went rogue as a result of the high temperature.?

What do you think?
 

Attachments

I didn't read though all that, but I had my phone periodically start overheating a few weeks ago. I first noted it after installing an update to Google Maps and after about two weeks I uninstalled the updates to Maps. Haven't had a problem since.
 
Another weird thing is that I have two battery temperature alarms set up (one in Tasker and one in GSAM) and based on the notification panel results I don't think they actually alarmed until 4:40 when the alarm clock went off on my phone. I also confirmed in my Tasker run log the Tasker battery alarm did not occur until 04:40. Perhaps the monitoring is curtailed when phone screen is off and phone is asleep. At any rate I wouldn't have heard the alarms even if they did generate a notification because I put my phone into silent mode while I sleep.

Based on your Maps comment, and also upon my concerns about recurrence of this problem with alarms not effective, I'm going to try to get in the habit of turning GPS off before I go to sleep with my phone charging.
 
Since your device is rooted, if you really want to get to the bottom of this, I suggest installing BetterBatteryStats and/or Wakelock Detector (CPU wakelocks are the ones of interest). Using the information they provide, judicious use of Greenify and Wakelock Terminator should allow you to mitigate, if not outright resolve, these issues.

If it turns out that Google apps are the culprit, get back to me, as I have specific experience with taming them (w/o killing functionality).
 
Back
Top Bottom