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

[Guest sej7278]

My Base Lutea (the german OEM ZTE Blade) is a Gen1 LCD, 5 MPX camera, roughly 14 months old, bought early january 2011. Yes, wifi works with the regular 2012-02-25 NIGHTLY. However, Tom's new kernel does also NOT work with the regular nightly. There I got only error, when trying to enable wifi. With your KANG, wifi tries to connect but fails, tries to connect and so on.

Ah, ok. I didn't wipe dalvik, only cache and formatted /system,. I'll give wipe dalvik a try. Nope, wipe dalvik doesn't make any difference. Even a full wipe was unsuccessful. I give up. ;).

At least the new system font looks nice. :)

if a full wipe of /data and dalvik doesn't work, then its not going to work i guess! i wonder if the lutea uses a different wifi chipset - or zte forgot about it in their lastest code drop!

i'll report it on gerrit if that's ok?

[Guest Benoe]

Tom's new kernel does also NOT work with the regular nightly.

Have you installed the separate uvkernel-signed.zip on top of the new feb27 build?

You shouldn't do that.

[Guest Master One]

if a full wipe of /data and dalvik doesn't work, then its not going to work i guess! i wonder if the lutea uses a different wifi chipset - or zte forgot about it in their lastest code drop! i'll report it on gerrit if that's ok?

sej7278, as mentioned, WIFI is working here with your latest KANG, and I have the European ZTE Blade P729B with 3.2MP camera GEN1-to-GEN2-converted, if that info is of any help.

[Guest sej7278]

Have you installed the separate uvkernel-signed.zip on top of the new feb27 build?

You shouldn't do that.

oh yes the uv-kernel isn't compatible with this build, the whole point of which is to test the new kernel!

although that would be old /boot and new /system, which is the reverse of what tom_g mentioned, but might have the same effect.

[Guest sej7278]

sej7278, as mentioned, WIFI is working here with your latest KANG, and I have the European ZTE Blade P729B with 3.2MP camera GEN1-to-GEN2-converted, if that info is of any help.

it looks like the problem is specific to the base lutea. i wonder if the gen1-to-gen2 tpt is needed or not with that - although then i guess it wouldn't even boot the nightly.

it seems all the european blade/osf's are ok, has anyone tried it with a chinese v880 ?

[Guest bhf]

Have you installed the separate uvkernel-signed.zip on top of the new feb27 build?

You shouldn't do that.

I didn't. I installed the kernel from sej's build on top of the regular feb25 nightly.

[Guest bhf]

if a full wipe of /data and dalvik doesn't work, then its not going to work i guess! i wonder if the lutea uses a different wifi chipset - or zte forgot about it in their lastest code drop!

i'll report it on gerrit if that's ok?

I had the same problem with burstlams latest cm7 kernel, if that's any help. And yes, your report on gerrit is highly appreciated. Thanks.

[Guest CaptainSpectacular]

Hey Sej.

I use your 26 or 24 Feb build.

Honnestly, there's any point to update from your very old n257 patch 2 to this news builds ?

I don't know if it's due to the rom or other things but my market miss some downloads sometimes, my gmail doesn't sync sometimes too. As all working fine on your old builds, maybe should I go back to old rom ?

Thanks. :)

[Guest sej7278]

I didn't. I installed the kernel from sej's build on top of the regular feb25 nightly.

did you? well that explains it then!

you have to use my complete rom, you can't mix a new kernel with an old nightly.

have you tried just installing my rom (including wiping dalvik)?

I had the same problem with burstlams latest cm7 kernel, if that's any help. And yes, your report on gerrit is highly appreciated. Thanks.

did you mix a new kernel with an old cm7 rom there too? you really can't do that.

Edited February 27, 2012 by sej7278

[Guest targetbsp]

you have to use my complete rom, you can't mix a new kernel with an old nightly.

I haven't been following this topic but I just thought I'd point out that if you look at the date you quoted, the nightly isn't old. They brought build bot out of retirement for a day. :)

[Guest sej7278]

I haven't been following this topic but I just thought I'd point out that if you look at the date you quoted, the nightly isn't old. They brought build bot out of retirement for a day. :)

yes but the point being that the wifi modules that my kernel is expecting are not in any rom but mine (they haven't been merged yet) and the new kernel cannot use the old modules, same goes for burstlam's kernel too i expect.

[Guest targetbsp]

New wifi modules? Damn I'm out of touch. Been following ICS the past few days lol. Sorry, I shall play catch up!

Oh are we talking about the new blade kernel source from ZTE or?

Edited February 27, 2012 by targetbsp

[Guest sej7278]

New wifi modules? Damn I'm out of touch. Been following ICS the past few days lol. Sorry, I shall play catch up!

Oh are we talking about the new blade kernel source from ZTE or?

yes, the new "4gb rom" source from zte: http://support.zte.com.cn/support//news/NewsDetail.aspx?newsId=1001722

i'm skipping ics until they get a leaked opengl2 its just not happening - although i thought i saw something about that lately?

Edited February 27, 2012 by sej7278

[Guest targetbsp]

The coldfusion CM9 version is fantastic! You should give it a go, far smoother than GB and actually fast to go with it this time. Though I have to admit I've not tried any of the other ICS versions recently for a point of reference!

Edited February 27, 2012 by targetbsp

[Guest Janil]

Do I recall correctly that newer CM7s require more space than earlier ones? I'm upgrading from n244 and I'm wondering if I need to TPT my phone again. How much space is needed again?

[Guest targetbsp]

It's been slowing increasing but I don't think it ever reached the point where anyone had to re-tpt from any previous tpt?

[Guest mgn.kir]

Lastest sej7278's build, Orange San Francisco White from UK bought on ebay.co.uk. Wifi and proximity sensor not work :angry:

[Guest Janil]

It's been slowing increasing but I don't think it ever reached the point where anyone had to re-tpt from any previous tpt?

Okay, my memory plays tricks on me then. Let me update and let you know if I had any problems. Thanks!

[Guest hankhandsome]

my GPS has been completely screwy the last few days. Restored a clockwork backup from a week or so ago because I can't remember what I flashed, but it's still borked so might have to completely re-flash something new .. hhmm ..

[Guest sej7278]

Lastest sej7278's build, Orange San Francisco White from UK bought on ebay.co.uk. Wifi and proximity sensor not work :angry:

did you try with the regular nightly? did you tpt it to gen2? you may have to run the proximity calibration in settings->device settings

[Guest sej7278]

It's been slowing increasing but I don't think it ever reached the point where anyone had to re-tpt from any previous tpt?

depends what the previous tpt was, i had a 130mb /system tpt to start with which was pushing it, then i tpt'd to 160mb which is fine for cm7 for sure - i doubt if latest nightlies are any bigger than n244, as the gapps haven't changed in a good few months

160mb will probably be ok for cm9 given that there are a lot of ICS gapps that don't work on the blade, so can be removed. i wouldn't bother with the 210mb+ /system

Edited February 27, 2012 by sej7278

[Guest targetbsp]

160mb will probably be ok for cm9 given that there are a lot of ICS gapps that don't work on the blade, so can be removed. i wouldn't bother with the 210mb+ /system

I've actually been discovering today that the mini gapps cause certain apps to show as incompatible in the market as you are missing libraries they need. It fits in 180, just, if you want access to all the market apps.

[Guest targetbsp]

A mirror of Sej's 27th Feb rom: http://www.mediafire.com/?ibr5q68ekz2q762

It + gapps (with latest market) weighs in at 135.8. So it should just fit in the older 138mb TPT's but it's getting damned close!

[Guest Hans Gruber]

<br />Lastest sej7278's build, Orange San Francisco White from UK bought on ebay.co.uk. Wifi and proximity sensor not work <img src='http://android.modaco.com/public/style_emoticons/default/mad.gif' class='bbc_emoticon' alt=':angry:' /><br />

I've found the new wifi drivers used by sej aren't working on my OLED OSF, but I haven't tried them with a full wipe so it could just be that.

[Guest targetbsp]

I actually had trouble upgrading a previous CM7 to Sej's new build. Some my icons went blue despite the theme engine being disabled. No big deal - I just enabled theme engine set them back green and disabled it again. But also, the superuser update which i'd told it to install from CWm appeared to have not applied (even though i watched it install) when I reached the rom. I set it to go again and superuser wrecked itself and FC'd in the rom.

I dropped back down to CWM, formatted system and installed the rom, gapps and superuser and it was all fine. super user was up to date, my icons were green. So might be worth trying if you;re having issues. It's a lot less effort than a data wipe!

Edited February 27, 2012 by targetbsp