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

[Guest sej7278]

Any ETA on 7.1 ? Don't want to go into all the hassle of upgrading to N62 and then discovering 7.1 will be released in a few days

n62 is 7.1 really - it builds as 7.1.0 RC0

RC1 is supposedly days away, but its not as if its going to be any different to a nightly.

final will be weeks off i'd think as it would require new gapps (not the iffy 05/03 ones) and a 2.6.35 kernel to be a "proper" 2.3.4 build.

i'm not bothering to upgrade from n60 until something major comes along in the changelog as facing no issues.

[Guest shad0wboss]

Is it really worth it to upgrade from SS RLS5 to n60? need some suggestions...

-for better battery life

-faster interface

-gps working....

and i'm still at gen1 here :/

[Guest dnaumov]

Check the loud speaker. Is it hissing?

Oh wow, yes it does. I wouldn't notice it if I didn't specifically check, the hiss is very very minor, I had to get into a very quiet corner of my work office and triple check (phone close to ear, phone far, phone close to ear, phone far, etc) to notice the hiss, but it's definately there.

[Guest Superfuzz]

Are there any changes to Auto Brightness in the last nightlies? Im using N61 atm and it doesnt seem to work (or at least it worked differently on 7.0.2).

[Guest DannyDanny]

I wonder if they will ever fix the reboot while charging issue. It was raised since the beginning and CM team did try to

fix this matter in alot of nightlies.

Maybe its just too difficult :mellow: Why does it happen by the way? Is it because CM7 uses more power?

[Guest shad0wboss]

I wonder if they will ever fix the reboot while charging issue. It was raised since the beginning and CM team did try to

fix this matter in alot of nightlies.

Maybe its just too difficult :mellow: Why does it happen by the way? Is it because CM7 uses more power?

This is the funny part about CM7 builds, i really respect the devs BUT i don't think they are fixing main bugs FIRST...i mean i've been waiting for a fix for a month now for accelerometer but it's still not fixed...gps gives problem...auto brightness works on early builds (sometimes) and then you have new issues along with the new build (speaker hiss)....i mean...to be honest, 2.3.2 was VERY stable apart from the force close error and next builds were 2.3.3 when they didn't even bother releasing a full stable 2.3.2 build and they just jumped to 2.3.3

I'm very disappointed by cm7...it's not that they can't fix it, it's just they keep releasing new stuff when the previous isn't fixed properly...to be honest....ALL these new builds should be used for TESTING only since they ALL lack something and NOT EVEN A SINGLE build has everything. such a pity for such skillfull devs.

[Guest hugobosslives]

doubt the reason is it uses more power....

tho it doesn't happen all the time. i have only had it twice (AFAIK). so doesn't bother me at all.

and i have used cm7 since RC1

[Guest Roku]

I don't know why I never had charging issues. I must be very lucky or can someone explain.

I have been using CM7 since N25. GPS issues I had in some point.

Now running N61 in Gen1 with KK converter.

Edited May 6, 2011 by Roku

[Guest Superfuzz]

This is the funny part about CM7 builds, i really respect the devs BUT i don't think they are fixing main bugs FIRST...i mean i've been waiting for a fix for a month now for accelerometer but it's still not fixed...gps gives problem...auto brightness works on early builds (sometimes) and then you have new issues along with the new build (speaker hiss)....i mean...to be honest, 2.3.2 was VERY stable apart from the force close error and next builds were 2.3.3 when they didn't even bother releasing a full stable 2.3.2 build and they just jumped to 2.3.3

So there are confirmed auto brightness issues? Care to give any link explaining more, cos I haven't encountered any, thanks.

But yeah that new bug of speaker hissing is bad news because battery drains seem to be bigger than 7.0.0 indeed, and seeing the issue marked as "Whiney" in bug tracker is disappointing as well.

I don't know why I never had charging issues. I must be very lucky or can someone explain.

Random bug is random, appears less often in 7.0.0 than latest versions. Maybe you're lucky, or maybe you have some other issue and your phone isn't sleeping while charging :mellow:

Edited May 6, 2011 by Superfuzz

[Guest k0zmic]

This is the funny part about CM7 builds, i really respect the devs BUT i don't think they are fixing main bugs FIRST...i mean i've been waiting for a fix for a month now for accelerometer but it's still not fixed...gps gives problem...auto brightness works on early builds (sometimes) and then you have new issues along with the new build (speaker hiss)....i mean...to be honest, 2.3.2 was VERY stable apart from the force close error and next builds were 2.3.3 when they didn't even bother releasing a full stable 2.3.2 build and they just jumped to 2.3.3

I'm very disappointed by cm7...it's not that they can't fix it, it's just they keep releasing new stuff when the previous isn't fixed properly...to be honest....ALL these new builds should be used for TESTING only since they ALL lack something and NOT EVEN A SINGLE build has everything. such a pity for such skillfull devs.

I believe the new kernel .35 is may be the answer to some of the problems since it was the one designed for Gingerbread. Remember, 'Stable' only means the Cyanogen specific stuff is 'Stable' not the entire ROM.

[Guest shad0wboss]

I believe the new kernel .35 is may be the answer to some of the problems since it was the one designed for Gingerbread. Remember, 'Stable' only means the Cyanogen specific stuff is 'Stable' not the entire ROM.

so are you suggesting me to flash nightly 61?

another question is that i heard that new nightly builds contain a radio firmware which can only work on gen2 devices? or can i still use converter? because i'm still on gen1

[Guest k0zmic]

so are you suggesting me to flash nightly 61?

another question is that i heard that new nightly builds contain a radio firmware which can only work on gen2 devices? or can i still use converter? because i'm still on gen1

The new kernel hasn't been integrated yet N62 is still .32 I believe so I wouldn't suggest it.

Not sure about that.

Edited May 6, 2011 by k0zmic

[Guest dadashi]

Oh no, there's definitely one of those. My phone's working loads better now :o

(plus my backache's very definitely a tiny tiny bit better, and that can't just be a coincidence. I'm 1,000,000% shure of that! "Chooz Nightlies[tm] - for fast and sometimes detectable relief of all known issues and difficulties")

:mellow:

I think you've got confused with night nurse from Beechams Powders...

[Guest mELIANTE]

Oh wow, yes it does. I wouldn't notice it if I didn't specifically check, the hiss is very very minor, I had to get into a very quiet corner of my work office and triple check (phone close to ear, phone far, phone close to ear, phone far, etc) to notice the hiss, but it's definately there.

I notice that when this happens battery gets drained. After a reboot there is no hissing and battery lasts long.

[Guest k0zmic]

I notice that when this happens battery gets drained. After a reboot there is no hissing and battery lasts long.

This might be what caused my battery to drain. I didn't check so I can't be sure.

Installed N61 enabled S2E then flashed Gapps. I reinstalled my apps without Titanium via Google Backup, changed hardly any CM settings, logged back into the apps I had just installed e.g Kindle and then rebooted a few times to check the phone would sleep and it was okay after two reboots. Rebooted the third time. The only accounts that were on sync were Whatsapp and Google. The phone was on 100% at around 12.30AM and around 7.45 when I woke up it had dropped by 60% with no usage.

Edited May 6, 2011 by k0zmic

[Guest KACE_231]

From using the the most recent nightly releases as soon as they come out I have observed the following problems from my experience, I have CM7 n62 installed:

1. accelerometer is not working properly (extremely laggy)

2. green LED on back button permenantly on

The following issue occur to me very rarely, but has happened in some occassions:

3. USB and mains recharging causes reboot

The following does not occur anymore:

4. GPS reboot

My response/observations about each issue:

1. The most UNIVERSAL issue to all our blades, what is taking so long to fix, possibly an issue with the OS itself?

2. New issue since upgrading to n62

3. I have noticed that this issue only happens when the cable becomes loose and comes out altogether, after I plug it back in and allow the recharge to continue, the reboot happens at some point during that charge cycle. In the occasions where the cable stays firmly in place there is no reboot during the charge cycle. My response is to try charging when the phone goes low on power (>20%) and allow it to charge fully before unplugging it, avoid constantly plugging/unpluggin/replugging the phone from the charger, within a short space of time.

4. Use google maps and navigation only to test GPS issue, sometimes it may reboot on first try but for following tries it is unlikely to happen again.

Further observations:

*Also N62 the kernel is still .32

*battery drain issue: try the battery recalibration technique, then try a full wipe and reinstall and test the battery usage with a stock CM7 ROM

*I do not have any hiss from my phone

Edited May 6, 2011 by KACE_231

[Guest The Soup Thief]

I think you've got confused with night nurse from Beechams Powders...

Just a placebo/homeopathy gag

Re: auto-brightness tho, yeah, it's very very hit or miss innit - it was working a while, then it wasn't and now (n62) it ain't (for me annyhoo)

[Guest targetbsp]

Just got an email, charging bug has been set to ShouldBeFixed. :mellow:

[Guest CaptainSpectacular]

It's strange but for me the most boring bug is the Back button Led stuck On (green or red depend of my SMS app installed). :mellow:

It's like my phone want to remind me something but he don't know what. xD

Also, one question stay in my mind until I use CM7 ROM. Why, yes why, why the screen doesn't turn On when we got new SMS/MMS/Mail ? :o

Anyway, I think if Kallt and others greats guys from here join their talent to the CM7 Blade team, the ROM will be finished tomorrow (or maybe today who now ?) :D

[Guest BillBong]

I'm looking to move from N57 to N61 (mainly because battery life on N57 is really bad for me). I did a clean wipe/install of N57 and I don't want to go through all that again so I 'm just going to wipe the dalvik cache and install over N57 which should be OK I hope. I've deleted ADW (I use GO instead) and also got rid off a few other CM7 things that came pre-installed. Will I have to strip these out of the N61 download again or will put ADW over my current setup if I don't?

[Guest abdn-android]

I'm noticing high sensor usage is hurting my battery life on n61 gen1. Every time I get/make a call my sensors seem to stay on until I reboot. Has anyone else seen this? Any ideas for a fix?

[Guest shad0wboss]

It's strange but for me the most boring bug is the Back button Led stuck On (green or red depend of my SMS app installed). :mellow:

It's like my phone want to remind me something but he don't know what. xD

Also, one question stay in my mind until I use CM7 ROM. Why, yes why, why the screen doesn't turn On when we got new SMS/MMS/Mail ? :o

Anyway, I think if Kallt and others greats guys from here join their talent to the CM7 Blade team, the ROM will be finished tomorrow (or maybe today who now ?) :D

i believe n 62 was kallt's work :/

[Guest alex1alex2alex3alex4]

I'm looking to move from N57 to N61 (mainly because battery life on N57 is really bad for me). I did a clean wipe/install of N57 and I don't want to go through all that again so I 'm just going to wipe the dalvik cache and install over N57 which should be OK I hope. I've deleted ADW (I use GO instead) and also got rid off a few other CM7 things that came pre-installed. Will I have to strip these out of the N61 download again or will put ADW over my current setup if I don't?

Yes, you will have to remove what you don't want installed - for every update.

[Guest bhf]

Just got an email, charging bug has been set to ShouldBeFixed. :o

Yay! The Devs are doing a great job. CM 7.1 could be the perfect ROM. :mellow:

[Guest]

has anyone been able to get the new google talk's voice chat working?? (on nightly 62 which is 2.3.4)

i can install the new client and the new lib and it runs fine but either nothing happens when i click the voice chate button or it crashes :/

Edited May 6, 2011 by Guest