Hello,
I am experiencing a rather odd issue since about a week. This is my story:
I am running CyanogenMod on my OPPO Find 7a. I stayed on a build from 2014 (a nightly) that was working okay for me (CM 11, Android KitKat). I decided to update my version last week to the latest CM 12.1 (on Lollipop), and even though I ran in some issues (gapps, update the recovery, etc.), after doing a clean install, it seemed to be fine.
However, just after installing this new build, my problems started: my phone was randomly shutting down (like if no battery was left), but then when plugging it back in I could see it wasn't empty (sometimes it was 20%, sometimes 50%, sometimes as high as 80%). I thought it could be caused by corrupted battery stats, so I tried a bunch of apps and different methods to reset this, without success.
I also tried a factory reset, reinstalling of the ROM, changing the recovery to the cyanogenmod's one, changing back to TWRP (latest 2.8.6.0), wiping the caches, etc. None of this helped.
Today, I decided to install a backup I had from before the installation (a KitKat backup then), to see if the problem came with the new ROM. The phone seemed to work better at first, but after a while I experienced again this sudden shutdown (black screen, phone dead, Android didn't shut it down). So I started to monitor the battery level and voltage, and I noticed something surprising:
When plugged in, the battery voltage is steady at 4300mV. When disconnecting the charger, the voltage is dropping between 3300 and 4100 depending on the charge level (from my understanding, it is a normal behavior). However, as soon as I start using an app that is heavier (for example, Google Maps and jumping from one city to another frequently), I notice that the voltage steadily goes down, and the temperature of the battery goes up.
My conclusion after these tests is that the phone shuts down when the voltage gets lower than 3000mV (something around that value), after few minutes of using a "heavier" app. I checked regularly the temperature, and it didn't go above 30C (it was 26C when idle, I doublt 30C is a problem for a Li-ion battery).
So I have now these questions:
Is this normal that the battery voltage drops when using heavier apps?
Shouldn't the OS handle the load to avoid it to get under the threshold shutting down the phone?
Is it my battery at fault or probably some wrong installation of something? I find it odd that the battery problem appeared EXACTLY at the same time than the Lollipop update I did (and I saw many people having battery issues with this update).
Unfortunately I don't have a second battery to test if it works better, and I'd like to avoid buying one for nothing if possible...
Thanks
EDIT: another weird thing happening, the phone seems to need to restart several time to get in the recovery...
I'm having this problem too. I just got the phone on eBay, and updated to Oppo's Lollipop AOSP beta. Hopefully it is something with a quick software fix. I haven't tried switching ROMs again.
I changed my battery and it fixed the problem. So it was a hardware issue apparently, just odd that it appeared exactly at the same time of the update.
Sangoria said:
I changed my battery and it fixed the problem. So it was a hardware issue apparently, just odd that it appeared exactly at the same time of the update.
Click to expand...
Click to collapse
Yeah. Your description was a clear indication of a failing battery or (possibly) at least a dirty battery contact.
Batteries will drop in voltage under load, but a healthy Li-Po should only drop a little bit (Probably maybe 100 mV, worst case 200 mV or so under load is my guess, I'd be pretty surprised to see a 200 mV drop from a healthy LiPo under reasonable load). If it's dropping a few hundred millivolts under load, the battery is toast or there's a loose connection.
Related
Having a problem with my One X.
The phone runs perfect when the battery has a good charge but as soon as the battery hits around 40% I get continuous force closes, problems waking from sleep etc.
Ive tried wiping battery stats, a few different roms after a full wipe but the problem still happens.
Does this sound like a faulty battery issue?
Really starting to wind me up now and want to sort it.
are you over clocking or undervolting etc?
could try running it completely stock for a while and see if it continues
standard voltage and speed.
might as well rough it out until jb is released before trying stock
Sent from my HTC One X using xda app-developers app
looks like hardware issue not battery precisely
i could add i had battery issues in my Chinese android tablet, android somehow changed the range of the battery voltage and when android said its 60% (and it was showing 100% very long time) the tablet hanged and shut down, OS reinstall helped to fix this issue because it was a software issue
Hello, I've just recently revisited my old android and discovered it rebooting randomly. A further look into this more into the hardware level, would need some statistics from users. I've installed Current Widget, and I've noticed the resets happen when my battery is quite low (20% (3.6v)). So i'm wondering if the problem is with either a bad battery (non linear voltage drops), or more into the battery circuitry myself. I've included the battery voltage I had at the time of the occurrence, because I'm in the middle of a battery calibration, but i do know that it still had plenty of 'juice' left in it because i used it for anther 20 minutes before plugging it in after the random reboot happened. It has done this in the past but this is the first time I've decided to log the reboot.
If anyone suffers from this (not the reboot loop), if you could, could you check your battery voltage level and possible mA amount before and after the reboots happen. (just mark the time down and refer to the logs later. Thanks!
It sounds like a battery issue to me. A new battery is £9 or around $15 max
Did I help you? Hit THANKS!
Galaxy S3 (BEAST, stock)
Desire HD (Retired, REVOlution)
Galaxy Note 10.1 (Big Bad Wolf, stock)
Dark-Show said:
Hello, I've just recently revisited my old android and discovered it rebooting randomly. A further look into this more into the hardware level, would need some statistics from users. I've installed Current Widget, and I've noticed the resets happen when my battery is quite low (20% (3.6v)). So i'm wondering if the problem is with either a bad battery (non linear voltage drops), or more into the battery circuitry myself. I've included the battery voltage I had at the time of the occurrence, because I'm in the middle of a battery calibration, but i do know that it still had plenty of 'juice' left in it because i used it for anther 20 minutes before plugging it in after the random reboot happened. It has done this in the past but this is the first time I've decided to log the reboot.
If anyone suffers from this (not the reboot loop), if you could, could you check your battery voltage level and possible mA amount before and after the reboots happen. (just mark the time down and refer to the logs later. Thanks!
Click to expand...
Click to collapse
You can goto Recovery then wipe davik cache or/and wipe cache +davik cache and reboot to check if it works
I know the GNex doesn't have the best reputation with its battery, but in the past couple of weeks, my phone's battery has been behaving very very strangely, and the problem is very intermittent.
Basically, I am seeing some odd battery drain issues, but there are a number of reported sources from looking at the battery information on the phone. Some behaviors that I have experienced:
1. Screen using 43% of battery with 22 minutes of screen on time.
2. Screen using battery when off.
3. Battery discharging down to almost 0 within an hour after unplugging it from being charged to full - no single app / resource reporting huge usage numbers, just a complete drop on the battery chart.
Other things I have observed; if I catch the system in a state where the battery is draining faster than it should, if I reboot, the system will often recover to normal usage.
I am currently using Paranoid Android 3.15 (I know they have updates - but they also broke their own PIE color scheme, apparently intentionally so, so I am sticking with the last known good version). I am using the stock kernel, and have not tried flashing a new one - if anybody has recommendations, I am all ears.
It is also possible that since this is the original stock battery that the battery itself may be going bad, but my observation about the problem tending to go away after a reboot makes me think the issue is not in the battery itself. I guess the ultimate question is, is there anything that can be done here? Or am I stuck with this until I replace the device in 6 months?
Hi guys -
My 8.4 has been driving me crazy for the past week. It is not rooted, running the stock Samsung image. The battery percentage seems to be wildly inaccurate. I've read through many of the battery threads here (most seem to deal with the inability to charge completely), but I have noticed some that seem to resemble my problem. The solution seems to be to pop the back off and replug the battery. I have not done that, and frankly, I don't think that's the issue here.
Symptoms: Battery appears to drain unevenly - will drop several 10's of % instantaneously during mixed use, and sometimes level off again. I haven't found any runaway processes. Bottom line, overall less then expected battery life followed by the system shutting down. HOWEVER, if I then reboot, it will boot up anywhere between about 5 and 30% remaining - and will continue to run. Sometimes it will drain quickly again, other times it will run for several more hours. Sometimes if I connect the charger after shutdown, it will immediately jump to 40% upon reboot.
Experiment: Drain battery smoothly after a full charge by looping a local video, and track battery percentage and voltage. When system automatically shuts down, reboot (it pops back to 30% or whatever) and continue. Keep rebooting and running until a reboot registers 0% and immediately shuts back down.
Result: Battery drains VERY evenly and consistently. It's only the android percentage that seems to be erratic and cause the system to shut down. I've attached a graph of what I see. The spikes represent points where I rebooted. Blue line = battery percentage (left axis), orange line = battery voltage in mV (right axis)
So given this, I'm having a hard time believing it's a battery connection issue. My uneducated guess is that unplugging the battery works for some because it forces android to recalibrate the battery meter. I've been unsuccessful in getting it to recal by charge/discharge cycles.
Does anyone have any thoughts or ideas on what I should do next? Is there a way to force a recal of the 0% point without rooting? As a side note, I find it odd that my Nexus 7 simply doesn't boot when it hits zero - just shows a battery symbol. Seems odd that the Samsung let's me constantly boot the thing.
Any thoughts would be appreciated!!
Mike
MikeNE said:
Hi guys -.....,..................
Mike
Click to expand...
Click to collapse
Hi! I own a tab S and some users get this problem also on the tab pro. Its something with the battery connection to the device which causes the gauge to be all wonky. Usually problems like you described need to be replaced by Samsung. If you are under warranty, then they'll replace it for free of charge. Better to be extra safe! Hope this helps!
DUHAsianSKILLZ said:
Hi! I own a tab S and some users get this problem also on the tab pro. Its something with the battery connection to the device which causes the gauge to be all wonky. Usually problems like you described need to be replaced by Samsung. If you are under warranty, then they'll replace it for free of charge. Better to be extra safe! Hope this helps!
Click to expand...
Click to collapse
Thanks...yeah, I saw all the comments about the battery connection. As I said in my post, I'm still struggling to believe that it's a connection issue when the battery voltage - reported through a battery widget - is very reliable and steady. It's only the percentage that's wrong. Sounds more like a software issue to me. If it was a connection issue, I'd think the battery voltage would be all over the place too.
Frankly, I'd rather not send it in if I can avoid it (no service centers local). I'd like to explore all possible other options first. Any other ideas on how to force a real recalibration?
Thanks,
Mike
MikeNE said:
Thanks...yeah, I saw all the comments about the battery connection. As I said in my post, I'm still struggling to believe that it's a connection issue when the battery voltage - reported through a battery widget - is very reliable and steady. It's only the percentage that's wrong. Sounds more like a software issue to me. If it was a connection issue, I'd think the battery voltage would be all over the place too.
Frankly, I'd rather not send it in if I can avoid it (no service centers local). I'd like to explore all possible other options first. Any other ideas on how to force a real recalibration?
Thanks,
Mike
Click to expand...
Click to collapse
When your device is fully charged, My guess is to turn your brightness up to the max and open an app that's like intense graphical games or Google earth. As long its stresses your CPU and GPU. That should make your battery drain really quick and cause random reboots because of the meter. Keep doing so till it reaches 0%. Then recharge. If that doesn't work then I don't know. I've done that many times after I flashed a custom ROM so it would calibrate. Doing that would draw all the power out hopefully
DUHAsianSKILLZ said:
When your device is fully charged, My guess is to turn your brightness up to the max and open an app that's like intense graphical games or Google earth. As long its stresses your CPU and GPU. That should make your battery drain really quick and cause random reboots because of the meter. Keep doing so till it reaches 0%. Then recharge. If that doesn't work then I don't know. I've done that many times after I flashed a custom ROM so it would calibrate. Doing that would draw all the power out hopefully
Click to expand...
Click to collapse
Ok...I gave up. I've tried the drain thing multiple ways. I don't want to root the thing or install a custom ROM because I won't be able to use it on my company network. I called Samsung and set up a return. What really bothers me about this is that without an explanation, it's likely to just happen again -because again, I'm still convinced it's software related.
Thanks anyway,
Mike
Sorry to hear that. Please come back when your device is returned from RMA and tell us how it's doing...
CalvinH said:
Sorry to hear that. Please come back when your device is returned from RMA and tell us how it's doing...
Click to expand...
Click to collapse
Will do Calvin - thanks. For the record, I tried one more thing before I boxed it up. I reflashed the firmware with Samsung Kies3. It all went smoothly, and I had high hopes....but shortly after logging in to start setting it up, the battery immediately dropped from 99 to 88....so no luck. I'll be shipping it out tomorrow. I'll post my findings when it returns.
Mike
Well guys - I got my GTP back earlier this week. The actually fixed it in one day and shipped it right back to me. Unfortunately, there was no explanation or description of the repair on any of the paperwork or their website - so I have no idea what they did. Regardless, it appears to be functioning normally now. I fully charged it when I got it, and then ran it down to zero through random usage throughout 2 days...and when it hit zero and shut off, that was it. It wouldn't turn on again (which is what I would expect). I charged it back up, and it's working fine again. So far, so good.
Bottom line, I guess I had some kind of a battery problem, but it appears to be working now. As I said before, I just hate problems with no explanation - it means they are likely to happen again. I guess time will tell...
Mike
I have a 2 year old S4 Mini (GT19195), currently running latest stable CM 13.
The phone is working fine except for the occasional (once a week or 2) unexplained battery drain.
With my fairly light daily use, the battery is lasting over 2 days. <And can usually run 4 or more hours screen on.> However, in the last few months, at random times (even with phone asleep - screen off for > 10 min, so presumably in doze), the phone will heat up, and battery will drop 5-10% per minute. After the phone shuts off from dead battery, recharging and restarting the phone will return things to normal, until the next time.
During these episodes, the phone behaved normally, I did not notice any lag on waking up the phone, switching/opening apps, etc. The battery meter page showed no unusual process using the battery (none of the process actually showed any increase in % battery use); except for the battery life dropping off a cliff as I watch. <I noted that the battery usage stat never adds up to 100% even in normal use ... It might show 10% screen, 5% Android, etc, but all that only adds up to 50% or so from full charge to when the battery is near dead.>
Anyone seen this before? Is this a sign of an ailing battery, or something else? Can this be a software problem - like something running away in the background? <Of note is that this happened once when I had completely wiped the phone and had the fresh install of CM 13 + Gapps (micro) ... so if this is software, it would be something in stock Android, rather than a 3rd party app.>
Thanks for reading & responding.
@JohnSoong
This sounds like the processor is stuck on max frequency. Either it is an app(s) playing up or some other process that is keeping the CPU working when it should sleep.
The first thing I would do is install BetterBatteryStats app or something similar to see what is keeping the device awake. You could also try to grab a logcat, but you would need to catch the incident and either plug into a pc with adb or run an app like catlog
JohnSoong said:
I have a 2 year old S4 Mini (GT19195), currently running latest stable CM 13.
The phone is working fine except for the occasional (once a week or 2) unexplained battery drain.
With my fairly light daily use, the battery is lasting over 2 days. <And can usually run 4 or more hours screen on.> However, in the last few months, at random times (even with phone asleep - screen off for > 10 min, so presumably in doze), the phone will heat up, and battery will drop 5-10% per minute. After the phone shuts off from dead battery, recharging and restarting the phone will return things to normal, until the next time.
During these episodes, the phone behaved normally, I did not notice any lag on waking up the phone, switching/opening apps, etc. The battery meter page showed no unusual process using the battery (none of the process actually showed any increase in % battery use); except for the battery life dropping off a cliff as I watch. <I noted that the battery usage stat never adds up to 100% even in normal use ... It might show 10% screen, 5% Android, etc, but all that only adds up to 50% or so from full charge to when the battery is near dead.>
Anyone seen this before? Is this a sign of an ailing battery, or something else? Can this be a software problem - like something running away in the background? <Of note is that this happened once when I had completely wiped the phone and had the fresh install of CM 13 + Gapps (micro) ... so if this is software, it would be something in stock Android, rather than a 3rd party app.>
Thanks for reading & responding.
Click to expand...
Click to collapse
That sounds like an issue I've had for several months, also running CM13 (Official) nightlies & Open GApps micro, unfortunately I've never had the time investigate (well I did once but it worked fine, I couldn't recreate the problem). It is currently happening less than once a week so not a major issue for me.
I've noticed several times that the phone felt hot, I've then used the Trepn profiler app, it would show the web browser running at 30-50% cpu constantly, so stuck as per @noppy22, though not at 100%. I have tried all the major browsers and they have all done it at some point, also most have crashed at some point, which I suspect may be related. Normally just the browser app crashed but yesterday using Chrome the phone FC and rebooted itself. Crashes seem to happen when I touch screen or scroll (though one may not have been when touching). Also XDA app crashed (1st time) when scrolling a couple of weeks ago, so probably not just browser issue on some sites as I thought previously, but might be unrelated. The stock battery meter did not show particularly high battery usage by browsers, though were a little elevated in % terms but hard to tell due to different usage patterns and not checking when things are good! I have noticed a bit of lag, which now makes we run trepn, if it shows high than expected usage by an app I close the app, which fixes it even if I go back to the same web page. This morning I woke up and my phone was off, I put it in my night-time profile (wifi & data off) that normally only uses a few % overnight but last night it must have used more than 30% of battery that was left, first time this has happened.
The other thing to consider is how good is your battery? At 2yrs old it could be tired if it's had a hard life (though yours maybe not) or you have allowed it to get very hot eg I did one trip using gps nav with phone mounted in windscreen cradle driving direct into the Aussie sun when my battery was about 2.5yrs old, thinking back I now think this was when I first noticed my battery was really dropping of quickly when around ~40% charge (though it was faster with more charge remaining also than my new battery, I would say), so think I the high temp the phone got to that day affected the battery. I think 4hrs of screen on time may be marginal, I was only getting about 3 to 3.5 when my battery dropped off fast, my new battery is giving me 6hrs SOT (mostly using browser app), so possibly you just need a new battery as only one other user has reported high cpu usage like I have.
Battery stats not adding up to 100% is normal.
I've just installed BetterBatteryStats, so I'll give it a week of so and see if it catches anything. So far nothing unusual in the stats.
I am leaning towards this being a hardware issue, likely the battery. Since the phone responded fairly normally during the overheat & battery drain episodes, this does not seem to me an app taking over the CPU. If the CPU was occupied by an app, shouldn't everything else be slowed down?
I have so far noticed no particular pattern to these episodes, and I cannot reproduce it at will. It is infrequent enough for now that I can live with it (although an unexpected dead battery is annoying.) I will see if the monitoring app pick up anything.
Hey guys,
Maybe you have to try to flash your stock or custom kernel again.
Thats probably the problem.
Xheers
When I got mine a few years ago the media process kept getting stuck and overheating/draining my phone and even a reboot wouldnt fix it. I found out because I was using the system panel app and monitoring cpu of system processes. I ditched and deleted the gallery app (it was trying to create thumbnails for 100+gb of photos and videos) for quick pic v.4.5.2 on every phone I've used ever since and haven't look back.