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.
Related
Alright so I've been running the cyan nightlies, I just updated to the latest one, installed the battery fix. Everythings working fine, put my phone down for and hour and the batt is at like %75, I go under battery use and it puts the screen at 79%, is this normal? I had my screen off most of the time and when it was on it wasnt bright and if this isn't normal how can I fix it?
Have you rebooted to see if it does this after every reboot? Try rebooting normally then see if its still doing it.
If so, then reboot into recovery, wipe dalvik, then reboot normally. Check your battery stats again after a couple hours and see if it's still doing it after the dalvik wipe.
(FYI, this belongs in Q&A section)
can you link to the battery fix plz?
I have had very high display usage on every version of CM6, and you will find it is a VERY common complaint on CDMA Hero's running CM6.
Everyone says it's because Froyo is more efficient, and uses less battery overall, so your display percentage is higher.
I call B.S. on that. I have had poor battery life with the more than 20 nightly versions I have run. I have had the Hero since the day before it came out, and I have never had worse battery life. I even bought a new battery thinking my battery was dying on me, and I still won't make it through a day (7 am - 11 pm) without plugging the phone in during the day.
My guess is there is something up with the display/lights/light sensor drivers that have been implemented in CM6 that don't allow something with the display to sleep properly. Either that, or the battery usage screen is simply completely inaccurate.
I could literally reboot my phone, leave it untouched with the screen off for four hours, then turn on the screen for one minute, and the display usage would shoot up to 50-75%. There is no way one minute of screen usage is using more battery than 4 hours of phone standby using the radio, checking email/twitter/facebook/gmail.
Anyway, that's just my opinion on the matter. Other than the battery life, the newest nightlies of CM6 are simply incredible, so I just deal with the poor battery life.
@ziggy682 -- Thanks for that info. I haven't yet tried CM6 (mainly cuz I'm so dependent on some Sense apps and widgets), and now that I'm reading about some battery issues I may hold off on trying it even longer.
@omair2005 -- if you haven't found it yet, here's the new thread on collin_ph's battery tweak specifically for CM/darch ROMs: http://forum.xda-developers.com/showthread.php?t=762283
After updating to 2.3.3 using COS-DS, my phone seemed to work fine. I initially had a battery drain with nothing taking up large battery usage, so I reset the battery stats and all was well.
However, after unplugging my phone from charging all night (100% upon unplug), I checked my phone two hours later and saw that my charge was down to 22%. Upon checking Battery Usage, I found that Android OS is using 76%! The only thing I've done today was answer a couple SMS messages. I don't have Sync, GPS, or Wifi on, but I do have Mobiledata and 3G+2G on, as well as Background Data. The only widget I have is Google Voice, which I've removed to no avail. I've tried rebooting (twice), but it stays the same. I've turned off data, gone to 2G-only, and turned off background data, and it still continues. In Spare Parts, under Battery history it says that the only thing using up the battery is Suspend in CPU, and Battery Status says that the battery's health is good. Something really strange is that after the initial power-off upon the discovery of this issue, I immediately plugged it into the charger. After about 3 minutes I turned it back on, and found that it's already charged back up to 86%. WHAT.
Also, I haven't plugged it into the computer once in the last few days, so it's not USB-bug related. Any ideas on what's going on here?
EDIT: Ok, it's been a couple hours since this began, but just now I checked the phone (it was on the charger) and suddenly EVERYTHING is gone from the Battery Usage page, save for Display and Android OS, and Android OS is back down to 5% now. Really bloody weird, but the issue seems to have resolved itself.
I've had similar issues. When my battery runs flat, dead. I plug it up and switched it on, and it shown "Charging (32%)". I get different but similar results with different ROMs. It could simply mean the battery is wasted couldn't it?
Have you gone into the Recovery mode and wipe the Battery Status? I was having similiar issue (but not a fast drain), I did maybe about 5 wiped and reboot the phone. My problem seem to go away.
I went from 1 day or less from 100% to having to recharge, to 2 and 1/2 days then charge.
The issue came back later that night, and has been happening ever since.
I've done the bump charge + stats wipe, where I let it charge to 100%, shutdown until green LED, wipe stats, restart, let drain to 0, restart and use. I've tried this about 3 or 4 times, and the issue persists. I've removed my 2 widgets (two sound effects widgets), and it persists.
Also, I've downloaded OS Monitor, and it shows the CPU to be resting at its min, 246.
I'm hoping it's just the battery at this point, and have already ordered another one. I'll let you guys know if that fixes it.
In that case it might be your battery that need to be replace. How old is the battery?
I really have no idea. I bought this G1 used on eBay 9 months ago.
2 things to note:
1. It actually stopped booting last night even while on the charger: I restarted, and it kept getting stuck on the splash image. So I superwiped, reflashed, and the drain is still there even with no user-installed apps.
2. About a month ago, (when I was back on a stable Froyo, which I had been on since I got the phone 9 months ago) it started to randomly shut off. It seemed like if it got just a little too hot (battery got to maybe 30 C, never was able to check what the temp was when this happened), it would shut down and wouldn't get past the boot screen without a reset. I had to either charge it or wait an hour for it to successfully boot again.
In retrospect, this is sounding more and more like the battery. The only thing that's strange is that Android OS takes up such high percentage. Oh well, hopefully the new battery gets here today or tomorrow, hopefully that fixes everything.
Since you have brought the G1 9 months ago, more than likely it's had been over two year or more (about the same age as mine more or less). I doubt that the seller would be giving you a brand new battery.
I noticed the reboot on mine G1 too. Ever so often, my G1 will reboot on me. But I do not have the problem getting stuck at the splash or boot screen. But then I am using the SuperAosp ROM not Froyo.
Let me know how the new battery will work out, I might have to end up getting it myself. Eventhough my battery life got better after I did the wipe battery status, sometime it still drain depending on the day I guess.
I noticed the same result with COSDS.
I moved to Ginger Yoshi with much better results.
Better, but not as good as stock, obviously.
COSDS turned into a real hog on me by the time the second or third reboot happened.
Heeter
I'll stay with SuperAosp, I take the performance over the battery life any day. My battery status an't that bad. Once in the while I used it up in a day or less, other I can stick around for a few days.
The rebooting part was not too bad on my end. Just once in a while. Nothing I can't handle.
@ psychosonic - You might want to try that if you want, Gingerbread Yoshi was one of my first choice before I found what I had.
Alright, got my battery. After calibrating it for one day, then using it today post-calibration, it's functioning phenomenally. After using wifi + internet for a period of time, and sms throughout the day, it's still at 70% 6 hours after charge. Essentially, the only thing that drains the battery is heavy internet use, which seems to make it go down 1% per 2 or 3 minutes.
Internet usage seem to take a lot out of the battery for sure. I know mine take a lot more than 1% every 2 or 3 mins when I use my internet.
Let see how will the new battery pan out. See if it will last you 2 or more days. Keep using it as such, and see where it goes.
Android OS Battery bug
Hi!
1. Install SystemPanelLite Task Manager from the market.
2. Run SystemPanel and open settings and check the "System processes" option. Close settings.
3. Scroll down in the process list until you find the process "android.process.media". If you have a CPU usage of more then 10-30s and the process usage gauge to the left moves up and down you probably have the Android OS battery bug.
At this point you can try the following;
- Shut down your phone. (Not just turn it of. The complete shut-down-power-off-thingy)
- Remove your external SD card.
- Start up your phone again.
- When the scan media is complete, do step 3 above again. If you don't see the problem at step 3 your SD card has a corrupt filesystem. And needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Unmount SD card
- Format SD card
- Restore files from your backup.
If the problem persists your internal SD card might have a corrupt filesystem and needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Format internal storage
- Restore files from your backup.
More details; What happens when you have a corrupt filesystem is that android.process.media tries to read a file but fails over and over again. The filesystem might not look corrupt to you. And you can read and write files on the SD card without problems. But at some point the android.process.media failes to read the files and loops like crazy, draining your battery.
I had a corrupt filesystem (FAT32) on my external SD card. I also had Android OS battery usage of 60-70% and a fast draining battery. I hope this can help others.
Best regards,
/Pontus
cos & yoshi
cos dds sucks battery.... yoshi"s awesome..!! fr battery!!
if you applied a theme in theme chooser it could have affected it
I love the Angry Team rom v3.6 no issues whatsoever. But now after flashing Angry ROM v4.2 I am feeling certain issues which are very isolated incident (not reported by any of the users so far, i guess). And the bugs are
1. The charging has just gone mad. I would charge it for 100% but once rebooting the phone says that there is absolutely no power or very less (~10% - 15%). Actually I tried to wipe the battery stats, but I could not able to find that option in Philz's Kernel. Can any of the techies help me on how to wipe the battery stats and how can I get the proper stats and correct battery level again. This is very annoying for me, because I dont know even if I see the phone is fully charged, it still may not be so actually.
2. My Note phone mysteriously flickers and automatically shuts down as such flickering intensifies. If I try to connect the phone immediately to charge the flickering stops and be stable for the next 30 mins. This flicker happens even when there is sufficient charge in the phone.
3. At times I see the phone gets hanged.
3. Contacts have a horizontal stripe at top making it difficult to read the recent dialed numbers. (Probably an issue in ROM or something needs to be changed).
Any help is greatly appreciated.
Your battery is dead.. Buy a new battery
Sent from my GT-N7000 using Tapatalk 2
When using the phone the battery indicator immediately drops from whatever it was at down to %0 and the phone shuts off.
When I start the phone up into recovery (Philz) it still shows the original battery percentage that was reported before the phone shut off. I rebooted the phone back up into system several times and sometimes I am able to use it for a minute or two and then it will repeat all over again: the battery drops back to %0 and the phone reboots, other times it says %0 immediately after bootup and shuts off right away.
It's intermittent, so sometimes I can go for a week or two if I'm lucky without it happening, but sometimes I can only go a few hours without being interrupted by the shutdowns. The only thing that seems to have helped me is charging my phone a little bit more and then it stops for a while, but I don't always have a charger with me so I would like to get this issue resolved if possible.
I know my battery is charged. I was able to sit there flashing my phone over and over trying to fix the issue and the phone kept working 45 minutes and even an hour later. Sometimes reflashing my ROM after wiping system, cache, etc. seems to fix the issue, other times it doesn't work.
I have done the EB40 mod to my phone, but I haven't had any issues with it. It's possible that this problem could be related to that as well, but I'm fairly confident that my battery is in good condition.
This issue has been occurring for quite a while and I have done full wipes and reflashed several times with multiple different ROMs and kernels to see if the issue was related to a certain ROM or kernel. All of the ROMs I have tried were very heavily based on CyanogenMod I believe, so if it turns out to be software rather than hardware then that seems to be the common link.
I need my phone for my job so this is something I really need to get sorted out. I have to use my phone for debugging and testing applications.
I have searched all over the web but no one I have found in any forum was having quite the same issue as me.
Does anyone know how to solve this issue? A suitable workaround if no other solution could be found would be somehow preventing the phone from rebooting when the battery reads %0 if that's at all possible.
Here's a screenshot of my battery history from today when this happened. Notice how the battery level goes right back to where it was after rebooting.
https://docs.google.com/file/d/0B6RpWzK5OKf4SFp1TWd1aUJ4ZlU/edit?usp=drive_web
Some additional info:
My battery is still at %52 as I type this and it's still running without a problem. Battery life is great in the CyanogenMod nightlies when I'm not having this issue.
I am running the October 12th nightly. The issue started while I was using arrrghhh's kernel, and it persisted even after wiping /system, and /cache and then using just the normal kernel that comes with the October 12th nightly.
Try a different rom?
Sent from my PACMAN MATRIX HD MAXX
I have tried flashing quite a few different ROMs and this has happened on all of them. CyanogenMod, PAC, JellyBam, and ProBAM come to mind.
Have you tried wiping every thing and fastbooting back to stock?
Sent from my MB886 using Tapatalk now Free
penser said:
Have you tried wiping every thing and fastbooting back to stock?
Sent from my MB886 using Tapatalk now Free
Click to expand...
Click to collapse
No. Would that really be necessary?
I wiped /system, /data, /boot, /cache, dalvik-cache, basically everything.
This sometimes does resolve the issue temporarily, but it comes back after a while.
UPDATE: I read somewhere that this may be an issue with the battery not being properly calibrated after installation. I don't think I've ever drained the battery all the way down since I got the EB40, so I figured I'd try it.
I tried completely draining it and charging it up to %100 with the phone off and I haven't had any issues so far. Sometimes it went for a week without having issues before though, so I'll be keeping an eye on it in case there are any more issues.
I have a T713 on Android 7. Once the battery level is below about 80%, the tablet will often crash into a bootloop when switching between screens/apps (not while using one app).
When the battery is below 45% it will always crash as above (e.g. wake the tablet to home screen, see that battery is 45%, launch an app = bootloop).
The only way to stop the bootloop is to plug in the tablet. On mains power, the tablet doesn't crash.
I've done a factory reset, wiped cache (after using it a while, of course), tried Safe Mode. Makes no difference. The crash is always reproducible below 45% battery. Battery charge logging does not show any sudden drop in battery reading immediately before/at/after the crash.
The Accubattery app says the battery is at 82% health.
There are reports of similar phenomena in other threads and sites, usually attributed to the battery, but I am sceptical that this is the issue because there is little evidence that people actually solve it by replacing the battery (and the symptoms don't seem to support the basic assumption that there is a loss of power). Any experiences/ideas?
bloomer2011 said:
I have a T713 on Android 7. Once the battery level is below about 80%, the tablet will often crash into a bootloop when switching between screens/apps (not while using one app).
When the battery is below 45% it will always crash as above (e.g. wake the tablet to home screen, see that battery is 45%, launch an app = bootloop).
The only way to stop the bootloop is to plug in the tablet. On mains power, the tablet doesn't crash.
I've done a factory reset, wiped cache (after using it a while, of course), tried Safe Mode. Makes no difference. The crash is always reproducible below 45% battery. Battery charge logging does not show any sudden drop in battery reading immediately before/at/after the crash.
The Accubattery app says the battery is at 82% health.
There are reports of similar phenomena in other threads and sites, usually attributed to the battery, but I am sceptical that this is the issue because there is little evidence that people actually solve it by replacing the battery (and the symptoms don't seem to support the basic assumption that there is a loss of power). Any experiences/ideas?
Click to expand...
Click to collapse
Have you reinstalled the factory image with Odin? That would be the logical place to start.
sliding_billy said:
Have you reinstalled the factory image with Odin? That would be the logical place to start.
Click to expand...
Click to collapse
Thanks for your suggestion. The device is currently stock, unrooted. Could you tell me why using a factory image could help? (The last official update to firmware on the device was a long time before this problem appeared in March this year.)
bloomer2011 said:
Thanks for your suggestion. The device is currently stock, unrooted. Could you tell me why using a factory image could help? (The last official update to firmware on the device was a long time before this problem appeared in March this year.)
Click to expand...
Click to collapse
Like any device, who knows what has managed to get jumbled up in the image. Security patches and other updates can only overwrite so much since they are doing in place updates. Even a factory reset has to be pulling the image from the device itself where a factory image is completely clean. I know it is a PITA to set a device up again, but the fact that you can do the system stuff before installing any apps or files or anything and then see if the problem shows up immediately after imaging. If so, then you pretty much have narrowed it down to at least a hardware problem and you have less places to look (the battery for example). The last time I flashed the stock image a month or so ago, it took a security updated Feb 2019 (maybe) before I rooted and such putting it in the "modified OS" world where it will not get updates again until I flash stock again. The last actual OS update might have been around the end of 2017 beginning of 2018. Too bad since the device can clearly run builds past Nugat and has never been deprecated.
sliding_billy said:
I know it is a PITA to set a device up again, but the fact that you can do the system stuff before installing any apps or files or anything and then see if the problem shows up immediately after imaging. If so, then you pretty much have narrowed it down to at least a hardware problem and you have less places to look (the battery for example)
Click to expand...
Click to collapse
Thanks for the extra info! I'll look into doing that.
A preliminary update, in case anyone visits this thread before I finish thorough testing:
The cause is emphatically NOT the battery. After reflashing firmware and then doing a factory reset, as sliding_billy suggested above, I am unable to reproduce the problem. The tablet appears to be working fine in its current fresh state, even running on low battery power. I'm now planning to gradually reinstall apps and system updates (if any) and continue testing.
bloomer2011 said:
A preliminary update, in case anyone visits this thread before I finish thorough testing:
The cause is emphatically NOT the battery. After reflashing firmware and then doing a factory reset, as sliding_billy suggested above, I am unable to reproduce the problem. The tablet appears to be working fine in its current fresh state, even running on low battery power. I'm now planning to gradually reinstall apps and system updates (if any) and continue testing.
Click to expand...
Click to collapse
Glad that at least the initial solution is working. We'll see as you reinstall apps and complete any settings if it really was that "simple."