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

[Guest Rotmann]

@everyone having problems with the screen staying black after a call:

Just move the phone again to your ear and back, then the screen will come back

This worked many times for me in nightly 8 and 11

Seems like the proximity sensor is working, but its sensibility has to be calibrated

tried the camera video function and it doesnt work properly, green with funny paterns...probably been mentioned here before...and as mentioned regularly, the prox. sensor screen stays off after a call...

And, if anyone finds a fix for the screen freezes, I will be right back @ CM. For now, I had to get back to JJ, because it was totally unusable for me..

Did you apply the build.prop mod from the second post?

[Guest Scoopading]

As expected, absolutely no change with battery behaviour on nightly 11. It still loses approx 2% per hour whilst the phone sleeps. Also, "echo 250 > /data/delay" definitely doesn't do anything for battery life whilst the phone sleeps. It doesn't even slow the usage down (as claimed in the second post on the first page).

I'll now check the larger value (echo "2147483647" > /data/delay) overnight and see if that does anything more.

The only differences I've noticed on nightly 11 is that the touchscreen has stopped responding a bit more than it did on nightly 8. But, since the freeze is fairly random, it's probably down to that rather than any real change.

Personally I will not be trying any more new nightly builds if it's just updates on the Cyanogen side. I will wait until if/when there's some real movement on the Blade side of things, in terms of fixes for battery / screen freezing / randomly dead touch zone at the bottom of the screen etc.

[Guest]

on N11 my battery dont seem to be charging right,so i looked in about phone,status,and it says im charging via usb.Should'nt it say by mains or something ?

edit: i am using mains charger

Edited March 2, 2011 by Guest

[Guest ThrashMan]

Personally I will not be trying any more new nightly builds if it's just updates on the Cyanogen side. I will wait until if/when there's some real movement on the Blade side of things, in terms of fixes for battery / screen freezing / randomly dead touch zone at the bottom of the screen etc.

and you are telling us because???

if the ROM doesn't "do it" for you then go back to Froyo and stop moaning. Far too many people expect too much too soon.

This ROM is refered to as "EXPERIMENTAL" for a good reason......if people aren't interested in testing and proving feed back of a constructive nature then leave the cutting edge stuff alone!!

[Guest ThrashMan]

on N11 my battery dont seem to be charging right,so i looked in about phone,status,and it says im charging via usb.Should'nt it say by mains or something ?

Well that kind of depends on what's plugged into the USB port?

[Guest Rotmann]

I have wiped everything today and have stock N11, no gapps or modifications. For the first 8 hours in airplane mode, it went from 100% to 92%, it's better than previous nightlies or RC1 where I would have lost around 13-15% but still bad compared to froyos. I have applied

echo "2147483647" > /data/delay

through terminal emulator now, let's see if it gets any better. Will report after 8 hours again.

Edited March 2, 2011 by Rotmann

[Guest Scoopading]

same question here. can I use it all day without the battery dissapearing too quickly or other odd bugs being prevalent?

It should probably get you through a single day, but the battery loses at least 2% every hour whilst the phone sleeps. The most severe bugs are related to hardware issues like the touch screen freezing so you have to use the power button to switch it off/on and reset it, as well as randomly not being responsive at the bottom of the screen, which you will notice most if you do things like pull down the notification screen from the status bar then try to pull it back up again (it often fails to register the touch to pull it back up). The GPS lock time is also slower for me on this rom. It consistently gets a fix on 1 or 2 satellites and then sits there for 10 minutes.. It does not behave like that on the stock rom. Also, it seems the WIFI still requires the Blade wifi fix from the market to properly reconnect after the screen goes off.

However, on the software side itself, things are stable (stable enough for daily usage). You'll get some programs which will FC straight away, but I've actually notice less "random" FC type behaviour on this firmware than some of the 2.2 based roms. The payoff is this will also perform significantly faster than any other roms. Things like browsing are much quicker on demanding pages, as is doing things like running Angry Birds, if you want that :huh:

[Guest]

Well that kind of depends on what's plugged into the USB port?

sorry i thought it was clear i had mains charger in

[Guest Scoopading]

and you are telling us because???

Because many people see nightly updates and expect it to fix Blade specific issues. They don't understand that there's a difference with the way things are done with Cyanogen and the other (Blade specific) 2.1/2.2 roms they're used to now. If more people understand that it's often only the Cyanogen side of things being updated, and those fixes are unlikely to impact the more major problems they're experiencing with the current version of CM7 running on the Blade, many more would probably skip the nightly updates.

The CM7 side of things seems pretty ready for daily usage, and the only fix I'm waiting for there is one so that Autostarts can work properly with other themes activated. Just because the difference may be obvious to you doesn't mean that everyone knows this. I mentioned it specifically because I got the impression, from some peoples comments, that they did not understand this important difference from other roms.

if the ROM doesn't "do it" for you then go back to Froyo and stop moaning. Far too many people expect too much too soon.

Where was the premature "expectation"? Pointing out that I'll only update when I see Blade specific fixes doesn't mean I expect everything to be perfect right now! It just means I'm going to start watching for changes which impact me, as a Blade user, directly - rather than more generic Cyanogen changes included in the nightly builds. In what way is that unreasonable?!

Also, I was on a tweaked stock rom. Current Froyo roms do not boost performance significantly enough for me to consider it worthwhile over a tweaked stock 2.1. CM7 is the first rom where I can notice large speed improvements in areas like the browser. There really isn't too much to moan about other than the Battery life and touch screen issues - everything else is fairly minor problems, to me at least :huh:

This ROM is refered to as "EXPERIMENTAL" for a good reason......if people aren't interested in testing and proving feed back of a constructive nature then leave the cutting edge stuff alone!!

Correct. And I am interested. I'll just wait until there's a nightly change with more Blade specific stuff for me to comment on :)

[Guest IronDoc]

The GPS lock time is also slower for me on this rom. It consistently gets a fix on 1 or 2 satellites and then sits there for 10 minutes.. It does not behave like that on the stock rom. Also, it seems the WIFI still requires the Blade wifi fix from the market to properly reconnect after the screen goes off.

What nightly? GPS is fixed for me now.

[Guest Scoopading]

What nightly? GPS is fixed for me now.

Nightly 8 and 11. I think nightly 6 was also the same. It will eventually (given about 10 minutes) get a fix. But there definitely seems to be some issue, because it will lock on to the first one or two satellites quickly, then struggles for several minutes, before finally getting a lock on more..

[Guest chall32]

Talking of battery, has anyone tried this: http://spences10.blogspot.com/2011/02/thin...-sussed-it.html ?

It's a CM7 tweak for the DesireZ.... Tempted to try it tonight on my (newly updated) Nightly11 install.... Worth a spin overnight tonight me thinks :huh:

Also can confirm that the Gingerbread Easter Egg exists on the blade CM7 builds.

What easter egg? http://www.peteralfonso.com/2011/01/ginger...dand-added.html - Bit early I know, but Happy Easter All!! :)

- Chris

[Guest t0mm13b]

Talking of battery, has anyone tried this: http://spences10.blogspot.com/2011/02/thin...-sussed-it.html ?

It's a CM7 tweak for the DesireZ.... Tempted to try it tonight on my (newly updated) Nightly11 install.... Worth a spin overnight tonight me thinks :huh:

Also can confirm that the Gingerbread Easter Egg exists on the blade CM7 builds.

What easter egg? http://www.peteralfonso.com/2011/01/ginger...dand-added.html - Bit early I know, but Happy Easter All!! :)

- Chris

Re: Easter Egg +1 confirmed... ha!!!!

[Guest targetbsp]

I've had tasker auto enabling and disabling gps since I've had the phone and it doesn't help CM7's battery. I've always left the wireless one on though so I can't comment on how it will affect the battery. However, as the battery drain is high in airplane when wireless locating wouldn't be able to do anything I'm not optimistic! Would be happy to be proved wrong though. The lack of battery standby is currently the main reason I don't use this

[Guest rbbrslmn]

For all those asking if this is 'ready' read the first post, the links provided and the thread if you have to. It's not exactly difficult and it'll give a more full answer than some meaningless yes or no from one of us.

/rant

it doesnt answer the question, whether you think it does or not. someone giving an subjective answer based on their own experience is what I was asking, and is all i was after.

[Guest jurrasstoil]

it doesnt answer the question, whether you think it does or not. someone giving an subjective answer based on their own experience is what I was asking, and is all i was after.

are you willing to tolerate the things listed under "still broken/missing": use it.

if not: don't use it.

The benefits over Froyo are small but present, it's just a matter of what you are willing to sacrifice for them.

[Guest mELIANTE]

I'm just waiting that apps2fat and battery drain are fixed. I miss Gingerbread and those are the absolute showstoppers for me :huh:

[Guest IronDoc]

Nightly 8 and 11. I think nightly 6 was also the same. It will eventually (given about 10 minutes) get a fix. But there definitely seems to be some issue, because it will lock on to the first one or two satellites quickly, then struggles for several minutes, before finally getting a lock on more..

Yeah I had it before (4 and 8 I think) but it's as fast as it should be now. Haven't wiped since I installed CM.

[Guest Poodha]

A question about the nomenclature here? How many nightlies will there be until they release another "stable" version? And what will they call that? RC2? Are RC the official Cyanogen versions? Or is RC(release candidate) not even beta?

[Guest IronDoc]

Release Candidate is when most major bugs are fixed and it should be relatively usable as an everyday ROM. We got RC1 because all the CM7s were getting it. I think RC2 will be when the Blade CM is up to standard, though I'm not sure about that.

[Guest r0by]

What nightly? GPS is fixed for me now.

Working me too, like a charm.

I am using RunKepper severeal time a day, and gps is very quick and stable. N8 and N11.

[Guest marra2]

I have an annoying problem since nightly 11, the top quarter of my screen keeps flickering ! Whether its my screen on its way out or the build ? Will go back to nightly 8 and see later .

[Guest Lasse-hatten]

Somhow I lost my lock screen. Probably by deleting to many apps before flashing the ROM. Any idea on what app it might be?

[Guest]

N12 has arrived

the adventure goes on

[Guest Scoopading]

I have an annoying problem since nightly 11, the top quarter of my screen keeps flickering ! Whether its my screen on its way out or the build ? Will go back to nightly 8 and see later .

I noticed some graphics corruption in the bottom right quarter of the launcher drawer too. A reboot fixed it. Still, I didn't ever notice that issue before nightly 11. Too early to say if it was a one off or not..