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

[Guest targetbsp]

do any of you guys get static noise through earphones when the volume is quite low while your playing music?

It happens if you use headphones other than the supplied ones. I thought the first person to tell me this was crazy but I dug out the orange box containing a pair of headphones I'd not even opened and they were right!

[Guest SantiagoChow]

Hi there, for those interested I'm using Simon's (sej7278) N142+, and the battery life is superb. No reboots or funny business, this is the best ROM to date, hands down. I'm so glad I switched back to CM7 over a month ago.

So a big thanks to Simon, a great ROM and your blog is very enjoyable too. Also want to say a massive thanks to the Cyanogen code team, we truly are not worthy. Blade + N142+ = salad days!

Anil.

Thanks for your recommandation!

But I still encounter imaging problems(error of displaying images) when I try to play games like plants vs zombies. Hope it can be better......

[Guest JimJam707]

No new nightly? :( I see a "Blade: updated kernel"!

2.3.5 Just got merged in. When 2.3.4 was merged in, or even 2.3.3, there was a few days gap where the build bot didn't build any nightlies.

[Guest targetbsp]

Thanks for your recommandation!

But I still encounter imaging problems(error of displaying images) when I try to play games like plants vs zombies. Hope it can be better......

Playing it following a reboot helps for me. Others have said turning off surface dithering in cm settings -> performance helps for them.

[Guest sej7278]

2.3.5 Just got merged in. When 2.3.4 was merged in, or even 2.3.3, there was a few days gap where the build bot didn't build any nightlies.

yes git is a bit in flux at the moment - you've got a new build id GRJ90 but the android version is still 2.3.4 (for everything except defy) and the sdk version is 2.3.5 so its probably a good idea not to be rushing out nightlies in that state!

the new kernel is the same as in my n142+, its not 2.6.35 so don't get too excited :D

[Guest Rucha]

Something is wrong with FM on 142+.

FM band can not be scaned correctly.

Does anyone faced this issue?

Edited July 27, 2011 by Rucha

[Guest ffoxsake]

Something is wrong with FM on 142+.

FM band can not be scaned correctly.

Does anyone faced this issue?

I noticed that too but only when i changed the settings from default of North America over to Europe.

When i changed back to North America the seeking worked ok, so have left it as that for now. Maybe that will help you too?

[Guest Rucha]

I noticed that too but only when i changed the settings from default of North America over to Europe.

When i changed back to North America the seeking worked ok, so have left it as that for now. Maybe that will help you too?

Same with North America. Thank's anyway!

[Guest Tetas]

Hi,

It happened the same to me. The thing is, beeing in Europe (Portugal) the settings for the US doesn't quite cut it since it's a 200Khz increase (instead of the 100khz for europe) , so even though you don't get stuck at 89.9 and you do have a wider frequency range, you do miss some stations in between. I tried manually select them and add my favourites but still there are some that you can't tune in. I read about this on a FM radio thread, about getting it to work on gen2, it started as a proof of concept, and I remember this being one of the issues.

[Guest Janil]

So, the changelog says

blade: update kernel

Add support for new LCD panel used in the V880.

Does this mean everything else is included aswell or just the support for the panel?

[Guest targetbsp]

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

I've seen people say this about past versions (able to overclock more than before) and I've always dismissed it because it makes no sense to me. An overclocking limit should be a hardware limit - not a software limit.

I have to say though, I was bored today and had a play and my phone seems stable at 748Mhz now as opposed to the 710 I tested to and used ever since the Froyos. I don't know whether this is a software change (if it is, bare in mind it could go the other way so if an update leaves you hanging or rebooting - try clocking less first) or if it's because I set my speed under Froyo with both the AHB and CPU overclocked and with CM7 where the AHB is not overclocked (I think?)and the CPU can overclock higher on its own?

In any case overclockers, if you set your speed a good while ago - you might be able to go higher these days! Might explain why newer users seem to overclock higher as far as I can tell too!

I'm not using 142+ though. In fact I can't remember what I'm using! Some random official nightly release from the past few days.

Edited July 27, 2011 by targetbsp

[Guest neologan]

I've noticed on my blade, ADW launcher seems to act really slow. I switched to Launcher Pro and it's super smooth now in the apps drawer, etc.

Is this normal? If so, why is ADW included as default with the build? Am i missing something good about it?

[Guest k0zmic]

I've noticed on my blade, ADW launcher seems to act really slow. I switched to Launcher Pro and it's super smooth now in the apps drawer, etc.

Is this normal? If so, why is ADW included as default with the build? Am i missing something good about it?

It is normal.

Because CM aren't really allowed to bundle LauncherPro for instance since it's not open source. I think they were looking into a way to bundle both ADW and the Stock Gingerbread Launcher so people could just choose between the two.

[Guest JustasU]

Is it possible to make scrolling faster? Because it's really bad compared to GSF...

[Guest targetbsp]

I've noticed on my blade, ADW launcher seems to act really slow. I switched to Launcher Pro and it's super smooth now in the apps drawer, etc.

Is this normal? If so, why is ADW included as default with the build? Am i missing something good about it?

Yeah, ADW doesn't like the Blade/CM7 combination. All of the 2d scrolling (the menu's and stuff) is pretty jerky in CM7 compared to Froyos and Ginger Stir Fry and ADW seems to suffer from this where other launchers (including ADW Ex oddly) don't. IIRC it has something to do with us needing official GB source code from ZTE to be able to user new/better graphics libraries.

As for what you're missing, I think that's probably that CM7 is used on dozens of devices and I imagine ADW works great on devices that don't have 2d scrolling issues.

[Guest neologan]

Is it possible to make scrolling faster? Because it's really bad compared to GSF...

Maybe install launcher pro, it's as smooth as smooth can be.

[Guest JustasU]

Maybe install launcher pro, it's as smooth as smooth can be.

Yes its smooth with LP but not everywhere. I mean to make smoother in settings.

[Guest qwerty_29]

Hi qwerty_29, I love ANDROID because of the vast choices I have, I also love it because of the OS tools. Unfortunately the tools, in this case the Running Services framework, and the battery usage stats, make people fret over inconsequential details. Is your battery running flat before you can get to a charger? Probably not.

I am very guilty of this fretting syndrome. But I am trying to keep on top of it. I have very similar services running as you do. So I wouldn't sweat it. I hope this is helpful. Anil.

Yes, Anil, you're (almost 100% :P) right! I am not running out of battery before getting to a charger. However, when you see reports of 48+ hour long phone usage without a charge it makes you think: "hey, I want that too! What if one of these days I have the chance to charge overnight?!" :lol:

Either way, I installed Autostarts. No longer have partial wakes. Does the battery last significantly longer? I don't know. But I am sure it is not being wasted by something useless. ;)

However, I still find the "Go to sleep" order (i.e., pushing the power button :P) pretty unreliable! :huh: Does anyone have this as well? I'm on Sej's 142+... I would say that half of the times I press the power button, the phone does not fall asleep, as if I press home/menu/back, the screen turns on again as if I am pressing the power button (despite having the configurations right in order to only wake with power button).

Another problem that has affected me lately: sending SMS.

Sometimes, the SMS sending is just not working. I can receive SMS, make and receive calls, but I just can't send SMS. The problem stays for some minutes (15 or so), and then out of the blue I am able to send SMS again. Reboots do not solve it, neither toggling from 2g to 3g or using stock message app. Never happened before installing CM7.

After some struggle trying to discover what caused the problem, I think (not sure) that the problem starts when I try to send a particularly big SMS (with 3 pages or more),. The strange is that then it spreads to all outgoing SMS, despite their size.

Searched the web, and found out that the problem might reside in the SMS Center Number misconfiguration. So went to check it: Dialed *#*#4636#*#* , "phone information", scroll all the way down to SMSC. There was no number there. Touched "Refresh" (the button on the right -> useful tip because of some mistranslations that make both the buttons have the same word). The text (without the brackets) ["+351911616161",145] appears on the box. Touched "Update" (the button on the left-> useful tip, same reason as before, and nothing happened. However, going back (back button), and then entering again in "phone information" reveals that the SMSC is blank again, no number there.

Searched the web further, learned how to convert my carrier (Vodafone, in Portugal) SMS Center Number into PDC Format (some forum like XDA inform that we should first do that), made the conversion, entered the converted number, pressed "Update", and an "Update Error" message shows.

Did anyone else experienced this? If so, any solutions?

PS: I do not think the problem resides in the SIM card itself as it is 3 months old. However, I did not try it on another phone, because I can't reproduce the issue every time I want to (thats why I wrote that I "think (not sure) that the problem starts when I try to send a particularly big SMS").

Any help would be very appreciated!

[Guest Jean85]

Is it possible to make scrolling faster? Because it's really bad compared to GSF...

I use ADW EX, and it's really smooth, even without overclock.

[Guest targetbsp]

d the "Go to sleep" order (i.e., pushing the power button :P) pretty unreliable! :huh: Does anyone have this as well? I'm on Sej's 142+... I would say that half of the times I press the power button, the phone does not fall asleep, as if I press home/menu/back, the screen turns on again as if I am pressing the power button (despite having the configurations right in order to only wake with power button).

You're not telling the phone to go to sleep. You're telling it to turn the screen off. It will then go to sleep after several seconds - not immediately. So when testing this - leave it a few minutes before pressing the keypad buttons to be sure.

As for how long it lasts - it depends on how you use it. I can flatten it from full to empty in 5 hours of grand prix story. Or I can have it mostly standby on 2g, with the odd text or short call for 8 days.

Edited July 27, 2011 by targetbsp

[Guest appolus]

hey guys which nightly do you recommend that is stable and have good battery life? thanks! thinking of going to cm7 after growing tired of gsf

[Guest k0zmic]

hey guys which nightly do you recommend that is stable and have good battery life? thanks! thinking of going to cm7 after growing tired of gsf

Sej's N142 build. Read the last few pages back for feedback on it and the download link.

[Guest sej7278]

So, the changelog saysDoes this mean everything else is included aswell or just the support for the panel?

that's what i'd like to know too - as there's been 6 commits after that one with v9 tablet fixes etc. (they're in my n142+)

this is the problem with the kernel not being stored as source in cyanogenmod's git repo, its stored as a binary, and the source is in tom_g's personal github account - so hope he doesn't get tired of blades :D

it kind of makes a mockery of gerrit code review, as what gets checked into gerrit is a binary, so how can the reviewers review it? (other than the binary loads ok on their phone!)

[Guest emc02]

N145 is ready!

[Guest k0zmic]

N145 is ready!

Nice, I checked for it 10 minutes ago but it hadn't come out. Cheers for the tip.

Anyway, this adds the new Blade kernel with support for the LCD Panel on the V880: http://review.cyanog...om/#change,6852

BTW if anyone has installed N145 could you let us know how it is?

Edited July 27, 2011 by k0zmic