Database Develop

V217 OTA - battery life / heat?

7 hours off fully charged battery since the upgrade completed, and down to 10%. Anyone else with battery life issues since receiving the OTA?
edit: phone temperature also runs very hot now since the update-- Gingerbread was quite a bit cooler to run.

I briefly ran the 217 OTA build before installing safestrap and rolling to a Cyanogenmod image.
I noticed that my phone was MUCH hotter than it had been while running the older GB-based rom -- however, I can't comment on the battery life itself.

mattvirus said:
I briefly ran the 217 OTA build before installing safestrap and rolling to a Cyanogenmod image.
I noticed that my phone was MUCH hotter than it had been while running the older GB-based rom -- however, I can't comment on the battery life itself.
Click to expand...
Click to collapse
I've been running .217 leak for a few weeks, and found that if you have a lot of MP3s on an SDcard, the phone will run really hot while it builds the MP3 database.

mattvirus said:
I briefly ran the 217 OTA build before installing safestrap and rolling to a Cyanogenmod image.
I noticed that my phone was MUCH hotter than it had been while running the older GB-based rom -- however, I can't comment on the battery life itself.
Click to expand...
Click to collapse
It does indeed run much hotter with the screen on. Are you experiencing heat issues with Cyanogenmod, or was it only under the 217 OTA?
edit: added quote for context

danifunker said:
I've been running .217 leak for a few weeks, and found that if you have a lot of MP3s on an SDcard, the phone will run really hot while it builds the MP3 database.
Click to expand...
Click to collapse
Was it a one-time or some-time thing, or was the phone constantly hot? Did you remove any of the files, or was there a workaround to prevent building the database?

It's been stated that initially expect very poor battery life immediately after upgrading to ICS and I would expect heat to be another factor as the CPU is in constant use updating all the new databases, sync'ing etc...that is going on.
(stated in the Motorola soak test forums to expect this).

tcrews said:
It's been stated that initially expect very poor battery life immediately after upgrading to ICS and I would expect heat to be another factor as the CPU is in constant use updating all the new databases, sync'ing etc...that is going on.
(stated in the Motorola soak test forums to expect this).
Click to expand...
Click to collapse
+1 its expected. I always try to give new roms/updates at least 3 or 4 days to smooth itself out. Especially when upgrading from cupcake to froyo to gingerbread to ics.......
Sent from my DROID4 using xda premium

vprasad1 said:
Was it a one-time or some-time thing, or was the phone constantly hot? Did you remove any of the files, or was there a workaround to prevent building the database?
Click to expand...
Click to collapse
Mine ran hot for a day. The next day I restarted it and haven't ran hot for a while.
Sent from my XT894 running ICS

Yeah it should be better after a couple of three days. I can get 14-16 hours on network and 25-30 hours when on steady wifi.

vprasad1 said:
It does indeed run much hotter with the screen on. Are you experiencing heat issues with Cyanogenmod, or was it only under the 217 OTA?
edit: added quote for context
Click to expand...
Click to collapse
It ran quite hot in the 217 OTA itself. Once I flashed over to cyanogenmod, it got cooler and has been running at roughly the same temperature as when i ran the GB rom.
I have very few MP3's on the SD card. It's actually the card from my old D1 and mostly has nandroid and titanium backup data on it

Odd, I haven't noticed any increase in heat, battery life is still good for me.
Upgraded OTA on monday, so 2 days now. I have a 32gig sd card, and the internal sdcard and the 32gig are loaded full of mp3's, a few videos, and titanium backups.
I want to say battery life is better than normal. But I believe this is only due to fixing a few issues over the weekend with misbehaving apps.

tcrews said:
It's been stated that initially expect very poor battery life immediately after upgrading to ICS and I would expect heat to be another factor as the CPU is in constant use updating all the new databases, sync'ing etc...that is going on.
(stated in the Motorola soak test forums to expect this).
Click to expand...
Click to collapse
Alright, it's been four days and battery life still sucks-- the phone is now only charging to 60% capacity, and phone spontaneously reboots, runs hot and apps still crash... and then I read that V217 OTA is halted due to "software issues"-- what recourse do I have? I don't pay "insurance" (which works out to the price of a new phone in 2 years). Will VZW address or swap the phone given that this power issue and phone instability was due to software upgrade they prompted on the phone?

Strange... Powered off the Droid 4 before bed and plugged into charger. Woke up and it was at 100%. Powered on, rebooted into safestrap/cwm and wiped cache, Dalvik, and battery stats. Rebooted and left it on charger, in case of quick drain again.
Will see if wife still experiences issues during her day. If so then this is most likely software or OS issue and after I get home from work I'll have to try backup and FXZ to see if a clean OS and gradual install of apps / restore some old data resolves the issue.
Step 1 is hunting down D4 FXZ threads on XDA and checking what's involved.
Sent from my ADR6425LVW using Tapatalk 2

I've been finding that the battery life and heat has improved for me since installing the OTA. I came from stock, rooted, Gingerbread 219. For the past month or so, I had been noticing that my phone was getting very hot just by charging it (could be due to some app that I couldn't narrow down), but that stopped after the ICS OTA.
Additionally, after the last GB OTA, I noticed that the keyboard lighting would shut off even in complete darkness. That also seems to be fixed with the ICS OTA.
Sent from my DROID4 using xda premium

I've had a couple of interesting issues since I updated this morning. First, my media files on my microSD card "disappeared" in that My Gallery no longer displayed pix and vids on the microSD card and Winamp couldn't find any of my MP3s. A reformat of the card seems to have fixed it, for now.
The other issue is that the battery seemed to drain much more quickly than it did when I had Gingerbread. I hope what was said here about that being the case for about the first day or so is true. I would hate to think that this is the nature of ICS.

Didn't do the FXZ / destructive reinstall yet; was doing some more investigation last night-- phone was draining about battery 10% every 10 minutes. The only two things showing under Settings-->Battery were Screen at 60% and Media com.motorola.android.omadrm at 40%. Rebooted, set to charge before bed and now this morning I see other items listed under battery: Android System, Android OS, Mail. Phone is now at 80% battery running on battery for the last 30 minutes. When the screen goes off and I turn it back on, I sometimes see "Battery Extender" flash in the status bar.
Did an
Code:
adb reboot bootloader
to get to the bootloader. Then did a
Code:
fastboot devices
and saw that the phone was listed. Launched RSDLite and flashed the fxz xml.zip file and all seemed well...
phone started up, there was a little android icon with gears spinning inside of it and a progress bar crossing. phone rebooted again, "optimized" android applications, and finally came back to the same system as before-- nothing got wiped. I guess I'll have to do a Settings/Privacy/Factory Reset to get an actual wipe.
Rather than doing a wipe, debating setting up safestrap, going to the safe partition and installing an alternate ICS ROM.
Before going that route at all, there are 27GB of about 7000 mp3 files on the external SD. I'm going to pull the external SD and see how battery life is first.

No battery benefit after pulling out the external SD card; still about 10% battery drain every 10-15 mins.
Did the Settings/Privacy/Factory reset-- currently at 30% drain in 120 minutes. Seems improved, but this is also without the external SD in the device.
Saw a few different things in forums, including searching through some of the alternate ROMs for D4 and looking at some of the Razr ICS upgrade battery issue complaints:
--some said they were having battery issues until doing factory wipe and then reinstalling apps from Play Store without restoring old data
--some said there was something stuck on their external sd that required a full re-format and then restoring data back to the external sd which returned battery life to "normal"
--others said that media indexing is taking place and to give it a few days (seriously? is there no way to disable this or uninstall whichever application is doing this??? the wife said she wouldn't mind scrolling through folders rather than having fully indexed media by artist/album/genre)-- And she raises the valid point, "It used to work fine before!" What changed between Ginger Bread and Ice Cream Sandwich to require this much indexing and what's the fix for it given that people can't return back to GB? Which QA engineer at Verizon/GoogleRola thought it would be a good idea to release an update with this massive issue? Is the intent to discourage people from listening to their locally stored music and to have them rely on data plan intensive "cloud services"? Is there some application that can do the indexing on a more powerful machine like a PC and then upload the indices / export databases to the phone?

140 minutes at 60%-- still at full factory resetted stock from this morning, no external SD card in phone, no media on internal SD card.
I suppose Plan B is to call Verizon and tell them that the battery life is complete crap since their update and to request a CLN-- hoping that it's not running ICS.
to clarify: no apps have been restored / reinstalled-- what on earth could possibly be digesting battery like this?
edit: saw someone's post suggesting settings/more.../mobile networks/network mode - preferred network = LTE/CDMA instead of Global. Giving that a shot.

Not sure what did the trick, but after observing 4 hours at 60%, and Disabling a bunch of the bloatware, re-added the external memory card (with all gazillion mp3s on it) and began installing previously used software. A charge later and a few reboots after, was getting 4 more hours with battery at 90%. No idea what did the trick as I ran through too many variables and never reset them to be able to isolate one specific one.
Good luck to anybody else that may experience this issue in the future.

Thanks for the report. I too did the factory reset and reformatted my card. I think I've had a tiny bit of improvement, but still go down to about 60% capacity after two hours away from the charger with moderate use (Facebook, Twitter, Tapatalk, etc., no streaming or media play). I have my display set to auto, have changed the radio to CDMA/LTE only and have disabled as much bloatware as I can. I'm now trying the battery training FoxKat recommends to see if that will help.

[Q] Weird battery issue, Razr i, after Jelly Bean

Hi all,
I have weird battery issue with my Razr i xt890 and I'd like some help. I have tried googling for information, but there's too much noise and I can't find anything suitable.
I'm asking on this site because I know the people on here are really knowledgeable.
My Razr i (with Jelly Bean) seems to have erratic battery readings. Sometimes it'll drop to 6%, and then go up to 90%, and jump around to points in between. I have even seen it drop to 1% and then go up to 6% (or something like that).
Needless to say, this makes the phone unusable because I don't know when it's on low battery so I can charge it. Furthermore, twice, it has reported low battery and then automatically shut itself down.
I hope someone can help with this, because I'm really stuck. I bought this phone overseas, and I don't really want to send it back overseas for warranty repairs.
So, some history.
Before the issue:
This is a stock Razr i, running Retail GB software. When I bought it, it was running 81.5.31002.Retail.en.GB 4.0.4. I upgraded to 81.5.39001.Retail.en.GB 4.0.4 and it's been running fine until this issue happened. I normally get about 4.5-5.5 days of battery before I recharge the phone.
This is stock software. No root. No bootloader unlock. No custom roms.
The issue:
I charged up my phone yesterday, and unplugged it from the charger at 100% battery. There was a notification that 91.2.29001.Retail.en.GB 4.1.2 was available. I selected 'Later' because I was busy at the time.
A bit later (maybe about an hour?), I went back to the phone and checked for updates, and selected to download the update. After it was downloaded, I noticed the battery was about 95%, and then I proceeded to install.
I figured 95% power should be sufficient to perform an upgrade.
The install took, maybe 10-15 minutes? At first glance, it seemed successful, but when the phone started up again, the battery reading was at 100%.
I distinctly remember thinking 'This is impossible. There's no way it could be 95% before the install, and 100% afterwards'.
I played around with the phone a bit (to try out Jelly Bean), and after a few minutes, the battery reading dropped to 60% or something.
That's when I knew something was wrong.
Since then, the phone battery reading has been erratic. If I plug it into a charger, it takes a few minutes and then shoots up to 100%. Unplug it, and it drops to a low level within minutes, and then goes up and down like a yo-yo. Twice, the phone went to a very low level, and then shut itself off.
I've tried various charging/unplugging cycles, and nothing has worked yet (Although I didn't have the patience to try an 8-hour charging cycle yet).
Please see the attached images to see what I mean.
The graphs are just bizarre.
I also did a factory reset (from the Privacy menu rather than 'recovery') but that didn't help.
At the moment, I haven't tried to root the phone or unlock the bootloader. I am still keeping the option of warranty open.
I can't think of a reason why this is happening. It doesn't seem to be a simple calibration or battery stats issue. I think the battery is working okay (because it was fine before the upgrade), just that the readings are wrong.
The phone is operating okay in all other respects. If I ignore the battery readings and the 'low battery' alerts, the phone continues to work ... except when it shuts itself down.
Another theory could be that ... because I upgraded without plugging the phone in, perhaps there was insufficient power during the upgrade and caused some corruption, and I have a faulty software/firmware? Not sure how I could test that though.
Any ideas, any one? Please?

Possibly related:
[Q] Randomly auto shutdown (battery problem)
http://forum.xda-developers.com/showthread.php?t=2195878
[Q] New phone battery jumping after JB
http://forum.xda-developers.com/showthread.php?t=2198772

MemendF Ranck
Looks like other people have a similar problem too.
Battery Fluctuation and Random Power off after JB
h t t p s:// forums.motorola.com / posts / cd3c7d3210

Jelly bean download issues
Hi, I have had exactly the same problem after downloading jelly bean. It even died when plugged in charging. As I had only had the phone for three weeks, I took it back to the shop, Phones 4 You, and they exchanged it for a new phone and told me not to download jelly bean until they let me know it's safe to do so. They said that it was a software problem. Prior to this the battery life was outstanding and I am very pleased with the phone. Phones 4 You gave me an excellent service.

Fixed!
For future readers ...
Someone on the motorola forums (see second reply on this thread) mentioned a possible solution which was to manually install the Jelly Bean version again. I decided to give this a try.
After some more research, I discovered that it should be possible to manually apply official Motorola (ie. OTA) updates using the stock bootloader (via the bootloader recovery feature). No unlocking, no root needed.
I gave this a try ... downloaded the software (keeping to the same version), placed it on an SD card, went to recovery and selected 'Updated from external card' (or something like that) and followed through ... and it has worked (Although this time I kept the phone connected to a usb cable throughout the upgrade). My battery readings are back to normal again. I didn't lose any data or apps as a result of this 'manual upgrade'.
And I am presumably still under warranty since I didn't root nor unlock the bootloader.
Other readers may consider trying this for themselves, however, I cannot guarantee that it will work for them. I can only say it worked for me.
Some references:
How to enter stock recovery in JB (razr i)
http://forum.xda-developers.com/showthread.php?p=38873652
(Apparently entering into stock recovery differs slightly between ICS and JB.)
The Unofficial Thread of Official OTA Updates
http://forum.xda-developers.com/showthread.php?t=2028814
I used the software package from the first post of this thread, labelled as 81.5.39001-91.2.29001.Retail.en.GB 4.0.4-4.1.2 (even though the filename is Blur_Version.81.5.39001.XT890.Retail.en.GB.zip).

I don't have the phone yet (supposed to get it tonight) but having read quite a bit it seems Moto suggests a factory reset after upgrading to JB in order to sort out battery drain etc. I think I saw it in the battery stats thread in RAZR i general.

I send my Razr I back to Germany (living in The Netherlands myself) yesterday! Had the same problem, only my battery get down to 0% all the time, so the phone shutsdown itself every 1 minute till 1 houre. (I'm from the topic: Auto shutdown (battery problem). I think i get my new one next week on wednesday. Dus the JB software manualy update works for more people?

mo976 said:
I don't have the phone yet (supposed to get it tonight) but having read quite a bit it seems Moto suggests a factory reset after upgrading to JB in order to sort out battery drain etc. I think I saw it in the battery stats thread in RAZR i general.
Click to expand...
Click to collapse
I think the problems described in this thread are relating to strange battery spikes in percentage and not a general drain of battery.
The problem is that everyone seems to be different. Some people report these spikes, some people are reporting high drains (which turning off google now or factory reset seem to fix) and some people (luckily me!) have had no issues at all - just an even faster phone

I did do a factory reset, though not immediately after the first JB upgrade. It didn't help.
I think describing this issue as battery drain or high battery usage is not quite correct. The battery is actually okay*, but the phone's indication of the battery capacity jumps all over the place (and sometimes causing automatic shutdown). I can see how it can be confused with battery drain though, especially if people only observe the reading going down (but didn't see the reading going up).
* At one point, I kept the phone screen on as an attempt to drain the battery. I got about 6 hours screen time (ignoring the intermittent battery low warnings) before I gave up.
Since I now have a phone with JB which is working, my guess is that this bug may not occur in all phones with JB. Instead, it seems to be triggered by something that happens during an upgrade.

OTA to JB on xt890 = battery problems
flashsam said:
I think the problems described in this thread are relating to strange battery spikes in percentage and not a general drain of battery.
The problem is that everyone seems to be different. Some people report these spikes, some people are reporting high drains (which turning off google now or factory reset seem to fix) and some people (luckily me!) have had no issues at all - just an even faster phone
Click to expand...
Click to collapse
i have the same problem. factory reset did not help me and i feel i made a mistake i have choosen this phone.i had motorola mobiles before even bought one to my wife.i know that motorola has a conservative atittude.i thought giving them a last chance now i know it was a mistake

Thanks bengtan.
I was having similar issues and a manual install of JB appears to have solved the issue.

Have you had any luck fixing your phone? I have the same problem since a few weeks ago. Bought a new battery and tried two calibration programs, but the issue persists.

Same here. I am on KK 4.4.2 and have the problem since yesterday. What to do?

Same here, my ROM is cm-11-20160524. After 3 years of usage I thought it's the battery and replaced it with a new one but the issue persists.

This is very odd, I'm here after my dad has the same issue and it looks like I'm the 4th poster to report the issue within 50 days after the thread hadn't any replies for over 3 years! Did any of you recent posters resolve the issue? I had a spare Razr-i and my dad took it to a phone repair shop where they swapped both batteries and the issue was still the same with the other battery, so it seems it's nothing to do with the battery itself for all the posters here so far.
Was there some recent update that spiralled all the phones into the erratic behaviour recently I wonder?
I'm trying to advise my dad what to do:
Try fix the issue on his current phone and keep using relatively old tech phone
Use my spare phone (same type) and keep using relatively old tech phone and try sell old XT890 for parts
Upgrade to brand new phone with latest tech and do him for a few years longer than the XT890 would.
Any feedback appreciated!

The issue flatened a bit now. After 2 weeks of brave usage the phone keeps the charge now normally with rare drops in between. So it's still not on an acceptable level but improved magically. I do not understand the physics of this behavior.

I'm having the same strange behaviour since yesterday!!
battery level drops when pluggin the charger,
after several minutes level is jumping to 100%.
whith unplugged charger, level in general inconsistent jumping up and down...!
could this be SW related? planned obsolescence?
edit: android 4.4.2. systemversion 990.43.74.XT890.Retail.en.EU

I have the same problem following an update to JB I don't even recall authorising
I'm now looking for a copy of the new firmware: 990.43.74.XT890.Retail.en.EU to try to resolve. If anyone knows where it can be found I'd be very grateful if you could point me in the right direction...

Same problem here.
I bought a new battery. No changes.
I than did a complete wipe, unlocked the bootloader and installed CyanogenMod 11 (this one http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855). No changes.
I than completely drained the battery (made sure of it) and left it on the charger over night. Now I don't get those weird spikes, the battery just drains really fast (about an hour an the phone is powering off).
Maybe I try a different ROM, or go back to KitKat

I found this but I dunno how to use it ??
h t t p s : / / forum .xda-developers .com /showpost.php?p=69816145&postcount=39
android 4.4.2. systemversion 990.43.74.XT890.Retail.en.EU

Why does this happen?! Battery annoyance.

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.

Nook HD battery issue but only on custom rom. Any fixes?

Hi,
I own a Nook HD Hummingbird tablet that on a custom rom experiences battery issues. The original battery was replaced after a issue caused unexpected shutdowns at 50% battery even on a stock rom. Now the new battery appears to give a good 4-5 hours on stock with no apparent issues. However when running a Cyanogenmod 13 build by @amaces the device or OS doesn't seem to know when to shutdown. I'll get the device to 1% then the device will last another 30 minutes or more with the low battery warning. Sometimes I'll see the battery percentage magically increase to 10% or more with reflecting results in the battery graph you can view in settings although I did not plug the Nook into any power source. When the device is truly out of battery it will just go off, no "power off" popup or any indication of a clean shutdown. This worries me that I might loose data unexpectedly if I go long enough without being able to plug the Nook into a power source. Does anyone have ideas why this maybe happening and any possible workarounds or solutions?

If you carefully check out the CM13 thread where you got your ROM from, you will find a couple of posts describing a solution for most battery woes. It essentially goes something like this: The battery status area in the hidden partition or folder has become corrupted. Wipe everything. Install the stock rom and stock recovery. Boot into the stock recovery and reset to factory settings. Boot the system and let it settle - this stock rom has some extra magic in it that apparently does something in the system and hidden partitions to re-create the hidden battery status sections that can become corrupted by repeated ROM installing. the stock OS may or may not be required to populate it first time around. I played safe and let it reboot fully as this only cost 15mins with no effort from me.
After it has settles from the re-boot you can run-down the battery to test the behaviour if you wish. Otherwise you can now reflash TWRP and re-install CM13.
I have paraphrased a little, but this is the gist of it. I suggest you search the CM13 thread for "battery woes" or something similar to get the exact details.
It worked form my HD.

Does CM13 on your Nook HD shutdown properly on low battery? I wonder because after all the resetting I performed on my Nook HD I still see the issue of CM13 not shutting down properly when battery is low 1%

You beat me to this one. That's pretty accurate paraphrasing.

Nougat Causes Random Reboots

Ever since I flashed the OTA my N6 has been having random reboots and battery life issues. The reboots happened three times today and all three times happened when the phone was just sitting next to me.
I originally had the WiFi problem where it wouldn't connect to anything until I reset the network settings. A factory reset didn't work for the WiFi issue. I am not rooted and just running stock with encryption.
Android OS is using a lot of the battery as well. You can see the three times today where it rebooted from the attached screenshot.
Any idea what is going on and how to stop it? So far Nougat has been horrible for me when I didn't have problems like this with the marshmallow upgrade.

as a rule of thumb avoid otas, always go for flashing the factory image via fastboot when available , in my experience otas=trouble
Sent from my Nexus 6 using Tapatalk

Endbringer42 said:
Ever since I flashed the OTA my N6 has been having random reboots and battery life issues......
Click to expand...
Click to collapse
I've had the same battery issue. I think it has to do with the data partition. I did not a full wipe when upgrading to Nougat.
Settings - Battery - 3dots -> Battery optimization, and manually optimize all apps for battery use.
When you upgraded without a full wipe -> consider a clean reinstall with a full wipe.

NLBeev said:
I've had the same battery issue. I think it has to do with the data partition. I did not a full wipe when upgrading to Nougat.
Settings - Battery - 3dots -> Battery optimization, and manually optimize all apps for battery use.
When you upgraded without a full wipe -> consider a clean reinstall with a full wipe.
Click to expand...
Click to collapse
All of the apps are setup for Doze. I did a factory reset after installing the OTA, which didn't seem to help. Also, I hooked up the charger last night at 1 am. It's now 6:50am and it only charged from 10% to 82% in that time. I never had issues like this before.

I did a clean install, I had to because it was from a custom rom, but it's been working perfectly for almost a week. If it had some problems they would have shown by now. No wifi trouble, no battery draining.

Endbringer42 said:
All of the apps are setup for Doze. I did a factory reset after installing the OTA.....
Click to expand...
Click to collapse
I noticed that your screen consumed 38% of the battery. That's very much in 15 hours.
Is it possible that there is something magnetic in the neighborhood that is constantly switching the screen on and off. This may happen with cases with magnetic closer.

NLBeev said:
I noticed that your screen consumed 38% of the battery. That's very much in 15 hours.
Is it possible that there is something magnetic in the neighborhood that is constantly switching the screen on and off. This may happen with cases with magnetic closer.
Click to expand...
Click to collapse
It was that high because I was trying to figure out what was going on. I ended up this morning doing a complete wipe and reflash of the factory images instead of the OTA. So far it seems to be stable, except the WiFi constantly is dropping strength and jumping back. Not sure what's causing that one.

what most people dont ever consider.. it can be your personal setup thats causing reboots on nougat.

simms22 said:
what most people dont ever consider.. it can be your personal setup thats causing reboots on nougat.
Click to expand...
Click to collapse
I use minimal apps, on a fully stock setup. I haven't tweaked anything, so how would that cause the reboots?
After reflashing the full factory images yesterday morning I did not have any random reboots. However, when I plugged in to charge last night, using the original cable and charger, it took over 3 hours to go from 55% to full. This was happening before the full flash, but only after Nougat. The other night it went from 10% to 68% in 6 hours. Quick charge doesn't seem to work in Nougat anymore.

Still getting this? Put stock nougat image on mine and experiencing random reboots. Going to try pure tomorrow, hopefully that resolves it.

Mine quick charges fine on a clean factory image install of Nougat. Battery life doesn't seem great but I'm still letting it settle and not sure how old this device is I picked it up off Craigslist the other day
Sent from my Nexus 6

OctoberNexus said:
Mine quick charges fine on a clean factory image install of Nougat. Battery life doesn't seem great but I'm still letting it settle and not sure how old this device is I picked it up off Craigslist the other day
Click to expand...
Click to collapse
Try Franco kernel I think he has added a fix for this