Database Develop

[Q] Something is wrong with my N1...

Over the past 12 hours I've had to pull the battery 3 times...
The phone was running fine all day (and generally is always very stable for the months I've had it). I put it down last night before I went to bed and when I picked it up again for some bedtime browsing the screen wouldn't come on. I pressed both the trackball (I have CM6 on it) and power button, nothing. I then plugged it in (I knew it was low, but not low enough to power off) and nothing, no light, nothing. I then got a touch scared. I pulled the battery, put it back in and it rebooted. It was fine for the rest of the night...
I plugged it in for the overnight, and when I woke up the light was still orange. The screen again wouldn't turn on. Battery pulled, it rebooted, and it was usable (full charge). I left the phone alone for about 20 mins (unplugged) and now it's back to being unable to turn on the screen.
- I've had CM6 final on it since soon after release with no issues
- I generally use Pershoot's kernels and I think (think) I updated to the latest .35 kernel yesterday. Again, I've never had an issue really in the past
- Updated TBA Pro, added the screen calibration apk, and removed quick office.apk via Root Explorer.
That's about it for "new" stuff I did yesterday.
Gonna put on Pershoots latest .34 kernel (I really don't think that's the issue) and see if that makes a difference (I always use the .35 kernels). I also wiped the dalvik cache. If that doesn't work, I'll remove the calibration app.
Any other opinions? Possible battery pooched? I charge it nightly, but other than that there hasn't been an issue. Certainly would be the first time I killed a battery in a phone...

tomedic said:
Over the past 12 hours I've had to pull the battery 3 times...
The phone was running fine all day (and generally is always very stable for the months I've had it). I put it down last night before I went to bed and when I picked it up again for some bedtime browsing the screen wouldn't come on. I pressed both the trackball (I have CM6 on it) and power button, nothing. I then plugged it in (I knew it was low, but not low enough to power off) and nothing, no light, nothing. I then got a touch scared. I pulled the battery, put it back in and it rebooted. It was fine for the rest of the night...
I plugged it in for the overnight, and when I woke up the light was still orange. The screen again wouldn't turn on. Battery pulled, it rebooted, and it was usable (full charge). I left the phone alone for about 20 mins (unplugged) and now it's back to being unable to turn on the screen.
- I've had CM6 final on it since soon after release with no issues
- I generally use Pershoot's kernels and I think (think) I updated to the latest .35 kernel yesterday. Again, I've never had an issue really in the past
- Updated TBA Pro, added the screen calibration apk, and removed quick office.apk via Root Explorer.
That's about it for "new" stuff I did yesterday.
Gonna put on Pershoots latest .34 kernel (I really don't think that's the issue) and see if that makes a difference (I always use the .35 kernels). I also wiped the dalvik cache. If that doesn't work, I'll remove the calibration app.
Any other opinions? Possible battery pooched? I charge it nightly, but other than that there hasn't been an issue. Certainly would be the first time I killed a battery in a phone...
Click to expand...
Click to collapse
That happened to me once when I installed one of IR's .35 kernel. I reverted to pershoot's and all was fine. (IR's new kernels are fine too)

ctbear said:
That happened to me once when I installed one of IR's .35 kernel. I reverted to pershoot's and all was fine. (IR's new kernels are fine too)
Click to expand...
Click to collapse
Ya, maybe... I put on the kernel in the morning though and all was fine all day. I installed his latest .34.7 kernel and wiped dalvik cache. So far so good...

Cheers, had the same issue and sofar this seems to have fixed it

[Q][Help] Bricked after running out of battery?

My NC had the following done to it:
Auto-Nooter'd (Most recent revision)
CWM installed
900Mhz OC kernel
I left it idle overnight and it ran out of battery. After getting the usual "Battery too low, wait 15 minutes" screen, I forgot about it. Came back an hour later and now it won't boot past "Touch the future of reading" screen.
I can't get into CWM until the grey 'n' screen, and right now I'm thinking it's bricked. Did I do something wrong? Do you think B&N will replace it like it is (Moral dilemmas aside)?
I have a backup and everything, I just didn't expect this type of situation to arise.
Thanks for any help!

Plug it in the wall for a while. Have you tried booting with Nookie on an USD?
Sent from my HTC Desire using XDA App

Link3737 said:
My NC had the following done to it:
Auto-Nooter'd (Most recent revision)
CWM installed
900Mhz OC kernel
I left it idle overnight and it ran out of battery. After getting the usual "Battery too low, wait 15 minutes" screen, I forgot about it. Came back an hour later and now it won't boot past "Touch the future of reading" screen.
I can't get into CWM until the grey 'n' screen, and right now I'm thinking it's bricked. Did I do something wrong? Do you think B&N will replace it like it is (Moral dilemmas aside)?
I have a backup and everything, I just didn't expect this type of situation to arise.
Thanks for any help!
Click to expand...
Click to collapse
NC favors booting from uSD (as in, it will prioritize booting from the microsd before booting from the internal memory, B&N gets serious love from me for this). It's really really hard to brick. Like you have to be trying to brick it. Boot from a nookie SD and start troubleshooting from there.

Link3737 said:
My NC had the following done to it:
Auto-Nooter'd (Most recent revision)
CWM installed
900Mhz OC kernel
I left it idle overnight and it ran out of battery. After getting the usual "Battery too low, wait 15 minutes" screen, I forgot about it. Came back an hour later and now it won't boot past "Touch the future of reading" screen.
I can't get into CWM until the grey 'n' screen, and right now I'm thinking it's bricked. Did I do something wrong? Do you think B&N will replace it like it is (Moral dilemmas aside)?
I have a backup and everything, I just didn't expect this type of situation to arise.
Thanks for any help!
Click to expand...
Click to collapse
Okay so am I missing something, or were you intentionally trying to drain the battery? I don't get this...
Anywho, my wifes NC I found seems to have stayed on after unplugging it the other day and the battery drained, but today it is fine. BTW, took almost exactly 12 hours for it to shut itself off. 8.3%/hr, or 333mAh to sit idle with the screen on.

[Q] Battery discharges when off and slow boot

Hi all,
Just rooted by Nook Color with CM7 and I 2 fairly major problems. I searched threads but could not find anything specific to my specific problems.
First, last night, I turned off the Nook Color by holding down the button on the left and selected "Power Off". When I booted it (after a long wait, see below), it booted but the battery was very low and I checked the battery life settings using Spare Parts app and it said it had been Running 100% of the time since last unplugged. Its as if it didn't power off when I asked it to.
Second, my reboots are super slow....I get the "Read Forever" words when I hold down the left button but it takes several minutes before I have to press the bottom button to get the screen (no indication that its booting or anything).
Any help would be greatly appreciated.

Why are you shutting it down at all? Just let it sleep. Even with the current sleep issues, it will only use 1% or so of the battery that way... try it. I hardly ever power off my nook. As for the slow boot time, there are a lot of reasons...
1. Did you install the OC kernel and forget to wipe dalvik cache?
2. Which version of CM7 are you running? a nightly, or the 7.0 release?

I just did a test.
CM7 cm_encore_full-63
update-CM7-dalingrin-OC-emmc-040411 set at ONDEMAND 300-1100
At 2am battery was at 100%
Standby for 9.5 hrs and it consumed 16% battery.
Not looking good to leave in standby.

Do you leave wifi on? It could be syncing or trying to sync the whole time it is on standby.

xdatoast said:
Hi all,
Just rooted by Nook Color with CM7 and I 2 fairly major problems. I searched threads but could not find anything specific to my specific problems.
First, last night, I turned off the Nook Color by holding down the button on the left and selected "Power Off". When I booted it (after a long wait, see below), it booted but the battery was very low and I checked the battery life settings using Spare Parts app and it said it had been Running 100% of the time since last unplugged. Its as if it didn't power off when I asked it to.
Second, my reboots are super slow....I get the "Read Forever" words when I hold down the left button but it takes several minutes before I have to press the bottom button to get the screen (no indication that its booting or anything).
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If you powered off your NC, it would not be using battery.. Period. Running 100% of the time is normal right now on CM7, but again, it was not running while it was powered off.
Slow boot? Are you using an SD card? If so, get a new one that's faster.

[Q] Phone turns off when charged

So it seems that my phone won't stay on when fully charged. If i leave it plugged in, once it gets to 100% it will shut itself off. I recently upgraded to CM10.1 nightly and have tried 3 different days. I've also found something about using setCPU, but that didn't seem to help either. Also, i can't turn it back on unless it is unplugged from the wall.
To make things worse, i noticed today that when i turned it back on (it turned itself off over night), it was at only 7% battery life. So now i have no idea what is going on.
Thoughts??

Griff43081 said:
So it seems that my phone won't stay on when fully charged. If i leave it plugged in, once it gets to 100% it will shut itself off. I recently upgraded to CM10.1 nightly and have tried 3 different days. I've also found something about using setCPU, but that didn't seem to help either. Also, i can't turn it back on unless it is unplugged from the wall.
To make things worse, i noticed today that when i turned it back on (it turned itself off over night), it was at only 7% battery life. So now i have no idea what is going on.
Thoughts??
Click to expand...
Click to collapse
SoD.
There are quite a few things that can trigger it (like deep idle) but first I'd need to know what changes/mods you made.

So i was running CM 7 when decided to finally update to 10.1 nightly. That was major change and it started happening. Last night i downloaded setCPU, and configured that to keep minimum @ 200MHz when screen is off (hoping to keep it running and not going into deep sleep).

Griff43081 said:
So i was running CM 7 when decided to finally update to 10.1 nightly. That was major change and it started happening. Last night i downloaded setCPU, and configured that to keep minimum @ 200MHz when screen is off (hoping to keep it running and not going into deep sleep).
Click to expand...
Click to collapse
Did you go back to stock and factory reset first? Also, did you restore any system app or data with TiBu?
Are you running with stock kernel? If so, you could try flashing Semaphore.

I do not have a stock kernel, but it was the same one from when i was using CM7. I also updated from CM7 to 10.1 (no from stock), but i did do a factory reset. ANd no programs were restored, i freshly installed them all from the play store. I will try flashing Semaphore tonight and see how it goes.

Griff43081 said:
I do not have a stock kernel, but it was the same one from when i was using CM7. I also updated from CM7 to 10.1 (no from stock), but i did do a factory reset. ANd no programs were restored, i freshly installed them all from the play store. I will try flashing Semaphore tonight and see how it goes.
Click to expand...
Click to collapse
Kernels for GB are quite different than for JB 4.2. When you flashed CM10.1, it most likely also flashed their stock kernel. This is what I meant by stock kernel.

any possibility that you've got a battery that is failing? or if the third pin is dirty, the power management chip could do that, even if the battery isn't fully charged. when the battery was at 7 percent after 'charging', what was the battery level before charging.
have you cleaned the batt terminals on both battery and phone?
hope this is helpful.
Sent from my SGH-I897

To make things even more confusing ... every time i reset the phone it comes up with a new battery level (anywhere from 5 to 17 to 60). new battery time?

Griff43081 said:
To make things even more confusing ... every time i reset the phone it comes up with a new battery level (anywhere from 5 to 17 to 60). new battery time?
Click to expand...
Click to collapse
Indeed, new battery time!

[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