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

[Guest Oyorf]

When people say that battery drain is heavy have you calibrated the battery always after changin ROM? I had pretty bad battery drain in FLB froyo rom (almost 70 %/night / 3g and wifi off) But after battery calibration, consumption is about 2%/night.(for me night is about 8 h and no usage at all)

Edited March 14, 2011 by Oyorf

[Guest supermies123]

Is proximity sensor working in N19? And is it good for everyday use now? Touch screen freezes or crashes?

[Guest alex1alex2alex3alex4]

When people say that battery drain is heavy have you calibrated the battery always after changin ROM? I had pretty bad battery drain in FLB froyo rom (almost 70 %/night / 3g and wifi off) But after battery calibration, consumption is about 2%/night.(for me night is about 8 h and no usage at all)

Yes, even after calibration it drains at a rate of approx. 2% PER HOUR.

[Guest css771]

Here's the kernel with the bt fixed from TomG's sources. bt turns on fine. Thought didn't test transfers or headset or anything.

boot.img

[Guest mELIANTE]

thank you Rotmann, in fact I was thinking about wiping everything... but, I don't understand why if I put the N8 (with cache + dalvik wipe only), the GPS is back... you think it's only a matter of wiping?

As I read in other threads/CM Forums, no wipe no whine :D

Edited March 14, 2011 by mELIANTE

[Guest Scoopading]

well, thanks for the info, but when the GPS was working (i.e., N8) I wasn't using any data service at all, nor Wi-Fi... and the GPS icon on the status bar was turning on/off according to the status of the module... that thing is not true anymore (from some nightly ago, can't remember when).

Yep, but it's not really about using data/WIFI.. it's just about allowing the clock to be set by the ntp service initially, so that its happy its time is up to date and accurate, and you can then disable the data. So it's possible it did that on the old install, and now it's ok with the time, whereas on the new one, if you didn't allow it yet, it might experience problems.. Just a possible cause. But, as said, any weird issues between nightlies and a full wipe should be the first stop. Wish you luck fixing it :D

Edited March 14, 2011 by Scoopading

[Guest Frankish]

Thanks @css for the boot.img. Now for me the only issue is those damned screen freezes. Makes me angry playing Fruit Ninja especially when i am trying to beat my scores :@ :D

I wonder what the best settings for alogcat are to get a decent log? I want to provide lots for them to look at. But not sure of settings...

CSS's boot.img in an update.zip provided. Most recent build so includes battery fixes and also fixes bluetooth. Apply over nightly 19 ideally but will work on others...

BatteryandBluetoothFixKernel.zip

Edited March 14, 2011 by Frankish

[Guest reluctant_traveller]

Is proximity sensor working in N19? And is it good for everyday use now? Touch screen freezes or crashes?

:D there is not that many posts to read to determine that, you only have to go a few pages back until you reach the point N19 hit the download servers.

stick the forum in Lo-Fi mode and you could skim the posts quicker than it took me to write this.

[Guest gat2011]

Thanks @css for the boot.img. Now for me the only issue is those damned screen freezes. Makes me angry playing Fruit Ninja especially when i am trying to beat my scores :@ :D

I wonder what the best settings for alogcat are to get a decent log? I want to provide lots for them to look at. But not sure of settings...

CSS's boot.img in an update.zip provided. Most recent build so includes battery fixes and also fixes bluetooth. Apply over nightly 19 ideally but will work on others...

big thx. have been to-ing and froing from rom to rom to suit needs,was getting dizzy remembering which rom had which glitch etc. can stick on this one now!

[Guest Frankish]

big thx. have been to-ing and froing from rom to rom to suit needs,was getting dizzy remembering which rom had which glitch etc. can stick on this one now!

Thank css for building the boot.img i just packed it up with a bow on it :D

Really must set up for building. I probably have time the little un has turned out to be a creature of the night. Daytime she slumbers :(

[Guest grmn]

Hmm I still get the occasional "screen stays blank after call" with N19 and have to cover/uncover the prox sensor with my hand to get the screen to come back.

I did: wipe cache/data/dalvik cache and format /system. Also didnt restore anything.

Of course I also ticked always use prox. and unticked in-call UI and restarted.

Anyone else? Or does it just take a really long time to come back?

[Guest css771]

Thank css for building the boot.img i just packed it up with a bow on it :D

Really must set up for building. I probably have time the little un has turned out to be a creature of the night. Daytime she slumbers :(

:( TomG is the one we should thank. He's the one writing and fixing the code while we just put bows on top of it :D

[Guest gat2011]

:D TomG is the one we should thank. He's the one writing and fixing the code while we just put bows on top of it :(

truly - thx to all of you. really is a great example of people working together to absolutely great effect.

[Guest Frankish]

@grmn It works for me with Always use proximity ticked and In Call UI TICKED.

@css771 Yeah TomG is a machine, he was quiet for a bit and all of a sudden BANG. Fixes galore, let's hope he knows how to fix screen freezes. All other bugs are minor!

[Guest grmn]

@grmn It works for me with Always use proximity ticked and In Call UI TICKED.

Ok will try that, thx.

[Guest Saransh Agarwal]

Thanks @css for the boot.img. Now for me the only issue is those damned screen freezes. Makes me angry playing Fruit Ninja especially when i am trying to beat my scores :@ :D

I wonder what the best settings for alogcat are to get a decent log? I want to provide lots for them to look at. But not sure of settings...

CSS's boot.img in an update.zip provided. Most recent build so includes battery fixes and also fixes bluetooth. Apply over nightly 19 ideally but will work on others...

Hey whileplaying fruit ninja try swipping mulriple fingrs on screenfreeze n it will come back

WORKS FOR ME PLS CHECK IF IT WORKS FOR U

[Guest marcodassi]

Well, there's definitely a GPS module issue.

Test bench: Nightly 19 + "bluetooth kernel fix" (some posts above); completely wiped phone - fresh ROM reinstall

1. Using power widget, turn on GPS module; status icon will NOT turn on (seems that if the GPS is not required, it stays in standby - nice!)

2. Using "GPS Status & Toolbox" as a tester, launch it; the status icon will turn on and flash (signaling activity) and it will fix the position

3. Exit GPS Status, turn off GPS module using power widget, then wait for the status icon to disappear

4. Turn on GPS module again; status icon will NOT turn on, as in point 1.

5. Relaunch GPS Status; this time the status icon will NOT show up, it will not fix anymore, and the display is very choppy

Workaround for now:

1. Using power widget, turn the GPS module on

2. Reboot; now the GPS will work again (you can test it from the above point 2)

Another "workaround" to be tested

1. Leave the GPS module always on... hoping it will turn off automatically when not required... have to check battery usage!

It seems like the power widget has some problems when turning the GPS "off"...

Please test...

PS: On nightly 8, everything was OK - you can turn on and off the GPS module as much as you want

PPS: Confirmed for now by Trademark-NRW

PPPS: Anyone can submit this issue to the developers? I think I haven't the rights...

Edited March 14, 2011 by marcodassi

[Guest fredewis]

im using rc2 with the kernel by css and it is awesome thankx also im using adw ex as main launcher and is as smooth as anything .......... impressed no lag at all i wonder if you guys could try my settings to see if it works for you.

adw_ex_settings.xml

all you do is place in sd card go into adw ex and restore settings .......(not too sure if it works).

Edited March 14, 2011 by fredewis

[Guest targetbsp]

0% drop in 5 hours of airplane from 100%. This would previous have been down in the 80's. You guys rule. :(

I know some of you guys don't rate measuring from 100% but in Froyo it has never failed to stay at 100% over several hours in airplane and in CM7 in has never previously failed to drop into the 80's so I personally am content with the consistency of my testing. :D

Edited March 14, 2011 by targetbsp

[Guest Trademark-NRW]

Well, there's definitely a GPS module issue.

Can confirm this. Same behaviour here.

[Guest Fransis.co]

im using rc2 with the kernel by css and it is awesome thankx also im using adw ex as main launcher and is as smooth as anything .......... impressed no lag at all i wonder if you guys could try my settings to see if it works for you.

adw_ex_settings.xml

all you do is place in sd card go into adw ex and restore settings .......(not too sure if it works).

Rename to adw_settings.xml

Very choppy App drawer for me, always has been.

To make it smooth, untick `Show App Labels`...if you can remember what the icons are !

Standard Gingerbread Launcher from the Market, is the only Launcher I`ve found that is smooth even with App Labels enabled.

[Guest JayGB1982]

Updated from Nightly 17 - 19 earlier and also updated the Kernel using the CSS Kernel ZIP.

The battery life issue is long gone :D Also sorted a issue I had where I had to re-connect wifi after sleep..

Thanks again :(

[Guest Scoopading]

0% drop in 5 hours of airplane from 100%. This would previous have been down in the 80's. You guys rule. :(

I know some of you guys don't rate measuring from 100% but in Froyo it has never failed to stay at 100% over several hours in airplane and in CM7 in has never previously failed to drop into the 80's so I personally am content with the consistency of my testing. :D

That's a good indicator that the battery behaviour is now similar to Froyo firmwares, but it doesn't really tell you how long the phone will actually last on standby. On previous CM7 kernels the charge would hold at 99-100% for the first 3 hours, then drop at just under 2% per hour. The reason for this is the phone doesn't want to overcharge the battery, so it'll say anything within a certain range is 99 or 100% when its actually less. In other words, your phone might've lost some battery, but Android won't really show you it because it's trying to prolong your batteries lifespan. That's why you can't really be sure when you measure from 100%.

On the updated CM7 kernel the behaviour appears to have changed. It took 18 hours to drop the first 6 percent on idle, but then the rate of loss started to speed up and become more predictable, and seems to be settling around about 0.7% loss per hour (which is still almost 1/3rd the rate of drain of the previous kernels). If the rate continued in a linear fashion (though it's unlikely to as it approaches zero percent) that means this updated kernel would give somewhere around 6.5 days of standby time. ZTE's (probably over-optimistic) standby specs rate the Blade as having 9 days of standby time, so if you can get about 7 days (or more if the rate of loss slows as it approaches zero) in "real world", non-lab, conditions with this rom then that's pretty decent. If someone wants to say for sure then they'll have to leave the phone sitting there for the next week :(

But it's great to have a rom which everyone can realistically use day to day now. It's all minor bugs left, except for the touchscreen freeze and lack of responsiveness at certain sections (like sometimes when you try to pull the status bar notifications menu back up).

[Guest Zythus]

Guys, when Im tryin to put my bluetooth on, it tries to get on, but it do not. Wtf? U have it too? :D

Using N19

[Guest alex1alex2alex3alex4]

Guys, when Im tryin to put my bluetooth on, it tries to get on, but it do not. Wtf? U have it too? :D

Using N19

Can I suggest you please read at least a page or two back before you ask questions which have

already been raised hours ago ?

An updated kernel fixing this is available for download on the previous page.