Database Develop

[CM7][BETA]Battery life and previous running ROM?

So if you guys running Beta 3.1 could vote and tell me if you've gotten a random shutdown at the 3X% to 2X% mark, that would be cool.
I DO NOT want you to vote if you have not discharged your Nook to at least 20%.
Refer to this post if you do not know what I'm talking about.

55 hours off charger (screen & wifi 6+ hours on)........Current battery level @ 9%. No SOD. Out of the box 1.1, straight to recovery, nand restored nightly 64, update u-loader, then Beta 3.1. On demand 300/1200.

I completely wiped the machine and went back to a fresh install of 1.0.1 and updated to 1.2 using the official B&N zip. Next used Manual Nooter 4.5.6 and ran stock rooted for a few days before flashing the beta build with OC kernal to emmc. I experienced the random shut-off/lock-up around 35% battery on the second drain. Battery life was in the upper teens on the charge before that without any issues. This has not occurred again. Although, I don't think I have let the battery get below about 50% since then. Other than this one lock-up, everything has been running great.

I went from Phiremod 6.2 to Beta 3.1 with OC kernel 300/1200 OnDemand. What option would I select here? It's definitely eMMC, but I'm unsure what the other options here mean.

Battery life is great! Although yesterday it turned off on its own when the reported charge was around 25% and could turn it back on unless plugged in. Once on, the meter was still showing ~25% battery, although the behavior was more like the one of a fully depleted battery. Another thing i'd like to note is that it seems that the charge sometimes jumps to higher %ages in less time than it should (maybe the actual charge is not reported correctly??). I'm using the Smartass governor.
Forgot to mention, I'm on CM7 2.6.32 Beta 3.1 with OC kernel, coming from nightly 64 (I think). I didn't do a full wipe, just cache/dalvik

I just experienced this and voted:
1.1->1.2, OC kernel, eMMC.
Interestingly, it refused to turn on again until I plugged it in, when it automatically booted up. Got me really shocked for a sec.
Battery level didn't change: It's still at 25%.
There's no last_kmesg, I'm afraid
EDIT: Ondemand governor

It's surprising that people that went straight from running 1.2 stock to beta are having this issue as well...

I had the issues, three times now :
1st : @ 9% 300/1200 smartass gov
2nd: @ 29% 300/1200 ondemand
3rd : @ ~14% 300/1200 smartass

ace7196 said:
It's surprising that people that went straight from running 1.2 stock to beta are having this issue as well...
Click to expand...
Click to collapse
I'm not knowledgeable about this at all, but that would seem to indicate that the kernel is doing it, right?

Didn't think twice about it yesterday when it happened, but last night right after I updated my SD boot to the beta for the first time with a clean SD card, I was testing Netflix and battery was very low but not in red and while the video was playing the screen went light gray and it was locked. I held the power button to turn it off, it rebooted and I played the videos again and it did not lock up again. Not sure if that's this issue but it seems very similar. I was using the OC kernel.

Clean install of beta 3.1 and 5.13 kernel set to 300/1200 smartass from nightly 67, 1.2 uboot this weekend. No SOD issues- left it deep sleeping for 16-ish hours yesterday with zero problems waking up. I have run the battery down below 15% a couple of times with no problems.

junkrobot said:
I'm not knowledgeable about this at all, but that would seem to indicate that the kernel is doing it, right?
Click to expand...
Click to collapse
Well...yes and no.
I've had the same issue with OC and stock. It seems to be related to the 1.2 bootloader and some weird calibration. I tweeted dal, but he's a busy man...I wonder if fattire or verygreen could give some insight?

Just tested it again via SD card with OC Kernel. Played netflix video with about 35% battery and it worked. Got a popup warning at 15% which paused the video but hitting play resumed playback. So no restart or lockup this time. Seems fine.

Previously it shut down around the 30% mark, this time around 20. This started when i updated the bootloader. The first 2.6.32 beta build was fine in this respect with the previous uboot. Doesn't seem to have anything to do with anything android uses to determine battery capacity or content.
Are there different versions of the 1.2 uboot floating around? Does reverting to uboot 1.1 fix the battery problem?

Phiremod 6.2 to Beta 3.1 with OC kernel 300/1200 Smartass. I wipe everything except data. Current battery level is 19% and I have no issue to use it.

not only 2.6.32
this is not specifically 2.6.32 related,
because I'm on 2.6.29 (OC 1.3) and CM7 Nightly #70
It happened to me also already two times
last time I'm not sure what the percentage was when it shut itself down, but after rebooting (only possible by charging the nook) it said it was at 20%
as far as I know this never happened to me with the OLD OC kernel
since the new nightlies I had to use this kernel:
http://forum.xda-developers.com/show...postcount=2382
Or is there already an "official" 1.3 OC kernel from dal?
(last time I flashed it from his site and from the app "kernel manager" my Nook refused to boot and I had to reflash either the stock CM7 one or the one posted in the link above)
it might also have to do with me updating to u-boot 1.2?
didn't happen with u-boot 1.1

Zorkman said:
this is not specifically 2.6.32 related,
because I'm on 2.6.29 (OC 1.3) and CM7 Nightly #70
It happened to me also already two times
last time I'm not sure what the percentage was when it shut itself down, but after rebooting (only possible by charging the nook) it said it was at 20%
as far as I know this never happened to me with the OLD OC kernel
since the new nightlies I had to use this kernel:
http://forum.xda-developers.com/show...postcount=2382
Or is there already an "official" 1.3 OC kernel from dal?
(last time I flashed it from his site and from the app "kernel manager" my Nook refused to boot and I had to reflash either the stock CM7 one or the one posted in the link above)
it might also have to do with me updating to u-boot 1.2?
didn't happen with u-boot 1.1
Click to expand...
Click to collapse
I think it has more to do with u-boot 1.2 than the OC kernels. With 7.03 and the latest .29 kernel I never had this issue, with the 7.1 and .32 betas and u-boot 1.2, I get the same battery issue. I fully charged my nook (green light) and then reset battery stats, we'll see what happens soon I am currently at 33% remaining.

Went from 7.0.3 with 1.1 BL (see below) to Beta3 with 1.2 BL--all on SD boot--and no problems so far. No OC kernel used, performance is set to ONDEMAND @ 925. I have discharged the battery to 7% and 18%.
FWIW, I'm using verygreen's boot method, which I believe uses a modified BL for both the 1.1 and 1.2 versions. I also recharge by shutting down CM7, ejecting SD boot, and recharging in stock 1.2 from eMMC.

Deaks2 said:
I think it has more to do with u-boot 1.2 than the OC kernels. With 7.03 and the latest .29 kernel I never had this issue, with the 7.1 and .32 betas and u-boot 1.2, I get the same battery issue. I fully charged my nook (green light) and then reset battery stats, we'll see what happens soon I am currently at 33% remaining.
Click to expand...
Click to collapse
Mine just shutdown at 24% battery left.

I've made it to 10% with no trouble. Coming from 1.2 rooted. I did wipe battery stats before my last charge. I get the green light on charge, and I hit 100%.

[Q] Having fast batt drain after installed Oversome 3.1.1

Dear all,
I just upgraded my tab into overcome 3.1 from my initial GB 2.3 . The reason why i started to discover some issue on my batt usage is within 2hrs it will take off 20% of my batt when i fully charged in the morning.
After which i check on my application - batt use - it show "display" is at 92% on the top and android system is at 2% at the bottom. Whereby when i use GB 2.3 rom, it will show andoid system is at 80~90% and display is at the bottom of 3%.
(Note: i have even set my display to the lowest and set it to Auto mode, some of the un use application i also shut down)
I have started to think should i change back to GB 2.3 or is there any brother outside can advise what should i do to change this situation. Hope someone can help me on this ..... Thanks in advance.

nikes60 said:
Dear all,
I just upgraded my tab into overcome 3.1 from my initial GB 2.3 . The reason why i started to discover some issue on my batt usage is within 2hrs it will take off 20% of my batt when i fully charged in the morning.
After which i check on my application - batt use - it show "display" is at 92% on the top and android system is at 2% at the bottom. Whereby when i use GB 2.3 rom, it will show andoid system is at 80~90% and display is at the bottom of 3%.
(Note: i have even set my display to the lowest and set it to Auto mode, some of the un use application i also shut down)
I have started to think should i change back to GB 2.3 or is there any brother outside can advise what should i do to change this situation. Hope someone can help me on this ..... Thanks in advance.
Click to expand...
Click to collapse
dear all, after further confirmed, my colleagues also having the same problem as my, I was wonder is there a bug in this version as em not sure why the consumption of the battery was so high after installing overcome 3.1

First of all, old ROM had a bug, battery usage was displayed wrong. That is fixed, but they are now working on R2 version of kernel (Reverted lowmemkiller change which may have been blocking kswapd0 from sleeping, resulting in battery leakage).
This last kernel has a new ROM as it's base, so you have to install new ROM first and then full wipe version of kernel.

Good to hear I am not the only one.
Hermes was an awesome rom concerning battery stamina. I hope the guys from Overcome will make this R2 release just as good.

Dardevil1977 said:
First of all, old ROM had a bug, battery usage was displayed wrong. That is fixed, but they are now working on R2 version of kernel (Reverted lowmemkiller change which may have been blocking kswapd0 from sleeping, resulting in battery leakage).
This last kernel has a new ROM as it's base, so you have to install new ROM first and then full wipe version of kernel.
Click to expand...
Click to collapse
Thanks for updating this good news as today I almost wanted to flash my rom again. from the moment upgraded to overcome 3.1, I have discovered this issue as I previously use g b 2.3. not sure how soon the r2 will be out ya?

Dunno that, i'm waiting too

Dardevil1977 said:
Dunno that, i'm waiting too
Click to expand...
Click to collapse
Bro, how do we got to know whenever there is a update on this R2 kind of version or we have to daily refer to this forum. Thanks in advance.

There will be new topic about it on Galaxy Tab Android Development as soon as they finish it

Dardevil1977 said:
There will be new topic about it on Galaxy Tab Android Development as soon as they finish it
Click to expand...
Click to collapse
thanks for your quick response.

The latest version of the overcome kernel is pretty good on battery life for me.. the only thing that seems to be wrong is the reported charge level against the battery display level..
Even after calibration its still way off (20%)..

Gainn said:
The latest version of the overcome kernel is pretty good on battery life for me.. the only thing that seems to be wrong is the reported charge level against the battery display level..
Even after calibration its still way off (20%)..
Click to expand...
Click to collapse
i think you need to perform a "wipe on batt" in cwm maybe can help. Anyway i also discover that my tap below 4 buttons occasionally the light will be blinking on and off during at the standby mode, i belived this also can cus some batt drain off too. Anyway, most of the people are concerning about batt duration especially devise such as non-detachable batt. For me, i use my tap outside most of the time especially during business trip hangging in the train station or airport.... Well, i think we appreciate the overcome team and the rest of you guys to test it out and gain feedback for improment.... cheerss... and Selamat Hari Raya to all muslim people ya.

did you try the tweaks here re: Battery Recalibration and Reconditioning…
http://p1000.teamovercome.net/?page_id=68
and do note that:
battery wipe by itself would not immediately “improve” your battery life. IN FACT, during the first charge cycle after a battery wipe, you might notice a slightly less than optimal battery-life! This is because, the stats have to be rebuilt, which is why after a couple of FULL charge cycles after the battery wipe, when the stats are properly “repopulated”, which is when you’ll see the difference.

eongab said:
did you try the tweaks here re: Battery Recalibration and Reconditioning…
http://p1000.teamovercome.net/?page_id=68
and do note that:
battery wipe by itself would not immediately “improve” your battery life. IN FACT, during the first charge cycle after a battery wipe, you might notice a slightly less than optimal battery-life! This is because, the stats have to be rebuilt, which is why after a couple of FULL charge cycles after the battery wipe, when the stats are properly “repopulated”, which is when you’ll see the difference.
Click to expand...
Click to collapse
yes, i have did that after going through the forum, and today is a second day after the wipe, but i would recognized that if you put the tab in Normal stanby mode, the batt will drop about 1% in about 4hrs since i have started to monitor this morning... well, i will continue to monitor aand post it again. thanks for your advise.

my one on overcome 3.3.1 seems to last at least 1 hr when the battery notification show 0!!!

I have tested my second days after batt wipe, it seem that if we put at standby mode the batt really better then earlier versions, i can notice that last night was 26% at 2.30am and this morning waikup at 7.15am, the batt indicate 24%. (Note : my wifi is on, except BT and GPS is off).
My conclusion for now is that the OC 3.1 batt life is ok and even better when it was in standby mode, however whenever any application for example browsing internet or starting reading news, the batt will start to drain off like 1% every 3min (my estimation point of view).
Hope the OC team can help to improve from here OR the nature of this OC 3.1 is normal on this circumstanses. Cheerssss....

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

CM10.1 battery issues

Im a sucker for AOSP Android Its smooth and simple just the way i like things. The only thing that keeps me going back to a Sense ROM (namely Nik Project X Rebirth and ARHD), is a slight battery issues. To put it simply, it either takes an extremely and painfully slow time to charge my phone from even 60% - 100% (about 6 or 7 hours which, if Im not wrong, should be the normal full charge of an HTC Incredible S stock??). After a week or two, the battery just screws up entirely. It takes EVEN longer than 5 hours to charge up like 20% of battery. Furthermore, it stops charging at 60% as if the battery was full!! I know this is not an issue with my battery because as soon as I flash any other ROM (thats not CM10.1 related) the battery starts charging up again. Dirty flashing CM10.1 nor clean install of CM10.1 seems to work for me
Does anyone know what the problem is and a possible fix?
I understand that I probably should be placing this thread in CM10.1 threads. I have posted in CM10.1 by dla5244 thread as well as the Lacoste thread. Yet no one has even RESPONDED to this issue.

072665995 said:
Im a sucker for AOSP Android Its smooth and simple just the way i like things. The only thing that keeps me going back to a Sense ROM (namely Nik Project X Rebirth and ARHD), is a slight battery issues. To put it simply, it either takes an extremely and painfully slow time to charge my phone from even 60% - 100% (about 6 or 7 hours which, if Im not wrong, should be the normal full charge of an HTC Incredible S stock??). After a week or two, the battery just screws up entirely. It takes EVEN longer than 5 hours to charge up like 20% of battery. Furthermore, it stops charging at 60% as if the battery was full!! I know this is not an issue with my battery because as soon as I flash any other ROM (thats not CM10.1 related) the battery starts charging up again. Dirty flashing CM10.1 nor clean install of CM10.1 seems to work for me
Does anyone know what the problem is and a possible fix?
I understand that I probably should be placing this thread in CM10.1 threads. I have posted in CM10.1 by dla5244 thread as well as the Lacoste thread. Yet no one has even RESPONDED to this issue.
Click to expand...
Click to collapse
May be Guidelines for Better Battery Life will help you

072665995 said:
Im a sucker for AOSP Android Its smooth and simple just the way i like things. The only thing that keeps me going back to a Sense ROM (namely Nik Project X Rebirth and ARHD), is a slight battery issues. To put it simply, it either takes an extremely and painfully slow time to charge my phone from even 60% - 100% (about 6 or 7 hours which, if Im not wrong, should be the normal full charge of an HTC Incredible S stock??). After a week or two, the battery just screws up entirely. It takes EVEN longer than 5 hours to charge up like 20% of battery. Furthermore, it stops charging at 60% as if the battery was full!! I know this is not an issue with my battery because as soon as I flash any other ROM (thats not CM10.1 related) the battery starts charging up again. Dirty flashing CM10.1 nor clean install of CM10.1 seems to work for me
Does anyone know what the problem is and a possible fix?
I understand that I probably should be placing this thread in CM10.1 threads. I have posted in CM10.1 by dla5244 thread as well as the Lacoste thread. Yet no one has even RESPONDED to this issue.
Click to expand...
Click to collapse
I am facing a similar issue, though not exactly. which you have mentioned, but recently my phone's battery does not charge beyond 60%; if the restart my phone, the battery charging status jumps to 80-85% and stays there..

srv.abhishek said:
I am facing a similar issue, though not exactly. which you have mentioned, but recently my phone's battery does not charge beyond 60%; if the restart my phone, the battery charging status jumps to 80-85% and stays there..
Click to expand...
Click to collapse
WTF m facing exactly same issue... itried every thing bt that dosent works...Changed rom, changed Kernel, changed Radio, twice revert to stock with locked bootloader... all waste ... I was thinkin take phone to HTC Care centre... m ****ed up... :crying:

Sandeep_Jagtap said:
May be Guidelines for Better Battery Life will help you
Click to expand...
Click to collapse
Thanks for your input but does not really help because my issue lies where my phone refuses to charge, not where my phone runs out of battery.
srv.abhishek said:
I am facing a similar issue, though not exactly. which you have mentioned, but recently my phone's battery does not charge beyond 60%; if the restart my phone, the battery charging status jumps to 80-85% and stays there..
Click to expand...
Click to collapse
I tried that. Just stays at 60% :/ it really sucks and I hope someone will find the source of this problem and provide a possible fix.

072665995 said:
Thanks for your input but does not really help because my issue lies where my phone refuses to charge, not where my phone runs out of battery.
I tried that. Just stays at 60% :/ it really sucks and I hope someone will find the source of this problem and provide a possible fix.
Click to expand...
Click to collapse
Try szeszo cm9 test tomorrow from his Google plus. It could be cm10 and incompatibility with our phone. So try cm9
Sent from my GT-I9300 using XDA Premium HD app

naathaanb96 said:
Try szeszo cm9 test tomorrow from his Google plus. It could be cm10 and incompatibility with our phone. So try cm9
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
Is there a link for the test? It would be great if you can post it here...
072665995 said:
Thanks for your input but does not really help because my issue lies where my phone refuses to charge, not where my phone runs out of battery.
I tried that. Just stays at 60% :/ it really sucks and I hope someone will find the source of this problem and provide a possible fix.
Click to expand...
Click to collapse
I had checked with HTC customer care.. they had asked me to discharge the battery completely, remove it for about 30 s and then charge using USB..
I performed the above steps but instead of switching on the phone, I kept it switched off while it was being charged..
What I noticed was the battery charging status jumped from 0 - 67% in 1 hour and then to 82% in next 1.5 hours.. post then it stayed there..
From what I deduce, it does not appear to be a software problem.. I am primarily facing with lots of ROM, AOKP, CM10.1, MIUI, Stock - Sabsa, Viper

Try this method
(do when you are not using mobile for long time at night)
Method 1(Normal User)
Get --Battery Calibration---from Market (Damo software)
--Keep Incs on charger
--Now open Battery Calibration--
--Chose remove battery_stats.bin---
--Now PowerOff Immidietely
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS -new battery_stats.bin will be created-You will see 100% charged Battery
Alernative Method (Advance user)
(Note:Keep desired Rom on Your SD card to flash)
--Keep Incs on charger
--Go into recovery
--Wipe all Partition except SD CARD
--Wipe Battery Stats
--Now PowerOff Immidietely By removing battery
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS Bootloader into recovery
--flash the ROM which you already saved on your sd-Card
--Reboot
--You will see 100% charged Battery
Note: Keep your charger ON in Entire Process

srv.abhishek said:
Is there a link for the test? It would be great if you can post it here...
Click to expand...
Click to collapse
U need to add him on google+ and he adds u back. Then ull find his test builds and stuff. szezso's google plus
Sandeep_Jagtap said:
Try this method
(do when you are not using mobile for long time at night)
Method 1(Normal User)
Get --Battery Calibration---from Market (Damo software)
--Keep Incs on charger
--Now open Battery Calibration--
--Chose remove battery_stats.bin---
--Now PowerOff Immidietely
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS -new battery_stats.bin will be created-You will see 100% charged Battery
Alernative Method (Advance user)
(Note:Keep desired Rom on Your SD card to flash)
--Keep Incs on charger
--Go into recovery
--Wipe all Partition except SD CARD
--Wipe Battery Stats
--Now PowerOff Immidietely By removing battery
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS Bootloader into recovery
--flash the ROM which you already saved on your sd-Card
--Reboot
--You will see 100% charged Battery
Note: Keep your charger ON in Entire Process
Click to expand...
Click to collapse
Alright Ill flash a CM10.1 ROM. When it reaches 60% and can no longer charge, ill msg u back to see if it worked (cuz it normally dont happen until like 2 or so weeks after) Thanks for the input

Sandeep_Jagtap said:
Try this method
(do when you are not using mobile for long time at night)
Method 1(Normal User)
Get --Battery Calibration---from Market (Damo software)
--Keep Incs on charger
--Now open Battery Calibration--
--Chose remove battery_stats.bin---
--Now PowerOff Immidietely
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS -new battery_stats.bin will be created-You will see 100% charged Battery
Alernative Method (Advance user)
(Note:Keep desired Rom on Your SD card to flash)
--Keep Incs on charger
--Go into recovery
--Wipe all Partition except SD CARD
--Wipe Battery Stats
--Now PowerOff Immidietely By removing battery
--Keep ChargerON till Entire Night
--At morning you will see green LED showing fully chared battery
--Boot IncS Bootloader into recovery
--flash the ROM which you already saved on your sd-Card
--Reboot
--You will see 100% charged Battery
Note: Keep your charger ON in Entire Process
Click to expand...
Click to collapse
tried charging over-nite but no luck.. charging status same as mentioned above

srv.abhishek said:
tried charging over-nite but no luck.. charging status same as mentioned above
Click to expand...
Click to collapse
ohh. Hope it get fix.
I could tell you this far only

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.