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

[Guest skyhacker]

Nope. The fixes haven't been merged yet.

Yup just tested Angry Birds and Fruit Ninja, don't work from SD, thank for the info flibblesan

[Guest VJJ]

for those of you trying to work out how this rom is doing with respect to battery usage; i would recommend a free app from the market called

"Battery Monitor Widget (Pro)"

it gives what look to me like some pretty accurate graphs of usage. they also record stats which can be uploaded to a pc to do real crunching on the data.

hope this is of some help

Or just show battery on status bar using CM's built in settings (simpler)

[Guest mehelan]

Nope. The fixes haven't been merged yet.

What is the fix?

[Guest tentric]

Has the proximity sensor problem been fixed in N17?

[Guest wishmasterf]

How is the speed of CM7 on blade/SF?

[Guest Simon O]

What is the fix?

http://review.cyanogenmod.com/#change,3812

[Guest The Soup Thief]

made one call and the screen woke immediately! I've had lots of problems w that previously so this is promising but just 1 call so far - much more testing needed

(EDIT - the screen freeze resolved with the power button as Alex says below -just rebooted as I often find ROMs behave a little differently on 2nd boot than after the first - installation - boot)

rebooted, made a couple of calls and each time the screen froze following, regardless who hung up first

It reawoke without a reboot each time after a minute or so's wait

This seems consistent with my phone's behaviour on the previous nightly

Edited March 12, 2011 by The Soup Thief

[Guest Saransh Agarwal]

Any news for FM RADIO on the rom or coming roms ???

[Guest Victor von Zeppelin]

@Victor - we just try to do our best like the rest of us here. Could you mark the proximity issue as solved? Ticking "Always use proximity" and restarting works

Is that it? Nothing to do with the new kernel at all. Because it's not officially fixed until something comes out of CM saying it's fixed :D

[Guest jayhix]

Is that it? Nothing to do with the new kernel at all. Because it's not officially fixed until something comes out of CM saying it's fixed :D

I just tried the always use proximity option. doesnt make a difference. still doesnt work. N17

edit: my bad, didnt restart, just restarted and appears to be fixed... easy enough :|

Edited March 12, 2011 by jayhix

[Guest targetbsp]

Despite working a couple of days ago - mine let me down whilst out and about this morning. Using experIt's kinda intermittent - which isn't fixed. :( I think other people have commented that it fails after the phone has had a prolonged uptime. That seemed to be the case with me too. Rebooting every hour isn't very convenient. :(

This was using Bl1nks kernel on RC2. Patiently awaiting t0mm13b's second experimental kernel. :D

Edited March 12, 2011 by targetbsp

[Guest DonJamal]

so...does the proximity workin or not on n17?

[Guest simonckenyon]

Or just show battery on status bar using CM's built in settings (simpler)

maybe simpler - but it doesn't show anything like the level of details that this app does

[Guest gwebb]

so...does the proximity workin or not on n17?

It does seem to, I've tried it a few times, but I've only just installed CM7, so I need to do more testing.

[Guest ThrashMan]

I have no idea what this means.....is it "bad"? (over about 2 hours)

taken from /proc/wakelocks

name						  count	 expire_count	wake_count	active_since	total_time		  sleep_time	  max_time		last_change

"rpcrotuer_smd_xprt"		  13001	 0			   177		   0			   2027051822		  317561813	   74976675		8661286556320

[Guest The Soup Thief]

so...does the proximity workin or not on n17?

OK - in call settings I had Always use proximity Ticked - and still it was temperamental - screen would often stay off following calls

Also had In-call touch UI ticked

So I did the following and it has worked - screen now comes back on reliably following calls

Homescreen>Settings>Call Settings Tick ONLY Always use proximity, nothing else is ticked

Reboot

It works fine

Rebooted again

It still works

Reboot again

Hope it will still work

etc

[Guest elinx]

I have no idea what this means.....is it "bad"? (over about 2 hours)

taken from /proc/wakelocks

name						  count	 expire_count	wake_count	active_since	total_time		  sleep_time	  max_time		last_change

"rpcrotuer_smd_xprt"		  13001	 0			   177		   0			   2027051822		  317561813	   74976675		8661286556320

In the old CM7 RC1 thread this was repaired by CS771 at postnr. #2313

http://android.modaco.com/content-page/332...ead/page/2300/#

Edited March 12, 2011 by elinx

[Guest metal.mickey]

Lost 13% in 3 hours.

proximity still not working without workarounds (called voice mail and had to flick the battery out) so it seems the problem is regardless of who hangs up first. I could stll hear the lovery woman from t-mobile whilst trying to end the call.

Back to JapJelly for the time being

[Guest tttonyyy]

Sorry to hear that - market's fine here. Sounds like it's not N17 specific though. Maybe hard reset full wipe etc?

I've tried to do this every week or so with the nightlies just to make sure I'm not carrying old errors forward, if you know what I mean

Just noticed - Modaco time = GMT again

Once again you are spot on sir - I haven't wiped since N5 or thereabouts. After a wipe all was working again.

Interestingly enough, a few nightlys ago I'd lost the power on/off animation (old TV style) and that's back after the wipe too - very happy with that :D

[Guest]

Once again you are spot on sir - I haven't wiped since N5 or thereabouts. After a wipe all was working again.

Interestingly enough, a few nightlys ago I'd lost the power on/off animation (old TV style) and that's back after the wipe too - very happy with that :D

this is caused by having window animations on fast in spare parts,to keep the on/off animations,have window animations as normal.

Edited March 12, 2011 by Guest

[Guest ThrashMan]

In the old CM7 RC1 thread this was repaired by CS771 at postnr. #2313

http://android.modaco.com/content-page/332...ead/page/2300/#

oic....pitty CM haven't implemented the correcton yet then :D

[Guest roulle]

Anoybody else having problem with camera's zoom?

If you try to zoom with the slider, it does not zoom very much, but then if you doubletap, it zooms much more. And when you take the picture, the zoom is not affecting at all?

[Guest Rotmann]

Nope. The fixes haven't been merged yet.

Oops, thought it has been already merged.

Is that it? Nothing to do with the new kernel at all. Because it's not officially fixed until something comes out of CM saying it's fixed :D

Yes, a lot of people confirmed that if you tick in Settings-Call settings "Always use proximity" and leave "In call touch UI" unticked, and RESTART, it works. I have tried it a lot of times now, it works very reliable

Lost 13% in 3 hours.

proximity still not working without workarounds (called voice mail and had to flick the battery out) so it seems the problem is regardless of who hangs up first. I could stll hear the lovery woman from t-mobile whilst trying to end the call.

Back to JapJelly for the time being

Did you tick "Always use proximity" in Call settings and restart? It will work.

Bad news regarding battery life, the kernel from Tom_G with the CPU scaling settings did not improve anything, back on testing, I am gonna wipe and remove the RIL tonight.

[Guest The Soup Thief]

@tttonyyy I'd forgotten all about the close screen - haven't seen it all week - must be time for a clean instal on the next nightly

@jikobutsu. I'm on normal transitions but no cool close screen

Gonna dig about in settings

[Guest The Soup Thief]

Easy - home screen> settings> cyanogenmod settings> display

tick screen off transitions. Leave screen on unticked