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

[Guest Anil k Solanki]

Sure I understand that and that isnt off topic.

Off topic for example is talking about the zte phone within an unrelated thread.

Maybe its just the ex moderator in me!

Hi tsddave, just to be clear, I was agreeing with you. So as well as the ex moderator in you, common sense was speaking it's mind too. FYI, this thread is heading towards one million views, yowser! I dread the day I have to give up the Blade, no other handset has anywhere near as much support and enthusiasm.

Anil.

[Guest drobson67]

Hi, Just installed n142+ and nothing happens when the home button is pressed, the soft home button works fine, is anyone else experiencing the same problem?

[Guest dadashi]

Ive been using N133 for some time and I keep getting reboots, for example a reboot after shutting down GPS/Navigation or a reboot when I open a picture in gallery......I thought the gps reboot bug had been resolved 50 nightlies ago....

[Guest Anil k Solanki]

Hi, Just installed n142+ and nothing happens when the home button is pressed, the soft home button works fine, is anyone else experiencing the same problem?

Hi drobson67, I don't use the soft buttons but my home button works just fine.

Anil.

[Guest Anil k Solanki]

Ive been using N133 for some time and I keep getting reboots, for example a reboot after shutting down GPS/Navigation or a reboot when I open a picture in gallery......I thought the gps reboot bug had been resolved 50 nightlies ago....

Hi dadashi, I suggest doing a Nandroid back up and then trying this build N142+ by sej7278 (Simon).

Link to Simons post.

I hope this helps. Anil.

[Guest drobson67]

<br />Hi drobson67, I don't use the soft buttons but my home button works just fine.

Thanks for your reply I will reflash and see if this fixes the problem.

Update, reflashed n142+ and home button is working now, I only wiped dalvik cache on second flash, the first time I wiped data/cache and dalvik, I didnt try to fix the problem via a reboot which I should have tried but wasn't thinking, the lockscreen wasn't working before, when I pressed the power button phone was going straight to home screen bypassing the lock screen with slide bar.

Edited July 24, 2011 by drobson67

[Guest sej7278]

Thanks for your reply I will reflash and see if this fixes the problem

i've never seen that, have you tried just rebooting? also did you wipe dalvik and cache (not data) ?

it could be some weirdness with the softbuttons, but i doubt it - its not like they disable the hardware buttons.

[Guest judev]

Do i need to wipe data and cache if i go from CM 7.0.3 to nightly?

[Guest fire_of_mind]

first what i can say about n142+ is that i can overclock processor to 768MHz (before 748), nice

Do i need to wipe data and cache if i go from CM 7.0.3 to nightly?

yes

Edited July 24, 2011 by fire_of_mind

[Guest Anil k Solanki]

Do i need to wipe data and cache if i go from CM 7.0.3 to nightly?

Hi judev, I recommend wiping only the Cache partition and the Dalvik cache. You will loose personal data if you wipe the Data partition. Visit the web link below to a web page with explanations of ANDROID partitions.

ANDROID partitions.

I hope this helps you. Anil.

[Guest BruxoMor]

Hi All!

I'm new to Android and new to this Forum - please be gentle ;)

I'm currently running CM7 7.1 RC1 [Gen 2] and having some problems with:

- GPs not connecting to satelites,

- WiFi not reconnecting after StandBy,

- Battery drain (2-3% every hour when in StandBy).

I'm about to try a more recent nightly build to see if it solves at least the Battery issue and was wondering if someone can briefly explain me what are the diferences between the CM7 nightly 142 (cm_blade_full-142.zip) and the CM7 142+ from Simon aka SEJ7278 (update-cm-7.1.0-RC1-Blade-KANG-signed-20110720-n142plus.zip)?

Thx in advance.

[Guest drobson67]

i've never seen that, have you tried just rebooting? also did you wipe dalvik and cache (not data) it could be some weirdness with the softbuttons, but i doubt it - its not like they disable the hardware buttons.

Hi sej7278, I didn't try a reboot after I first flashed and I wiped both data/cache and dalvik cache using rom manager, the second flash I only wiped the dalvik cache and home button works now, I updated from n125+ and that was the best rom I've been using so I was keen to give n142+ a try, great work and thanks.

Edited July 24, 2011 by drobson67

[Guest Comas]

Someone have news about, dynamic range compression "DSP"

[Guest Anil k Solanki]

I'm about to try a more recent nightly build to see if it solves at least the Battery issue and was wondering if someone can briefly explain me what are the diferences between the CM7 nightly 142 (cm_blade_full-142.zip) and the CM7 142+ from Simon aka SEJ7278 (update-cm-7.1.0-RC1-Blade-KANG-signed-20110720-n142plus.zip)?

Thx in advance.

Hi and welcome, Definitely CM7 142+ from Simon aka sej7278, it works a treat.

Anil.

[Guest sej7278]

Hi and welcome, Definitely CM7 142+ from Simon aka sej7278, it works a treat.

Anil.

too kind anil ! yes RC1 wasn't exactly at a great place for us bladers, it still had the old kernel and libaudio battery drainage problems.

roll on RC2 i say, as people who don't read this thread will probably think RC1 is the latest "stable" build.

i guess we should figure out what the first stable-ish build was - i guess n126 (or my n125+ ?) had the new kernel so nothing earlier than that should be used any more, what was RC1 - something like n114?

Edited July 24, 2011 by sej7278

[Guest BruxoMor]

Hi and welcome, Definitely CM7 142+ from Simon aka sej7278, it works a treat.

Anil.

I assume from your answer that "the difference" is that Simon's build is generally better ;) - downloading now.

Thank YOU Anil for you prompt reply.

Will post some feedback in a few days time.

[Guest qwerty_29]

Hi everyone!

Is there any way to configure the back button led (when it comes to notification).

I'll explain why do I want to do that: I use Handcent SMS as message app, and there is an option there to keep screen of when I receive a message (in fact, there's not much use in wasting battery turning on the screen for each message received if the phone is in your pocket and you are not going to read the message immediately). This is a battery saver, so I would like to use it. The problem is that the led doesn't do a good job informing me of any notification because despite going red once in a while if I have an unread message, it only stays like that for one or two seconds, goes of for more than 30 seconds, turns on for 2 seconds, goes off again and so on...

Handcent SMS has an option to configure led notification, but it seems to have no effect on led behavior...

Any tips?

Thanks!

PS: sej, will try yoru new build! As always, it surely is a great job!

[Guest sej7278]

I assume from your answer that "the difference" is that Simon's build is generally better ;) - downloading now.

Thank YOU Anil for you prompt reply.

Will post some feedback in a few days time.

the kernel for n142 is from July 4th; my n142+ has a kernel which includes all the fixes since then listed here so some performance improvements, support for newer blades, v9 tablet tweaks etc.

softbuttons are enabled (not displayed by default) and its ahead of n142 by one commit "Lockscreen Background imprv."

QWERTY - what build are you using, as i thought notification LED's had been completely disabled since july 4th (new kernel) http://code.google.com/p/cyanogenmod/issues/detail?id=3700

Edited July 24, 2011 by sej7278

[Guest targetbsp]

The ability to show led with the phone asleep isn't in the new kernel. TomG has said it will be re-added in a new improved form at a later date.

@Sej: the led's are functioning the same as every other rom currently. Flashing if the phone is awake, off if the phone is asleep.

Edited July 24, 2011 by targetbsp

[Guest mullen666]

Using simons N142+

Launcher Pro

OC to 729mhz

Phone is snappy and responsive in games and UI

Any minor bugs (such as led) are inconsequential

You gain so much more than you lose

Gives my missus HTC Mozart a run for its money

£100?

What a bargain!!!

[Guest sej7278]

The ability to show led with the phone asleep isn't in the new kernel. TomG has said it will be re-added in a new improved form at a later date.

@Sej: the led's are functioning the same as every other rom currently. Flashing if the phone is awake, off if the phone is asleep.

got you - i just re-read tom_g's comment and it makes a bit more sense now thanks.

[Guest ididmytime]

Hi everyone!

Is there any way to configure the back button led (when it comes to notification).

I'll explain why do I want to do that: I use Handcent SMS as message app, and there is an option there to keep screen of when I receive a message (in fact, there's not much use in wasting battery turning on the screen for each message received if the phone is in your pocket and you are not going to read the message immediately). This is a battery saver, so I would like to use it. The problem is that the led doesn't do a good job informing me of any notification because despite going red once in a while if I have an unread message, it only stays like that for one or two seconds, goes of for more than 30 seconds, turns on for 2 seconds, goes off again and so on...

Handcent SMS has an option to configure led notification, but it seems to have no effect on led behavior...

Any tips?

Thanks!

PS: sej, will try yoru new build! As always, it surely is a great job!

If you need LED notifications use a build before the new kernel was introduced, n121 I believe?

You will have to replace the libaudio or you will get battery drain.

Edited July 24, 2011 by ididmytime

[Guest qwerty_29]

the kernel for n142 is from July 4th; my n142+ has a kernel which includes all the fixes since then listed here so some performance improvements, support for newer blades, v9 tablet tweaks etc.

softbuttons are enabled (not displayed by default) and its ahead of n142 by one commit "Lockscreen Background imprv."

QWERTY - what build are you using, as i thought notification LED's had been completely disabled since july 4th (new kernel) http://code.google.c.../detail?id=3700

The ability to show led with the phone asleep isn't in the new kernel. TomG has said it will be re-added in a new improved form at a later date.

@Sej: the led's are functioning the same as every other rom currently. Flashing if the phone is awake, off if the phone is asleep.

Hum... if so, either my phone is definitely not asleep, or my notification led works... I would bet the first one as correct... :(

I am using sej's N136+, and when I receive a message, the led flashes every now and then, even though the screen doesnt turn on with any button except for power...

[Guest targetbsp]

Hum... if so, either my phone is definitely not asleep, or my notification led works... I would bet the first one as correct... :(

I am using sej's N136+, and when I receive a message, the led flashes every now and then, even though the screen doesnt turn on with any button except for power...

The notification led was on solid when it was working. You probably have a reminder for missed texts set in handcent? Various text and reminder apps will let you setup the behaviour you're experiencing.

Edited July 24, 2011 by targetbsp

[Guest qwerty_29]

The notification led was on solid when it was working. You probably have a reminder for missed texts set in handcent? Various text and reminder apps will let you setup the behaviour you're experiencing.

Yes, I do have that set in handcent... that is why I described this issue in the first place: I wanted the led to flash more often, but no matter how I change handcent led notification setup, that has no effect on led behavior...

EDIT: tried disabling led notification option in handcent. no led notification now. Given that, isn't it weird that handcent can make led work or not, but can't affect the way it works (handcent has the option to change led blinking frequency)?

Edited July 24, 2011 by qwerty_29