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

[Guest Scoopading]

Well, I tried echo "2147483647" > /data/delay. It also makes absolutely zero difference to battery life whilst the phone sleeps. So none of these data/delay values work - for me at least. The battery still falls around 2% per hour whilst sleeping.

Checking times with Logcat ( adb logcat -v time > sleeplog.txt ) showed almost no activity overnight. Exactly every 30 or 60 mins I'd get..

D/WifiService( 175): ACTION_BATTERY_CHANGED pluggedType: 0

Usually followed directly after by an I/EventLogService( 300)

Then, usually every 60 mins, D/dalvikvm( 300): GC_FOR_MALLOC

Not sure if it's normal for the Wifi service to write to the log every 30 or 60 mins if it's set to sleep when the screen goes off. But, either way, there really wasn't much happening outside those 3 events, and nothing in between those half hour periods. It seems like something isn't being turned off properly when the phone sleeps though..

[Guest Rotmann]

I have wiped everything today and have stock N11, no gapps or modifications. For the first 8 hours in airplane mode, it went from 100% to 92%, it's better than previous nightlies or RC1 where I would have lost around 13-15% but still bad compared to froyos. I have applied

echo "2147483647" > /data/delay

through terminal emulator now, let's see if it gets any better. Will report after 8 hours again.

Rubbish, still getting 1-2% drain per hour in airplane mode with echo "2147483647" > /data/delay , phone blank with nothing on it, just N11 installed. Lost 20% in 12 hours, phone slept, nothing woke it. I'm losing my patience and getting tired of flashing and testing, playing with the thought to go back to FLB Froyo :) Gonna try echo 250 today, if it still does not work and no change appears till the end of the week, I might switch to 2.2 :huh:

Edited March 3, 2011 by Rotmann

[Guest ThrashMan]

The link posted earlier referring to Desire battery loss mentions the CM7 is rather over eager in the use of its location updates.

Try turning off wireless and GPS location options overnight?

[Guest ThrashMan]

Rubbish, still getting 1-2% drain per hour in airplane mode with echo "2147483647" > /data/delay , phone blank with nothing on it, just N11 installed. Lost 20% in 12 hours, phone slept, nothing woke it. I'm losing my patience and getting tired of flashing and testing, playing with the thought to go back to FLB Froyo :P Gonna try echo 250 today, if it still does not work and no change appears till the end of the week, I might switch to 2.2 :huh:

No one is forcing you to partake in the testing of beta ROMs. How about trying to work out what is causing the problem rather than just performing random tests? :)

[Guest rayraven]

Are people still facing the touchscreen freezes with nightly 11? Or is that less common now?

[Guest Karl_K]

Hi all !

Has anyone noticed that the picture quality of this ROM is really bad ?

I tried taking several pictures with the camera, but the colors are completely washed out, its undersaturated and looks very bad. It looks the same in the preview and setting saturation and contrast settings does not change anything. I dont think the picture quality was soo bad in the original firmware.

Any ideas ?

This is with nightly#11 on a 3.2 MP blade.

[Guest curl66]

Hi all !

Has anyone noticed that the picture quality of this ROM is really bad ?

I tried taking several pictures with the camera, but the colors are completely washed out, its undersaturated and looks very bad. It looks the same in the preview and setting saturation and contrast settings does not change anything. I dont think the picture quality was soo bad in the original firmware.

Any ideas ?

This is with nightly#11 on a 3.2 MP blade.

for me pics quality is much better than before.

just play around with the settings.

[Guest Scoopading]

Gonna try echo 250 today

Good luck. Changes nothing here. These data/delay settings are barking up the wrong tree. They don't make any significant difference to battery performance in sleep mode.

[Guest r0by]

Are people still facing the touchscreen freezes with nightly 11? Or is that less common now?

For me in N8 and N11 touchscreen freezes is not exist yet, and hope it will never come :huh:

[Guest goatee]

Anybody tried N12 yet?

[Guest Scoopading]

Try turning off wireless and GPS location options overnight?

If you were responding to Rotmann, he already said he was using airplane mode, which should disable it. There's still drain..

How about trying to work out what is causing the problem rather than just performing random tests? :)

The problem for people with that is standard log files don't appear to be showing anything that'd be causing significant battery drain? Perhaps you can suggest something else people could try? :huh:

I think the drain is roughly the amount you'd get with something like the WIFI left on though. It's very much like the phone thinks it's turning something off when its not..

[Guest Scoopading]

Anybody tried N12 yet?

Nope. But there don't appear to be any new Blade specific fixes added to it?..

[Guest skull_fcuk]

I kind of sympathise with your feelings towards this ROM, but then again, i think to myself, this is FREE, it's custom made by enthusiast coders, in their spare time for no money, and as far as I can tell, it's bloody marvellous! I'm running N11, and just made a long phone call to a land line (Hi Mum :huh:), no problem with the screen coming back on afterwards. Never has been in my experience either.

I'm happy to get to test this, and to be able to contribute in some way to making it fully workable. I tend not to jump into the latest Nightly until i see a few posts about others experiences, and even then i'm not expecting it to be perfect. Hell, Windows is a retail product, and it's far from perfect.

Rant over.

Flashed to N11 last night (after a brief play with the Honeycomb ROM that's on here, which was fun) and did a full wipe, cache wipe and dalvik (what is that anyway?) wipe, and it seems lovely. Was on N8 before that, and it was lovely too. Have noticed though that there is some graphical problems with my camera, not big ones. A helicopter flew overhead this morning, so i used my phone to take a pic, and the resulting photo had two dark bands across the top and bottom, making the photo look like i'd taken a pic of an old CRT screen, and captured the flicker. No biggy though. This had failed to happen in the next pic.

Another thing I found by accident ( albeit in N6 ) was that if i set the camera to zoom using the Volume buttons, it would Force Close upon using that function. Just never bothered with the function.

[Guest birdibird]

running N12 here

looking good so far, not sure what changed

[Guest goatee]

running N12 here

looking good so far, not sure what changed

Thanks - downloading now as I'm still on 8.

[Guest uomoinutile]

Guys, have you noticed any troubles in connecting with protected WiFi networks? With 'protected' I mean with something more than a WPA2 passphrase: to me, this happens to the wifi I got at my university, which involves the use of certificates for a TLS encryption. I could connect till nightly 11, but I get kicked all the time since I got nightly 11.

[Guest Rotmann]

The link posted earlier referring to Desire battery loss mentions the CM7 is rather over eager in the use of its location updates.

Try turning off wireless and GPS location options overnight?

No one is forcing you to partake in the testing of beta ROMs. How about trying to work out what is causing the problem rather than just performing random tests? :)

Wiping everything and flashing nothing else but the ROM, having a non functional smartphone, testing, posting and staring at logcats is my trying to work out what is causing the problem, don't know what the role of your post was :huh: Also as I stated, the tests were done in airplane mode, GPS is off automatically.

[Guest Apeman85]

I'm running N11, and just made a long phone call to a land line (Hi Mum :huh:), no problem with the screen coming back on afterwards. Never has been in my experience either.

Do you get any delay before the screen comes back on after a call or is it completely normal? Mine takes about 15s which is a pain if you have to use the keypad during a call.

Guys, have you noticed any troubles in connecting with protected WiFi networks? With 'protected' I mean with something more than a WPA2 passphrase: to me, this happens to the wifi I got at my university, which involves the use of certificates for a TLS encryption. I could connect till nightly 11, but I get kicked all the time since I got nightly 11.

Yes I've had the same problem since nightly 11 connecting to a WPA enterprise network (PEAP, MSCHAPv2). It connects without trouble the first time, but won't reconnect unless you forget and reapply the settings. I'm going to do a full wipe and try again before adding a report.

[Guest Tsip4]

Hi all !

Has anyone noticed that the picture quality of this ROM is really bad ?

I tried taking several pictures with the camera, but the colors are completely washed out, its undersaturated and looks very bad. It looks the same in the preview and setting saturation and contrast settings does not change anything. I dont think the picture quality was soo bad in the original firmware.

Any ideas ?

This is with nightly#11 on a 3.2 MP blade.

Maybe is connected...

http://www.chazclout.co.uk/?p=138

[Guest tcpaulh]

No blade specific changes for 10 days in the change log at https://github.com/CyanogenMod/android_devi...its/gingerbread

:huh:

[Guest Karl_K]

Maybe is connected...

http://www.chazclout.co.uk/?p=138

No, i dont think so, the pictures look crap, colors are fine in the UI.

It might be a white-balance and saturation problem, however, i cant seem to influence it a lot using the settings.

Would someone be able to post a few pics from a 3.2 MP camera? Preferrably indoors with artificial lighting.

[Guest Shug_06]

I'm having same problem on 12 with screen taking ages to come back on after call, can manage to get keypad up sometimes during call but it seems a bit hit or miss. Apart from that all seems well. Only been using n12 for a few hours so dont know if any improvements have been made in battery life.

[Guest NightSt@lk3r]

ive lost 30% of battery in about 4 hours with n12, yesterday with n11 my battery went from full to flat in about 10 hours, im going back to a good 2.2 rom.

[Guest rayraven]

Maybe is connected...

http://www.chazclout.co.uk/?p=138

Not really, Google changed the color calibration on the Nexus S on purpose.

The Nexus One with 2.3 update has no such issues.

[Guest timsewell]

No blade specific changes for 10 days in the change log at https://github.com/CyanogenMod/android_devi...its/gingerbread

:huh:

I think it's still worth flashing these nightlies though. Without the overview that the CM devs have we have little way of knowing if some of the bugs are actually not device-specific. I know, for instance, that battery drain seems to be a concern across the board.

FWIW I have found a couple of fairly reliable solutions for the remaining problems:

1. Proximity sensor - since installing Nolock from the Market I haven't had a problem with this - and I see also from the issue tracker that Tom G is prioritising this bug for a proper fix.

2. Battery drain - don't ask me why, but setting WiFi to never sleep has drastically improved my standby time. Yesterday on N11 I only lost c5% between 0700 and midday, same the day before on N8 - this is with light use, ie the odd email check and text message, couple of calls.