• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM10 Development (moved to upp)

oh and as far as your query regarding submitting to koush, umm... nooo lol. we dont have any idea what we are doing obviously, all we really know is we fixed cwm somehow and we want cyanogen so if that takes figuring out how to be developers, so be it

to be quite honest i think you are getting a better handle on things than i am superr, i still cant even compile anything myself
 
there are 2 errors in the proprietary-files.txt. I have corrected them locally and will upload the whole thing in a little while :)
 
oh and as far as your query regarding submitting to koush, umm... nooo lol. we dont have any idea what we are doing obviously, all we really know is we fixed cwm somehow and we want cyanogen so if that takes figuring out how to be developers, so be it

to be quite honest i think you are getting a better handle on things than i am superr, i still cant even compile anything myself
kk, will look it over n do a few test builds on builder. and get koush to fork it and then I can build a official build. Everything working etc right?
 
just tried a test build myself, and got:

make: *** No rule to make target `vendor/zte/warp2/proprietary/lib/libcamera_client.so', needed by `/home/superr/android/out/target/product/warp2/system/lib/libcamera_client.so'. Stop.

edit: this is probably a problem with my edits. Not sure where to look though to fix it. I think I will just pack this up and let PlayfulGod do his thing :)
 
to be quite honest i think you are getting a better handle on things than i am superr, i still cant even compile anything myself

well that is a HUGE compliment, but I don't think so. You would've had this all finished by now if it weren't for your connection :)
 
just tried a test build myself, and got:

make: *** No rule to make target `vendor/zte/warp2/proprietary/lib/libcamera_client.so', needed by `/home/superr/android/out/target/product/warp2/system/lib/libcamera_client.so'. Stop.

edit: this is probably a problem with my edits. Not sure where to look though to fix it. I think I will just pack this up and let PlayfulGod do his thing :)
I'm building fine with the old vendor tree you had linked. ;)

Here is the newest warp2 device tree complete with the vendor tree (best guess on files to grab). Let me know if I can be of further assistance :)
will look thru it ;)
 
I'm building fine with the old vendor tree you had linked. ;)

will look thru it ;)

I am glad the old one allows you to build but I fear it incomplete. The new one is more complete, but apparently that comes with errors :( Thank you so much for all your help!!!!
 
brunch warp2...please don't judge me for I know not what I do ;)
lol, k thats what I use, to be more specific, I use:

Code:
. build/envsetup.sh && brunch warp2


And is this the error you're getting now?

Code:
make: *** No rule to make target `vendor/zte/warp2/proprietary/lib/libcamera_client.so', needed by `/media/playfulgod/Android1/CM10/out/target/product/warp2/system/lib/libcamera_client.so'.  Stop.
make: *** Waiting for unfinished jobs.

If so that means that file is missing. If you watch when you run the extract-files.sh you will see what files fail, as well as can see if its on the phone or in the dump.
 
damn, guess you guys told me huh.. lol but thats odd, i know the file is there, on my system dump at least... i have seen it with my own eyes
 
damn, guess you guys told me huh.. lol but thats odd, i know the file is there, on my system dump at least... i have seen it with my own eyes
think I see the problem...

yup!!! look at DEVICE in the extract-files. ;)

the vendor tree basically doesnt have a path other than proprietary but the vendor-blob.mk has full paths. ;)
 
wait... isnt that the very first lib file in our list??? i think you just didnt set up to pull the files properly when you ran it. did you have the phone in adb mode connected when you ran it so it could pull the stuff off of it?
 
what happened, what did we do now? lol

ah, ok well you guys have fun with that issue, i cant even see what your looking at so im taggin you back in superr
 
If so that means that file is missing. If you watch when you run the extract-files.sh you will see what files fail, as well as can see if its on the phone or in the dump.

there are no errors during the extract-files.sh script. I may not have the syntax correct for that file since it is not located in the /lib proper directory though.
 
GAWD, FRIKKIN IDIOT! lol nah i probably woulda done the same thing youre good, minor hiccup, we are well on our way to having something keep up the good work. ill just be here talking shit, quoting B movies, and providing little to no real help, you may proceed
 
damn...well that's extremely easy to fix at least :) Sorry guys

GAWD, FRIKKIN IDIOT! lol nah i probably woulda done the same thing youre good, minor hiccup, we are well on our way to having something keep up the good work. ill just be here talking shit, quoting B movies, and providing little to no real help, you may proceed
lol, yea just edit rerun, rezip vendor/zte up, and upload.. again ;)

I'll prolly push it to github too once it builds. ;)
 
zipping now, thought I would run a build real quick and I got this now:
Code:
Import includes file: /home/superr/android/out/target/product/warp2/obj/SHARED_LIBRARIES/libdivxdrmdecrypt_intermediates/import_includes
make: *** No rule to make target `/home/superr/android/out/target/product/warp2/obj/SHARED_LIBRARIES/libgenlock_intermediates/export_includes', needed by `/home/superr/android/out/target/product/warp2/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/import_includes'.  Stop.
 
Back
Top Bottom