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

Root Building CM 10.1 (JB 4.22) from source for Motion

Ah. Crap.
I don't have enough storage to actually help :/
I would love to help by testing anything though!
Or if I can do anything to maybe make a patch for something I will.
 
Dm47021 said:
@ Candoopa, If you want, you can use a prebuilt libsurfaceflinger.so from the cm10 rom. that will likely make camera easier to get working, as we are currently using a surfaceflinger_client stub
Click to expand...


what exactly does that folder make, there is only one android.mk file in it and nothing else, it does not use any libraries. I do not think that it does anything to be honest with you
 
If you would like to buy me a beer, you can click on the PayPal button
Click to expand...
i bought you a beer but i drank it.
vollkommenauf.gif
 
johnnyl1111 said:
well i'm mid build on my first test run build or i would try to add that.
Click to expand...


so now would be a good time to explain clobber to you

the command make clobber cleans everything out of the out directory

and when you start the build again it has to make everything form source again, and takes a long time

depending on what you change in your tree, you may not have to make clobber, you can just go into the cm10.1/out/target/product/l0 folder and delete the two zip files and the system folder, and then you do your build again with

. build/envsetup.sh && brunch l0

and it will build the rom really quick for you because it does not have to compile all the source again

if you make major changes to the boardconfig file you may want to make clobber

does this make sense to you ?
 
so do i just re-enter this command to update what you added
Code: 
git clone [URL]https://github.com/hroark13/device_lge_l0.git[/URL] -b cm10.1_Osiris device/lge/l0
or is there an easier or different way to do that.
what ever you tell me will help me understand in the future how to add other dev's updates.
 
johnnyl1111 said:
so do i just re-enter this command to update what you added
Code: 
git clone [URL]https://github.com/hroark13/device_lge_l0.git[/URL] -b cm10.1_Osiris device/lge/l0
or is there an easier or different way to do that.
what ever you tell me will help me understand in the future how to add other dev's updates.
Click to expand...


well you could do it that way, but I would delete the old l0 folder first

or you can do this

cd device/lge/l0
git pull
cd ../../..
 
johnnyl1111 said:
so do i just re-enter this command to update what you added
Code: 
git clone [URL]https://github.com/hroark13/device_lge_l0.git[/URL] -b cm10.1_Osiris device/lge/l0
or is there an easier or different way to do that.
what ever you tell me will help me understand in the future how to add other dev's updates.
Click to expand...


so you were able to setup the build environment and do a build, that is very good

if you want to learn how to build and fix device trees the best teacher you are going to have is looking at peoples commits in github

some people have very nice commits, they change one thing at a time, and it is very easy to learn from them

I am a lazy slob, so my commits usually have a lot of changes in one commit and it is very hard to tell what file or change fixed and issue
 
i wouldn't want to delete the old l0 folder if i had made changes myself. thanks for the code to update without deleting.
 
johnnyl1111 said:
i wouldn't want to delete the old l0 folder if i had made changes myself. thanks for the code to update without deleting.
Click to expand...


if you made changes, git pull may overwrite them

what you can do is zip up the l0 folder and then delete the folder, but keep the zip

you do not want to just rename the folder or anything because that will cause conflicts, but if it is stored safely in a zip file it will not
 
i guess ill wait till i have a viable fix to learn how to build and fix device trees. don't want to get overwhelmed.
 
well my build will be exactly like yours i assume. i guess i could have at least changed the buildprop to reflect a name change in the build to my own. too late now. but it's just a test run build anyway that i won't post or anything anyway.
this build will at least compile source. so unless i make major changes like you said it will be fast from now on.
 
johnnyl1111 said:
well my build will be exactly like yours i assume. i guess i could have at least changed the buildprop to reflect a name change in the build to my own. too late now. but it's just a test run build anyway that i won't post or anything anyway.
Click to expand...

there will be some changes, mainly in the build prop

like the build date, your computer name, your name and stuff

after it builds, install it, then go to settings - about phone

you will see the difference
 
oh it does that automatically. sweet. so then i could just change the name of the zip to what ever i want ie: johnnylawless_cm10.1_blahblahblah.zip
 
You all make sure to thank candoopa and those who can show him some appreciation by hitting his donate link for taking time to explain out how to do this. I for one know from exp, its not so easy trying to teach and do dev work, along with life in general. ;)
 
You must log in or register to reply here.
Back
Top Bottom