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

[Guest samjam]

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?

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

If I start DSP manager I get dreadful thumping distortion which won't go away or change regardless of any settings - I have to reboot my phone.

[Guest Simon O]

Guys, using Gen1 with KK converter, which converter you would recommend? With AHB or without AHB? I'm just going to flash 7.0.2 and double minded which one I should use.

None of them. Wait for somebody to update the converter with the very latest kernel. If you install 7.0.2 using the current KK converter then you'll have an older kernel with many of the recent fixed bugs present.

If anybody is installing 7.0.2 and coming from a nightly release then WIPE. The charging issue and GPS issues have been tested on several devices after a full wipe and they appear to have been resolved.

[Guest Android.Fan]

Updated from N54 to 7.0.2 and KK converter without AHB. Phone rebooted without any problem. Battery is low so I've put it on charging with my laptop. I had a charging reboot just the update i.e on N54. Lets see if this problem is still there or gone. BTW I just wiped cache and delvik cache. No factory reset.

[Guest sm4tik]

Guys, using Gen1 with KK converter, which converter you would recommend? With AHB or without AHB? I'm just going to flash 7.0.2 and double minded which one I should use.

If you have no particular reason for keeping you phone as a gen1, I highly suggest you use this method to convert your phone to gen2, as it is reversible if you ever need to convert back. Now that there is a stable release for gen2 which fixes (or atleast should!) gps and charging reboots, I see no reason why not to convert. The real reason why I suggest this, is that you then can actually start testing CM7 and report issues etc.

But if you still want to keep using the converter, you can just flash one and then if you want to give the other one a go, flash it "on top" of the previous. I think there haven't been any serious issues with ahb, atleast if you know your phone can handle it :)

edit: uh.. a bit late, but the first part still stands and please also see fibblesan's reply about the kernel. You'll be getting a reboot charging :)

Edited April 25, 2011 by sm4tik

[Guest hecatae]

Updated from N54 to 7.0.2 and KK converter without AHB. Phone rebooted without any problem. Battery is low so I've put it on charging with my laptop. I had a charging reboot just the update i.e on N54. Lets see if this problem is still there or gone. BTW I just wiped cache and delvik cache. No factory reset.

the converter has not been updated, sorry to be blunt but you are wasting your time.

may I point you to wbaw's gen1 to gen2 tpt method http://android.modaco.com/content/zte-blad...n2-tpt-upgrade/

completely safe, and reversible to gen1 if needed, also you can use cm7 without using a converter

[Guest Tsip4]

Updated from N54 to 7.0.2 and KK converter without AHB. Phone rebooted without any problem. Battery is low so I've put it on charging with my laptop. I had a charging reboot just the update i.e on N54. Lets see if this problem is still there or gone. BTW I just wiped cache and delvik cache. No factory reset.

The converter uses the old kernel, so no bugs fixed. Do not report errors because you create confusion.

[Guest Android.Fan]

None of them. Wait for somebody to update the converter with the very latest kernel. If you install 7.0.2 using the current KK converter then you'll have an older kernel with many of the recent fixed bugs present.

If anybody is installing 7.0.2 and coming from a nightly release then WIPE. The charging issue and GPS issues have been tested on several devices after a full wipe and they appear to have been resolved.

Sorry Flib I read your reply after the update. But I think we can flash the updated converter through clockwork any time it comes out. Can't we? I got your point we can't get kernel updates with the current converter.

[Guest Bonbergol]

Wich is the last stable Gen 1 nightly? isnt it n38?

[Guest Android.Fan]

If you have no particular reason for keeping you phone as a gen1, I highly suggest you use this method to convert your phone to gen2, as it is reversible if you ever need to convert back. Now that there is a stable release for gen2 which fixes (or atleast should!) gps and charging reboots, I see no reason why not to convert. The real reason why I suggest this, is that you then can actually start testing CM7 and report issues etc.

But if you still want to keep using the converter, you can just flash one and then if you want to give the other one a go, flash it "on top" of the previous. I think there haven't been any serious issues with ahb, atleast if you know your phone can handle it :)

edit: uh.. a bit late, but the first part still stands and please also see fibblesan's reply about the kernel. You'll be getting a reboot charging :)

Thanks for quick replies guys. I got your point. I actually got nothing by updating to 7.0.2 coz kernel changes (which are actually fixing the issues) would be gone after I flash converter.

I don't mind to upgrade to Gen2 but I'm concerned about partition sizes. As you can see CM7 size is growing. 136mb for system can run out in the future and I need to apply another TPT to change partitions. This is what I think I may wrong. Is it possible to make it 150mb? One more thing is it as much safe as flashing roms to play with partitions?

[Guest hecatae]

Thanks for quick replies guys. I got your point. I actually got nothing by updating to 7.0.2 coz kernel changes (which are actually fixing the issues) would be gone after I flash converter.

I don't mind to upgrade to Gen2 but I'm concerned about partition sizes. As you can see CM7 size is growing. 136mb for system can run out in the future and I need to apply another TPT to change partitions. This is what I think I may wrong. Is it possible to make it 150mb? One more thing is it as much safe as flashing roms to play with partitions?

HCDRJacob, one of the cm7 blade devs, uses a 136mb system partition. If cm7 gets any bigger he'll be the first to advise

[Guest Freekers]

Its recoverable. See previous posts :)

Yeah luckiliy it is !

None of them. Wait for somebody to update the converter with the very latest kernel. If you install 7.0.2 using the current KK converter then you'll have an older kernel with many of the recent fixed bugs present.

Thanks fibble !

[Guest dibbles]

Thanks for quick replies guys. I got your point. I actually got nothing by updating to 7.0.2 coz kernel changes (which are actually fixing the issues) would be gone after I flash converter.

I don't mind to upgrade to Gen2 but I'm concerned about partition sizes. As you can see CM7 size is growing. 136mb for system can run out in the future and I need to apply another TPT to change partitions. This is what I think I may wrong. Is it possible to make it 150mb? One more thing is it as much safe as flashing roms to play with partitions?

As I did not need to maximise the data partition I decided to go to GEN 2 with a 150mb System, 20mb cache and 270mb for data. Whether those are optimum or not I do have much more room for my apps within the data partition than I need at 270mb.

[Guest BladeSimon]

Wich is the last stable Gen 1 nightly? isnt it n38?

I'm running N39 and I'm pretty happy. It dies when I unplug the carger, but nothing more...

[Guest Freekers]

If you have no particular reason for keeping you phone as a gen1, I highly suggest you use this method to convert your phone to gen2, as it is reversible if you ever need to convert back. Now that there is a stable release for gen2 which fixes (or atleast should!) gps and charging reboots, I see no reason why not to convert. The real reason why I suggest this, is that you then can actually start testing CM7 and report issues etc.

I'm also still on Gen1 here. I heard in Gen2 the proximity sensor is broken ?

Also, what's exactly the difference between Gen1 and Gen2 ? Ugh, I've been out of the scene for too long (3 months to be precise..)

Edited April 25, 2011 by Freekers

[Guest lordofangels]

OSF Gen1 to Gen2 Converted. CM7.0.2:-

Proximity works, GPS works flawlessly and as AC Charger, does not reboot.

Fantastic build, Thanks to all the dev's Jacob, Tom and every other dev conected to CyanogenMod

[Guest hecatae]

I'm also still on Gen1 here. I heard in Gen2 the proximity sensor is broken ?

Also, what's exactly the difference between Gen1 and Gen2 ? Ugh, I've been out of the scene for too long (3 months to be precise..)

two different base addresses, so two different kernels

two different radio images amss.mbn

gen1 is a partition layout that seems to have been requested for the Orange San Francisco and subsequent official Eclair builds

gen2 is a partition layout that seems to have been requested for the Softbank 003Z and subsequent official Froyo builds.

as several countries now offer stock gen2 devices, the decision was made to make cm7 gen2 as it is very difficult for a gen2 blade to downgrade to gen1, but easy for a gen1 blade to upgrade to gen2 via the TPT method

Edited April 25, 2011 by hecatae

[Guest pellen]

Just done that! No wipe required.

GPS reboots now fixed.

Anyone having the issue of Facebook app crashing? (process com.facebook.katana) Had it since Nightly 41...

Facebook have been FCing since their last update. By reading the reviews on android market, its obvious that aloooot of ppl have that problem. Sucks that they haven't fixed it yet :)

I'm also still on Gen1 here. I heard in Gen2 the proximity sensor is broken ?

Also, what's exactly the difference between Gen1 and Gen2 ? Ugh, I've been out of the scene for too long (3 months to be precise..)

Proximity sensor works fine here. Running the latest stable released today.

[Guest Freekers]

two different base addresses, so two different kernels

two different radio images amss.mbn

gen1 is a partition layout that seems to have been requested for the Orange San Francisco and subsequent official Eclair builds

gen2 is a partition layout that seems to have been requested for the Softbank 003Z and subsequent official Froyo builds.

as several countries now offer stock gen2 devices, the decision was made to make cm7 gen2 as it is very difficult for a gen2 blade to downgrade to gen1, but easy for a gen1 blade to upgrade to gen2 via the TPT method

Proximity sensor works fine here. Running the latest stable released today.

Thanks guys !

Going to upgrade to GEN2 now. Hopefully all goes well !

[Guest CaptainSpectacular]

With GoSMS Pro (don't know if it's the problem), my back button Red light still On, it's a known bug ?

I'm on 7.0.2.

Thanks.

[Guest Freekers]

One more question:

When converting from GEN1 to GEN2, you will obviously lose all your data. Also, once on GEN2, you just can't simply upgrade your GEN1 firmware to GEN2, I understand that.

So, to keep your data, you will have to use Titanium Backup, right ?

But what function in Titanium Backup do you use to backup your data if you're going from GEN1 to GEN2 ? I assume 'Backup all user apps' ? Or do you 'Backup all user apps + system data' ?

I'm on CM 7.0.0 Stable GEN1.

Sorry for hijacking this thread !

Thanks !!

[Guest dibbles]

With GoSMS Pro (don't know if it's the problem), my back button Red light still On, it's a known bug ?

I'm on 7.0.2.

Thanks.

Fine for me :) I am still on GEN 2. I think you are on GEN 1..?

[Guest CaptainSpectacular]

Fine for me :) I am still on GEN 2. I think you are on GEN 1..?

Just converted with TPT method, so I'm on Gen2. :)

I think I have seen this problem before but can't remember where.

Edited April 25, 2011 by CaptainSpectacular

[Guest ropin]

has anyone got a working fm radio for this rom

[Guest stephen m]

Appears still to be issues with wi-fi fix (uninstalled Bladefix) using 7.0.2 on Gen1 with conversion. Anyone conformed it's resolved in Gen2 ?

[Guest hecatae]

Appears still to be issues with wi-fi fix (uninstalled Bladefix) using 7.0.2 on Gen1 with conversion. Anyone conformed it's resolved in Gen2 ?

fixed on Gen2, confirmed last night by several on irc