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] Battery dead in 8 hours, please help

After I flashed to the hardcore speedmod kernel my battery doesn't make it through the day; it was never that great in the first place. I've let it run down completely and then recharge, I've wiped the stats and turned off HSDPA, nothing....
I have GPS and WiFi off.
Here's my setup
Baseband: I9000UGJK3
Kernel: 2.6.32.9 hardcore k12k 500hz
Build #: FROYO.UCJI6
What should I do?

word38 said:
After I flashed to the hardcore speedmod kernel my battery doesn't make it through the day; it was never that great in the first place. I've let it run down completely and then recharge, I've wiped the stats and turned off HSPDA, nothing....
I have GPS and WiFi off.
Here's my setup
Baseband: I9000UGJK3
Kernel: 2.6.32.9 hardcore k12k 500hz
Build #: FROYO.UCJI6
What should I do?
Click to expand...
Click to collapse
Try a different ROM and kernel, say the one in my signature. If its still the same, go back to stock, and check once more. If its still bad, u could ask AT&T for a warranty exchange of the battery.

I had the same exact problem running Serendipity 2.0 with the speedmod kernel. I switched kernels (from the one that came with Serendipity to speedmod) since people claimed they saw improved battery life. As with the OP, i turned off HSDPA to save battery life, and I kept both wifi and BT off. In addition, I turned the display brightness to the lowest setting, turned off haptic feedback and all touchtone sounds.
Even with these changes to preserve battery life, I found my phone down to about 30% within 6 hours. In this time, I checked my FB account twice for about 2-3 minutes each time, and I read and replied to, maybe, 10-15 emails. I made no phone calls during this time. I actually found the battery life with the speedmod kernel to be worse than the stock kernel that came with Serendipity.
I re-flashed last night to Serendipity 3.0 and kept the kernel that came pre-installed with Serendipity. I did underclock the phone to 800 Mhz, so we'll see if that has any effect on battery life.

battery life
word38 said:
After I flashed to the hardcore speedmod kernel my battery doesn't make it through the day; it was never that great in the first place. I've let it run down completely and then recharge, I've wiped the stats and turned off HSDPA, nothing....
I have GPS and WiFi off.
Here's my setup
Baseband: I9000UGJK3
Kernel: 2.6.32.9 hardcore k12k 500hz
Build #: FROYO.UCJI6
What should I do?
Click to expand...
Click to collapse
make sure you apply the battery tweaks from CWM recovery for the speedmod kernel and try recalibration.. use screen filter if necessary or use low brightness and screen timeouts.

JOLiu said:
I had the same exact problem running Serendipity 2.0 with the speedmod kernel. I switched kernels (from the one that came with Serendipity to speedmod) since people claimed they saw improved battery life. As with the OP, i turned off HSDPA to save battery life, and I kept both wifi and BT off. In addition, I turned the display brightness to the lowest setting, turned off haptic feedback and all touchtone sounds.
Even with these changes to preserve battery life, I found my phone down to about 30% within 6 hours. In this time, I checked my FB account twice for about 2-3 minutes each time, and I read and replied to, maybe, 10-15 emails. I made no phone calls during this time. I actually found the battery life with the speedmod kernel to be worse than the stock kernel that came with Serendipity.
I re-flashed last night to Serendipity 3.0 and kept the kernel that came pre-installed with Serendipity. I did underclock the phone to 800 Mhz, so we'll see if that has any effect on battery life.
Click to expand...
Click to collapse
For me, personally, I found the kernel in my sig to have a better battery life.

Which ROM is better? di11igaf or Docs?

word38 said:
Which ROM is better? di11igaf or Docs?
Click to expand...
Click to collapse
di11igaf's v2.5 ROM has an awesome battery life. I would recommend this over the rest and Docs.

[Q] NC will black out ,when the battery reache 31%.

My NC is installed CM7.0.3 in emmc mode. Every time when the battery reache around 31%, it will black out. No matter how i press the power key,it hasn't any reaction. Untill i plug on the USB charger, it'll power on to the system and charge the battery at 31%, and It work at seem to be normal.
Has anyone else experienced problems like these?

nope ive gone down 20 percent this has never happened to me.

wah67 said:
My NC is installed CM7.0.3 in emmc mode. Every time when the battery reache around 31%, it will black out. No matter how i press the power key,it hasn't any reaction. Untill i plug on the USB charger, it'll power on to the system and charge the battery at 31%, and It work at seem to be normal.
Has anyone else experienced problems like these?
Click to expand...
Click to collapse
Have you tried recalibrating the battery with the menu option in CMR? Need to charge to 100% before you do it though. It may be displaying a false %.

angomy said:
Have you tried recalibrating the battery with the menu option in CMR? Need to charge to 100% before you do it though. It may be displaying a false %.
Click to expand...
Click to collapse
Yeah, i have tried the battery calibration, the battery doctor, and wipe the battery status at recovery mode, also every time i have waited the battery to charge up to 100%, but nothing to change.

Mines does that. Around 12%. Screen turns right Barack up when plugged in though
Sent from my NookColor using XDA Premium App

I had the exact same problem as you. In the end I flashed back to the stock B&N 1.2 firmware, then left it plugged in overnight. Next day I used CWM to reset battery stats and wipe system/data/cache, before installing CM7. Attempted to drain the battery and it went all the way down to 0% =).

celyst said:
I had the exact same problem as you. In the end I flashed back to the stock B&N 1.2 firmware, then left it plugged in overnight. Next day I used CWM to reset battery stats and wipe system/data/cache, before installing CM7. Attempted to drain the battery and it went all the way down to 0% =).
Click to expand...
Click to collapse
I have the same problem except I'm running stock 1.2 unrooted. I have a CM7 build on a microSD that I use sometimes. How would you recommend I reset battery stats?

Mine has the problem but it started when I updated u-boot.bin to 1.2 for putting 2.6.32 kernel and Dal's CM7 on my NC.
First time it happened at 40% and before that battery % went up while off charger with 2.6.29 kernel.
With 2.6.32 kernel, it happened at 37%.
Put it on USB charger, it booted up fine. Will try to reset battery stats once fully charged. By the way, charger N is orange when CM battery % says 100%. Stats definitely are screwed up. Hope CWR battery reset will do the trick.

Same issue, stumped
My battery seems to die (screen blacks out) at 30 percent, sometimes 28 or 29%. Uptime prior to that happening is roughly 11 hours or so, with these stats before blinking off:
Battery status: Discharging
Power plug: unplugged
Battery level: 28
Battery scale: 100
Battery health: Good
Battery voltage: 3373 mV
Battery temperature: 36.9 C
Running Android 2.3.3
CM 7.0.3-encore
It didn't always do this, just recently in the past two days. I can't help but feel it's tied to an install, but the Netflix build.prop fix is the only one I can really remember being significant.
At 100% charged I've wiped the battery status in recovery, cleared cache (tried to wipe dalvik but got an error) and the nook still turned off at 30%. I recharged just enough to get the battery up to 31% and re-edited build.prop back to the original settings, rebooted, and waited for it to run down again. It died at 29%.
Desperately looking for ideas short of a reinstall of the mod...

lilgrass71 said:
Screen turns right Barack up when plugged in though
Click to expand...
Click to collapse
Nice spellcheck you have there!

im getting this power out thingy also

Its an issue associated with the 1.2 upgrade not cm7. I have same problem at about 25%.
Sent from my Nook Color running CM7 nightly 74.

ddgarcia05 said:
Its an issue associated with the 1.2 upgrade not cm7. I have same problem at about 25%.
Click to expand...
Click to collapse
If it is related to the 1.2 upgrade, what's confusing me is that my nook just recently started doing it a couple of days ago. Prior to that I could get a full discharge.
Overall I don't think the battery is bad, since I can get a full day of play with it with Wifi on most of the time and streaming about a 2 hours of video. But having 30% be the new zero is just weird.

ddgarcia05 said:
Its an issue associated with the 1.2 upgrade not cm7. I have same problem at about 25%.
Sent from my Nook Color running CM7 nightly 74.
Click to expand...
Click to collapse
B&N 1.2.0 ROM or the 1.2.0 u-boot stuff? Because I'd only believe this if you're saying it happens consistently on the 1.2.0 B&N ROM..

cymoze said:
My battery seems to die (screen blacks out) at 30 percent, sometimes 28 or 29%.
Click to expand...
Click to collapse
I don't have it blanking out until I get to about 10%. I wonder what the difference is... I am using a nootered nook and OC kernel.

just noticed this over the weekend. I was actually charging to reset the battery stats. judging from the other posts I can expect that not to help.
I don't recall itdoing it immediately after the 1.2 uboot but I'm now on the cyanogen 1.2 and its the same. worst part istheres no warning at all just blanks out.

Check this thread for more info, everyone is trying to find out why as well.
http://forum.xda-developers.com/showthread.php?p=14182742#post14182742

I Am Marino said:
Check this thread for more info, everyone is trying to find out why as well.
http://forum.xda-developers.com/showthread.php?p=14182742#post14182742
Click to expand...
Click to collapse
Thanks for the link. I wish I could contribute on that discussion but I am about 7 posts short. I am not using an overclocked kernel whatsoever, but my experience mirrors those listed there: death at under 3000 Mv, which for me occurs around the 30% battery level.
My stats are, to the best of my knowledge since I'm very much a noob, here:
PBD REPORT FORM
TEST CONFIGURATION:
BOOT DEVICE: eMMC
MLO: BN 1.2 stock
U-BOOT: ?
KERNEL: 2.6.29-omap1
OVERCLOCKED?: No
GOVERNOR: ONDEMAND
SYSTEM: CM7 7.0.3-encore
PBD: YES
TEST COUNT: 3x
TRIED REVERTING TO OLDER HC/CM7: NO
TRIED WIPING CACHE/DATA?: YES
DID IT WORK? NO
PREVIOUSLY INSTALLED:
_ Stock 1.1
X Stock 1.2
_ CM7 2.29 (any)
_ CM7 2.32 beta 3

One more "me too"... Happens to me around 25%... Have to plug back into the wall for second and then boot back up when it happens... Pretty scary if I were using this thing for any real work - luckily, it's just a play-thing for me to learn Android (got my eye on the new Asus tablets though!)...

This problem is happening to me as well. I
haven't updated to the 1.2 firmware and running CM 7.03. The screen will black out at 30%. Will wiping battery stats in CWR not help?
PBD REPORT FORM
TEST CONFIGURATION:
BOOT DEVICE: eMMC
MLO: BN 1.1 stock
U-BOOT: ?
KERNEL: 2.6.29-omap1
OVERCLOCKED?: Yes to 1.2GHz
GOVERNOR: INTERACTIVE
SYSTEM: CM7 7.0.3-encore
PBD: YES
TEST COUNT: 1x
TRIED REVERTING TO OLDER HC/CM7: NO
TRIED WIPING CACHE/DATA?: NO, wiped battery stats
DID IT WORK?
PREVIOUSLY INSTALLED:
x Stock 1.1
_ Stock 1.2
_ CM7 2.29 (any)
x CM7 2.32 beta 3 -- reverted back to CM 7.03

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