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

[Guest Frankish]

Well yeah, it's the kernel and some files around it. An update zip should do the trick.

What other files? I though it just enabled wakelock for proximity in kernel?

[Guest Krinyo]

I have charging problem too. If I reset battery stats, then charging ok for the first time, but after that it's really slow, and stops at various percentages: 64-70, 80%. Weird. If I switch off the phone, it's chaging properly: it's not a hardware issue. And not with CM7, i'm using JJ atm...

I think this issue somehow related to the CW recovery flashing to the latest version. Really weird.

[Guest MestariEetu]

Is this yet usable for basic things to do with phone? Like wth flb 2.2? Thanks

[Guest Rotmann]

Is this yet usable for basic things to do with phone? Like wth flb 2.2? Thanks

Yesno, noyes? :(

P.S.: Read the damn two posts.

Edited March 5, 2011 by Rotmann

[Guest alex1alex2alex3alex4]

Is this yet usable for basic things to do with phone? Like wth flb 2.2? Thanks

Define "basic things".

It is for me - YMMV

[Guest MestariEetu]

Define "basic things".

It is for me - YMMV

Gaming, calling, messages, internet, etc...

[Guest Frankish]

Can anyone who has a build environment currently set up build toms kernel if the changes have been applied to let cpu sleep. Then upload it? I'm getting help to set myself up but i'm not home until later tonight.

[Guest spaceguy]

I've had similar and it turned out to be the usb lead I was using.Even though it showed as charging it was only Charging about 5% every couple of hours so I swapped that out for another and it fixed my problem.

If you guys want to go deeper, there is a application called battery monitor widget. This application helped me alot with my battery drain problems. Because it showes you how many mA you are consuming and how many mA you are charging with. When charging through the wall you get about 500 mA but that is not the case when using the usb to charge. Usb gives you a much lower number.

Edited March 5, 2011 by spaceguy

[Guest marcodassi]

Hello,

n00b question: regarding the N12 "idle" problem, how can I temporary fix that file? Can't find it in the N12 .zip ... maybe using something as root explorer, directly on the phone?

@@ -397,7 +397,9 @@ CONFIG_CPU_FREQ_GOV_POWERSAVE=y

CONFIG_CPU_FREQ_GOV_USERSPACE=y

CONFIG_CPU_FREQ_GOV_ONDEMAND=y

CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y

-# CONFIG_CPU_IDLE is not set

+CONFIG_CPU_IDLE=y

+CONFIG_CPU_IDLE_GOV_LADDER=y

+CONFIG_CPU_IDLE_GOV_MENU

CONFIG_CPU_FREQ_MSM=y

#

thanks a lot!!!

- marco

[Guest Victor von Zeppelin]

Can anyone who has a build environment currently set up build toms kernel if the changes have been applied to let cpu sleep. Then upload it? I'm getting help to set myself up but i'm not home until later tonight.

The latest kernel is actually Jacob's ATM, as hewas the one who pushed it upto cm. However, the latest commit shows a new kernal upload and a Few other files changed too. Ithink that those files will need to be rolled into an update, if anyone's gonna do it. Should be good.

[Guest skymera]

Hello,

n00b question: regarding the N12 "idle" problem, how can I temporary fix that file? Can't find it in the N12 .zip ... maybe using something as root explorer, directly on the phone?

@@ -397,7 +397,9 @@ CONFIG_CPU_FREQ_GOV_POWERSAVE=y

CONFIG_CPU_FREQ_GOV_USERSPACE=y

CONFIG_CPU_FREQ_GOV_ONDEMAND=y

CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y

-# CONFIG_CPU_IDLE is not set

+CONFIG_CPU_IDLE=y

+CONFIG_CPU_IDLE_GOV_LADDER=y

+CONFIG_CPU_IDLE_GOV_MENU

CONFIG_CPU_FREQ_MSM=y

#

thanks a lot!!!

- marco

Afraid not. That is from the .config file of the kernel. To include, those, the kernel must be recompiled.

[Guest alex1alex2alex3alex4]

Hello,

n00b question: regarding the N12 "idle" problem, how can I temporary fix that file? Can't find it in the N12 .zip ... maybe using something as root explorer, directly on the phone?

@@ -397,7 +397,9 @@ CONFIG_CPU_FREQ_GOV_POWERSAVE=y

CONFIG_CPU_FREQ_GOV_USERSPACE=y

CONFIG_CPU_FREQ_GOV_ONDEMAND=y

CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y

-# CONFIG_CPU_IDLE is not set

+CONFIG_CPU_IDLE=y

+CONFIG_CPU_IDLE_GOV_LADDER=y

+CONFIG_CPU_IDLE_GOV_MENU

CONFIG_CPU_FREQ_MSM=y

#

thanks a lot!!!

- marco

These are BUILD options, not runtime options ...

[Guest Victor von Zeppelin]

And Marco, it can't be updated manually, its compiled into the kernel, which is an uneditable binary file.

EDIT : beaten to the punch :(

Edited March 5, 2011 by Victor von Zeppelin

[Guest Mike_P]

If you guys want to go deeper, there is a application called battery monitor widget. This application helped me alot with my battery drain problems. Because it showes you how many mA you are consuming and how many mA you are charging with. When charging through the wall you get about 500 mA but that is not the case when using the usb to charge. Usb gives you a much lower number.

I used this fine on Froyo but on CM7 it just doesn't record any current usage at all.

I'm still on RC1 and I do wonder if the voltage reading bug (3/4mv) could be affecting this though.

[Guest marcodassi]

Thank you guys!

It's a compile-time config... got it :(

Waiting anxiously for the next ROM so (I'm on Win and can't compile it myself)

cheers

[Guest alex1alex2alex3alex4]

Gaming, calling, messages, internet, etc...

My profile may be different to that of many others, but there you go:

- gaming: I don't use the phone for it, but others reported CM7 does a good job in running games smoothly

- calling: I use a BT headset, no issues so far, others reported there are issues with the screen staying black when ending calls - please browse this topic and you'll find these reports as well as workarounds.

- messages, internet: no issues for me, all fine.

[Guest Victor von Zeppelin]

I used this fine on Froyo but on CM7 it just doesn't record any current usage at all.

I'm still on RC1 and I do wonder if the voltage reading bug (3/4mv) could be affecting this though.

Update to N12, then we'll help. At the current rate, RC 1 is positively ancient.

[Guest MrPhuong]

When I receive a call from anyone, after end, I can't turn on srceen by any way.

So I have to take out batery to reboot my blade.

Can you help me fix this error?

Edited March 5, 2011 by MrPhuong

[Guest alex1alex2alex3alex4]

When I receive a call from anyone, after end, I can't turn on srceen by any way.

So I have to take out batery to reboot my blade.

Can you help me fix this error?

did you set

Menu>settings >accessibility >powerbutton ends call

as has been recommended as a fix / workaround for this ?

[Guest simonckenyon]

is there a howto somewhere for building the kernel?

and more to the point - which kernel source is being used to build binary that is in the nightlies?

[Guest MrPhuong]

did you set

Menu>settings >accessibility >powerbutton ends call

as has been recommended as a fix / workaround for this ?

That's right!

Thank you so much for help me!

I'm a software developer.

So If you need to help anything, contact me. :(

[Guest alex1alex2alex3alex4]

is there a howto somewhere for building the kernel?

and more to the point - which kernel source is being used to build binary that is in the nightlies?

As I asked that question myself I went looking for such a guide and found

http://forum.xda-developers.com/showthread.php?t=915435

Trying that as we speak :(

[Guest IronDoc]

When I receive a call from anyone, after end, I can't turn on srceen by any way.

So I have to take out batery to reboot my blade.

Can you help me fix this error?

Read the OP for god's sake.

[Guest minz007]

i tried nightly 12 and i really like it :(

but every time i switch the phone off and then switch it back on it bootloops and i have to reinstall it again with a wipe otherwise it does not come back. :(

is there a fix?

im using an oled model

if this has been reported and solved already im sorry but i could not find it with the search

thanks in advance for any help

[Guest alex1alex2alex3alex4]

i tried nightly 12 and i really like it :(

but every time i switch the phone off and then switch it back on it bootloops and i have to reinstall it again with a wipe otherwise it does not come back. :(

is there a fix?

From which ROM / Version did you upgrade to N12 ?

Did you wipe anything or just install on top of what you had before ?