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

[Guest mobiles007]

So here's another Huge bug. After clocking to 710 MHz on demand with SetCPU I'm getting constant freezes a 2-3 mins after a boot and only taking the battery out helps. I'm on the latest nightly 54 with KK's kernel. Is a Overclocking at all possible on this Rom build and at which frequency does it can provide a stable use?

[Guest dibbles]

Sorry then :)

eek - no need to be sorry Alex :)

I am sorry for posting in such a way. You gave the best advice you thought was correct and thus tried to help. It was only due to me following that thread I linked (as I have had the need to do certain repairs on my phone) that I knew about it.

I must stress though to people who are thinking of doing this, please read the entire thread and ask questions within it. Also pay attention to CaptainSpectacular's tutorial on page 3. I have not done it myself but it seemed to work for him.

[Guest targetbsp]

Hi Guys. Got a gen1 phone. installed N39 and a full charged battery last only for 7 hours without any use as all (i.e. sleep mode). Is it possible? or this is my bad luck? came back to SSrls5 and it works fine. Are there really severe battery drain issues with CM7? I'm going to try N54 with KK converter. Fingers crossed.

Are you sure it was sleeping? Anything showing in partial wakes on spare parts? On N35, Mine's on its 5th day of light use without charge and 20% left. I run it on 2g and only switch to 3g as needed, i have tasker switching off the wifi when screen is off, and airplane it over night.

The light use for these 5 days has included a few texts, a level of refraction, several levels of toki tori, various app updates downloaded, 5 minutes testing the gps issue in maps.

If I sit and play games for a good length of time it needs charged every couple of days but 7 hours for no use doesn't sound right.

[Guest targetbsp]

So here's another Huge bug. After clocking to 710 MHz on demand with SetCPU I'm getting constant freezes a 2-3 mins after a boot and only taking the battery out helps. I'm on the latest nightly 54 with KK's kernel. Is a Overclocking at all possible on this Rom build and at which frequency does it can provide a stable use?

The speed you can clock you depends on YOUR cpu - not the rom. Have you done 710 previously? If not then I'd say your CPU can't handle 710 - try lower. If no overclocking speeds work then it may be a fault in the rom (that's happened in the past - N36). But you can;t claim that just because a speed you want to use doesn't work. :)

Edited April 24, 2011 by targetbsp

[Guest bhf]

So here's another Huge bug. After clocking to 710 MHz on demand with SetCPU I'm getting constant freezes a 2-3 mins after a boot and only taking the battery out helps. I'm on the latest nightly 54 with KK's kernel. Is a Overclocking at all possible on this Rom build and at which frequency does it can provide a stable use?

There is no 'stable use' when it comes to overclocking. Every CPU is unique, some can be better overclocked, some not. If your CPU can't handle 710 MHz, then that's the cold, hard truth you have to face. Go down two steps and try again. If the phone still reboots or freezes, go down 2 steps again and so forth.

[Guest mobiles007]

The speed you can clock you depends on YOUR cpu - not the rom. Have you done 710 previously? If not then I'd say your CPU can't handle 710 - try lower. If no overclocking speeds work then it may be a fault in the rom (that's happened in the past - N36). But you can;t claim that just because a speed you want to use doesn't work. :)

Strange is it had worked flawlessly on 710 with Froyo SS and now with nightly 54 it freezes. Under 700 is ok for an hour now.

[Guest targetbsp]

Strange is it had worked flawlessly on 710 with Froyo SS and now with nightly 54 it freezes. Under 700 is ok for an hour now.

It might just be that your phone was borderline stable at 710 and CM7 works some part of the CPU a bit harder than Froyo or something?

[Guest Android.Fan]

Are you sure it was sleeping? Anything showing in partial wakes on spare parts? On N35, Mine's on its 5th day of light use without charge and 20% left. I run it on 2g and only switch to 3g as needed, i have tasker switching off the wifi when screen is off, and airplane it over night.

The light use for these 5 days has included a few texts, a level of refraction, several levels of toki tori, various app updates downloaded, 5 minutes testing the gps issue in maps.

If I sit and play games for a good length of time it needs charged every couple of days but 7 hours for no use doesn't sound right.

Sorry I forgot to mention that I use 3g all the time. And SIP Voip is also connected constantly on 3g. Gmail is synced at default intervals and an IMAP account on Email application is synced after every hour. All the data transmission is on 3G. But I use all these things on SS RLS5 and it lasts for 48hrs easily with normal use of phone calls, messages, Emails some playing around with the phone. It was really a shock when I woke up in the morning and phone was off. I thought it could me random reboot as some people mentioned on this forum. But when I switched it on battery was ANGRY red with a cross on it.

I have just installed N54 with KK converter. Lets see how it behaves. Anybody experience the same problem at the same level of use?

Oh yes an important thing to mention. When I put it on charging (With CM7 installed) the back side of phone gets hot (more than normal) and and it takes much more than normal time to get fully charged. Normal means SS mod.

[Guest dr_AllCOM3]

Can I keep my (app) settings somehow when upgrading to a newer version?

[Guest Android.Fan]

Today I have decided to play around with my phone powered by CM7 N54.

Here is my first finding. If you feel your home screen not scrolling smoothly with static wallpapers then do the following

1. Disable Wallpaper Hack in ADW Launcher -> System Preferences.

2. Disable Surface Dithering in CyanogenMod Settings -> Performance.

It made my STATIC wallpapers scrolling as smooth as skating on ice.

[Guest ropin]

hi was just wondering how people on gen 1 phones have installed the latest nightly

if they have used the converter did they use the ahb overclocking. also has anyone tried with the alternative kernel

thanks

[Guest alex1alex2alex3alex4]

Can I keep my (app) settings somehow when upgrading to a newer version?

Depends on what you consider "a newer version", when upgrading from one nightly to

another of the same generation you won't lose anything - unless you deliberately wipe.

[Guest Android.Fan]

hi was just wondering how people on gen 1 phones have installed the latest nightly

if they have used the converter did they use the ahb overclocking. also has anyone tried with the alternative kernel

thanks

I installed one without AHB and Non Alternative (the very first in the KK post).

[Guest targetbsp]

Sorry I forgot to mention that I use 3g all the time. And SIP Voip is also connected constantly on 3g. Gmail is synced at default intervals and an IMAP account on Email application is synced after every hour. All the data transmission is on 3G. But I use all these things on SS RLS5 and it lasts for 48hrs easily with normal use of phone calls, messages, Emails some playing around with the phone. It was really a shock when I woke up in the morning and phone was off. I thought it could me random reboot as some people mentioned on this forum. But when I switched it on battery was ANGRY red with a cross on it.

I have just installed N54 with KK converter. Lets see how it behaves. Anybody experience the same problem at the same level of use?

Oh yes an important thing to mention. When I put it on charging (With CM7 installed) the back side of phone gets hot (more than normal) and and it takes much more than normal time to get fully charged. Normal means SS mod.

Ah I think people have commented earlier that it's harsh on the battery with 3g. I'm generally near wifi so I'm not too up on the problem.

[Guest Android.Fan]

Ah I think people have commented earlier that it's harsh on the battery with 3g. I'm generally near wifi so I'm not too up on the problem.

Well this is a 3G phone and it should be expected to work on 3G. I'm not saying that 3G should work as efficiently as 2G (battery wise) but it should last for at least 24hrs with 3G usage. As I mentioned in my previous post It runs for 48hrs on SS with constant 3G connection. It means something in CM7 is getting battery drained insanely.

[Guest Android.Fan]

Ah I think people have commented earlier that it's harsh on the battery with 3g. I'm generally near wifi so I'm not too up on the problem.

One more problem with WiFi is Android disconnects WiFi when phone goes to sleep mode even with WiFi sleep policy set to Never. It was the case with all froyo ROMs on Blade. I need a constant connection to internet all the time. I haven't got WiFi at the moment so anybody please confirm if this issue is still there on CM7.

[Guest t0mm13b]

One more problem with WiFi is Android disconnects WiFi when phone goes to sleep mode even with WiFi sleep policy set to Never. It was the case with all froyo ROMs on Blade. I need a constant connection to internet all the time. I haven't got WiFi at the moment so anybody please confirm if this issue is still there on CM7.

Look for either

• Blade Wifi Fix
  
• Wifi Fixer
  

Both of these are available in the android market-place... :)

[Guest bhf]

The WiFi transfer rates are abysmal. With every Nightly the transfer rates get worse. It started somewhere around N35. Up to N39 the transfer rates were just cut in half and get up to 2800 kBit (at a DSL line with 6000 kBit). Now, with the most recent Nightlies N51 and N54, I only get rates in the mid triple digits up to 650 kBit. That's about a tenth of the DSL Line.

Has anyone made similar experiences?

[Guest Superfuzz]

Does the bass boost feature of the DSP Manager works for you guys? Doesn't seem to work for me, using the stock Music app, also the max volume is way too low on earphones, any workarounds?

The WiFi transfer rates are abysmal. With every Nightly the transfer rates get worse. It started somewhere around N35. Up to N39 the transfer rates were just cut in half and get up to 2800 kBit (at a DSL line with 6000 kBit). Now, with the most recent Nightlies N51 and N54, I only get rates in the mid triple digits up to 650 kBit. That's about a tenth of the DSL Line.

Has anyone made similar experiences?

How do you check the rates? I'm not impressed by the Wi-Fi performance either, so I'd like some numbers.

Edited April 24, 2011 by Superfuzz

[Guest toytown]

With N35 i get anywhere between 700-1100KByte per second, so 5.6-8.8Megabit on WIFI. I'm measuring this his my the time it takes to transfer 100MB file over FTP.

[Guest bhf]

How do you check the rates? I'm not impressed by the Wi-Fi performance either, so I'd like some numbers.

I use two different apps. Traffic Monitor and SpeedTest.net Mobile

Both results are similar bad.

The last five results are as follow

587 kBit 24/04 04:58 pm

606 kBit 23/04 10:58 am

648 kBit 23/04 09:41 pm

213 kBit 22/04 01:27 pm

610 kBit 22/04 11:31 am

Mobile Data isn't affected by this at all. I get up to 3500 kBit, almost the maximum what the phone can handle. No complaint there.

The last three results were 2987 kBit, 2487 kBit and 2725 kBit

Edited April 24, 2011 by bhf

[Guest KACE_231]

The WiFi transfer rates are abysmal. With every Nightly the transfer rates get worse. It started somewhere around N35. Up to N39 the transfer rates were just cut in half and get up to 2800 kBit (at a DSL line with 6000 kBit). Now, with the most recent Nightlies N51 and N54, I only get rates in the mid triple digits up to 650 kBit. That's about a tenth of the DSL Line.

Has anyone made similar experiences?

Hi I'm on N54 with GEN1 kernel conversion.

Anyway when I first tried speedtest.net app I was getting ~650 Kbps, on my 15000 Kbps DSL line via WiFi. Then I went into settings and changed the animation settings to "maxiumum performance" and now I get ~3300 Kbps, so I guess that option may be a contributing factor?

Also what is the difference between Mbps and the advertised Mb/s

Edited April 24, 2011 by KACE_231

[Guest dadashi]

I'm new to CM7...

first problem,

Both my navigation software cause a forced close and GMaps bricks android and it reboots....Does Blade GPS work in CM?

Edited April 24, 2011 by dadashi

[Guest KasioPC]

I'm new to CM7...

first problem,

Both my navigation software cause a forced close and GMaps bricks android and it reboots....Does Blade GPS work in CM?

This has been discussed countless times. It even has it's own thread. Short answer: no.

[Guest dadashi]

This has been discussed countless times. It even has it's own thread. Short answer: no.

DAMN, I need GPS regularly....

Next Problem,

I can't get into recovery mode....I can run CM7 but when I choose to go into recovery either through power+volumedown or using reboot or rom manager the SF reboots but stays at the green android and doesn't go into recovery...

I have to remove battery to get it working again...