Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

CM6 Battery Drain?


  • Please log in to reply
148 replies to this topic

#1 Transmission3k

Transmission3k
  • Members
  • 11 posts
  • Twitter:Transmission3k
  • Country:
    us - United States
  • Device Model:
    G2
  • CM Version:
    7.1.0
  • Recovery Image:
    ClockworkMod

Posted 16 August 2010 - 12:58 PM

After spending the past week putting the phone (G1, black, CM6 RC2) through normal usage, I'm ready to eat this crow I've killed and dressed so nicely.

Here's the skinny: Though installing a new ROM usually resets your battery stats, it's not doing a reliable reset of stats. Most likely you don't have you phone plugged in to power when you're installing, you don't really have a full charge from the outset, etc. Letting it drain all the way down from this state and recharging WILL NOT HELP YOU, in the long run.

You need to be methodical in your approach, my friends. You mustn't skip steps (not implying that you were, but I definitely was).

For the record, we'll be referring to this bit on the wiki. Now, what's important is this:

Charge your phone. All the way. Top that sucker off. Then, with the power still connected (<- that's the important bit), reboot into recovery and wipe the battery stats. Once that is done, boot back to your normal phone, and once it's back up, remove the power cable. NOW! let it drain all the way down. Until it shuts off. Annoying little flashy red light doesn't count. Hell, I even let mine shut off, gave it a bit, turned it back on and ran it until it shut off again. After that, charge your phone all the way up again. You should be back to normal battery usage. I'm getting my standard day-and-a-half out of it, at this point.

In summation:
1. Charge phone completely, leave plugged into power
2. Boot into recovery
3. Wipe battery stats
4. Reboot to normal
5. Remove power cable
6. Drain that sucker all the way
7. Recharge fully
8. Rejoice!


MOD EDIT:
Reason for drain given at: http://droidbasement.com/db-blog/, under 'Known issues' for Dream/Sapphire 32B kernel.

Edited by Skrki, 25 December 2010 - 03:35 AM.
Added information


#2 Tim vd Leeuw

Tim vd Leeuw
  • Members
  • 2 posts
  • Device Model:
    ADP1
  • CM Version:
    CM5.0.8
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 12:25 PM

Hi,

I installed 6.1RC1 yesterday, did a wipe & clean install. I noticed that the battery seems to drain really fast, most of the drain attributed to 'Android System'...

G1, no swapspace, mobile data off.

Does anyone have similar experience?

Cheers,

--Tim

#3 Knothead

Knothead
  • Donators
  • 54 posts
  • Country:
    us - United States
  • Device Model:
    G1
  • CM Version:
    ezterry 285 Kernel with tnp285 xtra nightly & gb kbd
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 12:37 PM

View PostTim vd Leeuw, on 29 October 2010 - 12:25 PM, said:

Hi,

I installed 6.1RC1 yesterday, did a wipe & clean install. I noticed that the battery seems to drain really fast, most of the drain attributed to 'Android System'...

G1, no swapspace, mobile data off.

Does anyone have similar experience?

Cheers,

--Tim

My g1 went to 28% in about 3 hours yesterday then hung there (it was in my pocket w/no use) till 5 when I made a few quick calls for dinner plans then it went to 15%.

Unplugged this morning after a 12 hour charge and I am at 90 percent after 55 minutes with just idle time. It says cell standby used 37% phone idle used 21% gmail 21% screen 10% andriid system 6% android os 3% com.google .process.gapps 3% I also have it in 2g only.

#4 g1_froyo

g1_froyo
  • Members
  • 153 posts
  • Country:
    pl - Poland
  • Device Model:
    HTC Dream / ERA G1
  • CM Version:
    CM 6.1 stable
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 12:41 PM

For me CM 6.1 RC1 is much better than CM6 stable, even not using Toggle2G/3G from XDA forum , battery life is really not bad - from 6 AM to 2:40 PM lost 50% from full charge - that is not bad result .

#5 skraw

skraw
  • Members
  • 107 posts
  • Country:
    de - Germany
  • Device Model:
    i9000
  • CM Version:
    2.2.1 JPU+speedmod
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 12:48 PM

I might add some strange experiences round battery, too. It had around 58% battery, then I did a reboot. And when it was up again it told me around 90%. What are the proceedings to reset the battery state completely?

#6 guille26

guille26
  • Members
  • 41 posts
  • Device Model:
    HTC Dream
  • CM Version:
    Cyanogenmod 6.0
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 12:54 PM

I also have noticed it, may it be because the kernel CM6.1 is using is 2.6.35? Pershoot's 2.6.35 kernel has a bug, it drains your battery if you don't reboot after unplugging the USB.
I don't know if CM is OCing the CPU by itself because I haven't change my SetCPU config.

#7 feisty_noodle

feisty_noodle
  • Donators
  • 8 posts
  • Twitter:feisty_noodle
  • Country:
    us - United States
  • Device Model:
    HTC Magic (Rogers)
  • CM Version:
    6.1.0-DS-final
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 01:28 PM

I think it may have to do with 35.x series kernels.  I see the same behavior with bcrook's kernel as with pershoot's on my 32A.
The only solution I have  come up with (as have others) is to go back to older, series 34.x kernels.

#8 g1_froyo

g1_froyo
  • Members
  • 153 posts
  • Country:
    pl - Poland
  • Device Model:
    HTC Dream / ERA G1
  • CM Version:
    CM 6.1 stable
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 02:23 PM

I don't know how CPU speed is managed by the standard kernel on itself , but with setcpu this is possible set CPU governor to conservative mode . I have this setting on .

Edited by g1_froyo, 29 October 2010 - 02:23 PM.


#9 SDeba

SDeba
  • Members
  • 22 posts
  • Country:
    pl - Poland
  • Location:
    Warsaw
  • Device Model:
    Galaxy S
  • CM Version:
    CM7 Nightlies
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 04:56 PM

I have also noticed that my battery drains very fast. Unplugged on 7AM and on 3PM my G1 has turned off. That's a huge bug!

#10 Marko Janjic

Marko Janjic
  • Members
  • 15 posts
  • Location:
    Serbia
  • Device Model:
    |1|
  • CM Version:
    CM 5.0.8 DS Test 4
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 04:59 PM

mediaserver service keeps scanning SDCARD all the time and makes CPU clock to full , thus the battery drain... waiting for solution

#11 AjntOrnj

AjntOrnj
  • Donators
  • 42 posts
  • Country:
    us - United States
  • Location:
    Wash.
  • Device Model:
    Galaxy Nexus (GSM)
  • CM Version:
    CM (most recent Stable, RC or M)
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 05:02 PM

I have this same problem attributed mostly to "android os".

It's interesting to hear about battery drain after the USB is connected. I didn't change the kernel up or anything. Yesterday battery life seemed great, today it is horrible, down to 30% after 4 hours.

Wonder what the heck is draining my battery. :angry:

#12 Cydd

Cydd
  • Members
  • 1 posts
  • Device Model:
    T-Mobile G1
  • CM Version:
    CyanogenMod 6.X
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 05:34 PM

View PostAjntOrnj, on 29 October 2010 - 05:02 PM, said:

I have this same problem attributed mostly to "android os".

It's interesting to hear about battery drain after the USB is connected. I didn't change the kernel up or anything. Yesterday battery life seemed great, today it is horrible, down to 30% after 4 hours.

Wonder what the heck is draining my battery. :angry:

It's the kernel. Flash back to 2.6.34.7 and the problem is solved.

#13 guille26

guille26
  • Members
  • 41 posts
  • Device Model:
    HTC Dream
  • CM Version:
    Cyanogenmod 6.0
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 06:38 PM

View PostCydd, on 29 October 2010 - 05:34 PM, said:

It's the kernel. Flash back to 2.6.34.7 and the problem is solved.

Haha, I was just going to post that link! :)

I've flashed 2.6.34.7 from pershoot's, remember to make a NAND backup before flashing the kernel so you will be able to recover original CM's kernel.

#14 sboulema

sboulema
  • Members
  • 1 posts
  • Device Model:
    HTC Dream
  • CM Version:
    Cyanogen Mod 6
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 06:48 PM

Do I need to flash back to the old kernel via recovery and which exact zip to flash?

#15 billquinn1

billquinn1
  • Members
  • 20 posts
  • Twitter:billquinn1
  • Country:
    us - United States
  • Location:
    Columbia SC
  • Device Model:
    G1
  • CM Version:
    Latest Nightly or BiffMod
  • Recovery Image:
    Amon_RA

Posted 29 October 2010 - 07:08 PM

View Postguille26, on 29 October 2010 - 06:38 PM, said:

Haha, I was just going to post that link! :)

I've flashed 2.6.34.7 from pershoot's, remember to make a NAND backup before flashing the kernel so you will be able to recover original CM's kernel.
Yep, same deal. I flashed the kernel Ezterry built for Biffmod instead. So far so good. I am a little surprised this problem made it into a release candidate. Its not like it is an unknown never before seen bug. I know most of these guys have long ago moved on to other devices.
I suggest that Mrs. Cyanogen test the rom first. She wouldn't like that kernel either.

#16 hapa

hapa
  • Members
  • 440 posts
  • Country:
    us - United States
  • Location:
    Kaneohe, HI
  • Device Model:
    HTC Vision (T-Mobile G2)
  • CM Version:
    V7.1.0-RC1 (26 June 2011)
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 07:57 PM

maybe you all just need a new battery...
I unplugged mine at 12:30 last night and went to bed... woke up and it was at 98% when I woke up and left ~7:30am
;) battery drain seems to be quite well now

#17 SDeba

SDeba
  • Members
  • 22 posts
  • Country:
    pl - Poland
  • Location:
    Warsaw
  • Device Model:
    Galaxy S
  • CM Version:
    CM7 Nightlies
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 08:55 PM

View Posthapa, on 29 October 2010 - 07:57 PM, said:

maybe you all just need a new battery...
I unplugged mine at 12:30 last night and went to bed... woke up and it was at 98% when I woke up and left ~7:30am
;) battery drain seems to be quite well now
Definitly NO! Surely I don't need new battery. I bought a new one 1,5 month ago so it's just kernel problem - flashed 2.6.34 Pershoot's kernel and everything works fine!

#18 evermind

evermind
  • Members
  • 7 posts
  • Device Model:
    |2|
  • CM Version:
    6.x
  • Recovery Image:
    Stock

Posted 29 October 2010 - 09:28 PM

With 218 nightly my phone ran 5 days straight and still had 19% charge, I'm gonna test RC1 to see if I get the same awesome results.

Edited by evermind, 29 October 2010 - 09:30 PM.


#19 WannaBREz

WannaBREz
  • Members
  • 45 posts
  • Country:
    us - United States
  • Device Model:
    ION and Vibrant
  • CM Version:
    ION - Cyanogen 6.1 Stable(HBOOT-1.33.0013, RADIO-2.22.28.25) Vibrant - Nero v3 Voodoo
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 09:32 PM

I use my ION as a test device, no sim, all wifi.  So far with some use... flashing the rom, radio, mods, running tests, logcat a lot... still going good

Posted Image

Posted Image

Posted Image

#20 ChazzBG

ChazzBG
  • Members
  • 6 posts
  • Twitter:chazzbg
  • Country:
    bg - Bulgaria
  • Device Model:
    Nexus S
  • CM Version:
    AOKP M5
  • Recovery Image:
    ClockworkMod

Posted 29 October 2010 - 09:43 PM

i experienced some random life with battery, but it may be true that it drains batery faster after unpluging from usb
fully charged on usb to ~60% -> about 1-2 hours,with screen of, and turned off mobile data,wifi,bluetooth .... everything
fully charged on charger to 60% -> about 4-5 hours with about 20 minutes browsing with 2G
i noticed that powertop shows about 450-600 interruptions when on usb and after unpluging , but after restart interrupts drops to 240-350