[ROM] CyanogenMod-7 for ZTE Blade/San Francisco :: V7.0.0-RC1 (02/16/2011)

[Guest bhf]

The Update is available for three hours and you are seriously asking how the battery life is going?

[Guest feckineejit]

-A bit laggy scrolling the main screens.

-touch screen unresponsive a lot of the time.

-gps icon does not disappear after switching off the gps.

-buggy working proximity sensor, have to remove battery to get the screen back on after a call.

-battery draining fast, 14% in 8 hrs in sleep mode.

Edited February 17, 2011 by feckineejit

[Guest rishie]

The Update is available for three hours and you are seriously asking how the battery life is going?

I was not sure when the update was available, my intension is to just put some observation on the battery life as well, along with other features.

[Guest ztebladeuser]

its probably me being dumb, but i cant set up my contacts, theres no option for gmail, only exchange?

also i cant delete the android help dude on the desktop

edit: oh i get it, need to install google apps.

Edited February 17, 2011 by ztebladeuser

[Guest The-One]

Im getting above 1000 points in quadrant with oc, "most" of the rom choppiness is gone (im also using adw ex, but oc does make a bit of difference)

Have to test neocore and such.

Edited February 17, 2011 by The-One

[Guest rayraven]

Can someone confirm if the proximity/light sensor issue is closed?

I'd switch to it a flash if it was.

P.S: Does this anything to do with the OLED/TFT change?

Edited February 17, 2011 by rayraven

[Guest The-One]

Some results overclocked.

Edited February 17, 2011 by The-One

[Guest kang.t7]

Some results overclocked..............

Awesome, Thanks...... NEOCORE ?

Hitting 8.2 MFLOPS stock - COULD only manage that with 662MHZ on JJ9

[Guest tek2k]

Can't get mobile internet working, selected the o2 APN from the list but still nothing...i think i might go back to jellyfish until the fully stable version is out

You need to select the first O2 apn then you need to actually untick the use mobile data button then tick it again. This gets data working.

Also for anyone asking about USB connection to the PC it seems USB debugging is turned on by default. You need to turn it off and it will come up asking about USB storage so you can turn it on.

Edited February 17, 2011 by tek2k

[Guest Frankish]

Some results overclocked.

Is overclock in as standard? It wasn't in previous test builds.

[Guest The-One]

Awesome, Thanks...... NEOCORE ?

Hitting 8.2 MFLOPS stock - COULD only manage that with 662MHZ on JJ9

Neocore doesnt run, crashes on opening. I did a test with An3DBench witch is similar, the results are in the first screen.

Im also using the same method KK used to overclock AHB in his JJ kernels.

Is overclock in as standard? It wasn't in previous test builds.

Not yet.. infact if you try to oc from the cyanogen settings it will just fc (but if you use a custom kernel you can OC the old fashion way with oc widget or set cpu)

Edited February 17, 2011 by The-One

[Guest ololizoz]

Hello, can this be used for us that have used TPT? Which makes the system partition 128MB, will it fit into that?

[Guest ak89]

For me proximity sensor didn't work even on short calls. Then I googled a little and found this(or actually another bug report, but I don't remember where it was anymore, but this is the same thing) http://code.google.com/p/cyanogenmod/issues/detail?id=1916 and thought it might be because of this. There is setting in Call settings called "Always use proximity", I switched it on and after that screen woke up nicely. Atleast after short calls, haven't tested on longer calls.

Overclocking doesn't work for me with setcpu, is it supposed to work? Do I have to do something first before I can oc?

[Guest ak89]

Hello, can this be used for us that have used TPT? Which makes the system partition 128MB, will it fit into that?

I'm using this with 128MB partition size. I even installed that Google applications addon and it fit in. Although I first deleted some apk:s from that rom zip, don't remember what I deleted. Try it, if you have nandroid backup, there should be no risks, except for losing time.

[Guest SebbesApa]

Found that restoring an old backup of wifi AP's from JJ broke my wifi completely. Had to wipe and install cm7 again to get it to work...

Edited February 17, 2011 by SebbesApa

[Guest ufoman]

Neocore doesnt run, crashes on opening. I did a test with An3DBench witch is similar, the results are in the first screen.

Im also using the same method KK used to overclock AHB in his JJ kernels.

Not yet.. infact if you try to oc from the cyanogen settings it will just fc (but if you use a custom kernel you can OC the old fashion way with oc widget or set cpu)

Hi, from where you got the custom kernel for CM7 that has overclocking enabled? I'd be grateful, for now only thing CM7 lacks for me is OC...

[Guest Quu]

Overclocking doest work YET, because kernel doesnt support it.

Atleast 5mp cameras (default camera app) takes only black and white pics, but this can be solved with other camera app eg. camera 360.

[Guest Tarot]

What I noticed:

Autofocus in camera don't work.

Battery voltage incorrectly displayed (it would be correct if it is multiplied by 1000).

It's necessary enable/disable settings-application-Allow application moving that "move to SDcard" in Manage Applications correctly displayed.

Black screen after end call. :D

[Guest mvheuver]

What I noticed:

Autofocus in camera don't work.

Battery voltage incorrectly displayed (it would be correct if it is multiplied by 1000).

It's necessary enable/disable settings-application-Allow application moving that "move to SDcard" in Manage Applications correctly displayed.

Black screen after end call. :D

I'm giving this one a miss :D

Looking forward to trying it out once it becomes a bit more stable. A bit odd to attach the label RC to it at this stage, isn't it? (RC I consider something that is potentially stable and which is a "candidate" to be "released")

Other than that, interesting times!

[Guest tanivula]

For me proximity sensor didn't work even on short calls. Then I googled a little and found this(or actually another bug report, but I don't remember where it was anymore, but this is the same thing) http://code.google.com/p/cyanogenmod/issues/detail?id=1916 and thought it might be because of this. There is setting in Call settings called "Always use proximity", I switched it on and after that screen woke up nicely. Atleast after short calls, haven't tested on longer calls.

Overclocking doesn't work for me with setcpu, is it supposed to work? Do I have to do something first before I can oc?

Awesome, can you or someone please do a test on a longer call and post back results! This is the _only_ thing stopping me from trying out CM7

[Guest harry_m]

If somebody needs the hostspot-feature (or wifi tether) check my earlier post here:

http://android.modaco.com/content-page/331...0/#entry1602687

Edited February 17, 2011 by harry_m

[Guest bugeyes]

Awesome, can you or someone please do a test on a longer call and post back results! This is the _only_ thing stopping me from trying out CM7

tried this out and the proximity sensor still locks the screen out after 5 seconds for me! :D

Edited February 17, 2011 by bugeyes

[Guest r0by]

For me proximity sensor didn't work even on short calls. Then I googled a little and found this(or actually another bug report, but I don't remember where it was anymore, but this is the same thing) http://code.google.com/p/cyanogenmod/issues/detail?id=1916 and thought it might be because of this. There is setting in Call settings called "Always use proximity", I switched it on and after that screen woke up nicely. Atleast after short calls, haven't tested on longer calls.

Overclocking doesn't work for me with setcpu, is it supposed to work? Do I have to do something first before I can oc?

Did you try proximity calibration?

I am of the opinioin like tanivula. Proximity sensor is the _only_ thing stopping me from trying out CM7.

Edited February 17, 2011 by r0by

[Guest markastor]

I am of the opinioin like tanivula. Proximity sensor is the _only_ thing stopping me from trying out CM7.

Me too. :D

Edited February 17, 2011 by markastor

[Guest rayraven]

^+1, Once i can make calls without issues, i'd move to this in a heart-beat