CM7 Nightlies Topic [Nightly 28- 21/03/2011]

[Guest targetbsp]

Looks like they got a fix for Angry Birds etc not working on the SD card then! :( Comment from TomG saying patch supplied. Phone proximity fixed yesterday, apps2sd today. We're on a roll! :(

[Guest Frankish]

Looks like they got a fix for Angry Birds etc not working on the SD card then! :( Comment from TomG saying patch supplied. Phone proximity fixed yesterday, apps2sd today. We're on a roll! :(

Biggest bug now. Touchscreen freeze. I'm going to be a grump until i can play a full match of Pro Evo without having to sleep and wake my phone 2-3 times a match.

[Guest Blues003]

Biggest bug now. Touchscreen freeze. I'm going to be a grump until i can play a full match of Pro Evo without having to sleep and wake my phone 2-3 times a match.

Once the Touchscreen, the random reboots, and the proxy sensor is fully fixed, CM7 here I go! :(

[Guest Pelemane]

Once the Touchscreen, the random reboots, and the proxy sensor is fully fixed, CM7 here I go! :(

This fixes proxy :(

[Guest Blues003]

This fixes proxy :(

Already one user saying it did not work always. There was also another kernel fix on another topic, but I did not manage to flash it via CwM 3.0.0.5

[Guest Ufufu]

Looks like they got a fix for Angry Birds etc not working on the SD card then! :( Comment from TomG saying patch supplied. Phone proximity fixed yesterday, apps2sd today. We're on a roll! :(

Not only those, but the headset bug as well!

Thanks Tom & Jacob.

[Guest hecatae]

http://code.google.com/p/cyanogenmod/issues/detail?id=2971 28 hours before stale

Double-tapping camera creates a FC

same for http://code.google.com/p/cyanogenmod/issues/detail?id=2975

USB Tethering does not work on ZTE Blade

same also http://code.google.com/p/cyanogenmod/issues/detail?id=2951

USB Debugging icon not displaying in notification bar

I'll upload some logcats later for the above, if anyone else can test on rc2 too please

Edited March 11, 2011 by hecatae

[Guest Rotmann]

For people still having problems with the proximity sensor, you have to restart after you tick "Always use proximity". Anyway I've done some testing myself, ticking "Always use proximity" in Settings - Call settings and restarting solves the problem in CM7 and N15 with standard kernel too, no t0mm13b or bl1nk kernel needed.

Edited March 11, 2011 by Rotmann

[Guest ufoman]

For issue 2951, there seems to be a fix waiting for review here:

http://review.cyanogenmod.com/#change,3811

Also, fix for issue 2950 is already merged:

http://review.cyanogenmod.com/#change,3797

Fix for issue 2860 (ANGRY BIRDS CRASHING, OH NOES one) is awaiting review too:

http://review.cyanogenmod.com/#change,3812

[Guest DonJamal]

when will we get an official cyanogen proximity fix? cuz i dont want to play all the time with that damn kernel replace and so on

[Guest Roxxor91]

when will we get an official cyanogen proximity fix? cuz i dont want to play all the time with that damn kernel replace and so on

For people still having problems with the proximity sensor, you have to restart after you tick "Always use proximity". Anyway I've done some testing myself, ticking "Always use proximity" in Settings - Call settings and restarting solves the problem in CM7 and N15 with standard kernel too, no t0mm13b or bl1nk kernel needed.

[Guest Scoopading]

I deleted all sensor libs and akmd2, battery drain is still high 9% in 7 hours. On airplane mode and not touching the phone that is.

That just about leaves only things like the RIL to rip out then, huh? :( If it's CPU related then down-clocking the CPU might also be a temporary work around worth looking at, although the minimum it can be set to with Cyanogen is 122Mhz. Perhaps changing the Cyanogen/Performance/CPU Settings/Available governors from the default "ondemand" to "powersave" then setting the min and max clock to 122Mhz might gain something?

Anyway, my results were the same in RC2 with most apps removed. Wiped everything. No SIM (even during install), airplane mode always. 55 items removed, 16 things left installed (Could've probably been even more aggressive, but wanted to be sure it'd boot first time without messing about with things FC'ing on me :( ) Here's what was left installed..

Certificate Installer 2.3.3, Contacts 2.3.3, [CONTACTS/CALLS] Contacts Storage 2.3.3, [CM Settings] CyanogenMod settings 2.3.3, [VOICEMAIL] Dialler 2.3.3, [sMS/MMS/APN] Dialler Storage 2.3.3, DRM-Protected Content Storage 2.3.3, Google Services Framework 2.3, HTML Viewer 2.3.3, [sMS/MMS PREFS] Messaging 2.3.3, Package Access helper 2.3.3, Package Installer 2.3.3, [WALLPAPER/SETTINGS] Settings 2.3.3, [sETTINGS/BLUETOOTH] Settings Storage 2.3.3, Setup Wizard 1.3, Status Bar 2.3.3, Themes Provider 2.0.25. To that list I added Launcher Pro. Everything else wiped!

After 20hrs and 20mins the battery reading was 65%. Or 1.75% drain on average. Looking at the log it showed zero, nada, zilch activity during the period I left it idle. Not a single entry and it still dropped! Log files won't show this issue.

The conclusion is hardly unexpected. Unless there's something going on in one of the 16 components (plus Launcher Pro) I left installed, which somehow doesn't show up in logs, this is a core component/kernel issue. The cause could be down to unintended interactions with Cyanogen/Android 2.3.x (not forgetting Gingerbread was designed with a 2.6.35 kernel in mind), otherwise it seems likely something's been "damaged" in the move over to Cyanogen.

As it stands, CM7 still has 3 or 4x the idle power drain of every other Blade rom I'm aware of. Lets keep our fingers crossed someone spots something in the kernel source :)

Edited March 11, 2011 by Scoopading

[Guest Rotmann]

when will we get an official cyanogen proximity fix? cuz i dont want to play all the time with that damn kernel replace and so on

RC2 and N15 have to have it fixed, tick "Always use proximity" in Settings-Call settings and try. If it does not work reboot, it works with the stock kernels.

@Scoopading - I left the phone with removed sensors for 16 hours, 27% drain in airplane mode, no SIM. It's definitely no sensor problem. I wanted for my next text to remove the RIL but TOM_G said it's useless and that it will last longer anyway, I think I will remove it tonight for further testing. If you have time and are in the mood for proper testing (clean install on 100% battery, no additions, no gapps, no apps leave phone untouched for 12-16-24 hours), I can provide a kernel from Tom_G I'm testing right now where he added some CPU scaling settings he left away in the original release. He said that they made a big difference on the Pulse, from my testing it seems pretty good but I need more testing time. Just let me know.

Edited March 11, 2011 by Rotmann

[Guest Fransis.co]

Setting the WIFI sleep policy to NEVER appears to have quite an effect.

The Battery Use graph in About Phone has a much reduced gradient in the last 3 hours I`ve tried.

[Guest Rotmann]

Setting the WIFI sleep policy to NEVER appears to have quite an effect.

The Battery Use graph in About Phone has a much reduced gradient in the last 3 hours I`ve tried.

This is no relevant testing, 8+ hours sounds much more like it, because the android battery reporting is not what anyone would call accurate. Did you leave it connected to wifi or just with wifi unconnected but active?

[Guest Scoopading]

I wanted for my next text to remove the RIL but TOM_G said it's useless and that it will last longer anyway, I think I will remove it tonight for further testing.

Yep. No harm in trying it just to see what happens... :(

If you have time and are in the mood for proper testing (clean install on 100% battery, no additions, no gapps, no apps leave phone untouched for 12-16-24 hours), I can provide a kernel from Tom_G I'm testing right now where he added some CPU scaling settings he left away in the original release. He said that they made a big difference on the Pulse, from my testing it seems pretty good but I need more testing time. Just let me know.

Sure.. I'd be interested to check it out :(

Sounds more of a work-around than a true fix though.. But I'd certainly be willing to try it and see if there's any noticeable improvement :)

[Guest mELIANTE]

RC2 and N15 have to have it fixed, tick "Always use proximity" in Settings-Call settings and try. If it does not work reboot, it works with the stock kernels.

@Scoopading - I left the phone with removed sensors for 16 hours, 27% drain in airplane mode, no SIM. It's definitely no sensor problem. I wanted for my next text to remove the RIL but TOM_G said it's useless and that it will last longer anyway, I think I will remove it tonight for further testing. If you have time and are in the mood for proper testing (clean install on 100% battery, no additions, no gapps, no apps leave phone untouched for 12-16-24 hours), I can provide a kernel from Tom_G I'm testing right now where he added some CPU scaling settings he left away in the original release. He said that they made a big difference on the Pulse, from my testing it seems pretty good but I need more testing time. Just let me know.

I have a spare blade that I'm using just for that. If you provide the kernel I'll test it, as the spare blade is only there sitting and idling :(

Edited March 11, 2011 by mELIANTE

[Guest Rotmann]

Yep. No harm in trying it just to see what happens... :(

Sure.. I'd be interested to check it out :(

Sounds more of a work-around than a true fix though.. But I'd certainly be willing to try it and see if there's any noticeable improvement :)

Not really a workaround, he just some added CPU scaling stuff which may increase battery life with no cost on performance.

I have a spare blade that I'm using just for that. If you provide the kernel I'll test it, as the spare blade is only there sitting and idling ;)

Sent the links, check your PMs. Please respect a few steps so that we can compare:

1. Wipe data, cache, dalvik, format system

2. Flash the ROM with the new kernel completely new at 100% battery

3. Don't install any apps or gapps, leave all settings standard

4. Reboot 3 times (wait 5 minutes after each reboot) for the ROM to settle down

5. Try the first 12-16-24 hours in airplane mode and also try 12-16-24 hours with a SIM in it, no data active but with GSM/3G to be able to receive calls (I have some suspicions that airplane mode may eat battery when it actually should not).

I am running the new kernel after some fiddling and testing, for 6 hours now in GSM/3G mode but no active data and the battery % is stuck at 49%, too early to tell but looks good.

[Guest targetbsp]

Certificate Installer 2.3.3, Contacts 2.3.3, [CONTACTS/CALLS] Contacts Storage 2.3.3, [CM Settings] CyanogenMod settings 2.3.3, [VOICEMAIL] Dialler 2.3.3, [sMS/MMS/APN] Dialler Storage 2.3.3, DRM-Protected Content Storage 2.3.3, Google Services Framework 2.3, HTML Viewer 2.3.3, [sMS/MMS PREFS] Messaging 2.3.3, Package Access helper 2.3.3, Package Installer 2.3.3, [WALLPAPER/SETTINGS] Settings 2.3.3, [sETTINGS/BLUETOOTH] Settings Storage 2.3.3, Setup Wizard 1.3, Status Bar 2.3.3, Themes Provider 2.0.25. To that list I added Launcher Pro. Everything else wiped!

I can help narrow that down slightly further. It's not Certificate Installer or HTML Viewer because I delete them from every rom I use. They're not as important as they sound. :(

[edit]

Nor Launcher Pro for that matter cause I use ADW

Edited March 11, 2011 by targetbsp

[Guest lnva]

RC2 and N15 have to have it fixed, tick "Always use proximity" in Settings-Call settings and try. If it does not work reboot, it works with the stock kernels.

@Scoopading - I left the phone with removed sensors for 16 hours, 27% drain in airplane mode, no SIM. It's definitely no sensor problem. I wanted for my next text to remove the RIL but TOM_G said it's useless and that it will last longer anyway, I think I will remove it tonight for further testing. If you have time and are in the mood for proper testing (clean install on 100% battery, no additions, no gapps, no apps leave phone untouched for 12-16-24 hours), I can provide a kernel from Tom_G I'm testing right now where he added some CPU scaling settings he left away in the original release. He said that they made a big difference on the Pulse, from my testing it seems pretty good but I need more testing time. Just let me know.

I could allso do some testing.

[Guest DonJamal]

in android 2.1 there was an option under contacts\display option to show either the sim or the local contacts. this is not included in cm7. i really miss it and i cant add contacts to sim... can someone fix or include it?

thanks

Edited March 11, 2011 by DonJamal

[Guest jayhix]

right guys i have a prob when running this rom and overclocking, my phone randomly turns off or restarts or just freezes up and wont display the unlock screen. soo i was wondering if i have some settings wrong or whether its common with the rom.

Im running RC2 with 710 or 729 max, are these settings too high? are there recommended overclocking settings.

thanks

Edit: also i think modaco just died cuz i couldnt load it up for an hour nearly :| but its back now :(

Edited March 11, 2011 by jayhix

[Guest Len Ash]

in android 2.1 there was an option under contacts\display option to show either the sim or the local contacts. this is not included in cm7. i really miss it and i cant add contacts to sim... can someone fix or include it?

thanks

SIM contact storage is non-core to Android. Google "Sync" is your contact storage medium.

Part of the principle of Android

[Guest targetbsp]

right guys i have a prob when running this rom and overclocking, my phone randomly turns off or restarts or just freezes up and wont display the unlock screen. soo i was wondering if i have some settings wrong or whether its common with the rom.

Im running RC2 with 710 or 729 max, are these settings too high? are there recommended overclocking settings.

Yes that means your overclocking too high. Everyone phone is different. The only guaranteed speed is 600mhz. You need to find the speed that is stable for your phone. You can't use what anyone else says theirs runs at.

[Guest shakerist]

Ok I will start timing on how long my battery will last, starting from now, but tbh i think the battery is better then jj its been off the charger for 2 hours or so and its still 100%, im gona give it a 5 minute charge and se how it will go, and anyone take a look at my log a few posts ago coz i really need this dual sim working, thanks

edit: omg i turned 3g on for 6 minutes and battery dropped 4 percent !!!!

Edited March 11, 2011 by shakerist