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

[Guest The Soup Thief]

I've found the same in that randomly covering the screen seems to wake the phone (I've tried the build prop fix) although I can't replicate this every time. Can you tell me exactly where the proximity sensor is on the Blade?

Above the top left of the screen - little round purpley bit about 3 or 4mm accross - you can just about make it out in strong light (just noticed that I can't see it on mine due to poor light here and a screen protector which is just glossy enough to stop me making it out). Somewhere West-Northwest of the S in san francisco if memory serves

(this is the point where someone much smarter tells me that I'm a clown cos what I've been thinking was the proximity sensor is actually the Klempig gate or somesuch)

[Guest undisclosedpower]

Hi all,

Apologies if this has already been discussed but if I've got rc1 on my phone do I need to wipe before moving to a nightly? If so, do I have to wipe every time a new nightly comes out?

Cheers.

Udp.

[Guest nunoar]

Can anyone remember last nightly that had the sensors working?

[Guest Zythus]

My sensors are workin :(

[Guest doubleluckstur]

Can anyone remember last nightly that had the sensors working?

n8

[Guest The Soup Thief]

Can anyone remember last nightly that had the sensors working?

doubleluckstur says n8 was the last problem free one, but I've only been aware of the problem since updating from n6 to 8 then 11, having definitely had it when on RC1. I didn't have the problem for a few nighlies thereafter

However, other people are reporting the problem or reporting it fixed on different nightlies - plainly there's magick involved

TomG will rid our phones of this evil

[Guest PeaNut_HU]

I noticed that in every nighlty the build.prop file has "conflicting" and duplicate lines. Not sure how much it causes problems or not but i thought i should mention it.

(Talking about latest nightly number 12)

These lines are 3 times in the build prop, third time in another "format"

ro.com.android.dateformat=dd-MM-yyyy

ro.com.android.dateformat=dd-MM-yyyy

ro.com.android.dateformat=MM-dd-yyyy

also duplicated:

ro.com.android.dataroaming=false

And the conflicting lines:

ro.ril.hsxpa=1

ro.ril.gprsclass=10

...and later...

ro.ril.hsxpa=2

ro.ril.gprsclass=10

No logic in what settings come in which order in build.prop, so if it was in some logical order the duplicates and conflicting lines could be easily "filtered out".

Edited March 3, 2011 by PeaNut_HU

[Guest alex1alex2alex3alex4]

Apologies if this has already been discussed but if I've got rc1 on my phone do I need to wipe before moving to a nightly? If so, do I have to wipe every time a new nightly comes out?

I never do a "full wipe" (i.e. no data wipe / "factory reset"), but I do wipe the cache + dalvik cache + battery stats.

No issues with that so far on any nightly.

[Guest rapidone]

I noticed that in every nighlty the build.prop file has "conflicting" and duplicate lines. Not sure how much it causes problems or not but i thought i should mention it.

(Talking about latest nightly number 12)

These lines are 3 times in the build prop, third time in another "format"

ro.com.android.dateformat=dd-MM-yyyy

ro.com.android.dateformat=dd-MM-yyyy

ro.com.android.dateformat=MM-dd-yyyy

also duplicated:

ro.com.android.dataroaming=false

And the conflicting lines:

ro.ril.hsxpa=1

ro.ril.gprsclass=10

...and later...

ro.ril.hsxpa=2

ro.ril.gprsclass=10

No logic in what settings come in which order in build.prop, so if it was in some logical order the duplicates and conflicting lines could be easily "filtered out".

Interesting. I just read that in Europe ro.ril.gprsclass should be set to 12. Can anybody confirm?

This is some info I found at forum.xda-developers.com

ro.ril.hsxpa

* ro.ril.hsxpa=0 – UMTS r99

* ro.ril.hsxpa=1 – HSDPA

* ro.ril.hsxpa=2 – HSDPA/HSUPA

ro.ril.gprsclass

* Class 2 : 3 slots : 8 – 12 kbps upload / 16 – 24 kbps download

* Class 4 : 4 slots : 8 – 12 kbps upload / 24 – 36 kbps download

* Class 6 : 4 slots : 24 – 36 kbps upload / 24 – 36 kbps download

* Class 8 : 5 slots : 8 – 12 kbps upload / 32 – 40 kbps download

* Class 10 : 5 slots : 16 – 24 kbps upload / 32 – 48 kbps download

* Class 12 : 5 slots : 32 – 48 kbps upload / 32 – 48 kbps download

Edited March 3, 2011 by rapidone

[Guest targetbsp]

Hi all,

Apologies if this has already been discussed but if I've got rc1 on my phone do I need to wipe before moving to a nightly? If so, do I have to wipe every time a new nightly comes out?

Cheers.

Udp.

I've gone from RC1 up to and including N11 without wipe and it's been fine. Have a Froyo on atm so not tried 12 but I can't imagine it suddenly needs a wipe from 11 to 12 based on the lack of complaints about it here today. :(

[Guest fredewis]

ok so you guys agree barnacle works so it most be the settings i got on pc or phone can you guys share your settings....

[Guest Emaster]

wat the night 12 adds ??

[Guest alex1alex2alex3alex4]

wat the night 12 adds ??

About 1KB to the file size, uncompressed as well as to the zip :(

[Guest alex1alex2alex3alex4]

I've gone from RC1 up to and including N11 without wipe and it's been fine. Have a Froyo on atm so not tried 12 but I can't imagine it suddenly needs a wipe from 11 to 12 based on the lack of complaints about it here today. :(

Well, I guess many have given up on applying every single nightly ;-)

Noticed one thing, my power widget disapperead from the home screen with N12.

[Guest Rotmann]

Well, I guess many have given up on applying every single nightly ;-)

Noticed one thing, my power widget disapperead from the home screen with N12.

I will only update when significant things get changed. For one language correction and a few little things, no way.

[Guest hegde19]

Can anyone confirm this - have experienced the following

1. Download the Nightly 12 ROM via ROM Manager
   
2. Then prompted to wipe cache and reboot
   
3. Note: At this stage handset is plugged in for charging
   
4. Recovery clockwork fires up and starts doing the magic on the installation
   
5. Android Robot stays on screen and appears "locked up"
   
6. Unplug the cable, the handset vibrates and reboots then boots up normally :(
   

Then the CM7 ROM 12 appears....

Confirmed.. I too faced the same issue.. had to pull the battery and restart..

[Guest Drakedian]

Hey guys!

Are there any workaround for the wired headset calls problem ?

I want this fw so badly, but since im travelling a lot by bike,

and its impossible to make/get calls with wired headsets, i cant. =(

[Guest killthatwha]

So is this ROM stable enough for everyday use? It looks brilliant, but the screen freezes are a bit of a deal-breaker for me at the moment.

[Guest Zythus]

So is this ROM stable enough for everyday use? It looks brilliant, but the screen freezes are a bit of a deal-breaker for me at the moment.

This ROM is stable. Only problem I see, its screen freezes - which I had only one, today, playing a game. Locked-unlocked phone and it works :(

Edited March 3, 2011 by Zythus

[Guest skymera]

Problems I noticed:

- Vol controls no longer change music in N11 onwards.

- Screen turns off during NFS Shift for some reason?

- Perhaps proximity? Haven't had a phone call since I changed the prop file.

[Guest Rotmann]

So it seems that N8 was the best for proximity and volume controls?

[Guest kunis6]

I noticed a drop in performance from the NB 11? Is just me or is this fall with you too?

Sorry for my English:)

[Guest The Soup Thief]

I noticed a drop in performance from the NB 11? Is just me or is this fall with you too?

Sorry for my English:)

Perhaps - scrolling on N12 appears very slightly less smooth than on N11

[Guest ropin]

*BATTERY LIFE IS FIXED!

Using ADB shell, or the internal terminal emulator type:

This pretty much turns off AKMD2

adb shell (if using adb, otherwise skip this part)


echo "2147483647" > /data/delay

While this slows it down.

adb shell

echo 250 > /data/delay

when i try any of these using the internal terminal i keep getting permission denied, anyone know how to fix this

[Guest kunis6]

Perhaps - scrolling on N12 appears very slightly less smooth than on N11

I do not mind scrolling. Just like in the Reckless RACING lag what we can see there has been no update to the NB 11