Database Develop

[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] Gingerbread - Android OS taking up MASSIVE battery life, not USB bug-related

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

[Q] My Awful Battery Experience

The battery life on my NC is absolutely horrible. I average 3 hours unplugged, 1 hour if I'm using it. It doesn't seem to charge up all the way -- after plugging it in the light on the Nook cord is orange for about 10 minutes then goes green even though the screen still stays "Not enough power to turn on - Try again in 15 minutes".
I've tried using software like juicedefender and other battery mon apps that are supposed to be able to predict when you're going to lose your power -- but they appear to be useless. Often I'll get the "Your Battery is Getting Low" message at the very same time as the "Shutting Down" dialog appears -- almost like there was a very sudden dramatic drop in available power.
I am beginning to wonder if it's the result of faulty hardware.
Has anyone else experienced problems like these? Or should I restore back to stock and send it in for warranty?

That definitely sounds abnormal. I'd probably restore it back to factory and if it's still acting like that, you'll know it's not due to any modifications.

Yeah, I second that. Mine drains pretty quickly, I go from 100% to about 60% in a day with normal usage. I use Wifi Auto Toggle to turn Wifi off when the screen turns off. So far I have to recharge every other day or so. But what the OP has going on sounds pretty extreme.

What ROM are you using?
What programs have 'keep screen alive' do you run?
How bright is your screen?
Screen/wifi burn most of the power in this - so minimizing them helps battery life considerably.
I had one game (HexDefense) that prefers to run in maximum brightness and burned through the battery very quickly. Nook was the warmest I've ever seen it and the temperature on my battery monitor actually moved for the first time ever.
SO if you're getting 3 hours doing nothing, that's bad. If you're getting 3 hours running a really processor/graphic intensive game, that's good.
If you can get it back to stock and still have low battery life, consider talking to the manufacturers about it.

OverDrive33 said:
The battery life on my NC is absolutely horrible. I average 3 hours unplugged, 1 hour if I'm using it. It doesn't seem to charge up all the way -- after plugging it in the light on the Nook cord is orange for about 10 minutes then goes green even though the screen still stays "Not enough power to turn on - Try again in 15 minutes".
I've tried using software like juicedefender and other battery mon apps that are supposed to be able to predict when you're going to lose your power -- but they appear to be useless. Often I'll get the "Your Battery is Getting Low" message at the very same time as the "Shutting Down" dialog appears -- almost like there was a very sudden dramatic drop in available power.
I am beginning to wonder if it's the result of faulty hardware.
Has anyone else experienced problems like these? Or should I restore back to stock and send it in for warranty?
Click to expand...
Click to collapse
You really question this? Something is wrong with your NC, cable, or charger.

Dead Battery - Was 80% less than 18 hrs ago and not in use

Went to use my Nook Color today and battery was completely discharged. Showed 80% the previous night.
Not sure if something on RC1 could have done this. Put RC1 on my SD card this past weekend and it had been working fine except for dropping wifi.
Search not working so don't know if anyone has experienced this.

I had a similar experience, almost fully charged one night and left in the nightstand drawer.... next night the battery is dead, so dead it wouldn't turn on until I put it on the charger. I wondered if maybe I left it in the drawer with one of the buttons pressed on something... but maybe this is some kind of bug? Also CM7.1RC1. I see there have been a lot of updates committed since RC1 was released so I'm thinking about upgrading to the nightly build tomorrow. http://cm-nightlies.appspot.com/?device=encore

Me Too
I have CM7 also (7.3). I have noticed several times when I fully charge my nook, use it for a short while and then come back the next morning to find it fully discharged. It doesn't seem to matter if I just let it natural go to sleep or if I hit the power button one time to force it to sleep. Again, it doesn;t always do it but it happens about half the time after charging.

My phone suddenly shut down

Hello deer XDA friends
My phone suddenly shut down by it self every 3-4 days sometimes when the battery above 50% , when i try to booted up it wont until i remove the battery then it start normally .
what do you think is the problem here?
sorry my English is very bad

Eltoro2010 said:
Hello deer XDA friends
My phone suddenly shut down by it self every 3-4 days sometimes when the battery above 50% , when i try to booted up it wont until i remove the battery then it start normally .
what do you think is the problem here?
sorry my English is very bad
Click to expand...
Click to collapse
You might have some rogue apps running that overheat the cpu. Look in taskmanager which apps are using much power. Download cpu spy free from the market to see if the cpu comes in deep sleep or not.
Good luck

I also have it occasionally. POWER+HOME button to reset. One time need to remove battery. Actually I felt like phone is still open but screen cannot come back. Next time I will call my phone when it happens.

I've had this happen twice. Both times a battery pull fixed it. At first I thought the phone was going dead, completely black and the power button would do nothing, but the second time I hit the volume button several times and it started beeping, so even though it looked completely dead, it was still turned on. I don't know what the problem is, but probably something software.

Which ROM/kernel are you using?
Any special CPU profiles?
How's the temperature?
Sent from my GT-N7000 using XDA App

happened a few times too. So, last time when I found it "dead" I did some test.
1. used my bluetooth headset (MW600) tried to play music, surprisingly music started playing but screen cannot turn on by any keys.
2. I called myself using another phone, Caller can hear ring normally and the call NOT dropped to voice mail, however my Note doesn't ring at all, screen still cannot turn on by any keys.
So it doesn't look like it's auto switched off by overheating, seems like unable to completely wake up after deep sleep.
Phone using Stock Rom(rooted with CWM), with System Power Saving mode turned on. I suspecting it's related to the power saving mode.

I'm also stock 2.3.5 rooted, with CWM, but do not have system power saving turned on. I haven't noticed any heat, but haven't monitored temperatures.

Do you also have the stock kernel?
Are you using setCPU?
Try using cpuspy, from market.
Sent from my GT-N7000 using XDA App

Dead
I also had this case yesterday for the first time. I bought it the 30th november.
Did not want to wakeup, darkscreen. Only way to recover was to remove battery. I am on 2.3.6 french.
I do not use Setcpu.

Mine is unroot. In other words, stock ROM and kernel.
I think it is software problem. And I think it is either Samsung software or Android system. Someone need to run logcat though.

For your information.
When you sure it's sleep dead(not shutdown cause by no battery)
Disconnect any charger/USB connected. Press and hold the power switch for around 10-15 sec,
that will restart the phone, no need remove that inconvenient back cover for battery pull.

alexchan.ccs said:
For your information.
When you sure it's sleep dead(not shutdown cause by no battery)
Disconnect any charger/USB connected. Press and hold the power switch for around 10-15 sec,
that will restart the phone, no need remove that inconvenient back cover for battery pull.
Click to expand...
Click to collapse
The first time it happened to me I tried holding the power button but it didn't work, so I did the battery pull. I haven't tried again since then.

Sudden Shutdown
Mine too i've experience it 3 times, this happen when im opening some applications sudden black screen and restarted cannot access back button, haven't tried the power button. It just restarted thats it!!! Im at stock kernel unrooted 2.3.6 so what do you think guys should i root or just wait for Ice Scream Sandwich upgrade?

maxh said:
The first time it happened to me I tried holding the power button but it didn't work, so I did the battery pull. I haven't tried again since then.
Click to expand...
Click to collapse
See if you hold the button long enough for over 10 seconds, before I would release and think power button not work after 7-8 seconds.

I have experienced "sleep of death" many times on different firmware versions. I has never happened since I flashed KL3. I'm on AbyssNote 2.1 kernel.

update:
since I replaced the stock launcher & locker, no more sleep dead issues. I suspect the problem source is stock locker or some stock widgets. Also, battery last longer too.
now using: widget locker + awd launcher ex + multi-picture live wall paper.

For those wonder why phone can't wake up for some reason, a user at the green power app forum had got the solid evidence.
http://greenpower.pouzerate.com/ind...-s2-freeze--black-screen?limit=6&start=48#465
"And if then it looks like the touchwiz launcher has crashed and changed pid when restarting without telling the InputManagerService about it, so it can't wake up the screen for that reason."
So the culprit is the stock launcher. And this matched with my experience even after I uninstalled green power free, my phone still have "not waking up" problem . But since switched to use 3rd party lock and launcher for a month, the "not waking up" never happens again.

This happened to me for the first time yesterday, when I eventually got it restarted by removing the battery, it was at 88% so don't think it was overheating, otherwise it would be much lower. Also I had Go launcher Ex running so touch wiz unlikely to be the culprit. Maybe some widget, I have loads!

alexchan.ccs said:
For those wonder why phone can't wake up for some reason, a user at the green power app forum had got the solid evidence.
http://greenpower.pouzerate.com/ind...-s2-freeze--black-screen?limit=6&start=48#465
"And if then it looks like the touchwiz launcher has crashed and changed pid when restarting without telling the InputManagerService about it, so it can't wake up the screen for that reason."
So the culprit is the stock launcher. And this matched with my experience even after I uninstalled green power free, my phone still have "not waking up" problem . But since switched to use 3rd party lock and launcher for a month, the "not waking up" never happens again.
Click to expand...
Click to collapse
This actually fits well with my experience. Touchwiz crashes on me occasionally and just last night I was experiencing the sleep of death thing. This time I thought it might have been the battery, so plugged in the charger and that somehow woke the screen back up to show touchwiz in the process of starting up, caught red handed!

This has happened to me as well 3 times, and every time it has been related to using a highres picture on the stock locker. It would lag out on unlock, black screen of death, which i would have to batt pull to fix. Didn't realize i had to hold down the power button for 15 secs to achieve the same thing. Have since switched to a low res pic on lock screen and haven't experienced the issue since. Will try the alternative locker solution if it happens again.