Database Develop

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.

Since last flash I have had absolutely bullsh!t awesome battery usage :-) *READ*

Ok...this is going to sound completely outrageous! It seems outrageous to me even I have never had this good of battery consumption ever! The phone was purchased 16/08/10 and has retained the standard battery all this time and had various Samsung ROMs on it. Mostly DarkyROMs that have improved battery quite considerably. It currently has its first stable ROM of ICS since I started flashing ICS from just prior to RC1. The ROM is a bit of a mix-matched frankenstein build of a ROM by me originated from MyICS and OneCosmis RC3.1. I have recently experienced allot of issues (including very poor battery drain) prior to this last flash and so have many of my users...actually most jumping **** (and I don't blame them).
My last ROM flash seemed to stable and go through perfectly, I was running with my own 2.0.1 and was about to release this ROM (that I'm currently on from a system dump) as a 2.2.0 version update for everyone else.....however I have held back because of the announcement of RC4.....so any of the improvements I haven't released. The install procedure backs up battery stats so as not to need re-calibration and has done so for the last 3 or 4 install. I am running the latest platypus kernel made for RC4 though
Anyway the last time I had my phone on any decent charge 22hours ago. It's currently 10.40pm EST and phone went on charge about 12.30pm lastnight. Since then I have had data left on (something I wouldn't normally do...I was used to renaming APN prior to ICS) and wifi on* (granted I have latest Juice defender ultimate)
*set to trained locations to auto-on within 250m of known wifi access point and disable 3G when wifi connected
I have gone the whole day today, with a small amount of internet (damn genie widget gets me every time with cool interesting things flashing up on the screen lol) and moderate phone usage; texting and a hand full of 10-15min phone calls....nothing out of the ordinary.
I plugged the phone to USB to transfer some things from work and it was plugged in for approximately 15-20seconds. I use multi-mount SD card app (I have included the lite version in my ROM) and allows for fast transactions and also to be able to use the phone whilst connected etc (read up about it). And I did the same here at home to transfer the things off again. It has remained sitting beside my PC untouched (unusual cause I like to fiddle) for the last 3 hours...and decided to pick it up and glaced at the battery 90%. Ok so I waited another hour and glanced again and STILL 90%.
Is there something weird going on here that I should know about? My phone has never been this good even if I left it completely on standby and in flight mode it would have eaten more than that! It seems almost stupidly impossible.
Fill me in on your take of this situation? Happy to do a complete system dump to try figure this sh!t out cause I made so many mods last ROM update I wouldn't know which one is contributing or if all or none?
edit: included more information

It's now 2:20am I am going to bed. My phone is 86%
A drop of only 4% in nearly 4hours. 1% per hour is not too bad

How do you handle synchronization, and why kind of tweaks do you perform with juicedefender?

heh i know what you mean
Im using as well icssgs rc4 (pulled) for 3 days, and right now i have 10% left after 29 hours of using my phone as wifi, downloading, sync, calls, sms and some music, all i can say is that rc4 +platypus kernel is the beast for the battery. my phone never lasted for such a long time, even on rc3.1 it used to die after 18 hours of being idle.

Reporting
7am 77%
10am 62%
10.55am - poor signal and market prompted to download an update for LinkedIn battery has plumited to 23%
36hours use and still 23% battery is pretty good. At least the resil
I will be making a deodexed version of RC4 sometime soon with a few extra bonuses ....however it won't be all that special as I have been giving away my secrets everywhere on the forum to help others on any ROM (not just my own) so anything included in my next release will be old news lol
Juice defender? Tweaks? I am not sure what you mean? You mean what are my settings?

Ok...wtf? Battery is climbing back up again now? That is something that has never happened before! Im on 26% again

realy ? ))

Offfical time of death 4.34pm EST. approximately 40hours after full charge. I am stoked with that.
Edit: I will be making a donation to Platypus Kernel right now

Can you tell which rom you had before flashing rc4 and another question are you experiencing any other problems with the rom like sd problems because im considering to go rc4 too.

dimon28 said:
Can you tell which rom you had before flashing rc4 and another question are you experiencing any other problems with the rom like sd problems because im considering to go rc4 too.
Click to expand...
Click to collapse
I am still running RC3.1, I am just using the RC4 kernel
I am in the process of developing my own RC4 ROM based off this RC3.1 (my own version of it anyway) that is the first ROM I have that is stable. All versions of my ROMs prior to this have been very unstable. ROM is still odexed so that will be my first point of call and then repackage and get it up and running.
I am in the process of compiling some java code for wifi calling on vibrant though so I am too busy to even start on my ROM

[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!

Shutting down problem

Hi,
I'm experiencing this problem more than 1 month. I'm on CM10 with kowalski kernel. It seems my phone sometimes wrongly read battery status and drop battery level percentage from some value to 0 immidiatelly...and shut down occurs at the moment. I thought it could be caused by old battery, but it's not - I buy the new one and the problem still persist and it's VERY irritating...Any solution?
Thanks Jiri

Hello,
It happens also for me but only when I am around 15% and when somebody call me sometimes it fail down sometimes.
It seems that the deep sleep do not allow the system to read a correct battery value when screen came back and the system shutdown because of a too low voltage.
I did not found any solutions in several type of ROM.
Mike

This is a known problem..if i remember correctly tonyp and pengus will fix it in the neew 4.2.2
Sent from my LG-P990 using xda premium

But it's annoying as hell, for me, it starts when my batter is on 50% and low.... 5 - 10 times a day a have to turn on my phone...I cannot use alarm at all....

Andy HOT said:
This is a known problem..if i remember correctly tonyp and pengus will fix it in the neew 4.2.2
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Mmmhhhh I actually cant remembet them stating that it will be fixed. I remember tony mentioning that its a low priority rom bug. It might be fixed with 4.2.2 but i am not really sure. Regarding the issue I do experience it too but only once every few weeks.
Sent from my LG-P990 using xda app-developers app

I also have this shut down problem. A lot. Maybe 5 times a day and its also driving me nuts. Mine does not happen while phone is in charger - so its probably the "battery reporting wrong charge" problem. Im on new bootloader. I've seen it go from over 50% to 0% battery in an instant.
It might have happened before but much less frequently than now. I started noticing the problem a few weeks ago on Pengus CM10 rom with kowalski kernel (before reading about it). I reflashed the kernel a few times and upgraded the kernel once or twice during that period.
I switched to PA 2.6 - 10 without improvement (KK-116). No apps installed (except Antutu)
I even had the problem in TonyPs TWRP 2.4.3.0 when trying to backup my rom once. Phone shut down while running the backup. Plugged wall charger in while phone still being off and saw that i still had battery left - probably 30-50%. The LG charging graphics icon showed this (you know, the one that shows up if your phone is off and you plug in the charger).
I Tried the following using AIO v5 tool without luck:
1) Reintalled unlocked ICS bootloader
2) Reverting to Old bootloader / partition - then back to new bootloader. Then installed ROM.
I have also tried installing Django Manouche X 1.6.1 (KOB 0.7 kernel) and running Antutu a few times (right after first boot + reboot) with the same result: shutdown. No apps installed.
I can always reproduce the issue: run Antutu benchmark 1-5 times in a row manually on battery. Plugged in, this does not happen.
It happens with or without OC/UV.
I havent tested it extensively, so I cannot be sure, but it seems to me that the rom/kernel isnt the problem since it also happened (once) in TWRP. Could it be the bootloader? Granted this is only a guess, since i have NO knowledge of Android programming or inner workings. Or maybe this is what happens when the LG battery is dying? I got the phone just as it came out.
Edit: BB 30A

I guess i have the same problem but either worse or something totally different.
Regularly around 70%, my battery just drops to 0% and my phone shuts off. It can happen anytime for me and it usually happens just after about 10-15mn of using my phone.
This morning it shut off at more than 90% and then got stuck in a bootloop i presume because it says it doesn't have battery.

Update:
I tried reflashing 30A BB. Didnt help.
Tried Django Manouche X 1.6.1 with kernel without zRAM or ramhack mod. Didnt help.
I Also tried PA 2.6 - 11 on old bootloader, and the battery-jump shutdowns continued when running antutu.
Flashed (completely stock - no rooting etc) ICS 30A with 30A BB through AIO v5. Didnt help. No tweaks or apps (except Antutu) installed. On Antutu run number 5 the phone restarted (with bootloop). Had about 36% battery. Pulled battery, rebooted, phone shut down before booting ROM. Plugged in charger, booted into ROM, showed 100% battery for 10 seconds before showing 30% battery. Tried with quadrant and 30% battery: phone shut down on run 2. Pulled battery, rebooted. Messed around with camera and gallery for 5mins at 26%: phone shutdown.
Im totally lost ... if its not the battery (as indicated by the first post (OP)) i have no idea whats going on. Maybe some other piece of hardware inside the phone is to blame. A piece of hardware that is only called upon when on battery and not when on charger. Maybe a power regulator (or some such thing) is broken?
Next test: Stock GB with GB BB
Edit: Well, the GB ROM + GB BB didnt work either: Gueste2X GoodBye v2.0R + 20L BB rebooted at 75% battery running Antutu. It showed a pop up about low battery and shut down shortly after. For the first time the battery icon still showed 75% when it shut down though.. And this time it showed 21% (not the usual 0% battery) when rebooting to ROM.
I think Im throwing in the towel regarding the software.
My dad also has an o2x, so i will try and swap the batteries and test both phones. I will ofcourse run antutu several times on my dads phone before swapping the batteries..

Update 2:
So i tried my dads O2X battery in my O2X. I Ran Antutu quite a few times and my phone didnt shut down. So I'm pretty certain my battery is messed up which is the reason my phone shuts off "randomly" showing a sudden 0% battery.
Through a google search i found a guy stating that the battery often starts "bulging" when its messed up like mine. His test was to lay the battery flat on a hard even surface and spin the battery. If it keeps going for a couple of seconds it might be messed up. My battery is definitely "bulging" and spins for much longer than my dads. His spins for less than a second. Mine spins for maybe 2 seconds. Not very scientific, but i could definitely see a difference. And i can see the excessive bulging on my battery if i look at it from the side.
So Im ordering a new battery tonight - the originals dont cost much thankfully.
Hope my walls of text can help others in the same situation.

Last update (promise):
Got the new original battery today. Charged it to 100% and used my phone for various tasks until the battery hit 70%. (This was my old batterys absolutely certain "breaking point" when running Antutu benchmark. On my old battery Antutu would crash on first or second run every time when battery is at 70%.)
On the new battery i quit running Antutu after the 13th run in a row without a "battery low" shutdown. The battery was at 40% after the 13th run.
I lay the old and the new battery flat on my smooth metal mousepad and spun them around. The new battery spun for less than 1 second. The old battery spun for almost 4 seconds on one side - almost 3 seconds on the other side.
Two working batteries (my dads 2+ year old battery and my own brand new one) performing equally and at the same time differently to one defective battery. It lends some credence to "the guys" theory that battery defects might result in "bulging" of the battery.
Which means, your battery can be defective but not "bulge". If however, your battery is "bulging" something likely is or will be defective. Fantastic knowledge to posess, if true.
It might seem like a "well duh, thats obvious" revelation, but Ive held my old battery in my hands a lot the last 2 years (especially lately) and I did not notice the "bulging" at any time.

JB update screw up

Just thought I'd pass along my experience with upgrading to JB.
I have an international GT-N7000 which I was running the last ICS from Samsung, and with the Speedmod .13 kernel.
I never flash anything other than an official release.
I updated via pc-odin to the April DBT version downloaded from Sammobile.
After updating, I uninstalled SU, then loaded the Speedmod kernel for this release (LT4), via pushing it through recovery.
After rebooting, the splash screen lit up, then went blank, but the sound continued. NO video, or button lights.
Pulled battery, no go. I then downloaded (what I thought) was the Philz kernel for this version, rebooted. Everything
came up, along with the nags about not being rooted for some reason. I turned around to do something, and noticed
that 2-3 minutes later the battery was down 15% than 2-3 minutes earlier, and, the back was WARM. Pulled battery,
rebooted, still no go. Reflashed the entire machine, pushed Philz for (what I thought) this version (LT4), rebooted,
and again, slow, battery diminishing, back warm). Ran quad, score was 1/2 of what it was before the flash.
Did some more checking and there it was, I didn't upload the CORRECT kernel. Once I downloaded the CORRECT
kernel, rebooted, charged it up, and the back is not warm, battery sips juice, quad score back where it should be.
With all the roms, kernels floating around, might want to WAIT til daylight to update, instead of after a long day
at work, dealing with idiots, and before 10pm at night...ESPECIALLY if you are in your 50's
That or grab some red bull or something, and double check those kernels.
Might help someone dealing with battery drain, slow, freezing displays, poor quad scores etc...