CM7 Nightly Discussion Thread [Old, please use new thread]

[Guest Rotmann]

I noticed a drop in performance from the NB 11? Is just me or is this fall with you too?

Sorry for my English:)

What? You noticed a drop in performance in N11 or N12 compared to N8? Or in N12 compared to N11? a) N11>N8 b ) N12>n8 c) N12>N11? or the other way around

@Victor von Zeppelin. Also wanted to report that the build.prop trick does not work, Tom G was right, that is for motorola phones.

echo "2147483647" > /data/delay did not work or echo 2147483647 > /data/delay did not work and the power drain was 1-2% per hour but echo 250 has been online in airplane mode for 8 hours and has only eaten 2-3% but I looked quite often at the phone, don't know if it really worked or it is just coincidence.

@ropin, type su first, enter, then the echo... stuff

Edited March 3, 2011 by Rotmann

[Guest kunis6]

What? You noticed a drop in performance in N11 or N12 compared to N8? Or in N12 compared to N11? a) N11>N8 b ) N12>n8 c) N12>N11? or the other way around

a) and b ) :(

Edited March 3, 2011 by kunis6

[Guest VJJ]

*BATTERY LIFE IS FIXED!

Using ADB shell, or the internal terminal emulator type:

This pretty much turns off AKMD2

adb shell (if using adb, otherwise skip this part)


echo "2147483647" > /data/delay

While this slows it down.

adb shell

echo 250 > /data/delay

when i try any of these using the internal terminal i keep getting permission denied, anyone know how to fix this

su

gets superuser permission :(

Type this first

[Guest alex1alex2alex3alex4]

*BATTERY LIFE IS FIXED!

Using ADB shell, or the internal terminal emulator type:

when i try any of these using the internal terminal i keep getting permission denied, anyone know how to fix this

Forget it, it doesn't only not solve it, it doesn't change the battery drain a bit.

[Guest philmein]

*BATTERY LIFE IS FIXED!

Using ADB shell, or the internal terminal emulator type:

This pretty much turns off AKMD2

adb shell (if using adb, otherwise skip this part)


echo "2147483647" > /data/delay

While this slows it down.

adb shell

echo 250 > /data/delay

when i try any of these using the internal terminal i keep getting permission denied, anyone know how to fix this

if you are using terminal emulator forget the adb shell bit just type the line below

[Guest chall32]

echo "2147483647" > /data/delay did not work or echo 2147483647 > /data/delay did not work and the power drain was 1-2% per hour but echo 250 has been online in airplane mode for 8 hours and has only eaten 2-3% but I looked quite often at the phone, don't know if it really worked or it is just coincidence.

Hang on... I thought 2147483647 was supposed to work and 250 doesn't work... :( Agree 2147483647 gives 1 to 2% per hour drain as that's what I'm seeing here.... Setting 250 now :( :)

[Guest Victor von Zeppelin]

Problems I noticed:

- Vol controls no longer change music in N11 onwards.

- Screen turns off during NFS Shift for some reason?

- Perhaps proximity? Haven't had a phone call since I changed the prop file.

Volume controls work for me changing song, Proximity fix also works, I've had for successive long calls, screen came back every time.

So it seems that N8 was the best for proximity and volume controls?

As I feel, not overly

What? You noticed a drop in performance in N11 or N12 compared to N8? Or in N12 compared to N11? a) N11>N8 b ) N12>n8 c) N12>N11? or the other way around

@Victor von Zeppelin. Also wanted to report that the build.prop trick does not work, Tom G was right, that is for motorola phones.

echo "2147483647" > /data/delay did not work or echo 2147483647 > /data/delay did not work and the power drain was 1-2% per hour but echo 250 has been online in airplane mode for 8 hours and has only eaten 2-3% but I looked quite often at the phone, don't know if it really worked or it is just coincidence.

@ropin, type su first, enter, then the echo... stuff

My scrolling/ web browser etc. performance has dropped a lot recently- far slower than any other rom I've used. Makes browsing tedious, and navigating menus slow.

and by build.prop you mean the prox fix? That's a bummer. And yea, although the akmd fix has slowed down garbage collection, there is something else at work, chewing up battery. Also, charging is very slow from the wall, too.

[Guest nunoar]

n8

many thanks!

Downgrading it now

[Guest mankulito]

please add Honeycomb Lockscreen by default: http://www.androidng.com/install-android-h...comb-lockscreen

[Guest Victor von Zeppelin]

please add Honeycomb Lockscreen by default: http://www.androidng.com/install-android-h...comb-lockscreen

CyangoenMod team will almost definately say no, but you can still install the patch yerself.

[Guest doubleluckstur]

many thanks!

Downgrading it now

n8 is definitely the most stable (for me).. you guys seem to think n12 is stable, but for me even 'just shake free' from the market doesn't fix the prox. sensor on n12. something major gone wrong there, because n8 is just fine.

[Guest Rotmann]

many thanks!

Downgrading it now

Could you please tell us if it was better than n12?

@doublelockstur, thanks for the feedback. Does your proximity sensor work now?

Edited March 3, 2011 by Rotmann

[Guest nunoar]

Could you please tell us if it was better than n12?

@doublelockstur, thanks for the feedback. Does your proximity sensor work now?

I'm downgrading just for the proximity sensor fix. Today was a nightmare already, and as tomorrow it's I don't want to end up smashing my phone in anger :(

[Guest Rotmann]

please add Honeycomb Lockscreen by default: http://www.androidng.com/install-android-h...comb-lockscreen

Just flashed this, bootloop :( DON'T FLASH AND DELETE THE POST!

Edited March 3, 2011 by Rotmann

[Guest Pelemane]

Just flashed this, bootloop :(

Mine stayed at green android for 10 minutes so I took battery off and rebooted and it booted but nothing has changed :(

[Guest Scoopading]

size=5]*BATTERY LIFE IS FIXED!

echo "2147483647" > /data/delay

While this slows it down.

echo 250 > /data/delay

when i try any of these using the internal terminal i keep getting permission denied, anyone know how to fix this

Battery life is not fixed. These data/delay fixes do NOTHING measurable for battery life. If you want to waste your time, as some of us already did, then go ahead.. you'll find the same. Likewise, the proximity "fix" mentioned should also do absolutely nothing (even TomG says this, and it's confirmed by others tests). I'm not sure why this info hasn't been edited out from the main page of this topic yet as it doesn't help.

[Guest Rotmann]

Battery life is not fixed. These data/delay fixes do NOTHING measurable for battery life. If you want to waste your time, as some of us already did, then go ahead.. you'll find the same. Likewise, the proximity "fix" mentioned should also do absolutely nothing (even TomG says this, and it's confirmed by others tests). I'm not sure why this info hasn't been edited out from the main page of this topic yet as it doesn't help.

+1

@Victor, the fixes don't work, neither build.prop nor the echos, I thought for a moment that 250 works but after 3-4 hours the consumption in airplane mode was still 1-2%. I suggest you delete them as I have tested on a fresh CM7 without any adds or apps on it, just airplane mode, every setting minimum 8-12 hours.

@Pelemane, wiped, installed the ROM and the lock screen simultaneous, it boots now but no change, it's rubbish. Rebooted again to clockwork, flashed the lock screen, boot loop again.

Edited March 3, 2011 by Rotmann

[Guest Victor von Zeppelin]

+1

@Victor, the fixes don't work, neither build.prop nor the echos, I thought for a moment that 250 works but after 3-4 hours the consumption in airplane mode was still 1-2%. I suggest you delete them as I have tested on a fresh CM7 without any adds or apps on it, just airplane mode, every setting minimum 8-12 hours.

Aye, bit of a shame, isn't it. Ah well. Perhaps we'll get a fix, or perhaps CM7 just uses up a lot of bettery. Heard some Evo users were having problems, too.

[Guest robot1000]

Just flashed this, bootloop :( DON'T FLASH AND DELETE THE POST!

Happened to me as well :( . Anyway to restore it, without wiping?

[Guest css771]

Aye, bit of a shame, isn't it. Ah well. Perhaps we'll get a fix, or perhaps CM7 just uses up a lot of bettery. Heard some Evo users were having problems, too.

It's not only the Evo. Nexus One owners and Desire owners are all complaining of bad battery life on CM7 since CM7 RC1.

Now a few Nexus One owners whose phones got the 2.3.3 ota update from Google are also complaining of bad battery which was not an issue on froyo.

It may have to do with the concurrent garbage collection introduced by Google in 2.3 (Which may have to do with the excessive garbage collection on standby?) or it may be an issue with CM7.

Either way it's an issue with the code, and I don't think we'll have a good enough workaround to this, Only the devs can fix it. However I hope one can be found, since that's the only major issue I have with this ROM.

Edited March 3, 2011 by css771

[Guest t0mm13b]

It's not only the Evo. Nexus One owners and Desire owners are all complaining of bad battery life on CM7 since CM7 RC1.

Now a few Nexus One owners whose phones got the 2.3.3 update are also complaining of bad battery which was not an issue on froyo.

It may have to do with the concurrent garbage collection introduced by Google in 2.3 (Which may have to do with the excessive garbage collection on standby?) or it may be an issue with CM7.

Either way it's an issue with the code, and I don't think we'll have a good enough workaround to this, Only the devs can fix it. However I hope one can be found, since that's the only major issue I have with this ROM.

By perchance, would comparing and diffing on the different branches of the dalvikvm sources (say froyo, and gingerbread) and see what's changed... it could be a minor change... just a guess? or even check the configuration of the kernel used in cm7 and diff with one from a most stable rom such as JJ? (They are both kernel releases 2.6.32 right?)

Edited March 3, 2011 by t0mm13b

[Guest Rotmann]

Happened to me as well :( . Anyway to restore it, without wiping?

If you did not back up before, not. Or try to flash the ROM over it, maybe it will fix it.

Edited March 3, 2011 by Rotmann

[Guest css771]

By perchance, would comparing and diffing on the different branches of the dalvikvm sources (say froyo, and gingerbread) and see what's changed... it could be a minor change... just a guess? or even check the configuration of the kernel used in cm7 and diff with one from a most stable rom such as JJ? (They are both kernel releases 2.6.32 right?)

Well yes they both use 2.6.32. But the changes I'm guessing would be far from trivial. Since we haven't heard from any of the CM7 devs on this battery issue, I don't know where the issue lies, either only with CM7 or upstream with aosp.

[Guest fredewis]

If you did not back up before, not.

yes u can just reinstal the rom again ontop. and it will be as it was.

hahaha just saw your edit.... i can proof it works fine flashing on-top.

Edited March 3, 2011 by fredewis

[Guest Scoopading]

It may have to do with the concurrent garbage collection introduced by Google in 2.3 (Which may have to do with the excessive garbage collection on standby?)

Wouldn't that garbage collection show in the log? When I looked at the log it showed very little whilst it slept (only 2 or 3 events after exactly every 30 or 60 minutes), and it still consistently dropped around 2% per hour. So I don't think it's the garbage collection.. It behaves much more like the wireless WIFI component isn't being switched off or something (even though it's not connected to anything.. )

Edit - Btw, just to confirm what some others noticed. There seems to be a small performance drop on nightly 11, probably caused by the initial switch to 2.3.3.. hopefully something that can be fixed on the Cyanogen side of things quite quickly (indeed one or two have already mentioned nightly 12 was better in that regard.. )

Edited March 4, 2011 by Scoopading