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

[Guest The Soup Thief]

@richardkemp - absolutely - there's no obvious reason why it should make any difference whatsover, but I've just found that by toggling that my phone goes from waking fairly easily to being a bloody nightmare!

It seems to be consistently reproducable on mine at least - I always had mine set to show all animations (and it was a bit slow to wake, but did so with a brush of the thumb), but noticed earlier on that when I set it to show no animations, that one difference made my phone very hard to wake

Makes no sense but it seems so

Edited March 4, 2011 by The Soup Thief

[Guest tttonyyy]

tttonyyy - what do you have Settings>Display>Animation set to?

My guess is "All window animations are shown".... (if that worked for you)

Yes, all animations shown.

Edit: Just tried turning them off, but this doesn't seem to make any difference.

Edited March 4, 2011 by tttonyyy

[Guest The Soup Thief]

Yes, all animations shown.

Edit: Just tried turning them off, but this doesn't seem to make any difference.

Aww :( The mystery continues...

Its robust on mine

I'm a bit obsessional about these things but not quite obsessional enough to go through and list every single one of my settings

I don't suppose you are RichardKemp? (if yours is working you might well be doing a lot of people a big favour! Alternatively you'd be wasting 20 mins of your life....)

[Guest Rotmann]

Every call I've made today has left me with the screen off and no way to terminate the call without popping the battery out; it's annoying enough to make me want to move back to a 2.2 ROM until it's fixed. I'm on N12.

I think the best alternative is to switch to N8 as it seemed to be fixed, N11 and N12 have broken it.

Funny how many people still complains about blank screen / battery life / etc. on a NIGHTLY BETA firmware...

You have to use the phone all the day for voice calls? Keep the standard ROM so!

OR... as I've said before at least 2-3 times... use a BLUETOOTH HEADSET!

cheers

marco

PS I don't want to be offensive, but I get really annoyed at all those complains on a FREE product...

It's not complaining mate, it's tracking down bugs and trying to find fixes or work-arounds. Especially when the bug was fixed in N8 but got broken in N11-N12.

[Guest The Soup Thief]

Hi Rotmann

Do you know if there is a "manual" online or anything similar that explains the Cyanogenmod features? I'm talking about the groovy stuff in the settings menus - I've figured quite a lot out just by meddling but there's lots of stuff (such as the Haptic feedback tweaks) that looks a bit complex

I had a look round the cyanogen site, and was able to find some pointers, but I just wondered if you might know of some obvious "how to" guide

Thanks

EDIT as with Maringer below, I'm pretty sure I had the proximity problem on n8 too - maybe just important to advise all to change accessibility settings so they can end calls with the power button so they don't have to pull batteries

Edited March 4, 2011 by The Soup Thief

[Guest Maringer]

I think the best alternative is to switch to N8 as it seemed to be fixed, N11 and N12 have broken it.

I'm pretty sure that I had the proximity problem with N8 as well so I don't think you can claim this works for everyone.

I don't think that there is a definitive 'fix' for this problem yet. The sensors on some Blades seem to be a little screwy - you'll find various people with problems with proximity in other Eclair and Froyo threads which needed to fixed by calibrating using the engineering dialer codes - and I expect this is why some suffer from the problem more than others.

Hopefully Tom G (or another dev) will be able to sort this out definitively before too long as he's mentioned that he is looking into it.

[Guest ambak]

Install original Froyo dialer, it fixed it for me :(

[Guest kunis6]

Today I noticed a terrible slowdown in the phone. After reading the text display to start work after waking from 3s. Launcher starts to slow down the (adw ex) Overall, I'm not happy with was made to upgrade to 2.3.3 because nothing has been improved only slowed down my feelings

Edited March 4, 2011 by kunis6

[Guest Zythus]

Gingerbread Launcher by steven lin from market is very smooth, smoothest from those I used (ADW, Launcher Pro)

[Guest css771]

Thanks to Google, I have found a tiny setting hack which may improve battery life. I found that Cell Standby used to be at the top of Battery Usage. With this hack, I've found that overnight I lost 11% battery instead of 20% earlier. I'm on Nightly 12. Your Mileage May Vary. What I did is this:

1. Open up dialer and enter *#*#4636#*#*. Don't press dial.

2. You will get a testing screen. Choose Phone Information.

3. Scroll down. You will find a dropdown list saying WCDMA preferred. Change that to GSM Auto (PRL)*

4. Tap Turn off radio just below that. And turn it back on again.

5. Reboot. But the settings may work without a reboot. They did for me.

Now on the phone information screen, if you press menu, you get an option to select radio band. You could select accordingly between US, Europe, Japan, etc.

Supposedly the reason it works is because the phone stops scanning for a 3G signal constantly. I've noticed that right now my "Awake Time" is reduced a lot while in standby.

*A few users on other forums have reported that this causes their phone to go on roaming. That didn't happen on my phone however. So try it with caution and keep an eye out for excessive charges when on 3G. I take no responsibility for excessive data/call charges while on this setting. Just try it out yourself and if it doesn't work for you, you can go back to WCDMA Preferred using the same steps.

Edited March 4, 2011 by css771

[Guest Victor von Zeppelin]

What do you expect? Victor is not omniscient and can only assemble the information people provide here. Then again, since many people drop partial information and sometimes just outright wrong stuff ("battery drain SOLVED!!1!!" when having tested for 10 minutes etc. :( ), there's nothing he can do really about that. Plus the fact that the nightlies are a moving target does not help.

Plus, of course, the fact that forums are really not suited for managing actual information. The first post should be a wiki page really. Then other people could also fix it.

Haha, quite exactly, I have to read every post here, and assembling what's news and what's conjecture is tough. I'm sorry if I miss single posts that claim sourced truth, as they're usually buried beneath a pile of fixes and workarounds that even I sometimes get carried away with. One of these is the fact I believe the proximity bug has been fixed, as many calls have worked out perfectly. At the moment, it's so hard to tell. Perhaps the most annoying thing is that none of the devs actually talk to us, and the cold clinical CM issue trackers and changelogs aren't a good substitute for being told outright

[Guest That-Guy]

Im gutted, was on Nightly 8 and didn't have the proximity bug, but since updating to Nightly 12 I am getting it on every call lol.

One thing I will say about Nightly 12 is it seems to be so much smoother and more responsive when using the touch screen :(

[Guest bga]

I think the best alternative is to switch to N8 as it seemed to be fixed, N11 and N12 have broken it.

It's not complaining mate, it's tracking down bugs and trying to find fixes or work-arounds. Especially when the bug was fixed in N8 but got broken in N11-N12.

+1

It worked for me on N8, but it's broken now on N12.

[Guest Maringer]

+1

It worked for me on N8, but it's broken now on N12.

As I mentioned earlier, I encountered the proximity problem on N8 so this is not a definitive fix for everyone.

However, if others haven't had the problem on N8 it may be worth a try. YMMV, as always.

[Guest Letalis.se]

As everyone else says. screen was working on N8 but hopeless on N12.

It has been several times that I needed to remove battery just to kill the ongoing call.

But besides that It ROCKS

[Guest StevenHarperUK]

As everyone else says. screen was working on N8 but hopeless on N12.

It has been several times that I needed to remove battery just to kill the ongoing call.

But besides that It ROCKS

I agree R12 is even more likely to result in a Battery out procedure after every call.

R8 is the best Day to Day for now.

[Guest uskixboy]

As I mentioned earlier, I encountered the proximity problem on N8 so this is not a definitive fix for everyone.

However, if others haven't had the problem on N8 it may be worth a try. YMMV, as always.

I agree N8 wasn't a perfect fix, but something has definitely gone awry in the last couple of nightlies in this respect. However aside from this issue this is by far the best I've used. Huge thanks to the devs.

[Guest t0mm13b]

Uhhh... just doing a diff with MCR 12's 2.6.32 kernel config... just wondering as to add my input into this....

These are switched on in the current nightly 12...

CONFIG_MSM_SMD_DEBUG

CONFIG_MSM_ONCRPCROUTER_DEBUG

CONFIG_MSM_DMA_TEST <- that is set as a module? is that a mandatory thing?

CONFIG_VMSPLIT_3G is set, whereas in MCR 12 is off and CONFIG_VMSPLIT_2G is used instead

CONFIG_PAGE_OFFSET is set at a very high address (0xC0000000), in MCR 12 its, 0x80000000

CONFIG_CPU_IDLE is not set!!!!!!!! <- WHY?

in MCR 12, this is set - CONFIG_ZTE_SUSPEND_WAKEUP_MONITOR=y and CONFIG_SCREEN_ON_WITHOUT_KEYOCDE=y

CONFIG_MTD_TESTS=m <- again is this mandatory?

CONFIG_ANDROID_PMEM_KAPI_TEST=m that is switched off in MCR 12, but active under CM7

CONFIG_ANDROID_PMEM_KAPI_TEST=m, ditto ^^

WiMAX is activated under CM7 which is fair enough - have seen that in the change log... BUT

PPP stuff is activated... dunno - thought WiMAX is using the wireless? unless I am mistaken, that 3G uses that to "dial up"

CONFIG_INPUT_EVBUG=m, <- disabled under MCR 12

CONFIG_USB_GADGET_DEBUG_FILES=y

CONFIG_USB_GADGET_DEBUG_FS=y both of the USB gadget stuff are set

CONFIG_RTC_DEBUG=y

CONFIG_EXT4_FS_XATTR=y <- extra attributes for Ext4 FS.... needed?

CONFIG_CIFS_XATTR=y <- ditto for CIFS

CONFIG_DEBUG_KERNEL=y

CONFIG_DEBUG_BUGVERBOSE=y

CONFIG_DEBUG_INFO=y

CONFIG_DEBUG_USER=y

CONFIG_DEBUG_ERRORS=y

NB: This is a beta kernel so obviously an understanding is required to ensure that there's a reason for the battery draining like 'ell....Ok, so that looks like where the battery drain is coming in, surely with debugging events switched on and logs being produced... not exactly the optimized kernel configuration but at least the diffs highlight those that is mentioned in the above... I have excluded/ignored the CM7 specific patches...

Right lads, anyone willing to try re-compile the kernel ignoring the above and disabling all the debugging stuff and see what happens? :(

What you think? :(

/me fires up bash...

Edited March 4, 2011 by t0mm13b

[Guest tttonyyy]

Thanks to Google, I have found a tiny setting hack which may improve battery life. I found that Cell Standby used to be at the top of Battery Usage. With this hack, I've found that overnight I lost 11% battery instead of 20% earlier. I'm on Nightly 12. Your Mileage May Vary. What I did is this:

1. Open up dialer and enter *#*#4636#*#*. Don't press dial.

2. You will get a testing screen. Choose Phone Information.

3. Scroll down. You will find a dropdown list saying WCDMA preferred. Change that to GSM Auto (PRL)*

4. Tap Turn off radio just below that. And turn it back on again.

5. Reboot. But the settings may work without a reboot. They did for me.

Now on the phone information screen, if you press menu, you get an option to select radio band. You could select accordingly between US, Europe, Japan, etc.

Supposedly the reason it works is because the phone stops scanning for a 3G signal constantly. I've noticed that right now my "Awake Time" is reduced a lot while in standby.

*A few users on other forums have reported that this causes their phone to go on roaming. That didn't happen on my phone however. So try it with caution and keep an eye out for excessive charges when on 3G. I take no responsibility for excessive data/call charges while on this setting. Just try it out yourself and if it doesn't work for you, you can go back to WCDMA Preferred using the same steps.

Nice find. I've followed the steps so only time will tell now :(

[Guest Victor von Zeppelin]

Uhhh... just doing a diff with MCR 12's 2.6.32 kernel config... just wondering as to add my input into this....

These are switched on in the current nightly 12...

CONFIG_MSM_SMD_DEBUG

CONFIG_MSM_ONCRPCROUTER_DEBUG

CONFIG_MSM_DMA_TEST <- that is set as a module? is that a mandatory thing?

CONFIG_VMSPLIT_3G is set, whereas in MCR 12 is off and CONFIG_VMSPLIT_2G is used instead

CONFIG_PAGE_OFFSET is set at a very high address (0xC0000000), in MCR 12 its, 0x80000000

CONFIG_CPU_IDLE is not set!!!!!!!! <- WHY?

in MCR 12, this is set - CONFIG_ZTE_SUSPEND_WAKEUP_MONITOR=y and CONFIG_SCREEN_ON_WITHOUT_KEYOCDE=y

CONFIG_MTD_TESTS=m <- again is this mandatory?

CONFIG_ANDROID_PMEM_KAPI_TEST=m that is switched off in MCR 12, but active under CM7

CONFIG_ANDROID_PMEM_KAPI_TEST=m, ditto ^^

WiMAX is activated under CM7 which is fair enough - have seen that in the change log... BUT

PPP stuff is activated... dunno - thought WiMAX is using the wireless? unless I am mistaken, that 3G uses that to "dial up"

CONFIG_INPUT_EVBUG=m, <- disabled under MCR 12

CONFIG_USB_GADGET_DEBUG_FILES=y

CONFIG_USB_GADGET_DEBUG_FS=y both of the USB gadget stuff are set

CONFIG_RTC_DEBUG=y

CONFIG_EXT4_FS_XATTR=y <- extra attributes for Ext4 FS.... needed?

CONFIG_CIFS_XATTR=y <- ditto for CIFS

CONFIG_DEBUG_KERNEL=y

CONFIG_DEBUG_BUGVERBOSE=y

CONFIG_DEBUG_INFO=y

CONFIG_DEBUG_USER=y

CONFIG_DEBUG_ERRORS=y

NB: This is a beta kernel so obviously an understanding is required to ensure that there's a reason for the battery draining like 'ell....Ok, so that looks like where the battery drain is coming in, surely with debugging events switched on and logs being produced... not exactly the optimized kernel configuration but at least the diffs highlight those that is mentioned in the above... I have excluded/ignored the CM7 specific patches...

Right lads, anyone willing to try re-compile the kernel ignoring the above and disabling all the debugging stuff and see what happens? :(

What you think? :(

/me fires up bash...

That's actually verrrrry interesting. Considering Tom G's kernel is on github, perhaps these changes could be applied to a new Boot.img very quickly. I'd love to see if it helps battery life...

[Guest t0mm13b]

That's actually verrrrry interesting. Considering Tom G's kernel is on github, perhaps these changes could be applied to a new Boot.img very quickly. I'd love to see if it helps battery life...

Downloading Tom G's kernel and will give it a spin up.... :(

[Guest admanirv]

Thanks to Google, I have found a tiny setting hack which may improve battery life. I found that Cell Standby used to be at the top of Battery Usage. With this hack, I've found that overnight I lost 11% battery instead of 20% earlier. I'm on Nightly 12. Your Mileage May Vary. What I did is this:

1. Open up dialer and enter *#*#4636#*#*. Don't press dial.

2. You will get a testing screen. Choose Phone Information.

3. Scroll down. You will find a dropdown list saying WCDMA preferred. Change that to GSM Auto (PRL)*

4. Tap Turn off radio just below that. And turn it back on again.

5. Reboot. But the settings may work without a reboot. They did for me.

Now on the phone information screen, if you press menu, you get an option to select radio band. You could select accordingly between US, Europe, Japan, etc.

Supposedly the reason it works is because the phone stops scanning for a 3G signal constantly. I've noticed that right now my "Awake Time" is reduced a lot while in standby.

*A few users on other forums have reported that this causes their phone to go on roaming. That didn't happen on my phone however. So try it with caution and keep an eye out for excessive charges when on 3G. I take no responsibility for excessive data/call charges while on this setting. Just try it out yourself and if it doesn't work for you, you can go back to WCDMA Preferred using the same steps.

Thanks, i will try this.

So have you just adjusted to GSM auto (PRL) or have you also adjusted the radio abdn to Europe too?

Cheers

[Guest Victor von Zeppelin]

After a quick play through, after installing N12 (a bit late yes) the 2d performance is far better. Thank god.

[Guest admanirv]

Uhhh... just doing a diff with MCR 12's 2.6.32 kernel config... just wondering as to add my input into this....

These are switched on in the current nightly 12...

CONFIG_MSM_SMD_DEBUG

CONFIG_MSM_ONCRPCROUTER_DEBUG

CONFIG_MSM_DMA_TEST <- that is set as a module? is that a mandatory thing?

CONFIG_VMSPLIT_3G is set, whereas in MCR 12 is off and CONFIG_VMSPLIT_2G is used instead

CONFIG_PAGE_OFFSET is set at a very high address (0xC0000000), in MCR 12 its, 0x80000000

CONFIG_CPU_IDLE is not set!!!!!!!! <- WHY?

in MCR 12, this is set - CONFIG_ZTE_SUSPEND_WAKEUP_MONITOR=y and CONFIG_SCREEN_ON_WITHOUT_KEYOCDE=y

CONFIG_MTD_TESTS=m <- again is this mandatory?

CONFIG_ANDROID_PMEM_KAPI_TEST=m that is switched off in MCR 12, but active under CM7

CONFIG_ANDROID_PMEM_KAPI_TEST=m, ditto ^^

WiMAX is activated under CM7 which is fair enough - have seen that in the change log... BUT

PPP stuff is activated... dunno - thought WiMAX is using the wireless? unless I am mistaken, that 3G uses that to "dial up"

CONFIG_INPUT_EVBUG=m, <- disabled under MCR 12

CONFIG_USB_GADGET_DEBUG_FILES=y

CONFIG_USB_GADGET_DEBUG_FS=y both of the USB gadget stuff are set

CONFIG_RTC_DEBUG=y

CONFIG_EXT4_FS_XATTR=y <- extra attributes for Ext4 FS.... needed?

CONFIG_CIFS_XATTR=y <- ditto for CIFS

CONFIG_DEBUG_KERNEL=y

CONFIG_DEBUG_BUGVERBOSE=y

CONFIG_DEBUG_INFO=y

CONFIG_DEBUG_USER=y

CONFIG_DEBUG_ERRORS=y

NB: This is a beta kernel so obviously an understanding is required to ensure that there's a reason for the battery draining like 'ell....Ok, so that looks like where the battery drain is coming in, surely with debugging events switched on and logs being produced... not exactly the optimized kernel configuration but at least the diffs highlight those that is mentioned in the above... I have excluded/ignored the CM7 specific patches...

Right lads, anyone willing to try re-compile the kernel ignoring the above and disabling all the debugging stuff and see what happens? :(

What you think? :(

/me fires up bash...

Great find, good work.

[Guest css771]

Thanks, i will try this.

So have you just adjusted to GSM auto (PRL) or have you also adjusted the radio abdn to Europe too?

Cheers

I have set GSM auto(PRL) and left the radio band to automatic.