Related
The battery life on my NC is absolutely horrible. I average 3 hours unplugged, 1 hour if I'm using it. It doesn't seem to charge up all the way -- after plugging it in the light on the Nook cord is orange for about 10 minutes then goes green even though the screen still stays "Not enough power to turn on - Try again in 15 minutes".
I've tried using software like juicedefender and other battery mon apps that are supposed to be able to predict when you're going to lose your power -- but they appear to be useless. Often I'll get the "Your Battery is Getting Low" message at the very same time as the "Shutting Down" dialog appears -- almost like there was a very sudden dramatic drop in available power.
I am beginning to wonder if it's the result of faulty hardware.
Has anyone else experienced problems like these? Or should I restore back to stock and send it in for warranty?
That definitely sounds abnormal. I'd probably restore it back to factory and if it's still acting like that, you'll know it's not due to any modifications.
Yeah, I second that. Mine drains pretty quickly, I go from 100% to about 60% in a day with normal usage. I use Wifi Auto Toggle to turn Wifi off when the screen turns off. So far I have to recharge every other day or so. But what the OP has going on sounds pretty extreme.
What ROM are you using?
What programs have 'keep screen alive' do you run?
How bright is your screen?
Screen/wifi burn most of the power in this - so minimizing them helps battery life considerably.
I had one game (HexDefense) that prefers to run in maximum brightness and burned through the battery very quickly. Nook was the warmest I've ever seen it and the temperature on my battery monitor actually moved for the first time ever.
SO if you're getting 3 hours doing nothing, that's bad. If you're getting 3 hours running a really processor/graphic intensive game, that's good.
If you can get it back to stock and still have low battery life, consider talking to the manufacturers about it.
OverDrive33 said:
The battery life on my NC is absolutely horrible. I average 3 hours unplugged, 1 hour if I'm using it. It doesn't seem to charge up all the way -- after plugging it in the light on the Nook cord is orange for about 10 minutes then goes green even though the screen still stays "Not enough power to turn on - Try again in 15 minutes".
I've tried using software like juicedefender and other battery mon apps that are supposed to be able to predict when you're going to lose your power -- but they appear to be useless. Often I'll get the "Your Battery is Getting Low" message at the very same time as the "Shutting Down" dialog appears -- almost like there was a very sudden dramatic drop in available power.
I am beginning to wonder if it's the result of faulty hardware.
Has anyone else experienced problems like these? Or should I restore back to stock and send it in for warranty?
Click to expand...
Click to collapse
You really question this? Something is wrong with your NC, cable, or charger.
Just when I think I've got it all setup nicely...
Latest AOSIP rom with Hellscore kernel, stock settings greenify, full discharge and recharge, all seemed so good....
And then boom. Go to reboot to recovery and I get the little empty battery icon upon reboot - but I was at around 40%?!
I use the battery calibration app, for what it's worth knowing the debate about the battery stats file. I've done the bootloader logs 'trick' and still I get a random occurrence like this?!
Anyone else been plagued with this randomly happening to them?
There are so many reasons it can happen. on thing id recommend is install ampere form play. Using this you should be able to monitor the voltage of the battery and at least know that it is operating within the correct range. if your 0% voltage is too high, it could rule some stuff out.
rootSU said:
There are so many reasons it can happen. on thing id recommend is install ampere form play. Using this you should be able to monitor the voltage of the battery and at least know that it is operating within the correct range. if your 0% voltage is too high, it could rule some stuff out.
Click to expand...
Click to collapse
Many thanks for the suggestion, gonna give that a try now!
cd993 said:
Many thanks for the suggestion, gonna give that a try now!
Click to expand...
Click to collapse
Cool. Just periodically check the app and jot down the percentage and voltage. keep doing that until its ready to shut down. preferably a reading every 10-15% if you can but really important is to try and capture readings just before and after any drop off you may see.
rootSU said:
Cool. Just periodically check the app and jot down the percentage and voltage. keep doing that until its ready to shut down. preferably a reading every 10-15% if you can but really important is to try and capture readings just before and after any drop off you may see.
Click to expand...
Click to collapse
Perfect thanks for the advice, I've got it installed and now juts doing a full charge.
Following that drop out, the device then reported 7% battery so I let that go flat and now fully recharging.
If it's the case that there is something going on here, how can the issue be corrected? Does Ampere help configure reported VS actual readings, or does it purely show what's being drained?
cd993 said:
Perfect thanks for the advice, I've got it installed and now juts doing a full charge.
Following that drop out, the device then reported 7% battery so I let that go flat and now fully recharging.
If it's the case that there is something going on here, how can the issue be corrected? Does Ampere help configure reported VS actual readings, or does it purely show what's being drained?
Click to expand...
Click to collapse
Its worth getting a voltage reading now too then, to see if it is as low as expected. As for solution, we need a root cause first.
rootSU said:
Its worth getting a voltage reading now too then, to see if it is as low as expected. As for solution, we need a root cause first.
Click to expand...
Click to collapse
Ok here is my first screen. I'd browsed Facebook (web version) and watched a video or 2, battery dropped to 97% soon after.
Yep. Just keep going. Every 10% is fine. No more than that. Actual battery charge is voltage so we just want to see if there are any conflicting data sets later on
rootSU said:
Yep. Just keep going. Every 10% is fine. No more than that. Actual battery charge is voltage so we just want to see if there are any conflicting data sets later on
Click to expand...
Click to collapse
Thank you, I'll keep you posted.
danarama said:
Yep. Just keep going. Every 10% is fine. No more than that. Actual battery charge is voltage so we just want to see if there are any conflicting data sets later on
Click to expand...
Click to collapse
It just did it again!!?
I had even doing the Ampere monitoring but didn't go all the way down. But today I just experienced the random drop out again. Strangely when I booted back up, it was as if the cache had been wiped as the Android Optimising app screen came on.
This was from the other day though, if this helps?
The other day did it seem to deplete normally? I'm around 20%/right now and see similar voltage to you.
Sometimes my phone used to crash and when it booted up I had this graph / drainage issue. It's as if it goes into some manic sleep that kills everything. What you've got here seems similar. I don't think there's an issue with the battery cycle itself.
I'd be tempted to do a factory reset and start clean to be honest.
Is the back of your N6 lifting away from the frame? I had this issue too and ended up doing a RMA because the battery was bulging.
danarama said:
The other day did it seem to deplete normally? I'm around 20%/right now and see similar voltage to you.
Sometimes my phone used to crash and when it booted up I had this graph / drainage issue. It's as if it goes into some manic sleep that kills everything. What you've got here seems similar. I don't think there's an issue with the battery cycle itself.
I'd be tempted to do a factory reset and start clean to be honest.
Click to expand...
Click to collapse
Weird and annoying isn't it!
I've recently flashed this new rom and so has been a fresh start so I'm kind of at a loss as to what to try next.
drkboze said:
Is the back of your N6 lifting away from the frame? I had this issue too and ended up doing a RMA because the battery was bulging.
Click to expand...
Click to collapse
Just took off my case and checked and all seems normal, back doesn't appear to be coming away and seems to be ok.
It's times like this I miss my good old Note 3, never had a battery life like it for its flat lining ability!! (see attached)
If it were the battery capacity due to bloating, I would expect to see the Voltage value to be wrong
Go back to stock and run it with no restored apps / data. If it still happens RMA
cd993 said:
Just when I think I've got it all setup nicely...
Latest AOSIP rom with Hellscore kernel, stock settings greenify, full discharge and recharge, all seemed so good....
And then boom. Go to reboot to recovery and I get the little empty battery icon upon reboot - but I was at around 40%?!
I use the battery calibration app, for what it's worth knowing the debate about the battery stats file. I've done the bootloader logs 'trick' and still I get a random occurrence like this?!
Anyone else been plagued with this randomly happening to them?
Click to expand...
Click to collapse
Your battery calibration is messed up. It happens.
DO NOT waste your time with "battery calibration app" -- there is NO software you can install and run from Android that will have ANY impact AT ALL on the battery calibration. All those "battery calibration" programs do, is delete the battery stats file, and all the battery stats file does, is store a log of what programs are responsible for how much resource utilization -- nothing at all to do with calibration.
Battery calibration reset is done through the BOOTLOADER.
Reboot your phone to bootloader. Scroll to "bootloader logs". Press and hold power button until the phone shuts down.
And that is all there is to it.
doitright said:
Your battery calibration is messed up. It happens.
DO NOT waste your time with "battery calibration app" -- there is NO software you can install and run from Android that will have ANY impact AT ALL on the battery calibration. All those "battery calibration" programs do, is delete the battery stats file, and all the battery stats file does, is store a log of what programs are responsible for how much resource utilization -- nothing at all to do with calibration.
Battery calibration reset is done through the BOOTLOADER.
Reboot your phone to bootloader. Scroll to "bootloader logs". Press and hold power button until the phone shuts down.
And that is all there is to it.
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately, I have tried this many times and so there must be more to it than this. On my latest rom, I had wiped phone and clean flashed whilst phone was connected and at 100%. Therefore a new clean install whilst phone was at 100%. I cleaned that stats (for what it was worth) and also did the bootloader logs trick. I would have thought that would have solved the issue, but as reported it still happened.
cd993 said:
Thanks for the reply.
Unfortunately, I have tried this many times and so there must be more to it than this. On my latest rom, I had wiped phone and clean flashed whilst phone was connected and at 100%. Therefore a new clean install whilst phone was at 100%. I cleaned that stats (for what it was worth) and also did the bootloader logs trick. I would have thought that would have solved the issue, but as reported it still happened.
Click to expand...
Click to collapse
Your calibration is fine because the % matches up to the voltage, which is all calibration matches.
danarama said:
Your calibration is fine because the % matches up to the voltage, which is all calibration matches.
Click to expand...
Click to collapse
Thanks yeah, I thought as much.
The question remains then..... What in earth causes these drop outs!
cd993 said:
Thanks yeah, I thought as much.
The question remains then..... What in earth causes these drop outs!
Click to expand...
Click to collapse
It's hard to say. It seems like the system may be crashing or something at that time and causing an inordinate drain. Thats what mine used to do sometimes.
I'm currently running latest Pure Nexus ROM and Despair Kernel on my n6. While they have both been working fine, I was wondering if someone could shed some light on why certain things are happening. Yesterday I dirty flashed the despair kernel because only 2 cores were online and the other 2 wouldn't start. After the reflash, my phone was able to barely use any battery. So when I got home and i decided to plug my phone in around 20% battery. I wake up this morning and I unplug my phone thinking i'll have as good battery as I did before I plugged it in. Well, it seems that's not the case. My phone seems to be using more battery than it needs as it's just sitting on my desk not in use.
How come my phone starts to drain battery like crazy after a full charge? Is it because I reflashed the kernel and that fixed things? Is it because I rebooted the device? Do I need to reboot the device daily (after a full charge)? Is anyone else experiencing this?
This behavior has been happening on full stock as well and that's why I rooted and flash a custom rom/kernel because I was hoping this behavior would be gone. I know it's probably too early to tell and I guess my phone is "settling" after the reflash, but how come the day of the reflash it runs fine?
shugga101 said:
I'm currently running latest Pure Nexus ROM and Despair Kernel on my n6. While they have both been working fine, I was wondering if someone could shed some light on why certain things are happening. Yesterday I dirty flashed the despair kernel because only 2 cores were online and the other 2 wouldn't start. After the reflash, my phone was able to barely use any battery. So when I got home and i decided to plug my phone in around 20% battery. I wake up this morning and I unplug my phone thinking i'll have as good battery as I did before I plugged it in. Well, it seems that's not the case. My phone seems to be using more battery than it needs as it's just sitting on my desk not in use.
How come my phone starts to drain battery like crazy after a full charge? Is it because I reflashed the kernel and that fixed things? Is it because I rebooted the device? Do I need to reboot the device daily (after a full charge)? Is anyone else experiencing this?
This behavior has been happening on full stock as well and that's why I rooted and flash a custom rom/kernel because I was hoping this behavior would be gone. I know it's probably too early to tell and I guess my phone is "settling" after the reflash, but how come the day of the reflash it runs fine?
Click to expand...
Click to collapse
signal quality relates heavily to battery drain. if your signal is great quality, youll probably have great battery. but if your signal is bad quality, you can watch your battery basically disappear.
simms22 said:
signal quality relates heavily to battery drain. if your signal is great quality, youll probably have great battery. but if your signal is bad quality, you can watch your battery basically disappear.
Click to expand...
Click to collapse
I do have pretty bad in/out signal at work, but it wasn't draining my battery that bad after I did the reflash. I'm wondering if I made a change to a kernel setting that is now letting this happen.
I'll be monitoring it today. So far I'm at 86% with 42m SoT. BBS is saying that my phone has been unplugged for 4h 25m. So that is a 3.2%/h drain. My phone has been awake for 44m (screen off). This was increasing before I changed some settings for the kernel, but now seems to not be increasing as much.
Help! After latest "update", Bluetooth is the only thing showing in battery stats?
OK, so there was a new stock "update" and an old problem came back, namely that my phone shows Bluetooth as the only thing using battery. I had this a while ago (in this thread here about "crazy mega bluetooth battery drain") but the same fix of resetting the logs does not seem to be working.
A short time after charging the phone and resetting the logs, the phone shows Bluetooth has a CPU total of 0s, Keep awake of 7s, and computed power use of 17895mAh. No other process is listed as using battery!
The phone is stock, not rooted, "updated" to N8I11F with the OTA that came last week.
Anyone know how I might resolve this?
Various solutions have been discussed in this thread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Various solutions have been discussed in this thread.
Click to expand...
Click to collapse
Well, thanks again. I've tried turning off the Bluetooth headset in the Google app (Google app->Settings->Voice).
I guess I'll know after I use Bluetooth next if it helps or not.
ModemJunki said:
Well, thanks again. I've tried turning off the Bluetooth headset in the Google app (Google app->Settings->Voice).
I guess I'll know after I use Bluetooth next if it helps or not.
Click to expand...
Click to collapse
OK, yesterday after I drove my car which has Microsoft Sync 2, the bluetooth problem returned. So I went through the threads again and did found that maybe the reset wasn't working because I was charging with an LG charger at work. So I tried topping off the battery with the OEM turbo charger (and not using a Qi charger either). Tethering is off as well.
But this is also not seeming to work. After 22 hours, BT is showing 23% battery use (though I do now see other apps in the battery stats).
Still looking for a solution.
Did you turn off instant tethering as suggested in that thread?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Did you turn off instant tethering as suggested in that thread?
Click to expand...
Click to collapse
Yes, instant tethering is off.
I can confirm that if I charge the phone and don't use Bluetooth, the problem does not exist. I was able to let my phone run for 24 hours and the battery stats were normal, showing more than 1 day of runtime at the beginning.
As soon as I connect to my car, then only Bluetooth shows in the battery stats and the battery life is reported as shortened considerably.
ModemJunki said:
Yes, instant tethering is off.
I can confirm that if I charge the phone and don't use Bluetooth, the problem does not exist. I was able to let my phone run for 24 hours and the battery stats were normal, showing more than 1 day of runtime at the beginning.
As soon as I connect to my car, then only Bluetooth shows in the battery stats and the battery life is reported as shortened considerably.
Click to expand...
Click to collapse
I'd factory reset at this point. Something is wacky and it's not wide spread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I'd factory reset at this point. Something is wacky and it's not wide spread.
Click to expand...
Click to collapse
I was hoping to avoid that but I'll give it a shot later today or tonight.
ModemJunki said:
I was hoping to avoid that but I'll give it a shot later today or tonight.
Click to expand...
Click to collapse
Fingers crossed that once you put in that effort, the problem is fixed. You could try going into safe mode and see if that resolves things. Safe mode will reset ROM/system settings, but you won't lose your apps.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Don't do it, it's not going to work.
I learned how to live with battery drain stats
I'm on Oreo and doesn't matter what custom ROM I'm on this annoying issue occurs always when I keep my BT open, but not connected to any device
I've tried all the "fixes": not optimizing the BT, clear the BT cache, clear the bootloader logs, disabled the BT tethering etc... none of them helped.
When I connect to a device (headphones, or car) the consumption is normal and very low, no problem of showing the correct figures in Battery menu.
The issue occurs only if BT is not connected.
I can't believe this issue has not been reported yet to Google, but it seems they don't care about it...
Well, after using Safe Mode, no difference. I think that even if I don't use a Bluetooth device the problem comes up after a while.
How can we report this to Google? They don't support the phone any longer...
ModemJunki said:
Well, after using Safe Mode, no difference. I think that even if I don't use a Bluetooth device the problem comes up after a while.
How can we report this to Google? They don't support the phone any longer...
Click to expand...
Click to collapse
Use the Nexus support forums.
Is your battery original? The only time I have personally had to trouble was when my battery started failing. It was a precise to the early shutdowns and when I replaced the battery, I never had the problem again. Not on Nougat or Oreo.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Is your battery original? The only time I have personally had to trouble was when my battery started failing. It was a precise to the early shutdowns and when I replaced the battery, I never had the problem again. Not on Nougat or Oreo.
Click to expand...
Click to collapse
Yes, original battery. The phone was purchased as new old stock last August. The battery is good, runs all day with heavy use, or more than a day when I'm not using the phone much.
Well, all I can tell you is this doesn't not exist on every phone. And unlike the earlier post indicating it's an inherent problem on Oreo, the attached screenshots show that's not true on my device.
The first image is after some time with Bluetooth on but not connected and the second with a device connected.
OK, so Google support connected me to Motorola support and they had me try clearing my storage cache which did not work. I will try calling them back tonight as I have a case open.
If that doesn't pan out I'm going to try doing a factory reset and setting up the phone as a new device - I've not done this before so I hope it's straightforward. Then I will use the phone stock for a day to see what if anything happens. If it's all good I will re-add my applications one at a time. I don't have all that many apps on the phone.
It might have to wait since I have some other work and household projects going on, but if I do find the root cause I will post back here.
OK, reporting back. Motorola support was polite but unhelpful. Reset the phone, reset the logs, oh thats it - out of warranty, replace the phone for $$$ even though it was our OTA that caused the problem.
No thank you, Motorola. I'll spend my money elsewhere after you broke my phone.
However, my complaints aside, I am tentatively pleased to report that the behavior has changed, and if it keeps running this way I'll hang on to the phone until it's well worn.
The change is that now even though only Bluetooth is shown as battery draining, the phone shows more normal battery stats so it's like it was before the update. For example at the moment I have 68%, 1 day 6 hours left, 14 hours after last full charge (I charged it and let it sit idle overnight, then today have been re-installing the few apps I use like Authenticator, Outlook, Facebook, WhatsApp, WyzeCam, DropBox, Dark Sky, Alarm Clock Xtreme). The only change made from stock was to turn off Bluetooth tethering in settings and to turn off Bluetooth headset in the Assistant. Before this, after connecting to my car radio and driving for 30-40 minutes or so, the battery estimate would drop from >1 day to 7-8 hours. It did not do that today so I figured I'd try and reinstall my apps.
This change is purely by chance, I am not certain that this can help anyone else. Here is what I did:
1) Backup local data.
2) Reset phone to factory from the menu in Settings.
3) Setup up phone as a new device.
4) Turn off Bluetooth tethering in settings.
5) Turn off Bluetooth headset in the Assistant.
6) Shutdown, clear logs.
7) Restart, install Battery Calibration app (Imobs Ltd.) (paid version).
8) Run a "Premium Calibration".
9) Charge phone to 100% using the OEM TurboCharger.
10) Let phone sit idle overnight.
I'm hoping the behavior sticks after I reinstall my apps. I'll post back if it does not.
It's been a while and I was going through my phone cleaning up pictures when I remembered this thread.
So I opened my battery settings on the phone and somehow the battery statistics are working properly - I see a normal list of items for power consumption.
I am confused because I have not made any further changes to the phone settings or attempts to solve this aside from uninstalling Battery Calibration and using AccuBattery to keep an eye on battery life, but those changes were made months ago.
ModemJunki said:
It's been a while and I was going through my phone cleaning up pictures when I remembered this thread.
So I opened my battery settings on the phone and somehow the battery statistics are working properly - I see a normal list of items for power consumption.
I am confused because I have not made any further changes to the phone settings or attempts to solve this aside from uninstalling Battery Calibration and using AccuBattery to keep an eye on battery life, but those changes were made months ago.
Click to expand...
Click to collapse
Did you update your Oreo ROM to a newer version? I am running ABC ROM and my battery stats weren't working until a recent update. It never bothered me so I never made any attempts to fix it, it just started working on its own again.
alryder said:
Did you update your Oreo ROM to a newer version? I am running ABC ROM and my battery stats weren't working until a recent update. It never bothered me so I never made any attempts to fix it, it just started working on its own again.
Click to expand...
Click to collapse
No updates for me - I'm running stock build N8I11F.
It must have been an update to some other component that fixed it. I can not think of any other way for it to suddenly be "fixed".
Had anyone else noticed a Pixel 4 XL battery that's generally fine until it hits about 30% and then plummets to zero within minutes? Seems to be happening all the time at the moment. Any suggestions on how to solve this?
magnatom said:
Had anyone else noticed a Pixel 4 XL battery that's generally fine until it hits about 30% and then plummets to zero within minutes? Seems to be happening all the time at the moment. Any suggestions on how to solve this?
Click to expand...
Click to collapse
From personal experience with Google and battery issues, I'll tell you this...
Do a factory reset or better yet flash the next monthly update using the factory image with the -w still in the script to force the full wipe. If this does not fix the problem then your due a warranty claim in my opinion. They will tell you to do all this as part of the troubleshooting anyway and you'll probably have to go through the motions regardless but it'll at least give you a better idea where you stand before jumping through their hoops!
CyberpodS2 said:
From personal experience with Google and battery issues, I'll tell you this...
Do a factory reset or better yet flash the next monthly update using the factory image with the -w still in the script to force the full wipe. If this does not fix the problem then your due a warranty claim in my opinion. They will tell you to do all this as part of the troubleshooting anyway and you'll probably have to go through the motions regardless but it'll at least give you a better idea where you stand before jumping through their hoops!
Click to expand...
Click to collapse
This is good advice. If a factory reset doesn't help, I'd see about a warranty claim as well. The Pixel 4XL is a good phone but while the battery life isn't one of it's strong suits, I've never seen anything like you describe. They are pretty good about replacing a bad phone after the usual troubleshooting. It's a pain but worth the trouble.
This looks exactly like what was happening on the Nexus 6P phones. This is the first case that I've seen on the pixel like though. It was so widespread on the Nexus 6P line that there is a class action suit still going on. I had three of those phones with this issue. As CyperpodS2 said a factory reset should be your first option. I doubt it will help if it is a hardware problem but Google will require you to do that before the will RMA your phone anyway.
Thanks guys. Tried a factory reset but it has just done exactly the same thing as before. Gets to about 30-29% and then drops within a matter of seconds to zero and turns off. I'll phone my carrier today to see how they respond to this. I'll let you know how I get on.
Oh and here is the battery history.
Good luck. You shouldn't have any trouble getting a replacement.
Crap! Me too! Everything was fine and then all of a sudden battery is dead. I also have issues charging to 100% using my wireless charger but maybe it's the charger. The sudden death at 30% battery just started happening. I did install the latest February update and don't remember it doing this before then. Up until now I've been really happy with battery life.
I've been hitting 30% and lower recently due to changing when I charge the phone. I have not seen a sudden drop once I reach 30% and I have battery saver turn on automatically at 25% and can get hours out of that. To be honest, since I deleted facebook account my phones have always had better battery live than friends with the same device. It was the first thing I noticed about removing FB/Messenger, I went to a single charge for 1.5 days.
Just to update. Google did replace my Pixel XL without any issues. I didn't get any feedback on the phone I sent, but I assume the fact that they haven't charged me anything suggests that they did find a problem. Hope you get your issue sorted out @SnrSuave and that these are isolated problems.
I've been doing some testing and trying to recalibrate the battery. Seems to be better now. I let the battery run down completely empty and then fully charge while turned off. Last night I got the battery down to 10% without it dropping fast.
My experience last days
Once it didn't load over 15% (display bug)
All is fine after complete empty device
Good to hear others are solving their issues. I had run my battery down and charged fully a few times, but didn't improve things for me. Hopefully just one of those random issues that happen from time to time. replaced device running well. :good:
I had the same **** with my 3xl.
In the end i RMA it.....