Database Develop

Battery sucking down fast

I've got my autonootered 1.1.0 NC and it is working great. The only thing is the battery seems to be running out really fast on this. On my wife's autonootered 1.0.1, the battery isn't running out nearly so slow and we have all the same apps, although some of mine, since it's newer, may be more recent versions.
One thing I noticed is that she has very little time on "Android system", whereas 2/3 of the drain on mine is from that. The only apps that typically run though are advanced task killer and batter indicator. I regularly shut down everything else.
I've also renamed phone.apk and the telephony(something).apk on both of them as well.
Is there anything that will deep dive into "android system" on battery use? There are no rogue apps running (at least according the task killer). Or any suggestions?

First thing I'd suspect are live wallpapers followed by widgets. Verify that you have a plain wallpaper and remove any widgets that you would anticipate are doing frequent polling of any kind. I'd remove that battery indicator one and see if that helps.
Sent from my nook color using Tapatalk

Running zeam with plain nook wallpaper (just like on my wife's nook). No widgets. Am seriously wondering about the battery use thing though.

doncaruana said:
The only apps that typically run though are advanced task killer and batter indicator. I regularly shut down everything else.
Click to expand...
Click to collapse
Like I suggested, uninstall that battery indicator app. You didnt mention which one it is so for now based on the only info youve provided thats the only advice I can give.
In one test I did on my nookie froyo install I'm running, I tried a new spruced up kernel and ran a battery status widget. The widget caused the nook to stay out of deep sleep and also out of lower clock speeds when idle resulting in horrible battery life.
Are you running setcpu on either or both nooks and if so are they set the same?
Sent from my nook color using Tapatalk

Try systempanel lite task manager by nextapp in market. It might help show ram and cpu usage of things.
Sent from my nook color using Tapatalk

When not using wifi turn it off. That will save you some battery life as well.

Keep the suggestions coming
The battery app is "battery indicator". It is usually running on both nooks, but mine has a more recent version I think (this is my main suspect right now).
We always kill the wifi when not using it, so I know that's not it. Also not running setcpu on either.
I sucked down probably 5-10% while just reading with only "advanced task killer", "battery indicator", and the stock reader running for less than an hour last night.
I'm going to try systempanellite and see if that tells me anything. Also going to charge it up to 100%, boot into CMR and reset the battery stats.
If it is the battery app, wondering how to find the older version to downgrade to, or maybe just find a different one, I suppose...

45 minutes of simply reading and went from 99% all the way down to 88%. No battery utility. Systempanellite (only running for a few of those minutes) didn't really show anything sucking either.
Only other difference I can think of now is that I disabled OTA updates on my wife's nook.
I wonder if I just got a bad nook, battery wise...

doncaruana said:
45 minutes of simply reading and went from 99% all the way down to 88%. No battery utility. Systempanellite (only running for a few of those minutes) didn't really show anything sucking either.
Only other difference I can think of now is that I disabled OTA updates on my wife's nook.
I wonder if I just got a bad nook, battery wise...
Click to expand...
Click to collapse
So ~10% from about ~1 hour of use? Might be a little high for just reading, especially if your brightness is low and your wifi is off. However, I note a 10% per hour discharge with average use. I get about ~2% or so overnight loss with screen off and wifi off.
Rooted 1.1, Monster root pack. Overclocked with Dalingrin's kernel.

Looking at the two nooks, side by side, I notice that on mine, AFfileDownloadService and CloudService are background, while on my wife's, they are 'Service'. When DeviceManagerService is running, that is also background on mine and service on hers.
Could that be why the "Android system" is sucking so much battery? SystemPanel doesn't show anything sucking cpu....
I know it's supposed to be around 10 hours, but that works out to be about 7 hours reading a small, simple epub, which has me concerned.
I did lower the brightness on mine to match my wife's exactly. It was less than halfway, but heres was lower, right in between the two esses at the end of 'brightness'.

A more deliberate test shows 1% drain every 5 minutes (almost exactly) while just reading. That's a little over 8 hours and still less than I expect. Maybe I need to tweak the brightness a little more...

[Q] Phone Signal and Battery Drain -- is there a correlation?

Hello Everyone,
I am new to the forum, but not totally new to rooting and flashing ROMs. I have a MT3G (second android phone to come to the market...yes I'm old school ), rooted and flashed CM7-Gingerbread 2.3.3 and it's working very well.
I also managed to buy a NookColor, immediately rooted it and flashed phiremod nook v5.1. and everything is very good. My Quadrant Score is 1485
However, what I've noticed is that if I compare the battery usage on mytouch 3g vs the nookcolor I see something interesting and I think it might have to do with the overall battery drain I've noticed on the nook....I'm hoping someone here can shed some light.
When I go to my settings > about tablet > battery use, I can see a graph on the top. If I click it, it shows a nice relationship between time (x-axis), battery % (y-axis) and underneath it are 5 variables (Phone Signal, Wi-fi, Awake, Screen on, Charging). These variables are key because you can see what is really draining a battery.
See the two attached images. One is from mytouch 3g and the other is the nook. What you can see is that when my nook is sleep, it drains a lot faster than MT3G and in fact what you see is that the PHONE SIGNAL is constantly on, where when my MT3G is sleep, the PHONE SIGNAL IS NOT....
Is there a way to completely remove this 'phone signal'...I suspect we can get more battery life out of our nook if we can just remove this!!!
Thanks for reading.

easy to do if you have adb.. otherwise use terminal.
rename the following files in /system/app
Mms.apk
TelephonyProvider.apk
Phone.apk (phone will keep forceclosing.
reboot.
If you are not using adb, just force power off using the power button.
When it comes up, you will have much better battery life.

Yeah, I saw that posted somewhere, and I've done that. So does the phone signal still appear on yours after you renamed it?
I wonder if this procedure is enough.....

labrazil said:
Yeah, I saw that posted somewhere, and I've done that. So does the phone signal still appear on yours after you renamed it?
I wonder if this procedure is enough.....
Click to expand...
Click to collapse
Enough to remove Phone from being listed in Spare Parts? Yep. It won't change anything.

CM7 is really bad with the battery. It doesn't sleep properly. The phone or lack of phone has nothing to do with it. It doesn't have a cell radio after all ;-)
Apparently there is a bug and it crashes or something? when it sleeps. I read that the devs just disabled sleep until they can get it fixed. I think that will probably happen after video is all working.
It still easily lasts through the day with a fair bit of use though. I just charge every night instead of every third ;-)

ylixir said:
CM7 is really bad with the battery. It doesn't sleep properly. The phone or lack of phone has nothing to do with it. It doesn't have a cell radio after all ;-)
Apparently there is a bug and it crashes or something? when it sleeps. I read that the devs just disabled sleep until they can get it fixed. I think that will probably happen after video is all working.
It still easily lasts through the day with a fair bit of use though. I just charge every night instead of every third ;-)
Click to expand...
Click to collapse
Okay, so it's safe to assume that the devs are working on this for future ROMs/Kernals? I really like my nook even though I just got the wifi-xoom today.

There's already been a 20+ page thread on this, where comparitive testing found no actual diference in battery life by removing those functions. The result is a purely cosmetic change where the power consumed under "cell standby" is shifted to "phone idle" or something else, I forget exactly. Any perceived improvements in battery life are a placebo effect and/or simply the result of the variables in different day-to-day usage.
Removing them also causes Market problems with certain apps not showing up due to "incompatibility" with devices lacking those functions, which I suspect is why they are not removed in the first place.
The NC's "high" power drain on CM7 is because it's not allowed to actually sleep due too a kernal bug which prevents it from reliably waking up. This will get fixed eventually. Right now, "sleep" simply turns off the screen.

[Q] Nook Color Battery Use question

When I look at my autonooted Nook Color's battery use option from the NookColor Tools app, it shows that something called "Cellular Standby" has used up 86% of all power used by the battery.
Is "Cellular Standby" the name the Nook Color uses to identify the wireless connection? If it is, that's OK. I know wireless sucks up a lot of juice.
If it isn't is there a way to shut off the Cellular Standby? I'd hate to think of all that power being used for no good reason.
Thanks!
Nook Color Stats:
Purchased with 1.1.0 software from B&N. Used Autonooter 3.0 to root the device. No updates since then.

When I was in Customized Nookie Froyo (SD version 4), it was named 'Wireless'.
On Customized Nookie Froyo (SD version 6), it is named 'cellular standby'.
I'm hoping you are correct and it's just a misleading rename.

That seems a bit strange, because in normal usage, maximum power is always used by display, but it can be true if u are just streaming music on your nook or if u left it unused for a few days and left the wifi on.
Otherwise that's something i would never expect to see on my nook.

rigy73 said:
That seems a bit strange, because in normal usage, maximum power is always used by display, but it can be true if u are just streaming music on your nook or if u left it unused for a few days and left the wifi on.
Otherwise that's something i would never expect to see on my nook.
Click to expand...
Click to collapse
My wireless and display usually duked it out for top honors of battery usage. Of course I tend to run with my display all the way down in brightness and I'm banging on the wireless a lot when I'm doing set up (and having to redownload 20-30 apps from Market and Amazon).
I'm still wrestling with Nookie Froyo Custom a bit, at least the v6 release.

Instant charging?

Okay, this thread is probably misleading. This could be a bug, nothing more.
When I complete a build and then push it over the USB I have noticed something funny.
If I keep the cord attached when I flash, when the nook finishes booting, my battery gets reported as 100%. I can't say for sure that it happens everytime, but nt happens pretty often, at least.
It's pretty hard to tell, but it really seems to get 100% charged. The battery doesn't seem to drain any faster.
Now, I haven't checked it with any serious discipline. Maybe the nook would just shut off at 30% or whatever. Maybe it just reads the percentage it was at previously as 100% at this instance. Maybe its hard to tell if the nook just drains 15% faster. Maybe who knows what.
But its happened several times, and it sure seems to be 100%. I've checked all the levels in Battery Monitor Widget. (Science!)
So what do you think? Did my nook develop cold fusion or did I discover a misleading bug?
You can see the voltage jump in the attached screenshot. It jumped from about 80% to 100% in maybe ten minutes. I've seen jumps much more extreme.

I've had it happen to me too when I connect my nook to the pc with the usb cable. It will only jump to 100% if the battery level (for me) is above 80% when I connected it. Cold fusion, man I wouldn't be surprised with everything that's been done to it. I found when you reboot right after it jumps to 100%, it will drop back down to to what it was.

Yeah, mine maintains the charge level after reboot. At least, it reads as charged still.

I'm saying bug, not that it couldn't be cold fusion Obviously there are a few things you could do to see what is happening but I think the fun experiment would be to run down to something like 20% and then try what you have been doing. If you go from 20% to 100% it shouldn't take very long to see how it runs down if it is a bug.
Maybe it will correct and show 15% very quickly, maybe you'll see the percentages drop like seconds on a clock as it reports accelerated discharge or maybe you'll get a low battery warning at 95%! I am curious to see what it does.
Most likely it will just be wrong and shut down when it doesn't have enough juice without really giving any indication what it is doing. But we can hope for something more exciting
JP

Okay, I just had it happen again, and it is happening during adb push,
Maybe my computer is sending the update and throws in 1000 mAh as a tip.
Does this happen to anyone else?
Now that I think I know when it is happening, I will try and replicate it when the nook is at 25% or so. Then I will collect my noble prize. (If b&n tries to claim it, you guys will have my back, right?

mateorod said:
Okay, I just had it happen again, and it is happening during adb push,
Maybe my computer is sending the update and throws in 1000 mAh as a tip.
Does this happen to anyone else?
Now that I think I know when it is happening, I will try and replicate it when the nook is at 25% or so. Then I will collect my noble prize. (If b&n tries to claim it, you guys will have my back, right?
Click to expand...
Click to collapse
Interesting thread. I think it would be a noble prize rather than a Nobel as I suspect even B&N haven't found a way round the laws of physics.
I suspect the battery calibration is somehow getting mangled during the push somehow. What is quite interesting is that the battery monitor widget screenshot does show the charge at 100% whereas the battery voltage has only recovered a little bit. As the previous history indicates one should be getting close to 4200mV when the battery is really fully charged. Li PO batteries normally show a reasonably linear discharge curve from about 4200 at 100% down to about 3600mV when they are exhausted.

What, does the noble prize not have as much money, or something?!? Grumblegrumbleauto-correct-grumble...
I have wiped battery stats, rebooted a couple times, and have been using the nook...now at 93%.
It was at 78-80 before the miracle.

i personally would try using the Die Hard battery Calibration script and see what happens...

Yeah...you thought this thread was dead, but no.
Although I am unfortunately beginning to lean away from it being cold fusion. This time it happened upon connecting to ADB, no push or anything. That does kind of sounds Ike a bug.
But I did leave the whole history up for your perusal since the miracle energy. It's been a couple hours maybe. I was around 80 when it happened and I am just back to that level now.
You can see by the green portions, I noticed the miracle battery increase after I disconnected and it happened again upon reconnect a few moments later. Although to a much smaller degree as I was still running on a magical-miracle full charge.

I posted about this a while back.
With some microUSB cables, connecting the NC to a PC will munch the battery stats file and show instant 100%. You then have to leave it and let it charge fully and reset the battery stats using a battery calibration app or some other method. This happened to me using more than one micro USB cable, but I have several that do not do this. Given the pain it is to fix this problem, I just decided not to ever connect my NC to the PC again... wireless ADB and manage it over wifi instead.

Yes, there's some weird bug with this, it's been this way since day one. You'll see the level drop off drastically in steps.... It'll look normal, then boom, -10%, normal for a while, boom, -10%, etc...

Ah, so it just comes out in big chunks. I was wondering how it would eventually have to account for the discrepancy.

I had forgotten about this thread, sorry. But the heart remembered, so I have one last screenshot.
I never could actually catch the device catching back up, it seemed to just ease its way into it, if at all. But the other day I had the "instant charge" happen again. Later I flashed an update and left it in CWM for a couple hours. After flash, the system corrected itself. Have a look, the flat line is CWM.
I think I may have to return my noble prize.

[Q] Battery level issues

Battery can be at 90% in a blink of an eye drop to the point of a warning pop up showing 1 percent battery life, then shuts off.
If I plug it in battery level is back up where it should be.
Sometimes shutting it off for a few minutes & restarting battery level comes back up or just plug it in, level jumps right back up then unplug it, level stays up.
This problem has been going on for awhile, at first it was just hit & miss, more of minor annoyance, but now it is a royal pain in the behind.
As long as I am where I can plug it in for a minute or so I can still use the tablet. Kind of hard to do when reading at the gym though
I am running CM 11 on it, but I don't really think this is what the problem is since I have been CM 11 since it first came out & this problem started about 2-3 months ago. I tried wiping the whole system & started over with nothing but the bare minimum on the tablet & issue with battery level was still present.
Somebody my wife works with had this same issue with their Nook HD+, but luckily his was still under warranty and B&N replaced it.
I don't have that option.
Any ideas on fix for this issue other than buy another tablet?
Help or suggestions are greatly appreciated.
Thank you,
Mark

snoozer854 said:
Any ideas on fix for this issue other than buy another tablet?
Click to expand...
Click to collapse
I would've bought a new tablet 2-3 months ago. lol ...Unfortunately, mine keeps on going.
If you really want to see if its hardware, then try stock bn rom and check for issue.
You could also try full power discharge to full charge (several times) and see if it helps. I would try the bn rom first though as that's the most drastic difference.
And if it gives up on you along the way, c'est la vie.

sandsofmyst said:
I would've bought a new tablet 2-3 months ago. lol ...Unfortunately, mine keeps on going.
If you really want to see if its hardware, then try stock bn rom and check for issue.
You could also try full power discharge to full charge (several times) and see if it helps. I would try the bn rom first though as that's the most drastic difference.
And if it gives up on you along the way, c'est la vie.
Click to expand...
Click to collapse
Yeah I would have bought a new one 3 months ago, but takes money, due to health reasons something I do not have.
Tablet actually other then the battery issue works great.
Thanks for your suggestions though.
I was just curious if anyone else has come across this issue & any possible solutions.
Sorry to have taken up your time.

I solved this problem. To do this, disconnect and reconnect the battery cable. Now the battery is discharged smoothly. Battery life 8-10 hours

salexdv said:
I solved this problem. To do this, disconnect and reconnect the battery cable. Now the battery is discharged smoothly. Battery life 8-10 hours
Click to expand...
Click to collapse
Works sometimes doing this other times doesn't.
Problem seems to be getting worse.
In the beginning doing what worked for you would take care of it, but not any more.
Thanks for the suggestion though.
Sent from my BN Nook HD using Tapatalk

I had similar issue back in March. I read somewhere that it is battery cable connection/cold-solder problem. I opened up my nook and unplug/re-plug in the battery cable, didn't work. And then I taped a few layers of TP on top of the connector so that the back cover of the nook is supporting the connector. The battery discharge was back to normal since, but unfortunately it started to happen again last week.
snoozer854 said:
Works sometimes doing this other times doesn't.
Problem seems to be getting worse.
In the beginning doing what worked for you would take care of it, but not any more.
Thanks for the suggestion though.
Sent from my BN Nook HD using Tapatalk
Click to expand...
Click to collapse

V.I.P. said:
I had similar issue back in March. I read somewhere that it is battery cable connection/cold-solder problem. I opened up my nook and unplug/re-plug in the battery cable, didn't work. And then I taped a few layers of TP on top of the connector so that the back cover of the nook is supporting the connector. The battery discharge was back to normal since, but unfortunately it started to happen again last week.
Click to expand...
Click to collapse
Might have to take a look at that.
Thank you for the suggestion
Mark

Mark:
I had the same problem, with battery charge level appearing to fluctuate wildly. In the end, I fixed it by doing a full discharge followed by a full recharge.
You can't do a full discharge while running the normal ROMs, because they will shut down the Nook automatically when the charge level starts to get low. Instead, run a CWM ROM and let it sit until the Nook dies for lack of power. Then plug in the battery cable and leave it until the charge level returns to 100%. In my case that took quite a few hours.
Since doing that, I haven't had any repeats of the problem.

Delta^1_1 said:
Mark:
I had the same problem, with battery charge level appearing to fluctuate wildly. In the end, I fixed it by doing a full discharge followed by a full recharge.
You can't do a full discharge while running the normal ROMs, because they will shut down the Nook automatically when the charge level starts to get low. Instead, run a CWM ROM and let it sit until the Nook dies for lack of power. Then plug in the battery cable and leave it until the charge level returns to 100%. In my case that took quite a few hours.
Since doing that, I haven't had any repeats of the problem.
Click to expand...
Click to collapse
That is a bad idea the Nook does not like to recharge once it has been drained to that point.
Sent from my SPH-L900 using XDA Free mobile app

Delta^1_1 said:
Mark:
I had the same problem, with battery charge level appearing to fluctuate wildly. In the end, I fixed it by doing a full discharge followed by a full recharge.
You can't do a full discharge while running the normal ROMs, because they will shut down the Nook automatically when the charge level starts to get low. Instead, run a CWM ROM and let it sit until the Nook dies for lack of power. Then plug in the battery cable and leave it until the charge level returns to 100%. In my case that took quite a few hours.
Since doing that, I haven't had any repeats of the problem.
Click to expand...
Click to collapse
I am running CyangenMod 11 & battery drops from 100% to 1% whenever it feels like it. Plug it in for a second & level shoots back up to were it should be for a while then it does it all over again.
If the rom you are talking about is what I have installed I have tried & tried to run the battery completely down, but it is impossible.
Long as I have charging cable handy to plug it in things are fine.
Thanks for the suggestion.
Mark

snoozer854 said:
I am running CyangenMod 11 & battery drops from 100% to 1% whenever it feels like it. Plug it in for a second & level shoots back up to were it should be for a while then it does it all over again.
Mark
Click to expand...
Click to collapse
My Nook HD+ too have this problem after updating to Snapshot11 OTA. Currently it is unusable without the cable being connected to the power. Also have the ghost click/automatic click problem, where the touch events automatically registered without me even touching the screen. Waiting for the Snapshot 12 and hope that this will be corrected in the update.

mashac said:
My Nook HD+ too have this problem after updating to Snapshot11 OTA. Currently it is unusable without the cable being connected to the power. Also have the ghost click/automatic click problem, where the touch events automatically registered without me even touching the screen. Waiting for the Snapshot 12 and hope that this will be corrected in the update.
Click to expand...
Click to collapse
Mine has been doing it for awhile, just seems to be getting worse. If it is a rom issue I wish it would get fixed.
I am running the 10-24 nightly. This is the same release I am using on my wife's Nook HD & she is not having this issue.
Not seeing the auto click issues.

snoozer854 said:
I am running CyangenMod 11 & battery drops from 100% to 1% whenever it feels like it. Plug it in for a second & level shoots back up to were it should be for a while then it does it all over again.
If the rom you are talking about is what I have installed I have tried & tried to run the battery completely down, but it is impossible.
Long as I have charging cable handy to plug it in things are fine.
Thanks for the suggestion.
Mark
Click to expand...
Click to collapse
I was talking about CWM, not CyanogenMod. CWM is the ROM you use for making backups and installing Cyanogen in the first place. CWM will let you run the battery down to a very low level.

Delta^1_1 said:
I was talking about CWM, not CyanogenMod. CWM is the ROM you use for making backups and installing Cyanogen in the first place. CWM will let you run the battery down to a very low level.
Click to expand...
Click to collapse
Duh, should ave realized that was what you were talking about.
Sorry about that.
Will do it tonight & hopefully this solves it.
Once again thank you for your time
Much appreciated
Mark

Delta^1_1 said:
I was talking about CWM, not CyanogenMod. CWM is the ROM you use for making backups and installing Cyanogen in the first place. CWM will let you run the battery down to a very low level.
Click to expand...
Click to collapse
snoozer854 said:
Duh, should ave realized that was what you were talking about.
Sorry about that.
Will do it tonight & hopefully this solves it.
Once again thank you for your time
Much appreciated
Mark
Click to expand...
Click to collapse
It was probably confusing because CWM isn't a ROM, it's a recovery. If we get our terms and definitions right we will be more easily understood.
Not trying to pick a fight, just pointing out that communication is easier when we all have the same jargon.

bpaulien said:
It was probably confusing because CWM isn't a ROM, it's a recovery. If we get our terms and definitions right we will be more easily understood.
Not trying to pick a fight, just pointing out that communication is easier when we all have the same jargon.
Click to expand...
Click to collapse
I know what the terms mean. I just was tired & made a very simple mistake in my reply.
I know that CWM is recovery I have used it plenty of times for the past 2 years since I have owned my Nook HD.
My only mistake with terms & definitions was replying & answering a question when i should have been sleeping.
Want to pick a fight, bring it own! Just kidding you. I only do that in person, not behind a screen. Been a few years, but what the heck.
OK back to the topic at hand. Doing a full discharge in CWM recovery, didn't seem to do the trick. Tried unhooking battery & rehooking no go there either.
I do not believe it is a rom issue, since my wife works with a guy who had the same issue with his Nook that had the B&N setup still intact.
rom.
Plus I am running the same rom on my wife's Nook HD problem free.
Once again thank you very much for the suggestion I really do appreciate it.
Mark

salexdv said:
I solved this problem. To do this, disconnect and reconnect the battery cable. Now the battery is discharged smoothly. Battery life 8-10 hours
Click to expand...
Click to collapse
Didn't work

Seems to be others with this issue. I have tried removing battery cable, doing a complete battery drain in recovery, then full recharge. Problem is still there.
I am almost tempted to revert back to stock rom & see if problem goes away, but seems to be a bit tricky with the newer CWMrecovery installed.
Have gone through so many threads on reverting back to stock, I am more confused now then before.
I know I can't restore stock with the version of CWM that I have, but for the life of me I can't figure out how to revert back to the older version of CWM recovery, so I can flash the stock img.
I have the links for the dummies guide and I am sure what I am looking for is there, but as was mentioned here before I need to get with the program & use correct terms and the more I read this the more confused it makes me.

snoozer854 said:
Seems to be others with this issue. I have tried removing battery cable, doing a complete battery drain in recovery, then full recharge. Problem is still there.
I am almost tempted to revert back to stock rom & see if problem goes away, but seems to be a bit tricky with the newer CWMrecovery installed.
Have gone through so many threads on reverting back to stock, I am more confused now then before.
I know I can't restore stock with the version of CWM that I have, but for the life of me I can't figure out how to revert back to the older version of CWM recovery, so I can flash the stock img.
I have the links for the dummies guide and I am sure what I am looking for is there, but as was mentioned here before I need to get with the program & use correct terms and the more I read this the more confused it makes me.
Click to expand...
Click to collapse
Go to my HD/HD+ CWM thread linked in my signature and make a new bootable CWM SD per item 1a and then use that to flash the plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
Go to my HD/HD+ CWM thread linked in my signature and make a new bootable CWM SD per item 1a and then use that to flash the plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thank you, not sure if this will solve the issue, but I got the time to give it a shot.
What's your thoughts on this battery issue?
I have a funny feeling it is hardware related.
Once again thank you for all of your help
Mark