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

[Guest Lew247]

Don't think so, I never had 3G data on so far.

I think you'll find that "3G data" = 2G/3G data ie any data using the phone and not wifi

so having 3G turned off won't stop it using data

[Guest goatee]

I've only just downloaded N13, but even with previous versions, overnight, in airplane mode, I've been losing around 15% whereas in the past I'd lose around 1%. Looks like something else is going on - though of course it could be a process caning the CPU trying to get a data connection, even though it's in airplane mode.

I think you'll find that "3G data" = 2G/3G data ie any data using the phone and not wifi

so having 3G turned off won't stop it using data

[Guest alex1alex2alex3alex4]

I think you'll find that "3G data" = 2G/3G data ie any data using the phone and not wifi

so having 3G turned off won't stop it using data

Let me clarify:

I NEVER had data on AT ALL.

Only WiFi (which is a couple of reboots back now) to enable updates, but whether WiFi was on or off,

it drains at the same rate.

Edited March 7, 2011 by alex1alex2alex3alex4

[Guest curl66]

a question for the experianced guys here.

since i am got very strange effekts with N12. behavior differs totaly on 2 phones.

yesterday i upgrade a friends phone from JJ9 to N12. I did a full wipe, format system installed RC1 then N12.

homeboutton dosnt work, also lot of issues.

meanwhile my phone with N12 works fine. also homeboutton. difference was that i installed like this: JJ9, full wipe, format system, RC1 N1,N2,N3...N12

since a lot of other people complain about issues, others not i come to the conclusion that files from some Nxx builds are may be get mixed up?

so what ist the recommended way to install an Nxx ? just install it over a previous Nxx? or

do always full wipe, format system, install RC1 then actuall Nxx ?

[Guest ppa123]

About The Battery Drainage

Last night, running on N12 still got the 2-3% per hour drainage. Looked at spare parts/battery history and nothing special there in partial wake, cpu, network, gps or other usage. Then lurked into sensor usage and noticed that there was a lot of usage divided almost evenly between 4 processes/apps (Android system, Gallery, Maps and Camera). Phone had been on standby for 4,5h and each process had little more than 1h of sensor usage. What could that all be???

PS. Congrats to Frankish + missus = jr! :( Nice to hear that everything went well.

[Guest Scoopading]

so what ist the recommended way to install an Nxx ? just install it over a previous Nxx? or

do always full wipe, format system, install RC1 then actuall Nxx ?

I always do a full wipe. Whilst you can probably update most nightlies just fine, it's the only way to be "sure" problems aren't related to leftovers from a previous install.

[Guest Scoopading]

About The Battery Drainage

Last night, running on N12 still got the 2-3% per hour drainage. Looked at spare parts/battery history and nothing special there in partial wake, cpu, network, gps or other usage. Then lurked into sensor usage and noticed that there was a lot of usage divided almost evenly between 4 processes/apps (Android system, Gallery, Maps and Camera). Phone had been on standby for 4,5h and each process had little more than 1h of sensor usage. What could that all be???

Even if you kill the Gallery, maps, and camera, the battery still drains. It's often been noted that when you try "top -m 10" from a command line akmd2 (which is sensor related) is usually the top CPU process, eating about 6% CPU. But adding a data/delay value to minimize that doesn't seem to have any effect on battery drain either. As I said, this seems to be something more fundamental happening at driver/kernel level which is preventing the phone (other than the screen) from sleeping properly.

[Guest alex1alex2alex3alex4]

yesterday i upgrade a friends phone from JJ9 to N12. I did a full wipe, format system installed RC1 then N12.

homeboutton dosnt work, also lot of issues.

meanwhile my phone with N12 works fine. also homeboutton. difference was that i installed like this: JJ9, full wipe, format system, RC1 N1,N2,N3...N12

since a lot of other people complain about issues, others not i come to the conclusion that files from some Nxx builds are may be get mixed up?

so what ist the recommended way to install an Nxx ? just install it over a previous Nxx? or

do always full wipe, format system, install RC1 then actuall Nxx ?

Imho you could have gone straigth from JJ to N12 without any intermediate installs,

but yes, a full wipe IS required in that scenario.

The important thing here:

Do NOT, I repeat do NOT ('not' as in NEVER) restore anything from a backup taken from the Froyo ROM.

[Guest Scoopading]

BTW - earlier on I complained about slow GPS speed. I updated the gps.conf file manually to point to uk.pool.ntp.org, instead of the default europe which it was pointing to, but it didn't make much difference. So, as as per mbaws "GPS Fix, Speed up GPS response" thread, I used the additional lines there, and it does make a difference. GPS Status is now behaving normally, generally getting a first fix even from indoors in under 45 seconds. So, if anyone else experiences slow GPS, they might try changing to their local ntp server and adding these lines to the end of their gps.conf file

DEBUG_LEVEL=3

INTERMEDIATE_POS=1

ACCURACY_THRES=5000

ENABLE_WIPER=1

CURRENT_CARRIER=common

DEFAULT_AGPS_ENABLE=TRUE

DEFAULT_SSL_ENABLE=FALSE

DEFAULT_USER_PLANE=TRUE

[Guest mr_mufy]

Thanks Cm for this mods.

I have a problem, i'm traying install the HTC_IME of jonas but i can't.

The app give always a unknow error. our doens't do nothing.

any one has any idea?

[Guest alex1alex2alex3alex4]

Thanks Cm for this mods.

I have a problem, i'm traying install the HTC_IME of jonas but i can't.

The app give always a unknow error. our doens't do nothing.

Don't think there's a Gingerbread version of it, is there ?

[Guest t0mm13b]

Thanks Cm for this mods.

I have a problem, i'm traying install the HTC_IME of jonas but i can't.

The app give always a unknow error. our doens't do nothing.

any one has any idea?

uhhhh... that is for froyo and eclair, a mod to give "gingerbread" keyboard to those versions... :(

No need for it in this CM7... :(

[Guest ppa123]

Even if you kill the Gallery, maps, and camera, the battery still drains. It's often been noted that when you try "top -m 10" from a command line akmd2 (which is sensor related) is usually the top CPU process, eating about 6% CPU. But adding a data/delay value to minimize that doesn't seem to have any effect on battery drain either. As I said, this seems to be something more fundamental happening at driver/kernel level which is preventing the phone (other than the screen) from sleeping properly.

Ok, thanks for clearing that out. We've to wait and see what the devs and others find.

[Guest Zythus]

Going to flash N13 after I get back home

I saw battery usage in settings, and it shows 49% for screen! :(. Thats so much...

[Guest Chrisund123]

Going to flash N13 after I get back home

I saw battery usage in settings, and it shows 49% for screen! :(. Thats so much...

Thats nothing, my Desire HD shows 69% for the screen - and thats the lowest I've ever seen it, normally at least 75-80% :(

[Guest _BG_]

New Google apps as of: 20110307...

Can anyone place a link for downloading the new gapps pack? The one in first page is still the old one...

[Guest chall32]

Have my suspicions that proximity sensor issue and battery drain are linked some how. Remember the old "Turn to mute" issue? http://android.modaco.com/content/zte-blad...e-dialer-issue/ (for those not into what seems like ancient history now)

Except the drain isn't showing up as an app in battery history. No real substantial evidence for this other than we have seen battery drain due to sensors previously. Fix the proximity issue and battery life will improve.

As I say it's just a suspicion, that's all.....

[Guest bhf]

Can anyone place a link for downloading the new gapps pack? The one in first page is still the old one...

Gapps or Mirror. md5: 29efd1cc5457849b10d4f0dc31f7f04c

Edited March 7, 2011 by bhf

[Guest jayhix]

Re: proximity sensor for N13.

It does work better than N12, i can at least get the screen to come back on after taking it away from my face. however it doesnt do it automatically i have to cover up the sensor with my thumb and take it away once or twice but the screen comes back on then.. better than taking the battery out!

[Guest swordtail]

What are the ramifications of HDCRJacob going, is this going to have an impact on fixes for the Blade?

[Guest paulocostavct]

When i try to reboot my phone using n11 and n12 it get stuck and i have to flash the Tom again. Is it just me or did it happen to anyone else?

[Guest targetbsp]

What are the ramifications of HDCRJacob going, is this going to have an impact on fixes for the Blade?

Err... looking at the time of his going... I assumed he was going to sleep?? Not going going. Or am I wrong?

Edited March 7, 2011 by targetbsp

[Guest t0mm13b]

What are the ramifications of HDCRJacob going, is this going to have an impact on fixes for the Blade?

WHA'? :( :(

[Guest Watashi_PT]

When i try to reboot my phone using n11 and n12 it get stuck and i have to flash the Tom again. Is it just me or did it happen to anyone else?

it's just you. did you did a full wipe before installing the rom's?

[Guest paulocostavct]

yes i always do a full wipe. That's weird.