Guest vache Posted September 28, 2010 Report Posted September 28, 2010 and you Vache should not mind about that. Ok :lol:
Guest Piter1225 Posted September 28, 2010 Report Posted September 28, 2010 OMG, all devs are dead!! The scene is completely dead except for the MIUI port (excellent port tough). We don't have a FINAL rom based on the latest froyo bin, we don't have psfreedom (I know, there are compiling issues, but wtf, only one person tried? No one is trying to fix this...? Lots of devices already have this!), last post of xian about cyanogen is almost a week ago, and what we have so far is a ROM that, for the majority of us is awesome, but UNUSABLE for DAILY USE. I appreciate all the hard work of the devs, but, ATM the scene is almost STOPPED and I can't figure out why. We don't have a fully functional eclair kernel, why the hell a dev doesn't ask help from external developers that already managed to get a FULLY working kernel for other (similar) devices? Android is the same for all devices, the way drives are managed is the same for EVERY device... I really appreciate what we have so far but I feel the scene is stopped. So maybe you will move your bottom and try to make one of this things you say about? Really, there are many other things that normal man needs to do, not only new software for his phone. Noone is here getting paid for what he does, we are just doing things for fun in our FREE time. Sometimes that is more, sometimes less time.
Guest Rajit Posted September 28, 2010 Report Posted September 28, 2010 Because the devs have a life. And you should consider getting one as well !!! OMG, all devs are dead!! The scene is completely dead except for the MIUI port (excellent port tough). We don't have a FINAL rom based on the latest froyo bin, we don't have psfreedom (I know, there are compiling issues, but wtf, only one person tried? No one is trying to fix this...? Lots of devices already have this!), last post of xian about cyanogen is almost a week ago, and what we have so far is a ROM that, for the majority of us is awesome, but UNUSABLE for DAILY USE. I appreciate all the hard work of the devs, but, ATM the scene is almost STOPPED and I can't figure out why. We don't have a fully functional eclair kernel, why the hell a dev doesn't ask help from external developers that already managed to get a FULLY working kernel for other (similar) devices? Android is the same for all devices, the way drives are managed is the same for EVERY device... I really appreciate what we have so far but I feel the scene is stopped. Guys, WAKE UP!
Guest lvcargnini Posted September 28, 2010 Report Posted September 28, 2010 I'm trying to set up dev machine - what's the prefered choice Linux or Windoze? Also is Eclipse all that good ? Any pointers or links will be greatly appreciated... Cheers Linux Eclipse android-sdk android-ndk than .... cyanogen main git tree clone than Xian git tree clone and that is it, I'm working with it, but not sure how to integrate the Xian tree with the cyanogen tree to build a rom, I have already everything if someone can give a hint on how to continue like Monsieur Vache I would appreciate that.
Guest CedricGatay Posted September 28, 2010 Report Posted September 28, 2010 Linux Eclipse android-sdk android-ndk than .... cyanogen main git tree clone than Xian git tree clone and that is it, I'm working with it, but not sure how to integrate the Xian tree with the cyanogen tree to build a rom, I have already everything if someone can give a hint on how to continue like Monsieur Vache I would appreciate that. Just follow the how to build provided on cyanogen wiki and / or aosp pages. I think you'll have problem with librpc.so go build it manually under msm7k/librpc.
Guest lvcargnini Posted September 28, 2010 Report Posted September 28, 2010 Just follow the how to build provided on cyanogen wiki and / or aosp pages. I think you'll have problem with librpc.so go build it manually under msm7k/librpc. do you know how to generate the .map file for vendor liquid ? Xian did it, but I want to review the file, as well I'll change the extract-files.sh to bring additional stuff including the working libs and the OpenGL/ES libs that came in last leak.
Guest koudelka Posted September 28, 2010 Report Posted September 28, 2010 do you know how to generate the .map file for vendor liquid ? Xian did it, but I want to review the file, as well I'll change the extract-files.sh to bring additional stuff including the working libs and the OpenGL/ES libs that came in last leak. You mean a prelink map? you don't need a special prelink map if you dont want to compile libaries that should be compatible with official acer rom. Cyanogen is not compatible with the prelink acer is using, we need some patches from codeaurora for that. (I have talked to cyanogen about it, he said he tried making 2G prelink map work before but failed and didn't bother much with it) short answer is, Xian github includes all the file you need to compile cyanogen. just add his files to your cyanogen clone and you can compile it same way as following any cyanogen guide.
Guest lvcargnini Posted September 28, 2010 Report Posted September 28, 2010 You mean a prelink map? you don't need a special prelink map if you dont want to compile libaries that should be compatible with official acer rom. Cyanogen is not compatible with the prelink acer is using, we need some patches from codeaurora for that. (I have talked to cyanogen about it, he said he tried making 2G prelink map work before but failed and didn't bother much with it) short answer is, Xian github includes all the file you need to compile cyanogen. just add his files to your cyanogen clone and you can compile it same way as following any cyanogen guide. ok, continuing so ....
Guest TheShak Posted September 28, 2010 Report Posted September 28, 2010 Linux Eclipse android-sdk android-ndk than .... cyanogen main git tree clone than Xian git tree clone and that is it, I'm working with it, but not sure how to integrate the Xian tree with the cyanogen tree to build a rom, I have already everything if someone can give a hint on how to continue like Monsieur Vache I would appreciate that. thanks Dude. I'll be doing this on fresh pc this weekend. :lol:
Guest snootched Posted September 28, 2010 Report Posted September 28, 2010 (edited) You mean a prelink map? you don't need a special prelink map if you dont want to compile libaries that should be compatible with official acer rom. Cyanogen is not compatible with the prelink acer is using, we need some patches from codeaurora for that. (I have talked to cyanogen about it, he said he tried making 2G prelink map work before but failed and didn't bother much with it) short answer is, Xian github includes all the file you need to compile cyanogen. just add his files to your cyanogen clone and you can compile it same way as following any cyanogen guide. I've been playing with this on and off over the past weeks - but Xian's git was very active so never got a proper build. Just wondering if you've gotten the latest commits to compile. I've fully sync'd cyanogen repo, placed Xian's vendor and device trees into that repo. Followed cyanogen build docs (ie lunch combo and selected cyanogen_liquid-eng, etc) and started with build.. it's always stopping with: make: *** No rule to make target `build/core/init.salsa.rc', needed by `out/target/product/liquid/root/init.salsa.rc'. Stop have you seen this as well? or have been able to compile the current without issue? Thanks. Edited September 28, 2010 by snootched
Guest xian1243 Posted September 28, 2010 Report Posted September 28, 2010 (edited) Just add an empty file named init.salsa.rc to /device/acer/liquid/root I forgot to upload it to my git. :lol: And yes, I have a lot of schoolwork to tend to (phhusson and piter do too, Malez works, Vache works, we all have lives, and we do this out of good heart!), it doesn't mean we're dead! Get a grip, and a life! Edited September 28, 2010 by xian1243
Guest Andrea1Liquid Posted September 28, 2010 Report Posted September 28, 2010 First of all, scuse me if I was unpolite. I know that devs have a life and I said multiple times that I sincerly appreciate all their hard work. The fact is that no one knows what there's behind the scenes and sometimes is frustrating. Btw, I have a life and I went out of my house today and while I was with my friends (one of them with a Desire) I realized that I was very unpolite. The reason because I was so rude is that I felt frustrated because of the fact to don't know anything of the scene, but I was definetely unpolite than what I normally be. Scuse me all...Yes, I know that devs have a life! Don't be so angry with me, I just felt that the scene stopped and needed to wake up a little the people. You know, take off the dust... Scuse me from the bottom of the heart, I was an a*s! * BTW: I tried to do a custom ROM on my own, but I didn't get a very beutiful result. :lol:
Guest snootched Posted September 28, 2010 Report Posted September 28, 2010 Just add an empty file named init.salsa.rc to /device/acer/liquid/root I forgot to upload it to my git. B) And yes, I have a lot of schoolwork to tend to (phhusson and piter do too, Malez works, Vache works, we all have lives, and we do this out of good heart!), it doesn't mean we're dead! Get a grip, and a life! LOL thanks Xian :lol: Thanks for all your work (and to any contributor of this community for that matter!) This is my first droid phone, and it's an absolute pleasure to play around with. There's some satisfaction in knowing you can build your phone from the source - and if you don't like it - change it! Cheers.
Guest Rajit Posted September 28, 2010 Report Posted September 28, 2010 Whats done is done. Lets move on now. :lol: @xian, with soo much goodies already coming up in 1.2, I just drool at the thought of what v2 might be!!! B)
Guest lvcargnini Posted September 28, 2010 Report Posted September 28, 2010 (edited) people from this set of libs which one I can leave out ? http://pastebin.com/edNR1qy2 Edited September 28, 2010 by lvcargnini
Guest Piter1225 Posted September 28, 2010 Report Posted September 28, 2010 BTW if you wanna know what's going on behind the scenes you can follow your fav devs on twitter, or visit irc chanel.
Guest lvcargnini Posted September 28, 2010 Report Posted September 28, 2010 final extract-files.sh http://pastebin.com/Bq1nbPd6 building now .....
Guest lvcargnini Posted September 28, 2010 Report Posted September 28, 2010 ok I had some problems http://pastebin.com/fhR4eBP5 specially this one: make: *** No rule to make target `build/core/init.salsa.rc', needed by `out/target/product/liquid/root/init.salsa.rc'. Stop. make: *** Waiting for unfinished jobs.... any suggestions ?
Guest snootched Posted September 28, 2010 Report Posted September 28, 2010 ok I had some problems http://pastebin.com/fhR4eBP5 specially this one: make: *** No rule to make target `build/core/init.salsa.rc', needed by `out/target/product/liquid/root/init.salsa.rc'. Stop. make: *** Waiting for unfinished jobs.... any suggestions ? I had the same issue today and am at the same point (see above posts..) Issue as far as I can tell comes when it's processing AndroidBoard.mk from the device tree. Xian was doing some work around there before - so maybe it's not all finished yet. I'm sure Xian will work on it, time willing. Cheers
Guest lvcargnini Posted September 28, 2010 Report Posted September 28, 2010 I had the same issue today and am at the same point (see above posts..) Issue as far as I can tell comes when it's processing AndroidBoard.mk from the device tree. Xian was doing some work around there before - so maybe it's not all finished yet. I'm sure Xian will work on it, time willing. Cheers hummmm :lol: Ok, because I made a workaround, but two steps after request a new one I did it again, than for the third I didn't had an answer, simply I copied from device/acer/liquid/root/ the init.alala.lalal to the directory (or simply make a touch) into build/core, after this it requested the build.prop ... Since I have one that unlocks the Market I put that one, than I stopped at the point where it requests default.prop So basically which are this .prop files ? can I use my build.prop as default.prop, also in extract file I noticed it will extract the material of device into vendor/ creating the acer directory, shouldn't it be inside of the cyanogen directory ? thanks
Guest snootched Posted September 28, 2010 Report Posted September 28, 2010 hummmm :lol: Ok, because I made a workaround, but two steps after request a new one I did it again, than for the third I didn't had an answer, simply I copied from device/acer/liquid/root/ the init.alala.lalal to the directory (or simply make a touch) into build/core, after this it requested the build.prop ... Since I have one that unlocks the Market I put that one, than I stopped at the point where it requests default.prop So basically which are this .prop files ? can I use my build.prop as default.prop, also in extract file I noticed it will extract the material of device into vendor/ creating the acer directory, shouldn't it be inside of the cyanogen directory ? thanks Ok looks like I'm actually building now.. high-level steps of what I did: copy Xian device tree into <cyanogen>/device tree rename original cyanogen vendor tree, and put Xian's into <cyanogen>/vendor/cyanogen copy from /device/acer/liquid/root to /build/core : default.prop, init.goldfish.rc, initlogo.rle, init.rc, init.salsa.rc, init.salsa.sh copy from /device/acer/liquid/root/sbin to /build/core/sbin : mountbind.sh, qmuxd.sh, rild.sh build as usual ( . build/envsetup, lunch combo, make -jN otapackage) It seems to be working so far.. my laptop CPU is cooking my legs... I'll post back in a bit and let you know how it builds. Cheers
Guest koudelka Posted September 28, 2010 Report Posted September 28, 2010 Ok looks like I'm actually building now.. high-level steps of what I did:copy Xian device tree into <cyanogen>/device tree rename original cyanogen vendor tree, and put Xian's into <cyanogen>/vendor/cyanogen copy from /device/acer/liquid/root to /build/core : default.prop, init.goldfish.rc, initlogo.rle, init.rc, init.salsa.rc, init.salsa.sh copy from /device/acer/liquid/root/sbin to /build/core/sbin : mountbind.sh, qmuxd.sh, rild.sh build as usual ( . build/envsetup, lunch combo, make -jN otapackage)It seems to be working so far.. my laptop CPU is cooking my legs... I'll post back in a bit and let you know how it builds. Cheers I have also done this kind of ugly fix (moving the needed files to build/core) but the I was not able to boot that image, I think there is something wrong with the build files atm, and I have not been able to find it. My theory is that somewhere global variables are not being cleaned or something, that causes the buildsystem believing it should find the ramdisk files in build/core, and I think it also causes the boot problem I am having after compiling. Please let me know if it works for you, if it does not post logcat and dmesg here =)
Guest snootched Posted September 28, 2010 Report Posted September 28, 2010 I have also done this kind of ugly fix (moving the needed files to build/core) but the I was not able to boot that image, I think there is something wrong with the build files atm, and I have not been able to find it. My theory is that somewhere global variables are not being cleaned or something, that causes the buildsystem believing it should find the ramdisk files in build/core, and I think it also causes the boot problem I am having after compiling. Please let me know if it works for you, if it does not post logcat and dmesg here =) Definitely ugly :lol: This is my first crack at using the cyanogen build system, so I'm still learning the lay of the land. I suppose I should be learning it by looking at the trees that are already supported - but what fun is it working with things that already work. Still building.. it's going to take a while B)
Guest L0cu7us Posted September 29, 2010 Report Posted September 29, 2010 I also find strange why with 2 or 3 Froyo leaks devs are still beating on the Eclair ROM when these Froyo leaks are of such high quality and stable. Time to move on and do some "Froyo Magic"! because there aren't acer sources ! so the possible changes are very limited to repacked rom only, no OC, no swap, no compcache ecc...
Guest lvcargnini Posted September 29, 2010 Report Posted September 29, 2010 (edited) because there aren't acer sources ! so the possible changes are very limited to repacked rom only, no OC, no swap, no compcache ecc... there are Acer sources ! in fact you only need they're .config file to applyt to a new kernel source, and add the modifications. Edited September 29, 2010 by lvcargnini
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now