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

[Guest robinhud2010]

interesting to hear that there will be no nightlies until cm9, i thought they were going to release 7.2 at least.

anyway, patches included are miui-like battery bar, softbuttons, my kernel based on the latest in github, the new 5mp camera libs, plus all the commits since n257, which is a grand total of about six since n257+2 :D

the kernel has lots of taos/synaptics changes, so backup your old install as this might do odd things to touchscreen/proximity again, i've not noticed any problems overnight though.

usual place

md5sum: 9100d68f52713d8ccf90feec494da377 update-cm-7.2.0-RC0-Blade-KANG-15dec-signed.zip

can someone mirror it to megaupload or something, as this is likely the be the last cm7 build we'll see, i don't want my server to be the only download location for blades lol!

Thanks again, sej.

I thought all hopes of ics on blade(or any armv6 phones for that matter) were dashed after steve kondiak's announcement that nexus one was minimum hardware supported. Guess that's goodbye for cyanogenmod for blade then. or do you know something i dont?

back to cm7 now. Battery issues were still present in n257+2 and bustlam's kang+patch... Is it just me?

[Guest 4pda]

lol, yeah there's not much worth looking at in cm7 right now, i only built my 15dec to make sure that the libsurfaceflinger revert had worked and that we could build the kernel from github still - as tom_g never uploaded the .config, so i built with config.gz i extracted from patch4.

interesting to hear that there will be no nightlies until cm9, i thought they were going to release 7.2 at least.

anyway, patches included are miui-like battery bar, softbuttons, my kernel based on the latest in github, the new 5mp camera libs, plus all the commits since n257, which is a grand total of about six since n257+2 :D

the kernel has lots of taos/synaptics changes, so backup your old install as this might do odd things to touchscreen/proximity again, i've not noticed any problems overnight though.

usual place

md5sum: 9100d68f52713d8ccf90feec494da377 update-cm-7.2.0-RC0-Blade-KANG-15dec-signed.zip

can someone mirror it to megaupload or something, as this is likely the be the last cm7 build we'll see, i don't want my server to be the only download location for blades lol!

Thanks! Can you add change like in burstlam's kang: Support 2 way PCM stream Call recording?

And i have two ideas.

In moldavan rom i like one thing. Its auto-play music in hands-free after hang-out incoming call. I think its good thing, and be great see it in cyanogenmod. And one little improvement: if i listen music and make outgoing call - after hangout music must be continue.

[Guest sej7278]

Thanks again, sej.

I thought all hopes of ics on blade(or any armv6 phones for that matter) were dashed after steve kondiak's announcement that nexus one was minimum hardware supported. Guess that's goodbye for cyanogenmod for blade then. or do you know something i dont?

back to cm7 now. Battery issues were still present in n257+2 and bustlam's kang+patch... Is it just me?

given that there's an AOSP port in progress and tom_g already has a partial CM9 working, i think we'll be ok for some form of ICS on the blade.

cyanogen just said no 256mb ram devices, he didn't say no arm6 devices.

as far as battery issues goes, god knows, its always been that some people get them and some don't, some say its down to LED notifications, others 3G. i don't have any issues but i don't use 3g or miss many calls....

[Guest Blues003]

sej7278, did you ever consider doing what burstlam did with his ROM? ("odexing", I think it was called). I am asking this because Burstlam's ROM is *considerably* smoother and faster than any other CM7 ROM I tried. Perhaps that was the cause of it?

Edited December 16, 2011 by Blues003

[Guest sej7278]

sej7278, did you ever consider doing what burstlam did with his ROM? ("odexing", I think it was called). I am asking this because Burstlam's ROM is *considerably* smoother and faster than any other CM7 ROM I tried. Perhaps that was the cause of it?

no as de-odexing should make things considerably slower - especially booting as the dalvik cache has to be rebuilt. its usually only used when you're modifying themes or apk's and don't want to rebuild them "properly".

perhaps the ics theme is less graphics-intense than the cyanogenmod theme, seems more like the opposite would be true though.

[Guest brickornot]

burstlam compiled something new, 15.12.2011 ?

http://translate.goo...DU8YfZolfj_T4Gw

[December 15] N280X-35:

http://115.com/file/cly6u25n

Edited December 17, 2011 by brickornot

[Guest yadayada]

Hi,

I'm trying to compile cyanogen, but in the middle of the make process I get the following error:

target thumb C: gps.blade <= hardware/gpsshim/gps.c

make: *** No rule to make target `out/target/product/blade/obj/lib/libloc.so', needed by `out/target/product/blade/obj/SHARED_LIBRARIES/gps.blade_intermediates/LINKED/gps.blade.so'.  Stop.

make: *** Waiting for unfinished jobs....

Did anybody had this error?

I followed the instructions in cyanogen wiki, plus some tips from targetbsp and sej7278 .

I'm using vmware with ubuntu 11.10 64bit.

The only thing out of the ordinary when configure the system was regarding:

For 64-bit only systems:

g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib

NOTE: gcc-4.3-multilib g++-4.3-multilib is no longer available for Ubuntu 11.04 64-bit, but should still build without issue.

I was unable to install lib32readline5-dev and the two 4.3-multilib refereed in the "note".

Thanks!

[Guest Blues003]

no as de-odexing should make things considerably slower - especially booting as the dalvik cache has to be rebuilt. its usually only used when you're modifying themes or apk's and don't want to rebuild them "properly".

perhaps the ics theme is less graphics-intense than the cyanogenmod theme, seems more like the opposite would be true though.

I said "odex", not "de-odexing". In any case, it's a pity. Burstlam's ROM really is noticeably faster and smoother than the previous CM7 official and KANG builds; odexing seems to be the reason why that happened.

[Guest targetbsp]

I was also unable to install those files in 11.10 - it doesn't seem to cause issue.

The file it's complaining about is one of the proprietary libs so I would guess this bit has gone wrong?: http://android.modaco.com/topic/335328-cyanogenmod-7-android-237-is-now-gen-2-only/page__st__10740__p__1838970#entry1838970

Check that you have that file (and many other files) in android/system/vendor/zte/blade/proprietary

IIRC you need to make the folders zte and zte/blade in the vendor folder otherwise the

cp -R proprietary *.mk ~/cyanogenmod/vendor/zte/blade/

fails.

Also you'd need to replace cyanogenmod in the above with android/system if your following the directory structure suggested by the compiling CM7 guide.

Sorry if any of this is blindingly obvious. As A Windows user, none of it is to me. :D

[Guest hedgepigdaniel]

Hi,

I'm trying to compile cyanogen, but in the middle of the make process I get the following error:

target thumb C: gps.blade <= hardware/gpsshim/gps.c

make: *** No rule to make target `out/target/product/blade/obj/lib/libloc.so', needed by `out/target/product/blade/obj/SHARED_LIBRARIES/gps.blade_intermediates/LINKED/gps.blade.so'.  Stop.

make: *** Waiting for unfinished jobs....

Did anybody had this error?

I followed the instructions in cyanogen wiki, plus some tips from targetbsp and sej7278 .

I'm using vmware with ubuntu 11.10 64bit.

The only thing out of the ordinary when configure the system was regarding:

I was unable to install lib32readline5-dev and the two 4.3-multilib refereed in the "note".

Thanks!

Did you copy the proprietary files? I couldn't install those packages either; it didn't cause me any problem.

[Guest yadayada]

I was also unable to install those files in 11.10 - it doesn't seem to cause issue.

The file it's complaining about is one of the proprietary libs so I would guess this bit has gone wrong?: http://android.modac...70#entry1838970

Check that you have that file (and many other files) in android/system/vendor/zte/blade/proprietary

IIRC you need to make the folders zte and zte/blade in the vendor folder otherwise the

cp -R proprietary *.mk ~/cyanogenmod/vendor/zte/blade/

fails.

Also you'd need to replace cyanogenmod in the above with android/system if your following the directory structure suggested by the compiling CM7 guide.

Sorry if any of this is blindingly obvious. As A Windows user, none of it is to me. :D

I thought I had copied the proprietary files... but i might I've missed the .mk ones, I used a graphic file browser for the copy.

Let's try again.

ps: if my old c programming teacher saw the amount of warnings while compilling... I think he would have an heart attack :P

Edited December 17, 2011 by yadayada

[Guest yadayada]

Did you copy the proprietary files? I couldn't install those packages either; it didn't cause me any problem.

It seems the problem was the missing .mk in the proprietary folder.

Package complete: /home/yadayada/android/system/out/target/product/blade/update-cm-7.2.0-RC0-Blade-KANG-signed.zip

3772450ab842c780aa5654ec9b29ee6f update-cm-7.2.0-RC0-Blade-KANG-signed.zip

Yey! :P

A couple of questions:

Every time I do a 'repo sync' it will download all the new merged commits right?

Everything in http://review.cyanog...atus:merged,n,z (gingerbread branch)

Do I need to do some sort of 'make clean' between builds?

Anyway if I would like to force a build from scratch, is there a special command for that? Or '. build/envsetup.sh && brunch blade' always builds from 0?

Once again, thanks.

[Guest Amphoras]

It seems the problem was the missing .mk in the proprietary folder.

Package complete: /home/yadayada/android/system/out/target/product/blade/update-cm-7.2.0-RC0-Blade-KANG-signed.zip

3772450ab842c780aa5654ec9b29ee6f update-cm-7.2.0-RC0-Blade-KANG-signed.zip

Yey! :P

A couple of questions:

Every time I do a 'repo sync' it will download all the new merged commits right?

Everything in http://review.cyanog...atus:merged,n,z (gingerbread branch)

Do I need to do some sort of 'make clean' between builds?

Anyway if I would like to force a build from scratch, is there a special command for that? Or '. build/envsetup.sh && brunch blade' always builds from 0?

Once again, thanks.

You don't need to make clean between builds, but if you want to build from scratch, then just use the make clean command before the . build...etc.

[Guest targetbsp]

I just do a repo sync and then the . build line each time (also update rom manager if there's been one). It only recompiles changed files I think from the speed difference. If you especially wanted to recompile it all (not sure why, it'd just increase the compile time) I believe emptying the out folder would do the trick. Having said 'I'm not sure why', I had to do that to get mine to start using the 7.2 name rather than 7.1

Edited December 17, 2011 by targetbsp

[Guest yadayada]

You don't need to make clean between builds, but if you want to build from scratch, then just use the make clean command before the . build...etc.

I just do a repo sync and then the . build line each time (also update rom manager if there's been one). It only recompiles changed files I think from the speed difference. If you especially wanted to recompile it all (not sure why, it'd just increase the compile time) I believe emptying the out folder would do the trick. Having said 'I'm not sure why', I had to do that to get mine to start using the 7.2 name rather than 7.1

Thanks. It's cleaning/compiling/sync fine.

[Guest zardari]

cyanogen just said no 256mb ram devices, he didn't say no arm6 devices.

I understand you correctly, that the CM9 will not work on devices with 256 MB RAM?

[Guest jurrasstoil]

burstlam compiled something new, 15.12.2011 ?

http://translate.goo...DU8YfZolfj_T4Gw

[December 15] N280X-35:

http://115.com/file/cly6u25n

is it good? I'm on N218 and feel like upgrading again some time soon.

[Guest brickornot]

is it good? I'm on N218 and feel like upgrading again some time soon.

i dont know because nobody replied.

I installed it and yes its good but there is only english language and chinese inside.....

[Guest fradleyp]

Can someone please point me in the direction of the newest quicket variation of the CM7 ROM

whether that be Sej or burl thanks

[Guest burstlam]

All locales included.

Revert Carrier label change for Chinese Community~ should fixed no service issue

fixed FM.app auto seeking and sensitivity (note : this is a diry hack and pls stay on default banding, )

ODEX VERSION

http://www.multiupload.com/DWFAP3B4O1

md5 :4d7c68696405da45ba05b6e3d501f3fe

NORMAL VERSION

http://www.multiupload.com/CN2K4NHBL1

md5: 42876499a602cc91e32f3148f884c4e0

Edited December 18, 2011 by burstlam

[Guest brickornot]

and this is still actual for odex version ?

only the odex version contain the usb host mode patch~

and if u want to mount usbdisk , add this line to system/build.prop

ro.additionalmounts=/mnt/usbdisk

then add the following line to system/etc/vold.fstab :

dev_mount usbdisk /mnt/usbdisk auto /devices/platform/msm_hsusb

extra usb power mod is needed for other devices ~ something like this on youtube :

ODEX VERSION -this version has usb host ?

http://www.multiupload.com/DWFAP3B4O1

md5 :4d7c68696405da45ba05b6e3d501f3fe

Edited December 18, 2011 by brickornot

[Guest fradleyp]

thank you, going to try now

[Guest ShahinTehShiz]

no as de-odexing should make things considerably slower - especially booting as the dalvik cache has to be rebuilt. its usually only used when you're modifying themes or apk's and don't want to rebuild them "properly".

perhaps the ics theme is less graphics-intense than the cyanogenmod theme, seems more like the opposite would be true though.

Wait so Odexed ROM's are better?

Thanks!

[Guest brickornot]

probably difference will be seen only at first boot when cache will be builded.

later difference probably will not be noticeable.

[Guest bhf]

NORMAL VERSION

http://www.multiupload.com/CN2K4NHBL1

md5: 42876499a602cc91e32f3148f884c4e0

Thanks burstlam for your ROM. I'm running the normal version. I noticed, that in calls the proximity sensor needs about three seconds to activate the display. I then calibrated the sensor again. The data is now again in the three digit area, low 418, hi 523. The former releases including sej's plus builds 257+and up to 15th dec build the low and hi threshold was about 6800 and 9500.

So, just in case recalibrate your prox sensor.