698 replies to this topic

[Iceman1906]

CM6 had an option under Settings > Wireless & Networks > Proxy Settings. Does anyone know if CM7 will bring this feature back?

[s4t1sfy]

just curious... nightly B41 = RC1?

[Iananan]

no, it may have come out on the same day, but from what I understand, nightlies are automatically compiled at the end of a day, whereas the RC will have been tailored somewhat more carefully. or something. I could be talking out of my bum here.

anyone know if the battery percentages are back in the nightlies yet? I went from 33, to the RC1

[s4t1sfy]

Iananan, on 20 February 2011 - 01:55 PM, said:

no, it may have come out on the same day, but from what I understand, nightlies are automatically compiled at the end of a day, whereas the RC will have been tailored somewhat more carefully. or something. I could be talking out of my bum here.

anyone know if the battery percentages are back in the nightlies yet? I went from 33, to the RC1

both of the batt. % and network signal strength on notification bar are not yet available on nightly build 2. I want them back.

[Iananan]

hmm, I can't download nightly build 2 or 3, the google apps won't download

[rzaratin]

Any news about CM7 with Android 2.3.3?

Any nightly available?

[SomethingMore]

rzaratin, on 24 February 2011 - 02:22 PM, said:

Any news about CM7 with Android 2.3.3?

Any nightly available?

Personally, the only thing I want from 2.3.3 is the fix for my carrier (Wind Mobile in Canada). With all current versions of 2.3, it shows up as 302490 in the Network Operators list.  2.3.3 fixes that.

[Kenvan610]

rzaratin, on 24 February 2011 - 02:22 PM, said:

Any news about CM7 with Android 2.3.3?

Any nightly available?

Definitely like to see this. Its what I'm waiting for to update from RC1.

[Robbie Crash]

SomethingMore, on 25 February 2011 - 04:15 PM, said:

Personally, the only thing I want from 2.3.3 is the fix for my carrier (Wind Mobile in Canada). With all current versions of 2.3, it shows up as 302490 in the Network Operators list.  2.3.3 fixes that.

Do you know if it fixes Mobilicity, which usually shows up as 302320, as well?

[Robbie Crash]

Please ignore, accidental double post.

Edited by Robbie Crash, 27 February 2011 - 10:38 AM.

[s4t1sfy]

The browser is slower than the one in Nexus One... is it software or the CPU?

[SomethingMore]

Robbie Crash, on 27 February 2011 - 09:54 AM, said:

Do you know if it fixes Mobilicity, which usually shows up as 302320, as well?

No idea, but I would assume so.

[under9round]

I have never been able to access the "CPU settings" under CyanogenMod's performance settings. I consistently get force closures. Am I doing something wrong?

[Martyn]

Using CyanogenMod-7-02262011-NIGHTLY-NS

Having a bit of an issue revolving around the notification power widget toggle buttons - specifically the Toggle 2G/3G button.  Over the last few days it's been playing up - I'm never quite sure if it's on or off and it's currently not responding to input.  In the settings the option is also greyed out.  

Also I'm getting issues when I reboot - the phone doesn't ask me for a PIN for my sim card and when I get past the lock screen it tells me that com.android.phone has stopped unexpectedly with the following error in my logcat viewer:

AndroidRuntime   E  FATAL EXCEPTION: main
AndroidRuntime   E  java.lang.NullPointerException
AndroidRuntime   E     at com.android.internal.telephony.cdma.CDMAPhone.getState(CDMAPhone.java:268)
AndroidRuntime   E     at com.android.internal.telephony.CallManager.getState(CallManager.java:241)
AndroidRuntime   E     at com.android.phone.PhoneUtils$ConnectionHandler.handleMessage(PhoneUtils.java:187)
AndroidRuntime   E     at android.os.Handler.dispatchMessage(Handler.java:99)
AndroidRuntime   E     at android.os.Looper.loop(Looper.java:123)
AndroidRuntime   E     at android.app.ActivityThread.main(ActivityThread.java:3812)
AndroidRuntime   E     at java.lang.reflect.Method.invokeNative(Native Method)
AndroidRuntime   E     at java.lang.reflect.Method.invoke(Method.java:507)
AndroidRuntime   E     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
AndroidRuntime   E     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
AndroidRuntime   E     at dalvik.system.NativeStart.main(Native Method)

on clicking OK this error keeps coming up and the phone is unusable.  the only way to get past this is to restore a previous recovery image.

anyone else seeing these issues?

[Verba]

Update to the latest nightly and check

[no_one_can]

Is the latest nightly 2.3.3?

[s4t1sfy]

Yes build 11 is 2.3.3

[no_one_can]

already flash the build#11
2 questions here


1.) just notice that there is no FM radio in CM7? I've ever use N1 and got that (not sure cm6 or 7)
2.) can I changed to colur profile to the original one, I've got a yellow tint problem with this 2.3.3

thanks

[Verba]

no FM Radio with the NS
Yellow tint is not a problem, it's a choice by Google

[bakron1]

Flashed build #11 this morning and the CPU Settings function is fixed and so far this is nice and stable for my everyday use. Great job