Guest MrVanes Posted February 28, 2010 Report Posted February 28, 2010 (edited) Hi, I have some background in programming and a profound interest in compiling from sources, so a logical result is I'd like to (be able to) compile AOSP for my Liquid one day. But since there's a little more to compiling Android than there is to compiling a linux Kernel e.g. I'd like to dedicate this topic to all tips and tricks to (eventually) compile 2.1 for our Liquids ourself. This is what I found so far: - The AOSP download and start page: http://source.android.com/download This contains good information about getting started with the code (GIT checkout) dependancies (for 32-bit Ubuntu) and compiling. As far as I understand it now, this will build you an emulator build of Android 2.1. - Then the next step is to build for a specific device: http://source.android.com/documentation/building-for-dream It involves extracting certain proprietary files from the original ROM, setting up an environment and running a tool called 'lunch' to select a certain vendor/harware profile. - I found one reference to a Liquid vendor tree here: http://wiki.github.com/loxK/android_vendor...for-acer-liquid but it's a work in progress and the intsruction result in a failing 'repo sync'. So... what other places are publically available to help compiling AOSP for the Liquid and another question I have is: what's next once the tree is built? What is the result of the build? flashable images, or a bare tree that needs to be packaged? If it's just not worth the hassle because compiling requires 'secret' or non-disclosed code and binaries from Acer, I'd like to hear that too, so I'd know where we stand at the moment. Edited February 28, 2010 by MrVanes
Guest behnaam Posted February 28, 2010 Report Posted February 28, 2010 Hi, I have some background in programming and a profound interest in compiling from sources, so a logical result is I'd like to (be able to) compile AOSP for my Liquid one day. But since there's a little more to compiling Android than there is to compiling a linux Kernel e.g. I'd like to dedicate this topic to all tips and tricks to (eventually) compile 2.1 for our Liquids ourself. This is what I found so far: - The AOSP download and start page: http://source.android.com/download This contains good information about getting started with the code (GIT checkout) dependancies (for 32-bit Ubuntu) and compiling. As far as I understand it now, this will build you an emulator build of Android 2.1. - Then the next step is to build for a specific device: http://source.android.com/documentation/building-for-dream It involves extracting certain proprietary files from the original ROM, setting up an environment and running a tool called 'lunch' to select a certain vendor/harware profile. - I found one reference to a Liquid vendor tree here: http://wiki.github.com/loxK/android_vendor...for-acer-liquid but it's a work in progress and the intsruction result in a failing 'repo sync'. So... what other places are publically available to help compiling AOSP for the Liquid and another question I have is: what's next once the tree is built? What is the result of the build? flashable images, or a bare tree that needs to be packaged? If it's just not worth the hassle because compiling requires 'secret' or non-disclosed code and binaries from Acer, I'd like to hear that too, so I'd know where we stand at the moment. The local manifest for the Liquid vendor Lox set up is old now that he moved over to cyanogen mod base. Now our first goal shouldnt be a fully working build, instead we need to get a AOSP build booted onto the liquid, then we can go on fixing hardware and bugs. What im doing at the moment: - I synced to cyanogens repo, due to the fact of a huge amount of bugfixes that isnt present in AOSP - Nexus and Liquid have very similar configs and also the same arch, therefore I used passion vendor and modified it with acer specific stuff. - So atm I've set up the basics for the vendor, I need to fill in whats missing for liquid specific changes What to do: - Find all properitary bits for acer liquid, drivers etc Will try to compile my first build of cyanogenmod for Liquid tonight, since I've done a the basic changes needed OBS! And a tip to everybody that want to compile, go for cyanogens source, alot better than AOSP and it has several other phone vendors that u can take inspiration from
Guest MrVanes Posted February 28, 2010 Report Posted February 28, 2010 What't the exact git location of the cyanogen mod base? What is the result of a succesful build and what to do with it? And will you make your Liquid modifications available?
Guest eldiau Posted February 28, 2010 Report Posted February 28, 2010 (edited) Hey MrVanes, I'm very happy to read this thread, I share the same linux background and interest in playing with the inner working of the android system. The structure of the system and the boot sequence are quite simple, almost plain linux without substitution of the initrd image which remains the root on the running system. Apart from the full system cross compiling is easy too (check this simple howto Compiling bash) Compiling the kernel is another story, the source from acer for donut lacks the "real" .config, hope we will get a proper source tree with eclair! Unfortunately I can't find specific information about the structure of img's for the liquid and I'm a bit afraid of trying the ones I built with the risk of bricking my phone. This page drops a bit of light: Unpack Re-Pack Boot Images on my liquid (Acer_Liquid_2.000.16_G1_EUU) the partitions structure is slightly different: # cat /proc/mtd dev: size erasesize name mtd0: 000a0000 00020000 "misc" mtd1: 00500000 00020000 "recovery" mtd2: 00500000 00020000 "boot" mtd3: 08000000 00020000 "system" mtd4: 0c0c0000 00020000 "userdata" mtd5: 05b60000 00020000 "cache" mtd6: 00040000 00020000 "dinfo" mtd7: 00060000 00020000 "setupdata" @behnaam Do you have any advice on ho to build this images? Do we need do digitally sign them to get the liquid boot from them and how? Links? Howtos? HELP!! :( It looks like mkbootimg does the trick... still missing the right base address for liquid... One more EDIT: digging more deeply the forum found the infos I was looking for in this interesting thread: mkbootimg thank you! Edited February 28, 2010 by eldiau
Guest behnaam Posted February 28, 2010 Report Posted February 28, 2010 @behnaam Do you have any advice on ho to build this images? Do we need do digitally sign them to get the liquid boot from them and how? Links? Howtos? HELP!! :( It looks like mkbootimg does the trick... still missing the right base address for liquid... One more EDIT: digging more deeply the forum found the infos I was looking for in this interesting thread: mkbootimg thank you! system.img is a yaffs2 image, pretty easy to just yaffs it lol :( boot.imgs are repacked with mkbootimg tool from android source, but for eclair it needed slight modifications which disc0 (thanks) did, so im able to repack the eclair boot.imgs.... PM him and he will send them I think :( @MrVanes If it compiles without errors and boots I will release the modifications I made, it would be against the community spirit not to do that :(
Guest g4rb4g3 Posted March 2, 2010 Report Posted March 2, 2010 ... If it compiles without errors and boots I will release the modifications I made, it would be against the community spirit not to do that :( Any news? :(
Guest behnaam Posted March 2, 2010 Report Posted March 2, 2010 Any news? :( Im working this whole week, so im pretty busy, but I'll try to give it a go during the weekend :(
Guest Nova2.1 Posted March 6, 2010 Report Posted March 6, 2010 this seems a very intregeing idea, cannogen on liquid
Guest g4rb4g3 Posted March 13, 2010 Report Posted March 13, 2010 Im working this whole week, so im pretty busy, but I'll try to give it a go during the weekend :mellow: I don't wan't do annoy you, I'm just curious if there is any progress? <_<
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now