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

[Guest wbaw]

I don't know how this patch works/worked. But on B27, the green LED stays on irrespective of any notification. Even when the phone is in deep sleep the LED stays on. Is it meant to stay on all the time and correctly blink when I have notification?

It's supposed to stay on only when you have a notification, then disappear a couple of seconds after you wake the phone. It works on my phone, but I had the same problem with the red led sticking on before I 'fixed' the patch to only affect the green led.

Plugging a usb cable in will reset it, but then it'll probably come back next time the phone sleeps, if it's the same problem that I was seeing with the red led. It's probably some bug in the zte rom & the bug might not occur in cm7.

The patch still needs more work. I think part of the problem is due to the status of the led not being reset to the previous state on resume. There were similar bugs when it was used in CM7 on the old kernel.

https://github.com/John-Kenney/kernel-35/commit/adebf262536e83e6dac99d570598cafa1da4c396

https://github.com/John-Kenney/kernel-35/commit/1be339cc17619bc67f537ca8b76f77b33c4b13fe

Edited September 28, 2011 by wbaw

[Guest StarG]

Hi all, I'm a Noob here, though I've been following the forum for months. I would like to flash N209, but I would also really like Sej's Softbuttons but I don't know how to add them. Can anyone help? Cheers.

[Guest Psyloid]

WiFi settings - MENU / advanced

I feel pretty dumb, but it says either "when creen turns off', "never when plugged" in or "never"

I remember users saying that it could stay on for 15 minutes when screen turns off, which option do i need to take???

[Guest shmizan]

the 15 minutes thing was a bug, not a feature. what happened was when you picked the "never" option it would only last for 15 minutes.

the options listed now work as they should.

also, I'm still on 179 patch 7. the notification LED works but I went to sleep with 80%, got a message sometime during the night and work with 11%.

is something wrong? I remember TomG said blinking LED needs a lot of CPU power and will drain battery.. is this it?

[Guest zasten]

I don't have any GPS issues with N208, reasonably fast lock and it seems to turn off O.K.

Everything seems to be working ok even if the lag before displaying the lock screen is a little anoying. First impression is that bluetooth is working, although a little flakey. More testing needed to confirm. Battery life very good.

A definite improvement over patch 7 kang from sej and Tom G. The wifi now stays on together with GPS.

Good work! N208 looks like a keeper.

[Guest Kamikaze.]

Phew! Finally got this rom to work(208). I just had to be careful restoring my apps. I only restored data for like 5 apps...

Sent using Tapatalk

[Guest jackal-sk]

After watching furutama for 1 hour on 1/4 backlight the battery went down by only 16% ! I'm very satisfied with this rom now. :)

[Guest targetbsp]

the 15 minutes thing was a bug, not a feature. what happened was when you picked the "never" option it would only last for 15 minutes.

the options listed now work as they should.

also, I'm still on 179 patch 7. the notification LED works but I went to sleep with 80%, got a message sometime during the night and work with 11%.

is something wrong? I remember TomG said blinking LED needs a lot of CPU power and will drain battery.. is this it?

with screen off is 15 minutes.

the led notifications are not implemented yet to my knowledge - it's GSF it was added to. I expect your phone failed to sleep for some reason (hence the drain)

Edited September 28, 2011 by targetbsp

[Guest shmizan]

with screen off is 15 minutes.

the led notifications are not implemented yet to my knowledge - it's GSF it was added to. I expect your phone failed to sleep for some reason (hence the drain)

ok. I stand corrected.

and I guess something WAS failing to sleep. no other explanation.

[Guest sej7278]

lockscreen in n209 is asking for trouble if you ask me - it would be so easy for that to unlock in a pocket, all you have to do is drag one of the circles a bit, there doesn't appear to be a specific pattern or direction needed like with the rotary lockscreen.

[Guest muller37]

lockscreen in n209 is asking for trouble if you ask me - it would be so easy for that to unlock in a pocket, all you have to do is drag one of the circles a bit, there doesn't appear to be a specific pattern or direction needed like with the rotary lockscreen.

I agree the new lockscreen is not my cup of tea, but never had a problem with unlocking in my pocket especially as hard to press power button first to wake it up with a jelly case on then drag screen within 5 seconds. suppose it could happen though

[Guest !Amo!]

how can I restore the default (new) lockscreen?

Btw I got FC when I try to start the brightness menu in the display settings :(

[Guest Benoe]

lockscreen in n209 is asking for trouble if you ask me - it would be so easy for that to unlock in a pocket, all you have to do is drag one of the circles a bit, there doesn't appear to be a specific pattern or direction needed like with the rotary lockscreen.

You don't need to use the new locks, you can still select the rotary one in settings.

(settings - cm settings - lockscreen - style options - lockscreen style)

Edited September 28, 2011 by Benoe

[Guest t0mm13b]

I seem to be experiencing random reboots at intervals and had a look at the last_kmsg log...

[09-28 13:00:22.030000] [187: Playback Thread][audmgr.c:audmgr_disable] session 0xc0769528

[09-28 13:00:22.030000] [689: audmgr_rpc][audmgr.c:audmgr_rpc_thread] rpc_reply status 0

[09-28 13:00:22.050000] [689: audmgr_rpc][audmgr.c:process_audmgr_callback] DISABLED

[09-28 13:00:30.340000] [4: events/0]TAOS: als_interrupt =545

[09-28 13:00:31.220000] [4: events/0]TAOS: als_interrupt =158

[09-28 13:00:32.200000] [1: init]init: untracked pid 729 exited

[09-28 13:00:33.240000] [4: events/0]TAOS: als_interrupt =100

[09-28 13:00:39.690000] [4: events/0]TAOS: als_interrupt =299

[09-28 13:00:40.870000] [4: events/0]TAOS: als_interrupt =61

[09-28 13:00:44.080000] [4: events/0]TAOS: als_interrupt =193

[09-28 13:00:47.300000] [4: events/0]TAOS: als_interrupt =120

[09-28 13:00:48.940000] [4: events/0]TAOS: als_interrupt =70

[09-28 13:00:50.820000] [4: events/0]TAOS: als_interrupt =172

[09-28 13:00:51.850000] [4: events/0]TAOS: als_interrupt =267

[09-28 13:00:53.900000] [7: suspend][ZYF] lcdc_set_bl level=5, 1

[09-28 13:00:53.900000] [7: suspend][LY] send_bkl_address

[09-28 13:00:53.900000] [7: suspend][LY] send_bkl_data

[09-28 13:00:54.080000] [4: events/0]TAOS: als_interrupt =109

[09-28 13:00:54.280000] [7: suspend][ZYF] lcdc_set_bl level=6, 1

[09-28 13:00:54.280000] [7: suspend][LY] send_bkl_address

[09-28 13:00:54.280000] [7: suspend][LY] send_bkl_data

[09-28 13:00:54.679999] [7: suspend][ZYF] lcdc_set_bl level=7, 1

[09-28 13:00:54.679999] [7: suspend][LY] send_bkl_address

[09-28 13:00:54.679999] [7: suspend][LY] send_bkl_data

[09-28 13:01:00.630000] [4: events/0]TAOS: als_interrupt =296

[09-28 13:01:02.400000] [4: events/0]TAOS: als_interrupt =157

[09-28 13:01:04.150000] [4: events/0]TAOS: als_interrupt =103

[09-28 13:01:05.210000] [4: events/0]TAOS: als_interrupt =303

[09-28 13:01:07.090000] [4: events/0]TAOS: als_interrupt =127

[09-28 13:01:07.660000] [4: events/0]TAOS: als_interrupt =65

[09-28 13:01:21.580000] [4: events/0]TAOS: als_interrupt =138

[09-28 13:01:26.420000] [4: events/0]TAOS: als_interrupt =199

[09-28 13:01:38.370000] [81: binder]binder: release proc 1763, transaction 22956, not freed

[09-28 13:01:40.650000] [4: events/0]TAOS: als_interrupt =124

[09-28 13:01:48.829999] [4: events/0]TAOS: als_interrupt =234

[09-28 13:01:49.570000] [4: events/0]TAOS: als_interrupt =484

[09-28 13:01:50.300000] [4: events/0]TAOS: als_interrupt =152

[09-28 13:01:51.030000] [4: events/0]TAOS: als_interrupt =244

[09-28 13:01:51.620000] [4: events/0]TAOS: als_interrupt =456

[09-28 13:01:52.530000] [4: events/0]TAOS: als_interrupt =98

[09-28 13:02:10.660000] [4: events/0]TAOS: als_interrupt =386

[09-28 13:02:11.670000] [4: events/0]TAOS: als_interrupt =77

[09-28 13:02:20.920000] [4: events/0]TAOS: als_interrupt =133

[09-28 13:02:23.549999] [4: events/0]TAOS: als_interrupt =179

[09-28 13:02:25.020005] [4: events/0]TAOS: als_interrupt =54

[09-28 13:02:26.080000] [4: events/0]TAOS: als_interrupt =97

[09-28 13:02:33.240000] [4: events/0]TAOS: als_interrupt =167

[09-28 13:02:33.690000] [4: events/0]TAOS: als_interrupt =74

[09-28 13:02:39.390000] [4: events/0]TAOS: als_interrupt =91

[09-28 13:02:42.320000] [4: events/0]TAOS: als_interrupt =114

[09-28 13:02:46.410000] [4: events/0]TAOS: als_interrupt =157

[09-28 13:02:54.980000] [4: events/0]TAOS: als_interrupt =109

[09-28 13:02:56.660000] [4: events/0]TAOS: als_interrupt =148

[09-28 13:02:59.010000] [4: events/0]TAOS: als_interrupt =331

[09-28 13:02:59.780000] [4: events/0]TAOS: als_interrupt =505

[09-28 13:03:00.510000] [4: events/0]TAOS: als_interrupt =133

[09-28 13:03:06.040000] [4: events/0]TAOS: als_interrupt =444

[09-28 13:03:07.210000] [4: events/0]TAOS: als_interrupt =93

[09-28 13:03:12.630000] [4: events/0]TAOS: als_interrupt =76

[09-28 13:03:20.689999] [4: events/0]TAOS: als_interrupt =51

[09-28 13:03:21.590000] [4: events/0]TAOS: als_interrupt =162

[09-28 13:03:22.450000] [4: events/0]TAOS: als_interrupt =52

[09-28 13:03:24.789997] [4: events/0]TAOS: als_interrupt =112

[09-28 13:03:28.460000] [4: events/0]TAOS: als_interrupt =62

[09-28 13:03:33.210000] [4: events/0]TAOS: als_interrupt =113

[09-28 13:03:34.460000] [4: events/0]TAOS: als_interrupt =64

[09-28 13:03:59.080000] [4: events/0]TAOS: als_interrupt =472

[09-28 13:04:00.260000] [4: events/0]TAOS: als_interrupt =61

[09-28 13:04:01.270000] [4: events/0]TAOS: als_interrupt =257

[09-28 13:04:01.860000] [4: events/0]TAOS: als_interrupt =396

[09-28 13:04:02.450000] [4: events/0]TAOS: als_interrupt =96

[09-28 13:04:02.879999] [4: events/0]TAOS: als_interrupt =181

[09-28 13:04:03.320000] [4: events/0]TAOS: als_interrupt =44

[09-28 13:04:07.420006] [4: events/0]TAOS: als_interrupt =532

[09-28 13:04:09.739999] [7: suspend][ZYF] lcdc_set_bl level=8, 1

[09-28 13:04:09.739999] [7: suspend][LY] send_bkl_address

[09-28 13:04:09.739999] [7: suspend][LY] send_bkl_data

[09-28 13:04:10.060000] [4: events/0]TAOS: als_interrupt =43

[09-28 13:04:10.260000] [7: suspend][ZYF] lcdc_set_bl level=9, 1

[09-28 13:04:10.260000] [7: suspend][LY] send_bkl_address

[09-28 13:04:10.260000] [7: suspend][LY] send_bkl_data

[09-28 13:04:21.929973] [4: events/0]TAOS: als_interrupt =184

[09-28 13:04:22.949999] [4: events/0]TAOS: als_interrupt =52

[09-28 13:04:24.420000] [4: events/0]TAOS: als_interrupt =250

[09-28 13:04:25.880000] [4: events/0]TAOS: als_interrupt =47

[09-28 13:04:31.890022] [4: events/0]TAOS: als_interrupt =226

[09-28 13:04:32.620000] [4: events/0]TAOS: als_interrupt =43

[09-28 13:04:40.830005] [4: events/0]TAOS: als_interrupt =77

[09-28 13:04:46.250000] [4: events/0]TAOS: als_interrupt =107

[09-28 13:04:46.690000] [4: events/0]TAOS: als_interrupt =48

[09-28 13:04:49.790000] [4: events/0]TAOS: als_interrupt =82

[09-28 13:04:50.200000] [4: events/0]TAOS: als_interrupt =47

[09-28 13:04:54.180000] [4: events/0]TAOS: als_interrupt =81

[09-28 13:04:55.040000] [4: events/0]TAOS: als_interrupt =133

[09-28 13:04:56.240000] [4: events/0]TAOS: als_interrupt =40

[09-28 13:04:57.260000] [4: events/0]TAOS: als_interrupt =92

[09-28 13:04:58.260000] [4: events/0]TAOS: als_interrupt =45

[09-28 13:05:08.830000] [4: events/0]TAOS: als_interrupt =71

[09-28 13:05:28.760000] [4: events/0]TAOS: als_interrupt =143

Its almost like as if the proximity/light sensor is causing it to reboot, the screen goes bright when the light sensor handles it and then it freezes and reboots.

Any one experiencing this....? :unsure:

Edit: have done full wipe data/cache, calibrated proximity sensor, cpu using interactive governor overclocked to 729Mhz (it was perfect on n179...its this n208 that this is showing up...)

Edited September 28, 2011 by t0mm13b

[Guest sej7278]

You don't need to use the new locks, you can still select the rotary one in settings.

(settings - cm settings - lockscreen - style options - lockscreen style)

yes, i'm sticking with rotary, but just saying the new one isn't really adding value, its just gimmicky.

not such a problem as a lockscreen as you need to press power too, but as a phone answer screen it could be nasty.

[Guest shmizan]

the new lockscreen is nice.

could be really cool if it was responsive and smooth like it should and not laggy

[Guest t0mm13b]

I have experienced a reboot just now. Last thing I did, was activate wifi, went to market - updated Titanium Backup, ran the backup, then the handset vibrated to indicate it was done, the screen brightened up, then it froze. No response to touch, buttons etc. Plugged in the USB cable then it rebooted

I have attached the log here for info :)

Edit: Battery charging stats was inconsistent. Prior to reboot, it was charged. Then after reboot it dropped to 79%. Then just now its jumped to 95%....

reboot2.zip

Edited September 28, 2011 by t0mm13b

[Guest tsddave]

I have experienced a reboot just now. Last thing I did, was activate wifi, went to market - updated Titanium Backup, ran the backup, then the handset vibrated to indicate it was done, the screen brightened up, then it froze. No response to touch, buttons etc. Plugged in the USB cable then it rebooted

I have attached the log here for info :)

Edit: Battery charging stats was inconsistent. Prior to reboot, it was charged. Then after reboot it dropped to 79%. Then just now its jumped to 95%....

You should mention which version you are using.Also are you overclocking?

[Guest Simono]

I have using N208, now use N209 and don't have any issue, but I don't overclocking my Blade.

[Guest t0mm13b]

You should mention which version you are using.Also are you overclocking?

Please refer to the previous posting here #8915 a few posts back.... :)

[Guest Pieniek]

WOW, i just moved from 173+ to 209 without full wipe, and I must say, I am suprised with speed of my Blade! OC to 710 like on 173, but it's much faster! Thank you guys for your work, love you :)

[Guest jackal-sk]

WOW, i just moved from 173+ to 209 without full wipe, and I must say, I am suprised with speed of my Blade! OC to 710 like on 173, but it's much faster! Thank you guys for your work, love you :)

Great to hear that. One question I'd like to ask, can you recognize a difference between default clock and 710 mhz ? If so where ?

[Guest rockstarszzzz]

N209 is like a dream ROM!

Games - lustfully smooth

Scrolling - warm knife on butter

GPS, Wifi bla blah - solid as a rock

Battery so far - promising

[Guest Lost_Animal]

I think 209 is the BEST ROM tested So far.

All working without any problem any OMG really Fast.

I am running this ROM with Custom Themes and Full of GO Apps.

This Rom is a Keeper for me....

Edited September 28, 2011 by Lost_Animal

[Guest jackal-sk]

Well, here's mine environment, I was showing this to a friend but I can share here also. :)