Hi. I'm glad I found this discussion. I'm not very experienced with modding, but I have successfully updated my G1 from the stock 1.6 to CM 6.1.0-DS, using the instructions in the wiki. And like many others, I quickly noticed that battery life went down the tubes. I am currently going through the process described in the first post of this thread, and have completed step 7 (recharge fully). In case things don't work out the way they're supposed to, I would like to try flashing the 2.6.34.8 kernel that was referenced a few posts back (i.e. ezBiffTestKernel20110222-ebi0_S.zip). But I have some noob questions that I hope won't seem too tedious. First, here's my current setup:
Baseband: 62.50SC.20.17U_2.22.23.02 (i.e. radio is 2.22.23.02)
Kernel: 2.6.35.9-cynogenmod shade@toxygene #2
Mod version: CM-6.1.0-DS
Build: FRG83
I suppose the first question should be, is the kernel in ezBiffTestKernel20110222-ebi0_S.zip compatible with my current setup? If so, ...
In order to flash the 2.6.34.8 kernel, is this ALL I have to do:
1. Put ezBiffTestKernel20110222-ebi0_S.zip on an SD card.
2. Boot to recovery.
3. Flash ezBiffTestKernel20110222-ebi0_S.zip from the SD card.
4. Reboot.
Am I correct in my understanding that flashing the kernel is an independent operation wrt. the CM mod itself, and the Google apps? So I don't need to worry about things like update-cm-6.1.0-DS-signed.zip and gapps-mdpi-tiny-20101020-signed.zip, right? That is, flashing the kernel leaves my current CM 6.1 and gapps alone?
[Update on my battery wipe - doesn't look good; in 45 minutes, level has gone from 100% to 88% with the phone sitting beside me doing nothing, with the screen off.]
Thanks for any pointers!
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.
|
Guest Message by DevFuse
21
CM6 Battery Drain?
Started by Transmission3k, Aug 16 2010 12:58 PM
206 replies to this topic
#201
pdxesto
-
- Members
- 3 posts
- Device Model:Google G1
- MOD Version:CM6
- Recovery Image:Amon_RA
Posted 06 May 2011 - 04:49 AM
#202
roccoadam32
-
- Members
- 76 posts
-
Country:
- Device Model:g1
- MOD Version:Tmus official froyo
- Recovery Image:Amon_RA
Posted 07 May 2011 - 04:31 AM
#203
lovemarvel
-
- Members
- 6 posts
- LocationPhilippines
-
Country:
- Device Model:HTC Dream
- MOD Version:Cyanogen 6.1
- Recovery Image:ClockworkMod
Posted 11 May 2011 - 11:07 PM
roccoadam32, on 07 May 2011 - 04:31 AM, said:
Are they stable and doesn't disable any other features?
#204
roccoadam32
-
- Members
- 76 posts
-
Country:
- Device Model:g1
- MOD Version:Tmus official froyo
- Recovery Image:Amon_RA
Posted 12 May 2011 - 04:07 PM
lovemarvel, on 11 May 2011 - 11:07 PM, said:
Are they stable and doesn't disable any other features?
#205
pdxesto
-
- Members
- 3 posts
- Device Model:Google G1
- MOD Version:CM6
- Recovery Image:Amon_RA
Posted 13 May 2011 - 12:42 AM
pdxesto, on 06 May 2011 - 04:49 AM, said:
First, here's my current setup:
Baseband: 62.50SC.20.17U_2.22.23.02 (i.e. radio is 2.22.23.02)
Kernel: 2.6.35.9-cynogenmod shade@toxygene #2
Mod version: CM-6.1.0-DS
Build: FRG83
In order to flash the 2.6.34.8 kernel, is this ALL I have to do:
1. Put ezBiffTestKernel20110222-ebi0_S.zip on an SD card.
2. Boot to recovery.
3. Flash ezBiffTestKernel20110222-ebi0_S.zip from the SD card.
4. Reboot.
Am I correct in my understanding that flashing the kernel is an independent operation wrt. the CM mod itself, and the Google apps? So I don't need to worry about things like update-cm-6.1.0-DS-signed.zip and gapps-mdpi-tiny-20101020-signed.zip, right? That is, flashing the kernel leaves my current CM 6.1 and gapps alone?
Baseband: 62.50SC.20.17U_2.22.23.02 (i.e. radio is 2.22.23.02)
Kernel: 2.6.35.9-cynogenmod shade@toxygene #2
Mod version: CM-6.1.0-DS
Build: FRG83
In order to flash the 2.6.34.8 kernel, is this ALL I have to do:
1. Put ezBiffTestKernel20110222-ebi0_S.zip on an SD card.
2. Boot to recovery.
3. Flash ezBiffTestKernel20110222-ebi0_S.zip from the SD card.
4. Reboot.
Am I correct in my understanding that flashing the kernel is an independent operation wrt. the CM mod itself, and the Google apps? So I don't need to worry about things like update-cm-6.1.0-DS-signed.zip and gapps-mdpi-tiny-20101020-signed.zip, right? That is, flashing the kernel leaves my current CM 6.1 and gapps alone?
Here's an update on where I'm at. I successfully flashed the 2.6.34.8 kernel using the 4 simple steps I asked about, quoted above. Yes, it really is that simple. And the results are fantastic! No more battery drain! So in my experience, the instructions listed in the original post of this thread did absolutely nothing to solve my battery drain problem. For me, it was all in the kernel. THANKS mytouchdude69!!
#206
lxtbattery
-
- Members
- 1 posts
- Locationhttp://www.lxt-group.com/02/en/
-
Country:
- Device Model:CM6
- MOD Version:2019
- Recovery Image:Cyanogen
Posted 15 October 2011 - 01:47 PM
Thanks for your sharing.
#207
romulan
-
- Members
- 4 posts
- Device Model:HTC Dream
- MOD Version:6.1
- Recovery Image:Amon_RA
Posted 30 December 2011 - 10:59 PM
My battery drained within a day always with minimal use, and I thought it was normal.
I listen to the G1 in my car over bluetooth. I used to turn on bluetooth in the car and off
later, to save on battery. Recently I found out (accidentally) that if I leave my bluetooth on all time the
battery lasts longer. It seems counter intuitive, but it is repeatable. With bluetooth
on the battery lasts 2-3x for me compared to bluetooth off. Anyone see this too? Any guesses as to
why this might happen?
--
I listen to the G1 in my car over bluetooth. I used to turn on bluetooth in the car and off
later, to save on battery. Recently I found out (accidentally) that if I leave my bluetooth on all time the
battery lasts longer. It seems counter intuitive, but it is repeatable. With bluetooth
on the battery lasts 2-3x for me compared to bluetooth off. Anyone see this too? Any guesses as to
why this might happen?
--
