• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [BETA]Cyanogen!! Landed!!! :) Go get it![Updated 7/12/2011]

If I'm in the office (one bar) I get about 24 hours on CM7. At home (full bar) I get ~48hrs if it's idle or ~24hrs during heavy usage (justin.tv streams, music, etc.).
 
yawdapaah said:
If I'm in the office (one bar) I get about 24 hours on CM7. At home (full bar) I get ~48hrs if it's idle or ~24hrs during heavy usage (justin.tv streams, music, etc.).
Click to expand...

yeah 24hrs is kinda farfetched on cm7

i have mine on airplane mode, display off for 8 hours and when im leaving work its at around 70-80% so i kinda just dont see how during heavy usage you get 24 hrs. thats not possible
especially without some charging going on
 
  • Like
Reactions: foo
VoidedSaint said:
yeah 24hrs is kinda farfetched on cm7

i have mine on airplane mode, display off for 8 hours and when im leaving work its at around 70-80% so i kinda just dont see how during heavy usage you get 24 hrs. thats not possible
especially without some charging going on
Click to expand...

I am on ssx and doing everything possible and still not getting close to that
 
I can go about 24 hours now with normal use, with light use I'm able to go 24 hours and have about 20% battery left. I'm using the stock clock speeds but at lower voltages.
 
Airmaxx23 said:
I can go about 24 hours now with normal use, with light use I'm able to go 24 hours and have about 20% battery left. I'm using the stock clock speeds but at lower voltages.
Click to expand...

+1. Signal strength seems to hit CM7 especially hard but it seems much more efficient that blur/de-blurred roms overall.
I'll conduct an experiment this weekend and post my battery stats.

Edit #1: Do you guys still have Cell Standby, Android OS/System battery drain? When I'm in the office, Cell Standby spikes to >20%. At home, it doesn't go above 10%.
Another thing I do is to switch my Wifi Sleep Policy from Screen off > Never > Screen off. That helped, in the earlier builds, to curb the Android OS/System drain.

Edit #2: If you want, you can download alogcat and look for "wakelock" in the output. I did some reading last weekend and here's what I found.

Android uses a somewhat hacked procedure called "Wakelock" to keep applications alive. Said applications are able to wake the phone from a sleeping state. I say hacked because it appears that "Wakelock" was not merged into Linux (Android in general has this issue).

"Wakelock" is not implemented (as far as I understand) at the application level (probably System or Kernel). So, applications request a "wakelock" from the system (you'll see wakelock increment and decrement in you logcat). So if apllications are not releasing "wakelock" correctly, your system cannot enter a low power sleep state (I think coolguy was complaining about this).

If you check your battery usage (in Spare Parts), you may see a process called "Suspend." As far as I can tell, there are two types of Wakelock; Suspend and Idle. Idle seems like a low power state that keeps the apps right below the surface so they can be quickly restarted. Suspend is probably an even lower power state. It seems like Android OS (particularly Gingerbread) has issues with the Suspend state. Android OS tries to put the "Wakelock" processes in Suspend mode but but some "rogue" apps/processes may be maintaining a "Wakelock".

The reason I've been harping about Wifi Sleep Policy (no one seems to care though :'( ), is that it's one of the known "Wakelock" triggers.

I always have alogcat on my phone. Recently, "Wakelock" seems to be released correctly. Maybe Team Douche figured out a solution to this (in the recent builds) or maybe it's because I have Wifi set to "Screen off". I haven't had time to test this out yet.

Eitherway, this is what I've gathered so far; someone correct me if I've gotten something wrong.
 
yawdapaah said:
+1. Signal strength seems to hit CM7 especially hard but it seems much more efficient that blur/de-blurred roms overall.
I'll conduct an experiment this weekend and post my battery stats.

Edit #1: Do you guys still have Cell Standby, Android OS/System battery drain? When I'm in the office, Cell Standby spikes to >20%. At home, it doesn't go above 10%.
Another thing I do is to switch my Wifi Sleep Policy from Screen off > Never > Screen off. That helped, in the earlier builds, to curb the Android OS/System drain.

Edit #2: If you want, you can download alogcat and look for "wakelock" in the output. I did some reading last weekend and here's what I found.

Android uses a somewhat hacked procedure called "Wakelock" to keep applications alive. Said applications are able to wake the phone from a sleeping state. I say hacked because it appears that "Wakelock" was not merged into Linux (Android in general has this issue).

"Wakelock" is not implemented (as far as I understand) at the application level (probably System or Kernel). So, applications request a "wakelock" from the system (you'll see wakelock increment and decrement in you logcat). So if apllications are not releasing "wakelock" correctly, your system cannot enter a low power sleep state (I think coolguy was complaining about this).

If you check your battery usage (in Spare Parts), you may see a process called "Suspend." As far as I can tell, there are two types of Wakelock; Suspend and Idle. Idle seems like a low power state that keeps the apps right below the surface so they can be quickly restarted. Suspend is probably an even lower power state. It seems like Android OS (particularly Gingerbread) has issues with the Suspend state. Android OS tries to put the "Wakelock" processes in Suspend mode but but some "rogue" apps/processes may be maintaining a "Wakelock".

The reason I've been harping about Wifi Sleep Policy (no one seems to care though :'( ), is that it's one of the known "Wakelock" triggers.

I always have alogcat on my phone. Recently, "Wakelock" seems to be released correctly. Maybe Team Douche figured out a solution to this (in the recent builds) or maybe it's because I have Wifi set to "Screen off". I haven't had time to test this out yet.

Eitherway, this is what I've gathered so far; someone correct me if I've gotten something wrong.
Click to expand...

I don't know about anyone else, but I thought the Wi-Fi tip was good. Using 'Screen off' helped a lot with battery life. I would rather leave Wi-Fi on all the time, but without a charger handy, it drains my battery. Keeping Wi-F off helps a lot.
 
yawdapaah said:
+1. Signal strength seems to hit CM7 especially hard but it seems much more efficient that blur/de-blurred roms overall.
I'll conduct an experiment this weekend and post my battery stats.

Edit #1: Do you guys still have Cell Standby, Android OS/System battery drain? When I'm in the office, Cell Standby spikes to >20%. At home, it doesn't go above 10%.
Another thing I do is to switch my Wifi Sleep Policy from Screen off > Never > Screen off. That helped, in the earlier builds, to curb the Android OS/System drain.

Edit #2: If you want, you can download alogcat and look for "wakelock" in the output. I did some reading last weekend and here's what I found.

Android uses a somewhat hacked procedure called "Wakelock" to keep applications alive. Said applications are able to wake the phone from a sleeping state. I say hacked because it appears that "Wakelock" was not merged into Linux (Android in general has this issue).

"Wakelock" is not implemented (as far as I understand) at the application level (probably System or Kernel). So, applications request a "wakelock" from the system (you'll see wakelock increment and decrement in you logcat). So if apllications are not releasing "wakelock" correctly, your system cannot enter a low power sleep state (I think coolguy was complaining about this).

If you check your battery usage (in Spare Parts), you may see a process called "Suspend." As far as I can tell, there are two types of Wakelock; Suspend and Idle. Idle seems like a low power state that keeps the apps right below the surface so they can be quickly restarted. Suspend is probably an even lower power state. It seems like Android OS (particularly Gingerbread) has issues with the Suspend state. Android OS tries to put the "Wakelock" processes in Suspend mode but but some "rogue" apps/processes may be maintaining a "Wakelock".

The reason I've been harping about Wifi Sleep Policy (no one seems to care though :'( ), is that it's one of the known "Wakelock" triggers.

I always have alogcat on my phone. Recently, "Wakelock" seems to be released correctly. Maybe Team Douche figured out a solution to this (in the recent builds) or maybe it's because I have Wifi set to "Screen off". I haven't had time to test this out yet.

Eitherway, this is what I've gathered so far; someone correct me if I've gotten something wrong.
Click to expand...


yes that was my complaint, seems to have settled down. this is my 2nd go on ssx
 
Coolguy71261 said:
yes it is doing much better this time around.

hmm how would the average battery life be on miui, close to the battery life of apex?
Click to expand...

I don't know. If it's built the same way CM4DX is then it will, probably, fare no better. I also don't know if running Gingerbread on the Froyo kernel is kosher.
I wonder if Cvpcs will update 2nd init to a GB compliant version now that a fix has been found...

Do me a favor Coolguy; check the "sensor usage" in the Spare Parts battery history.
 
Does anyone know if you can backup your messages and calls using titanium on the blur rom and restore the messages into cyanogen? I want to put CM7 on my wife's Droid X but she has messages she cant afford to lose.
 
Metfanant said:
Interesting...is that something that was added back in by cyanogen in particular?...because it doesn't actually exist in Gingerbread as far as I know...
Click to expand...

It could be because cm7 is using the froyo kernal or it was just put back in. It can also be accessed through settings>about phone>battery use. It was one of the things I missed when going from froyo to gb, I was pleasantly surprised to find it in cm7.
 
zanoodi said:
It could be because cm7 is using the froyo kernal or it was just put back in. It can also be accessed through settings>about phone>battery use. It was one of the things I missed when going from froyo to gb, I was pleasantly surprised to find it in cm7.
Click to expand...

it shouldn't have anything to do with the kernel...because there is really no such thing as a "froyo kernel" it just happens to be the kernel that came with froyo on our phones...its no more a froyo kernel than the current kernel is a "gingerbread kernel"
 
Metfanant said:
it shouldn't have anything to do with the kernel...because there is really no such thing as a "froyo kernel" it just happens to be the kernel that came with froyo on our phones...its no more a froyo kernel than the current kernel is a "gingerbread kernel"
Click to expand...

On another note for some reason my dock keeps randomly disappearing and the only way I've had success in getting it back is rebooting. Anyome else havong this issue or know to resolve it? CM7 nightly 28.
 
VoidedSaint said:
yeah 24hrs is kinda farfetched on cm7

i have mine on airplane mode, display off for 8 hours and when im leaving work its at around 70-80% so i kinda just dont see how during heavy usage you get 24 hrs. thats not possible
especially without some charging going on
Click to expand...

Nah. I get around 22 hours heavy use.
Check it.
20110705195455.png
 
just so im clear...when someone says something that is incorrect we are simply to ignore it?[/QUOTE]


It was all in good fun relax dude. I actually appreciate the correction it only adds to my knowledge. Sorry for the sarcasm.
 
You must log in or register to reply here.
Back
Top Bottom