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

[Guest mankulito]

Why Honeycomb lockscreen works only with rc1, not with nightly?

[Guest css771]

Wouldn't that garbage collection show in the log? When I looked at the log it showed very little whilst it slept (only 2 or 3 events after exactly every 30 or 60 minutes), and it still consistently dropped around 2% per hour. So I don't think it's the garbage collection.. It behaves much more like the wireless WIFI component isn't being switched off or something (even though it's not connected to anything.. )

It does show up in the logs. Atleast all logs I've looked at on my phone running N8. On standby, every 15-20 secs, there's a GC_Concurrent or GC_EXTERNAL_ALLOC running. Now I'm not saying that's what's resulting in the bad battery life. I'm not sure. It may be due to something else, or not.

[Guest Victor von Zeppelin]

Why Honeycomb lockscreen works only with rc1, not with nightly?

Different Framework-res apk. As a lot of devices were pretty stable at RC1, it's safe to assume some people are still using that. But as our RC1 was our first official build, we've progressed far since then. Also, the lockscreen doesn't look like much cop, so it can be disregarded.

[Guest Scoopading]

It does show up in the logs. Atleast all logs I've looked at on my phone running N8. On standby, every 15-20 secs, there's a GC_Concurrent or GC_EXTERNAL_ALLOC running. Now I'm not saying that's what's resulting in the bad battery life. I'm not sure. It may be due to something else, or not.

Unfortunately it's not what's eating the battery life. If you do echo "2147483647" > /data/delay it does stop that behaviour. To quote myself..

Checking times with Logcat ( adb logcat -v time > sleeplog.txt ) showed almost no activity overnight. Exactly every 30 or 60 mins I'd get..

D/WifiService( 175): ACTION_BATTERY_CHANGED pluggedType: 0

Usually followed directly after by an I/EventLogService( 300)

Then, usually every 60 mins, D/dalvikvm( 300): GC_FOR_MALLOC

Unfortunately, even without much activity there, it makes absolutely no measurable difference to battery life whilst the phone sleeps. It'll still drop 2% per hour. Since the battery life is much the same, whether it's writing to the log constantly or writing to it every 30 minutes, this would seem to confirm that some component(s) of the phone are not entering sleep mode correctly.

[Guest Stuart_f]

Don't suppose anyone has an RF meter and can check to see that airplane mode actually turns all the radios off properly?

[Guest Treacles]

Would the two different Blades (OLED and LCD) be a cause for why some people are experiencing problems and others not?

[Guest Simon O]

Sorry for asking since I really can't be bothered flashing nightly 12 but does it have the new profile support added? I've been testing it since it was first posted to gerrit and it's a bloody awesome feature!

http://review.cyanogenmod.com/#change,3016 if nobody knows what I'm on about!

[Guest Scoopading]

Would the two different Blades (OLED and LCD) be a cause for why some people are experiencing problems and others not?

Possible, but fairly unlikely, since I'm not sure any hardware (other than the screen) is different between them. Much more likely is that people use their phones in different ways, and so some notice certain problems more than others. Also, some of the problems, such as the touch screen freeze or the proximity problems appear random. This means some people may use something a dozen times and not experience the issue, whilst another will notice it the first time.

[Guest css771]

Sorry for asking since I really can't be bothered flashing nightly 12 but does it have the new profile support added? I've been testing it since it was first posted to gerrit and it's a bloody awesome feature!

http://review.cyanogenmod.com/#change,3016 if nobody knows what I'm on about!

Nope it's not there yet. Don't see it anywhere in Settings or in CMSettings.

It was merged on the 4th and nightly 12's build date says 2nd. So maybe the next nightly?

Edited March 4, 2011 by css771

[Guest Treacles]

Possible, but fairly unlikely, since I'm not sure any hardware (other than the screen) is different between them. Much more likely is that people use their phones in different ways, and so some notice certain problems more than others. Also, some of the problems, such as the touch screen freeze or the proximity problems appear random. This means some people may use something a dozen times and not experience the issue, whilst another will notice it the first time.

Ah okay, i was just reading through the thread and it occured to me that noone was stating the model of phone they had (As we did when the LCD first came out, on all ROM issues) But, seeings as the hardware isnt that much different, i guess it probably makes no difference as you said.

[Guest skymera]

Volume controls work for me changing song, Proximity fix also works, I've had for successive long calls, screen came back every time.

Odd. wiped and reflashed Nightly 12, volume can increase / decrase with screen off but the song does not change on long-press. hmm

Edited March 4, 2011 by skymera

[Guest Rotmann]

yes u can just reinstal the rom again ontop. and it will be as it was.

hahaha just saw your edit.... i can proof it works fine flashing on-top.

Thanks for confirming this :(

Some important changes will be merged into N13, responding to some people having problems/questions with the volume music control or to the notification profile support:

Merge "Fix: Readded Volume-Music-Control to changed Android 2.3.3 logic" into gingerbread

Merge "Added notification profile support." into gingerbread

Edited March 4, 2011 by Rotmann

[Guest skymera]

Thanks for confirming this :(

Some important changes will be merged into N13, responding to some people having problems/questions with the volume music control or to the notification profile support:

Awesome :(

Also, good battery life on Nightly 12 today. Heavy WiFi use, heavy 3G use, heavy market usage, 30mins of Need for Speed, 2 hours of music and been unplugged for 13 hours, still have 30%

Need for Speed drained 20% itself, so without that should have 50% ish.

[Guest ufoman]

Anyone having problems with Radiant HD? Towards the later stages in 1st episode, game gets increasingly choppy, touchscreen stops responding, and if you get to the boss stage either the boss or your ship doesn't appear and the game is super slow...

[Guest _BG_]

Has anyone tried to make a call through a wired headset? Is so, what's the result?

The last time I tested a nightly, when making a call through a wired headset I couldn't hear anything, because the sound was redirected to the phone and not to the headset, but if I was hearing music everything was ok...

[Guest giannakis1984]

did anyone noticed very low in call sound??? volume is set to max but i can barely hear the other person calling..also volume buttons don't seem to work....the "orange" meter shows up but i can't hear any difference in my call...

[Guest doubleluckstur]

Oh.. No n13... n8 it is then

[Guest Jekle]

Something seems really weird, No Nightly on the Team Douche mirror is on 13? Is the server down? (wait the Buildbot says its purposely hiding :()

[Guest Simon O]

Something seems really weird, No Nightly on the Team Douche mirror is on 13? Is the server down? (wait the Buildbot says its purposely hiding :()

Latest is 12. 13 may be build later.

[Guest uskixboy]

I am still having problems on 11 with prox-fix, it doesn't work at all for me. Are there any improvements in n12 for this or should I go back to an earlier nightly such as 8 as it worked much better then? Any thoughts?

[Guest eucurto]

Don't suppose anyone has an RF meter and can check to see that airplane mode actually turns all the radios off properly?

You can try to take off your SIM card from the phone and let it over night to see how much battery it will take...

[Guest Maringer]

I've only encountered the proximity problem once so far (I'm now on N11), but I think that this may be because a) I've not been making many calls recently and b ) I'm fast on the draw and am doing my best to end calls before the other person!

My phone is set to do an automatic Titanium Backup (free version) during the night on a Thursday and this morning the screen was switched on once again. This was a problem I noticed last week (using Nightly 6 then, I believe). For some reason, after Titanium has run the backup, the screen switches on (I presume this occurs when a notification arises), but then does not automatically turn off as you would expect. In fact, it also seems to disable the automatic dimming as, though I can turn the screen off using the power button, if I leave it on, it remains on. A reboot is required before the usual automatic screen switch-off occurs. This is not too much of a problem at present but I wonder whether this is CM or Titanium-specific?

One thing which is noticeable is that the battery life when the phone is active seems normal and, in fact, when playing Angry Birds the battery seems to drain less quickly on CM7 than on my previous Eclair/Froyo ROM installations. As others note, this would indicate that the unusual battery drain when the phone is in theory sleeping is because something is not switching off correctly. Am I right in thinking that CM automatically downclocks the CPU when the phone is sleeping? If so, perhaps this is not functioning correctly and the CPU clock remains at 600MHz? Just a wild guess, obviously.

If the erratic proximity problem and the battery drain when sleeping can be resolved I would be very comfortable using this ROM full-time. I'm not using my phone for much at present but have a busy weekend soon so may need to downgrade to a Froyo ROM for more reliability and better battery life. I hope the Devs keep up the good work!

Edited March 4, 2011 by Maringer

[Guest swordtail]

Has anyone tried to make a call through a wired headset? Is so, what's the result?

The last time I tested a nightly, when making a call through a wired headset I couldn't hear anything, because the sound was redirected to the phone and not to the headset, but if I was hearing music everything was ok...

Yes I have the same problem no sound through wired headset and this morning it took ages to actually dial the number,not good really as it's what I need to work.I'll wait for N13 and if no good it's back to good old 2.2 until CM7 is sorted.

[Guest Nuuna]

Is gapps included?

[Guest Zythus]

Well, I have N12. Left my phone on 98%, and woke up with 89%.

Putted it on 6:40 on charging, on 7:00 there was 94%. I went to bathroom, 2-3 mins later there was 99%..lulz