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

[Guest muluman]

Does WiFi disconnect on sleep on CM7 like it does on other roms?

[Guest t0mm13b]

Am running nightly 8 and the battery is desperate!!! Never seen anything like it - I barely get a day on the battery and used the Spare Parts option to set End button to sleep. However, was digging around and came across this thread which may provide a clue - the lockscreen, since it would be consuming power and draining it. The most common theme here among the posts, is that at nighttime, with airplane mode on, the lockscreen could be the likely culprit. I will set alogcat to record the log tonight and report on this tomorrow.

[Guest Chris_M]

Am running nightly 8 and the battery is desperate!!! Never seen anything like it - I barely get a day on the battery and used the Spare Parts option to set End button to sleep. However, was digging around and came across this thread which may provide a clue - the lockscreen, since it would be consuming power and draining it. The most common theme here among the posts, is that at nighttime, with airplane mode on, the lockscreen could be the likely culprit. I will set alogcat to record the log tonight and report on this tomorrow.

If you read the link carefully, he's suggesting that some AFTERMARKET lock screens may stop the phone from going into sleep mode. This doesn't (or at least shouldn't) affect the default Android lockscreen...

[Guest Maringer]

On Nightly 8 and I've just encountered the proximity problem for the first time. Following a 3 minute call, the screen refused to come on again and I could hear white noise coming out of the speaker.

I think the problem may be down to an unexplained quirk of my phone. For some reason, whenever I have been connected with a call to a landline, the dialler won't automatically disconnect when the call ends. On previous ROMs, this hasn't been a problem as I can simply press the end call button. However, I obviously can't do this if the screen is not reactivating...

I'll have to decide whether it is worth my rolling back to a Froyo ROM. Can I avoid phoning landlines? Could be inconvenient!

Incidentally, does anybody know why my phone should refuse to automatically disconnect after calls to landlines, both incoming and outgoing calls?!? A strange phenomenon for me.

[Guest Victor von Zeppelin]

With my normal usage on a work day today, which pretty much means my usage is identical, i managed to squeeze 11 hours max today. Other roms like FLB last around 18 hours for me. I disable data when not using it (manually), i do not use wifi, i always set the end button behaviour with SP, i have nothing suspicious reported in spare parts relating to battery use for time since unplugged or all time.

Pretty much nothing obviously apparent is draining the battery. It's something deep in the rom, standby time is pretty poor. :huh:

Fantastic rom otherwise. Battery drain and screen freeze my only real issue with this bad boy rom.

Pretty much this. I use my phone very responsibly, and when it's on, battery life is standard. Pocketed and put to sleep, battery falls far too fast, and there's nothing that changes it. Nightly 8 seems worse, too. I've resorted to turning the phone off at night, so it doesn't use up 20% of the battery.

Thing is, we can rant, but no logcats are showing the probelm it seems, and hence the fix is pretty far off, as the cause isn't known.

[Guest The Soup Thief]

On Nightly 8 and I've just encountered the proximity problem for the first time. Following a 3 minute call, the screen refused to come on again and I could hear white noise coming out of the speaker.

I think the problem may be down to an unexplained quirk of my phone. For some reason, whenever I have been connected with a call to a landline, the dialler won't automatically disconnect when the call ends. On previous ROMs, this hasn't been a problem as I can simply press the end call button. However, I obviously can't do this if the screen is not reactivating...

I'll have to decide whether it is worth my rolling back to a Froyo ROM. Can I avoid phoning landlines? Could be inconvenient!

Incidentally, does anybody know why my phone should refuse to automatically disconnect after calls to landlines, both incoming and outgoing calls?!? A strange phenomenon for me.

:huh:

Bah! After thinking I was over that proximity sensor problem, my phone having reawakened happily on Nightly 6 many times friday and saturday, I too just had it fail to wake from a call on nightly 8. It was unresponsive to any amount of button pushing though I could still hear the call (to my voicemail) was connected, meaning I had to pull the battery

Very annoying

Fraid to report that I've bailed on N8 and reverted to my last known good nandroid with N6, so I'm afraid that's what I'm driving til the next nightly raises his sleepy head

@Maringer As I mention, mine just failed to hang up on a voicemail call (to Vodafone IE) - not sure whether that counts as landline or mobile. Aside from that call to voiccemail I've only made a couple of brief calls to mobiles since installing so can't really comment on your point about landline calls

Remember that on the RC1 I was getting it with calls to mobiles

Edited February 28, 2011 by The Soup Thief

[Guest Zythus]

Dunno where is the problem of that screen.

Maybe try to phone to different devices - mobiles, and landline phones, different lengths of calls... maybe we can find out what it is...

Edited February 28, 2011 by Zythus

[Guest wbaw]

Does WiFi disconnect on sleep on CM7 like it does on other roms?

No :huh:

It defaults to wifi off when the screen goes off, but if you change it to never go off, then it actually does what it says it will on this rom :)

[Guest muluman]

No :)

It defaults to wifi off when the screen goes off, but if you change it to never go off, then it actually does what it says it will on this rom :P

Aha perfect :huh: thanks

[Guest t0mm13b]

Ok, I have attached here the log via aLogCat, on pastebin.

The goal was to set it to sleep, and see what happens...

Can someone check this as I cannot find this - there seems to be intermittent polling for the ntp server....this happens periodically - time server app or is it GPS...?

request time failed: java.net.UnknownHostException: europe.pool.ntp.org

Also...

Can't open keycharmap file

Error loading keycharmap file '/system/usr/keychars/blade_keypad.kcm.bin'. hw.keyboards.196609.devname='blade_keypad'

Using default keymap: /system/usr/keychars/qwerty.kcm.bin

I'm tired mEndcallBehavior=0x2

And there seems to be excessive gc running... in between the log

Configuration:

Running ADW Ex with Fancy Widget...

Instead of tearing off to file on the cyanogenmod issue tracker...hope this would help with a few eagle eyes to see what's happening.

[Guest Spaennis]

also encountered the proximity sensor problem with nightly 8 now...

[Guest tttonyyy]

Yep me too, calling voicemail. Pressing vol up/down seemed to bring the screen back but that might be a coincidental timing thing (was pressing everything trying to get the screen back to end the call!)

[Guest IronDoc]

The keymap thing happens every time you press a button afaict. I assumed that it wasn't finding a specific blade layout and using the default, but now I look at it it seems there is a file which it fails to load.

Not sure if this matters at all though.

Edited February 28, 2011 by IronDoc

[Guest fonix232]

The keymap thing happens every time you press a button afaict. I assumed that it wasn't finding a specific blade layout and using the default, but now I look at it it seems there is a file which it fails to load.

Not sure if this matters at all though.

It does not matter, a usual message what is declared as a problem. If you copy the matching binary key layout and rename it as the missing file, you will make that message disappear.

[Guest css771]

All right, there is something going on with the battery reporting too, probably related to or not related to the fast battery drain.

I rebooted the phone on 42% battery life while connected to a computer. After the reboot, the phone reported 22% battery life. Since it was already connected, the phone went up to 42% again in maybe 2 minutes (literally.) I dont know for sure if this is a bug related to the battery reporting in CM. Just an observation I thought I'd put out there.

[Guest uskixboy]

also encountered the proximity sensor problem with nightly 8 now...

Hmm me too... sort of... took the phone from my ear so as to press end call, but screen stayed black. For some reason though I put the phone back to my ear and away again this time screen came on... curious.

And still getting touch screen freezes sometimes but after turning display off and on again it re-activates.

[Guest Zythus]

but screen stayed black

So after the call, it goes black, and stays black yeah?

So maybe let's try, when u are calling, to make it still active - it won't go black and wont freeze?

[Guest dadashi]

First question, is it possible to install the cm7 rom from FLB-10 without a wipe...?

Secondly, I installed the "night-6" and it didn't see my Ext2 partition, apps don't install to Ext2 partition any more...none of the usuall system apps like Titanium or Astra see the partition either...

[Guest wbaw]

First question, is it possible to install the cm7 rom from FLB-10 without a wipe...?

No

Secondly, I installed the "night-6" and it didn't see my Ext2 partition, apps don't install to Ext2 partition any more...none of the usuall system apps like Titanium or Astra see the partition either...

Get simple2ext, Android Market.

[Guest martyCZ]

All right, there is something going on with the battery reporting too, probably related to or not related to the fast battery drain.

I rebooted the phone on 42% battery life while connected to a computer. After the reboot, the phone reported 22% battery life. Since it was already connected, the phone went up to 42% again in maybe 2 minutes (literally.) I dont know for sure if this is a bug related to the battery reporting in CM. Just an observation I thought I'd put out there.

I think this is standard Android behaviour. Boot process is decent load and battery voltage drops under that load. During boot process there battery percentage is calculated from actual - dropped - battery voltage. After boot is completed battery voltage is restored nearly to level before boot. But because Android never (or nearly never) rises estimated battery percentage you can see same percentage for next few hours. If you reboot for second time there probably will be no drop in percentage at all because final voltage will be same. If you connect phone to computer/charger Android must rise its estimated percentage and because battery voltage is already restored Android rises battery percentage very quickly to previous level.

[Guest Szpilman]

Does the 3d hardware acceleration work with any of those Nightly builds? I can't launch any 3d games i get "Failure to initialize Your hardware does not support this application, sorry!" and it worked before when I used JJ. I cant even benchmark in Quadrant because of black screen in 3d mode. Is it because the kernel? Or my Blade is phucked? I couldn't find any solution :/

[Guest LordKickapoo]

Quadrant runs full benchmarking in my Blade with flaming 813 points (FLB and JJ about 550).

[Guest Pelemane]

Does the 3d hardware acceleration work with any of those Nightly builds? I can't launch any 3d games i get "Failure to initialize Your hardware does not support this application, sorry!" and it worked before when I used JJ. I cant even benchmark in Quadrant because of black screen in 3d mode. Is it because the kernel? Or my Blade is phucked? I couldn't find any solution :/

What 3D games are you trying to play? Need For Speed Shift runs perfectly on nightly 8.

[Guest Brumski]

Using nightly 8. Have noticed 3 random restarts. 2 of which when I wasn't using the phone and I just happened to see the blue Cyanogenmod startup logo. Happened today when I was using the Youtube application, watching a video and pressed the power button then it came back on and then just suddenly the startup logo appeared.

[Guest Rotmann]

Is there any way to make the killing of background threads less aggressive in CM?

My sportstracker pro bluetooth heart rate monitor keeps getting killed when the screen is on sleep. The tracker keeps on recording the GPS position / speed etc and it *thinks* the monitor is still connected but reports a constant bpm - it could be a bluetooth stack issue. It works fine on Paul's R12 rom. I do see these in the logcat sometimes:

I/am_kill ( 176): [659,com.sportstracklive.android.zephyr,12,too many background]

I/am_proc_died( 176): [659,com.sportstracklive.android.zephyr]

It might be another issue but I'd like to eliminate this as a potential source of the problem!

You can set the behavior in spare parts.

All right, there is something going on with the battery reporting too, probably related to or not related to the fast battery drain.

I rebooted the phone on 42% battery life while connected to a computer. After the reboot, the phone reported 22% battery life. Since it was already connected, the phone went up to 42% again in maybe 2 minutes (literally.) I dont know for sure if this is a bug related to the battery reporting in CM. Just an observation I thought I'd put out there.

As stated lots of times, the android battery reporting is not what people would call accurate.

First question, is it possible to install the cm7 rom from FLB-10 without a wipe...?

Secondly, I installed the "night-6" and it didn't see my Ext2 partition, apps don't install to Ext2 partition any more...none of the usuall system apps like Titanium or Astra see the partition either...

1. Surely not, it will screw your system.

2. You have to put an ext3 partition and install s2e (simple2ext) from the market and set it once to install apps to SD, reboot and that's it. If you would have read the first two posts you would have known this.

Does the 3d hardware acceleration work with any of those Nightly builds? I can't launch any 3d games i get "Failure to initialize Your hardware does not support this application, sorry!" and it worked before when I used JJ. I cant even benchmark in Quadrant because of black screen in 3d mode. Is it because the kernel? Or my Blade is phucked? I couldn't find any solution :/

Games rock on CM7, you screwed something. Did you wipe and install according to the instructions?

Regarding battery, I have had RC1 clean installed, no gapps, no settings no nothing, all standard, left it in airplane mode for 12 hours and it has eaten 20%, spare parts reported the phone slept like a baby. I have attached the log on the issue tracker if some people are interested. The things that seem dubious to me are the hyperactive garbage collector and the time actualization.

Edited February 28, 2011 by Rotmann