Building CyanogenMod7

[Guest madnav]

getting stuck

username@machine:~/cm7$ repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

fatal: Not a git repository (or any of the parent directories): .git

.repo/manifests/: leaving master; does not track upstream

error: .repo/manifests/: manifests checkout 335302515599d4435f39ca2e2e81cbf9e42d7b48

fatal: manifest 'default.xml' not available

fatal: manifest default.xml not found

nevermind.

deleted .repo and redid the step..

Edited February 10, 2011 by madnav

[Guest Pierg75]

The blade source tree was updated today.

I checked it but I still get these 3 errors when running the "extract-files.sh" script:

remote object '/system/wifi/regcode' does not exist

remote object '/system/lib/libOmxAacDec.so' does not exist

remote object '/system/lib/libOmxMp3Dec.so' does not exist

I copied the libOmxAacDec.so from a JJ6 rom, I couldn't find the libOmxMp3Dec.so and the regcode is "reg_code" in the phone.

I'll try to make a new build right now.

[Guest metzench]

did you use unzip-files.sh or extracted-files.sh?

Both, same results there.

brunch did nothing for me, going to try building cm6 and froyo-stable branch

brunch works when called with the zte_blade-eng argument that lunch lets select you.

But remember, my main problem is not a failed build, the builds suceed, but there are files missing ( that will be build by the process itself like the CM stuff and so on ) that are included in TomGs build.#

Regards,

Christian

[Guest hecatae]

pulled todays update and building. must remember to format system to avoid boot loop

and my recovery directory is not missing

edit oh and building froyo fails, libaudiopolicy.so mismatch, must be something in the buildspec.mk causing the error

Edited February 10, 2011 by hecatae

[Guest metzench]

pulled todays update and building. must remember to format system to avoid boot loop

and my recovery directory is not missing

edit oh and building froyo fails, libaudiopolicy.so mismatch, must be something in the buildspec.mk causing the error

Do you have the missing apk in system/app now you mentioned before?

Regards,

Christian

[Guest hecatae]

Do you have the missing apk in system/app now you mentioned before?

Regards,

Christian

done a gitpull just now, 108 insertions, 42 deletions, just tried my ota eng rebooted to recovery, now trying cm nightly, and again reboot to recovery.

[Guest metzench]

After investigating the make files further, i think what we are building is pure asop without cyanogen additions. Think there needs to be an mk file for cyanogen_blade in vendor/cyanogen/products

Perhaps we need to message TomG

Regards,

Christian

[Guest hecatae]

After investigating the make files further, i think what we are building is pure asop without cyanogen additions. Think there needs to be an mk file for cyanogen_blade in vendor/cyanogen/products

Perhaps we need to message TomG

Regards,

Christian

TomG betas are cyanogen_blade, so we need a brunch mk file,, i think we should hack another mk file to suit the purpose. cyanogen_generic.mk looks a great place to start, we need a cyanogen_blade.mk in the vendor/cyanogen folder so we can brunch, lunch just gives an AOSP build

Edited February 11, 2011 by hecatae

[Guest metzench]

TomG betas are cyanogen_blade, so we need a brunch mk file,, i think we should hack another mk file to suit the purpose.

Yes, thats what i thought too. Did one, build is finished, will try to install it now.

Regards,

Christian

[Guest metzench]

Yes, thats what i thought too. Did one, build is finished, will try to install it now.

Regards,

Christian

s***, boot loops and then back to recovery. Tells me back to drawing board. :-(

Regards,

Christian

[Guest hecatae]

s***, boot loops and then back to recovery. Tells me back to drawing board. :-(

Regards,

Christian

we are going to have to compare them then, copy z71 and alter to suit blade is what I'm doing

[Guest metzench]

we are going to have to compare them then, copy z71 and alter to suit blade is what I'm doing

Does yours boot?

I used z71 too. Only changed PRODUCT_* tags for now and changed bootanimation to hdpi as i think the Blade is hdpi...

Edited February 11, 2011 by metzench

[Guest hecatae]

Does yours boot?

I used z71 too. Only changed PRODUCT_* tags for now and changed bootanimation to hdpi as i think the Blade is hdpi...

mine does not boot, might try this device tree https://github.com/HCDRJacob/device_zte_blade

HCDRJacob seems to be doing a lot of work

Edited February 11, 2011 by hecatae

[Guest metzench]

mine does not boot, might try this device tree https://github.com/HCDRJacob/device_zte_blade

HCDRJacob seems to be doing a lot of work

Do you report back when you get a working one, we don´t need to tryout the same tree both? ;-)

[Guest rjm2k]

mine does not boot, might try this device tree https://github.com/HCDRJacob/device_zte_blade

HCDRJacob seems to be doing a lot of work

does look that way, surpsied tom isn't pulling changes through to his though I guess that can be difficult. it's a shame we appear to have 2 people working to the same goal on different code but hopefully one of them will finish soon and with the apparent UK 2.2 coming soon CM6/7 should become even better for us!

[Guest hecatae]

Do you report back when you get a working one, we don´t need to tryout the same tree both? ;-)

got a new pc to build this weekend, so I wont be building android on my netbook, HCDRJacob states his kernel does not boot, so I'd give the tree a miss

[Guest hecatae]

cyanogen_blade.mk contains removed as Tom G has provided link

copy device/zte/blade/overlay to vendor/cyanogen/overlay/blade

Edited February 12, 2011 by hecatae

[Guest Tom G]

does look that way, surpsied tom isn't pulling changes through to his though I guess that can be difficult. it's a shame we appear to have 2 people working to the same goal on different code but hopefully one of them will finish soon and with the apparent UK 2.2 coming soon CM6/7 should become even better for us!

There is nothing to pull. Everything he is fixing is already fixed in my config.

To get the build to work, get the cyanogenmod source and clone my config from github.

Then apply these patches.

http://review.cyanogenmod.com/2947

http://review.cyanogenmod.com/2958

http://review.cyanogenmod.com/2946

http://review.cyanogenmod.com/2945

Edit. 2945 & 2946 should not be needed any more and 2958 has been updated.

Edited February 12, 2011 by Tom G

[Guest hecatae]

thank-you Tom G for sharing those files,

[Guest metzench]

Well thanks TomG, thanks for the patches. Applied them, build runs fine now. And runs really smooth for now. Will do some more investigation tomorrow, anything one might be helpful? Kernel Optimization, specific bugs not yet tracked down?

Regards,

Christian

[Guest Tom G]

Well thanks TomG, thanks for the patches. Applied them, build runs fine now. And runs really smooth for now. Will do some more investigation tomorrow, anything one might be helpful? Kernel Optimization, specific bugs not yet tracked down?

Regards,

Christian

Video overlays die with OMX enabled. That would be a good one to work on.

Or the video camera problem.

[Guest fonix232]

Video overlays die with OMX enabled. That would be a good one to work on.

This is because the OMX H.264, MP3 and AAC codecs are broken (and I suppose the others too). A complete rebuild of the OMX libraries would solve the problem.

Or the video camera problem.

This is because

a, the camera image buffer is called incorrectly (too high FPS request, or something like that, too frequent calls for the image)

b, the qualcomm driver calls the camera incorrectly

c, some missing bits in the camera app:

This happens when I open the camera app: http://pastebin.com/9gccCut0

And this when I change to video mode: http://pastebin.com/EqTp1sm3

And this, when I try to record something: http://pastebin.com/zizyA9ne

It is definitely missing a media descriptor XML!

02-12 12:12:27.287: WARN/MediaProfiles(127): could not find media config xml file

And, camera won't show preview because the camera usage is being stopped before the UI is drawn.

[Guest Tom G]

This is because the OMX H.264, MP3 and AAC codecs are broken (and I suppose the others too). A complete rebuild of the OMX libraries would solve the problem.

As far as I know they are proprietary.

The no video looks like it is actually from a problem in surfaceflinger. It appears to be falling back to a software codec which surfaceflinger is incorrectly say is not supported. If you modify surfaceflinger to take out the check then video works, but it is black and white (its meant to be with the software codec).

The real problem though is that it is falling back to the software codec. It should be using a hardware codec, the problem may be as you say that the codecs are simply broken however codecs from other similar platforms should work and all that I have tried fail. Jacob has video working in his build, but I'm not sure if that is fully working or if it is all in software (like when you delete bits out of my build).

As for the media profiles thing, I dont think the ZTE roms had one either.

[Guest fonix232]

As far as I know they are proprietary.

The no video looks like it is actually from a problem in surfaceflinger. It appears to be falling back to a software codec which surfaceflinger is incorrectly say is not supported. If you modify surfaceflinger to take out the check then video works, but it is black and white (its meant to be with the software codec).

The real problem though is that it is falling back to the software codec. It should be using a hardware codec, the problem may be as you say that the codecs are simply broken however codecs from other similar platforms should work and all that I have tried fail. Jacob has video working in his build, but I'm not sure if that is fully working or if it is all in software (like when you delete bits out of my build).

Do we have any general Qualcomm builds?

I've been looking through the Qualcomm vendor tree of AOSP, and only found reference to these files regarding to OMX:

system/etc/01_qcomm_omx.cfg

system/lib/libqcomm_omx.so

Also, here is the OMX (and stagefright) general AOSP source:

http://android.git.kernel.org/?p=platform/...81aec56;hb=HEAD

EDIT:

CodeAurora Qualcomm OpenSource OMX stuff:

https://www.codeaurora.org/gitweb/quic/la/?...o.git;a=summary

https://www.codeaurora.org/gitweb/quic/la/?...o.git;a=summary

https://www.codeaurora.org/gitweb/quic/la/?...e.git;a=summary

Qualcomm general hardware media tree:

https://www.codeaurora.org/gitweb/quic/la/?...edia.git;a=tree

It includes some general HW Stagefright stuff, omx audio and video, and such.

And also CAF Qualcomm proprietary files:

system/etc/pvasflocal.cfg

system/lib/libomx_wmadec_sharedlibrary.so

system/lib/libomx_wmvdec_sharedlibrary.so

system/lib/libpvasfcommon.so

system/lib/libpvasflocalpbreg.so

system/lib/libpvasflocalpb.so

I guess it has to be modified to work on the Blade, but as a beginning, it is more than nothing!

As for the media profiles thing, I dont think the ZTE roms had one either.

May not but do not forget those ZTE ROMs had modified Camera app :P

Edited February 12, 2011 by fonix232

[Guest eAlex79]

Ppl, is this the used kernel source: https://github.com/ZTE-BLADE/ZTE-BLADE-2.6.32.git ?