[ROM][GEN2]CyanogenMod 7 (Android 2.3.7)

[Guest tomasvilda]

I have read the last page and I can't see where it says why we have lost the sensors. OK there is something on the previous page but I don't understand how the sensors where lost.

Please point me to the name of the person on this page that has stated why the sensors have gone

current page - http://android.modaco.com/content-page/335...nly/page/3060/#

[Guest cjp666]

Hello,

at the moment I use this Image:

http://android.modaco.com/content/zte-blad...r-easy-install/

Can I flash now without problems the image from this Thread?

--> sry for my English...but I'm non-native English speaker! :unsure:

There are still a number of issues so you would need to check if any of the issues will affect you. If not then go ahead and flash, CM7 is very good. There appears to be a problem with the sensors in the currently nightly

[Guest cjp666]

current page - http://android.modaco.com/content-page/335...nly/page/3060/#

I still don't understand what went wrong. Never mind, I'm sure it will get fixed at some point. Sorry I caused offence by reading something, not understanding it and then posting a question.

[Guest tomasvilda]

I still don't understand what went wrong. Never mind, I'm sure it will get fixed at some point. Sorry I caused offence by reading something, not understanding it and then posting a question.

Old sensor library was removed before new one was merged, so there is no sensor library at all.

Edited May 10, 2011 by tomasvilda

[Guest Maringer]

Can you install this APK?

I've tried both versions (signed and unsigned)...both fail on install.

Whats the magic?

Since CM7 went to 2.3.4 I needed to copy the apk into /system/app. I used ES File Manager to do this (there is an option which allows you to make root writeable).

However, just checking the Toggle2G thread, I see that TheMasterBaron has updated the zip so it can now be installed using Clockworkmod 3+.

[Guest Psyloid]

I'm sorry that i don't wanna read 152 pages, so, if i flash my phone to N67, i will have :

-GPS working

-Sensors working like they should (autobrightness, proximity)

-Accelerometer working without lag

-No random reboots

-No shutting down while charging

-No touchscreen input lag

-WIFI works in sleep mode

optional:

- can I make stagefright working correctly

- Is there a way to have an ext3 partition work with this build

Basicly; would it be as good as SS5, but then gingerbread ... :unsure:

THANKS THANKS THANKS

Edited May 10, 2011 by Psyloid

[Guest _amano]

The accelerometer is not fixed with N67.

All the sensors have been removed in N68 (that makes it a very broken build) and an updated sensor lib will return in N69 (hopefully!!). The patch for it is awaiting its final review now, but the accelerometer should be fixed with it.

The other things should work in N67 (GPS working, charging bug fixed).

Edited May 10, 2011 by _amano

[Guest Psyloid]

The accelerometer is not fixed with N67.

All the sensors have been removed in N68 (that makes it a very broken build) and an updated sensor lib will return in N69 (hopefully!!). The patch is awaiting its final review, but the accelerometer should be fixed with it.

The other things should work in N67 (GPS working, charging bug fixed).

cool that means i will almost be ready for CM7 :unsure:

I need accellerometer for some games :)

[Guest dadashi]

I've had 7.0.3 on my SF last couple of days and had many problems wgich didn't exist in 7.0.2, for example:

-GPS- inaccurate and phone reboots after GPS fix!!

-SF dies after charging and only removing the battery helps

I went back from 7.0.3 to 7.0.2 and my navigation app is working again and I've recharged without a reboot...

[Guest _amano]

Strange. 7.0.3 and 7.0.2 should be nearly identical. It is the old 7.0 codebase with all its issues and 7.0.3 was just 7.0.2 + an additional security fix. Current nightly builds should have both issues fixed.

One problem with N67 is the silent hissing (which drains probably a bit of battery as well), but the patch for that is also in review.

Tomorrow is Wednesday. If the "hissing" and the "accelerometer lag" patches are merged in time (and work!), we could get the perfect ROM then :unsure:

Edited May 10, 2011 by _amano

[Guest supermies123]

CM7 light sensor is waaay slower than in Android 2.2 ROM's. Why is that?

[Guest The Soup Thief]

Strange. 7.0.3 and 7.0.2 should be nearly identical. It is the old 7.0 codebase with all its issues and 7.0.3 was just 7.0.2 + an additional security fix. Current nightly builds should have both issues fixed.

One problem with N67 is the silent hissing (which drains probably a bit of battery as well), but the patch for that is also in review.

Tomorrow is Wednesday. If the "hissing" and the "accelerometer lag" patches are merged in time (and work!), we could get the perfect ROM then :)

Perfect Wednesday ROM - haven't read about that Modaco meme for a while! :unsure:

fwiw, I've had unreasonably good battery life out of the last couple of nightlies - and having played no games today I've not missed the sensor libs on n68

So will the buildbot be making a young Jimjam707 very happy with a perfect wednesday n69? (he's posted previously about his particular affinity for that number :P )

[Guest Michealtbh]

CM7 light sensor is waaay slower than in Android 2.2 ROM's. Why is that?

Default values aren't very good, change them yourself in CM settings

[Guest Len Ash]

The accelerometer is not fixed with N67.

All the sensors have been removed in N68 (that makes it a very broken build) and an updated sensor lib will return in N69 (hopefully!!). The patch for it is awaiting its final review now, but the accelerometer should be fixed with it.

The other things should work in N67 (GPS working, charging bug fixed).

N67 - GPS causes random reboots, accelerometer U/S, Wifi reconnections poor, autobrightness completely erratic and limited (reduced to 5 steps).

Other than that, all good.

[Guest sej7278]

One problem with N67 is the silent hissing (which drains probably a bit of battery as well), but the patch for that is also in review.

what's the silent hissing bug?

the non-silent hissing bug (3608) libaudio.so patch 2 has been submitted but not merged yet, seems not to drain battery.

[Guest targetbsp]

N67 - GPS causes random reboots, accelerometer U/S, Wifi reconnections poor, autobrightness completely erratic and limited (reduced to 5 steps).

Other than that, all good.

I've never had a GPS reboot

Autobrightness takes all of a minute to sort out and I've only ever had to do it once - admittedly, it should be sorted out from the start.

Wifi reconnection is 100% reliable if your sleep policy is set to never. (Even the Froyos are only about 95% reliable for me)

Accelerometer I never use but I accept from others it is probably broke! Meant to be a fix incoming though.

Edited May 10, 2011 by targetbsp

[Guest Len Ash]

I've never had a GPS reboot

Autobrightness takes all of a minute to sort out and I've only ever had to do it once - admittedly, it should be sorted out from the start.

Wifi reconnection is 100% reliable if your sleep policy is set to never. (Even the Froyos are only about 95% reliable for me)

Accelerometer I never use but I accept from others it is probably broke! Meant to be a fix incoming though.

I have removed most of the CM bling for now...

Autobrightness using the ROM, not the bloaty app. 2 things wrong, someone has fiddled with the array values and the brightness level locks up at high brightness levels

WiFi (for battery life) needs to switch off - never is no use to me, the Atheros WLAN module in the ROM is "not good". Agree with 95% on 2.2s.

I use accel and Nav....

Edited May 10, 2011 by Len Ash

[Guest targetbsp]

Autobrightness using the ROM, not the bloaty app. 2 things wrong, someone has fiddled with the array values and the brightness level locks up at high brightness levels

WiFi (for battery life) needs to switch off - never is no use to me, the Atheros WLAN module in the ROM is "not good". Agree with 95% on 2.2s.

I use accel and Nav....

I don't use an app? Unless you mean CM settings - in which case I have it running for overclocking anyhow so its nothing extra to me. :unsure:

I haven't decided whether wifi never uses more power or not - it certainly doesn't hold a wifi connection much to a lot of peoples (but not mines :) ) annoyance. But I do have Tasker enable and disable the wifi with screen on and off anyway. This with sleep never gives me a 100% reconnection which leaves CM7 (at least N35) a completely flawless rom for my purposes. :P

Froyo has the less than 100% (but admittedly still good) wifi reconnection plus except swedish spring, i have super user troubles with them.

CM7 also has the stunningly useful ability of telling me via the notification led when I've missed a call when the phone is asleep. This is frankly the main reason I use it. ;) Someone should stick that in a Froyo.

Edited May 10, 2011 by targetbsp

[Guest Mushroom_Lord]

I am just hopping between the stable builds at the moment, and haven't any issues with them.

I wish for menu speed, (FLB!!!!!!!) but Everyone else is experiencing bugs so I will have to wait.

OH wait, one bug. After a while some "pop ups" (like long press on home) don't draw, the buttons work but I cant actually see them.

Luckily a reboot fixes :unsure:

[Guest Len Ash]

I don't use an app? Unless you mean CM settings - in which case I have it running for overclocking anyhow so its nothing extra to me. :unsure:

Yes, it's an app. There are a lot of apps in CM7... lol

[Guest targetbsp]

Yes, it's an app. There are a lot of apps in CM7... lol

Yeah but if I wasn't running that I'd be running SetCPU or Nofrills anyway...

Personally I uninstall all the other CM apps. And quite a few of googles for that matter.

[Guest Superfuzz]

Autobrightness takes all of a minute to sort out and I've only ever had to do it once - admittedly, it should be sorted out from the start.

Where exactly can I do that? :unsure:

[Guest targetbsp]

Where exactly can I do that? :unsure:

CM Settings -> Display -> Auto Backlight -> edit other levels

Make them look like this: http://android.modaco.com/index.php?act=at...st&id=71188

[Guest targetbsp]

Where exactly can I do that? :unsure:

CM Settings -> Display -> Auto Backlight -> edit other levels

Make them look like this: http://android.modaco.com/index.php?act=at...st&id=71188

Oh and set buttons to 255 on the top couple and 0 on the rest. That will turn on the keypad backlight when it's dark

[Guest Fou-lu]

I am just hopping between the stable builds at the moment, and haven't any issues with them.

I wish for menu speed, (FLB!!!!!!!) but Everyone else is experiencing bugs so I will have to wait.

OH wait, one bug. After a while some "pop ups" (like long press on home) don't draw, the buttons work but I cant actually see them.

Luckily a reboot fixes :unsure:

Really should try N67, absolutely no bugs so far,first build that I've not needed to reboot once, 2.3.4 seems to fix everything, except accelerometer.

anyone getting bugs on this version try format system + boot, wipe everything and don't restore nothing! 95% perfection, even battery improved which i didn't notice needed improvement...