Hi,
As a noob i came across a word related to android "compiling". What does compiling exactly mean?
Not very experienced with android but compiling usually means converting codes to executables
Sent from my LT30p using xda app-developers app
Zip->unzip
Compile->install
sony xperia ray
ics 4.0.4 rooted
stock rom
126 posts on XDA and you still don't know how to use Google or a dictionary?
snapper.fishes said:
126 posts on XDA and you still don't know how to use Google or a dictionary?
Click to expand...
Click to collapse
i do but i am not sure does compling mean making a rom?
Nono...see in terms of android.
Decompiling= breaking some files into many parts
Compiling=Joining the broken parts to get back the original file back.
Its usually associated with Decompiling and Compiling apk files to mod them or stuffs.
Dont worry we all were "noobs" once
TarunDham said:
i do but i am not sure does compling mean making a rom?
Click to expand...
Click to collapse
It's not too different from the usual programming definition of compiling. When you write a programme, you write it in a higher language that reads almost like English (unless if you are a nut case/genius who likes coding in assembly). However, for a computer (in this case your phone) to run it you have to translate the programme into machine readable language first. This translation process is called compiling.
Sent from my Nexus 4 using Tapatalk 2
---------- Post added at 01:11 AM ---------- Previous post was at 12:59 AM ----------
Rittik said:
Nono...see in terms of android.
Decompiling= breaking some files into many parts
Compiling=Joining the broken parts to get back the original file back.
Its usually associated with Decompiling and Compiling apk files to mod them or stuffs.
Dont worry we all were "noobs" once
Click to expand...
Click to collapse
I am afraid that is not the correct definition of compiling. The apk file is just a zip file of media files and code. When you break apart an apk file all that you are doing is just unzipping. The codes are still inaccessible. To be able to read them humanly you need to decompile the codes, which is usually impossible. That is why people need to post source codes.
Compiling takes quite a bit of computing power and can take hours if your code is long. Packaging and signing an apk? Not si much.
Sent from my Nexus 4 using Tapatalk 2
phew........... dat was a lot... hahaha i read a tutorial here that says "compile a gingerbread rom" so will that tut make me a gb rom??
It should, just make sure it's meant for your phone
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
It should, just make sure it's meant for your phone
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
here's the link
http://forum.xda-developers.com/showthread.php?t=1598713
so what do u think?
That guide was for porting roms made for other devices using roms that already exist for your device. For example, someone has already made a cm7 rom for your device, but you want a miui rom. Since miui is based on cm7, you can use the guide to create a miui rom for your device. However, if nobody has made a cm7 rom for your device, you cannot use that guide to port miui rom.
If you read the guide carefully, it's just a while load of copy and paste work, hence not compiling. The guide teaches you to take advantage of existing work done by other people instead of starting from the scratch, but it can't teach you to build a rom from scratch.
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
That guide was for porting roms made for other devices using roms that already exist for your device. For example, someone has already made a cm7 rom for your device, but you want a miui rom. Since miui is based on cm7, you can use the guide to create a miui rom for your device. However, if nobody has made a cm7 rom for your device, you cannot use that guide to port miui rom.
If you read the guide carefully, it's just a while load of copy and paste work, hence not compiling. The guide teaches you to take advantage of existing work done by other people instead of starting from the scratch, but it can't teach you to build a rom from scratch.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
i totally agree with you but in the start of the post the guy says "Android Source | Compile GB | Compile ICS | Compile JB ~ Thanks dastin1015 |- Building/Compiling - Durations" what does that mean? will the link to the tut help me make a gingerbread for my ics based device??
and last advice will porting any roms to my device has any threat to it like bricking???
I took a look at those links. The first link is simply what it says - the basic source code for Android. The other compile links contain instructions on how to compile the source code into roms. They do not teach you how to write the source code for different devices, which is the most difficult part of porting a rom. Anyone can learn to compile a rom from pre written codes. It's the writing part that matters. You need to find the drivers and other proprietary codes for your device.
The guides can help you get started on making a gingerbread rom, but it won't fix the hundreds of bugs you are sure to encounter.
As for bricking, there's always going to a chance that flashing a rom might brick your device.
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
I took a look at those links. The first link is simply what it says - the basic source code for Android. The other compile links contain instructions on how to compile the source code into roms. They do not teach you how to write the source code for different devices, which is the most difficult part of porting a rom. Anyone can learn to compile a rom from pre written codes. It's the writing part that matters. You need to find the drivers and other proprietary codes for your device.
The guides can help you get started on making a gingerbread rom, but it won't fix the hundreds of bugs you are sure to encounter.
As for bricking, there's always going to a chance that flashing a rom might brick your device.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
thaknz a lot for ur help
To sum up in basic words, compiling is turning a code from a high language into machine code so the computer can read it.
Also , if you din't know what is compiling i don't think you should be making roms
Related
hey everyone, I've been with android since release on the g1 and have followed it since. but now I'm tired of being just a user and want to learn how to develope roms. I would rather have some one teach me first hand, but links to some places that helped you would be great too. So again, Im looking for a dev who would want to teach me, if some money is wanted, that's fine. thanks for reading. reply here and/or PM me. I am very serious about learning, I dont just want little tips/tricks or pointers.
Edit: I have a bit of skill in C++ and Java, but nothing too significant. I lost interest in writing programs, same with apps, no interest, everything has been done over and over again.
I have created a site specifically just for this. I have a link in the signature but feel free to just click here @green rom project
stoute said:
I have created a site specifically just for this. I have a link in the signature but feel free to just click here @green rom project
Click to expand...
Click to collapse
Thanks alot.
thank you too
I didn't find anything there that isn't here on xda.
JDV28 said:
I didn't find anything there that isn't here on xda.
Click to expand...
Click to collapse
Maybe, but for new users in building roms, it's easy if it is gathered in one place, instead of searching all over xda that sometimes you can get yourself lost
What ARE you looking for?
Sent from my DROID2 using Tapatalk
jbirdvegas said:
What ARE you looking for?
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
Some sort of a guide to developing roms. even porting. not an "all in one" guide. thats unrealistic and would most likely suck, seeing as its such a broad subject.
that site, is... i dont even know. not to insult you, but i found it to be useless. the single guide you have on there is for setting up the htc kitchen, which i figured out in 5 minutes on my own. I would suggest making a "Guides" section of that site, so it isnt JUST forums, and adding, well, GUIDES. you pointed me there to help me, but there was nothing on the forums even close to helping me.
What os are you running? Have you succesfully compiled the source yet either aosp or cm?
CyanogenMod's github is a great place to learn repo the source. Read the commits @ github.com/cyanogenmod all commits are commented to make reading changes easier.
Aosp is also on [email protected] github.com/android building aosp can be more tricky.
Cm is aosp with many custom packages included to see what is and isn't aosp [email protected] github.com/CyanogenMod/android
default.xml contains references to what packages are cyanogen and what is aosp
Either way you need to start by getting very familiar with
github.com/CyanogenMod/android_vendor_cyanogenmod
Look in the products folder at the .mk files
and how they are invoked by core/Makefile in
github.com/CyanogenMod/android_build
Also pay attention to build/envsetup.sh
Sent from my DROID2 using Tapatalk
How noob at developing are you?
Sent from my DROID2 using Tapatalk
jbirdvegas said:
How noob at developing are you?
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
your last post was quite helpful. Barely anything at all.
best bet start by getting the source to compile... sounds simple but can be tricky
most importantly get to know ~/android/system/build
you can't produce a custom rom without understanding when and how everything is compiled
JDV28 said:
hey everyone, I've been with android since release on the g1 and have followed it since. but now I'm tired of being just a user and want to learn how to develope roms. I would rather have some one teach me first hand, but links to some places that helped you would be great too. So again, Im looking for a dev who would want to teach me, if some money is wanted, that's fine. thanks for reading. reply here and/or PM me. I am very serious about learning, I dont just want little tips/tricks or pointers.
Edit: I have a bit of skill in C++ and Java, but nothing too significant. I lost interest in writing programs, same with apps, no interest, everything has been done over and over again.
Click to expand...
Click to collapse
Android Kitchen will be your best bet. Very easy to follow. Read the whole post at least twice and you will be good to go. Follow all the links.
This is what i used from the ground up and i have my own rom on my HTC EVO 4G.
http://forum.xda-developers.com/showthread.php?t=633246
http://theunlockr.com/2010/03/26/ho...om-for-android-part-1-setting-up-the-kitchen/
http://theunlockr.com/2010/04/15/ho...m-for-android-part-2-creating-your-first-rom/
Credit goes to dsixda. he created android kitchen. If you like this, please donate to him.
"Dont forget to hit the thanks button if i helped you"
I'm new to the Dev world myself... I've done a lot of reading and research and I've gotten to the point of building and modding Roms to contribute to the community here. I've only done rom's for the Eris, which isn't as complex as some of the other devices, but I'm willing to share my knowledge if you need it.
The basics you will need:
1. Linux (I've tried doing this in windows, not worth the hassle!), either ubuntu or linux mint work well (Mint is a windows "like" os, so it might be easier to start with that).
2. Android SDK Kit (You can google it)
3. APK Manager (If you need to decompile APK's to make changes, this tool makes things a lot easier!)
4. Android Kitchen (A must if you are porting and to keep your Rom's cleaned up!)
5. A working understanding of XML and some java code is extremely helpful!
6. Time and Commitment! Devving, by any standard, is a time consuming process! You can easily make a Rom, but keeping the masses happy requires updates to nightly sources and time to rebuild what you've started!
I've spent so much time updating, compiling, modding and theming that my family voices plenty of complaints! But, the reward of building something that works and seeing others benefit from your creation is well worth the effort! Balancing your time, if you have a family to consider, is key to succeeding with this!
If you'd like more help, send me a PM! I'll work with you as much as I can!
I setup the kitchen, as i previously said, but didnt find any use for it except maybe adding minor features to a completely stock rom. i have linux set up with the SDK. i just dont know where to go from there...even compiling from source
Read everything here
http://wiki.cyanogenmod.com/index.php?title=Building_from_source
Sent from my DROID2 using Tapatalk
JDV28 said:
I setup the kitchen, as i previously said, but didnt find any use for it except maybe adding minor features to a completely stock rom. i have linux set up with the SDK. i just dont know where to go from there...even compiling from source
Click to expand...
Click to collapse
Sent you a PM back, bro.
Having Linux, SDK and the Kitchen setup gets you about 75% of the way there!
The basic steps to compiling from source run through the Terminal in Linux. You will need to pull in the CM repository (the link jbirdvegas posted will give the instructions to do that). Once the repository is setup, you will need to load the proprietary files for the device you're building for in order to sync the correct source. (repo sync -j16 will sync the source and build your folders for compiling). You will need to plug in your phone through USB and extract the proprietaries through ADB. Example, my build location in Linux is "android/system" in that folder there will be a device folder with folders for each device brand and build. My eris is listed in CM as desirec, so my drive folder location is "android/system/devices/htc/desirec". In order to pull my proprietary files, I would have to do the following:
1. In terminal; "cd android/system/devices/htc/desirec" (This puts me in the correct build folder)
2. su (puts terminal in root) - type in password
3. "./adb kill-server" (shuts down adb)
4. "./adb start-server" (starts adb)
5. "exit" (puts you back in standard terminal)
6. "./adb devices" (verify your device shows - if you get ????????, adb did not start right)
7. "./extract-files.sh" (this will extract the proprietary files from your device and place them in the device folder for building)
8. "cd"
9. "cd android/system" (puts you back in the CM build folder)
Once that's done, all you basically need to do after that is:
"source build/envsetup.sh" (Setup source build)
"lunch" (this will give you a list of builds - pick your device)
"make -j# bacon" (# is the number of processors your phone has +1)
The Repo Sync and Make commands will take time, but once you've finished the Make cycle, your Rom (if there were no errors) will be compiled, signed and ready to flash on your device. From there, you can use the kitchen to add "tweaks" to your rom (CM sources are usually pre-setup, but you can still add things like "data/app" access to your Rom).
Hopefully this takes you to the next step. PM me if you run into problems, I'll help you through it.
If you get abd shows your device as ??????????
Google 51-android.rules on how to setup udev
Sent from my DROID2 using Tapatalk
jbirdvegas said:
Read everything here
http://wiki.cyanogenmod.com/index.php?title=Building_from_source
Sent from my DROID2 using Tapatalk
Click to expand...
Click to collapse
about 50% of those pages are empty, does it matter what phone i click on for now? nothing shows up for Glacier
JDV28 said:
about 50% of those pages are empty, does it matter what phone i click on for now? nothing shows up for Glacier
Click to expand...
Click to collapse
jbirdvegas has it right on the adb correction if your device isn't found. I'll look for setting up the rules and post the link a little later.
Glacier doesn't have instructions yet, but there are CM builds for it. If you follow the evo instructions that will get you setup. Just replace supersonic with glacier to get your device established. There wasn't one for the Eris, either, and the EVO instructions are what I used.
Also, if you're building for GB and you're on a 32-bit system, it will tell you you cannot build it. There is a bypass; I'm using a 32-bit system and just removed the "end" statement in the make file. My builds work just fine, so bypassing the environment won't mess up your builds...
Below are links to a ICL23D Ice Cream Sandwich development build for the Galaxy Nexus!
Originally posted at:
http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Some points to note about the files...
All 3 files are completely stock and unedited
This build is a dev build, not a release build
This build is from a test Galaxy Nexus
This build is not odexed!
I know a lot of people are hacking up ports for other devices, so hopefully the non-odexed nature of this release together with the fact it includes the boot and recovery images will help make that happen.
All I ask is that you don't mirror the files elsewhere, that you link back to this topic rather than deeplinking the files and that if you use them you credit the source. So here they are...
Galaxy Nexus ICL23D boot image - http://www.filesonic.com/file/2985317613 - MD5: 8ad48c176eb12b33e436f38a8d9711f8
Galaxy Nexus ICL23D recovery image - http://www.filesonic.se/file/2985400373 - MD5: c02fe19e8b0d162e225597aab26704cb
Galaxy Nexus ICL23D system image (tar.gz) - http://www.filesonic.se/file/2985366173 - MD5: 7a47451ace5689b0fefbec64a7b911a0
(NOTE I WILL NOT CREATE ANY MULTIUPLOAD MIRROR OF THIS FILE!)
DUE TO I WANT YOU TO SUPPORT THIS GUY!
Enjoy!
Damn, was literally coming here to post this, DAMN...
but how hard would it be to port it over to our phone?
Jameslepable said:
Damn, was literally coming here to post this, DAMN...
but how hard would it be to port it over to our phone?
Click to expand...
Click to collapse
you can give it a try
It's same situation with SDK,armv7-built libs. Need to wait for sources
ciaox said:
It's same situation with SDK,armv7-built libs. Need to wait for sources
Click to expand...
Click to collapse
this was meant to have here as people are "collector's" and expect stuffs like this, look at zte blade they may have this also
SWEATTAIMI said:
you can give it a try
Click to expand...
Click to collapse
Tbh i wouldn't even know where to start.
Sent from my LG-P500 using Tapatalk
Jameslepable said:
Tbh i wouldn't even know where to start.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
to start is to make it to boot, using the changes in init.rc (however this is not nessesary as our boot.img already seems to have these, but needs to be edited a bit if i aint wrong,
then create boot.img
go for libs, try edit em to make it work for our armv6, boot and it should be starting
however editing libs takes good time,
i still wonder how Honeycomb were ported and not ics
SWEATTAIMI said:
to start is to make it to boot, using the changes in init.rc (however this is not nessesary as our boot.img already seems to have these, but needs to be edited a bit if i aint wrong,
then create boot.img
go for libs, try edit em to make it work for our armv6, boot and it should be starting
however editing libs takes good time,
i still wonder how Honeycomb were ported and not ics
Click to expand...
Click to collapse
Could ask they guy (forget his name) that got honeycomb running and see how its done? That would be a good start.
Sent from my LG-P500 using Tapatalk
I dont get the reason by posting a new thread?? Devs are not doing anything, so why bother to post? Even though, ciaox is planning it but he said "wait for the source"...
Sent from my Nexus One using Tapatalk
Jameslepable said:
Could ask they guy (forget his name) that got honeycomb running and see how its done? That would be a good start.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
ah you mean だ(da)っ(SS)ち(chi)ん (Dastin) but that's not exactly in hiragana
so litterarly i wrote dasschin (trust me i know i read japanese)
anyhow he maybe want this (Y)
I've tried porting several roms to my devices and every time I try to flash I always get status 0 or some type of error! I can't logcat from recovery because some things do not work completely with clockworkmod I have. I even manually tried porting the same method that android kitchen does and still run into the same problem. I have no idea what I should try next? This is really making me made. I get no help at all after searching and searching every where!
android kitchen
http://forum.xda-developers.com/showthread.php?t=633246
all in one guide
http://forum.xda-developers.com/showthread.php?t=1273718
And some other methods and still no luck!!
You are right. There is no guide. It's trial and error. Logcat helps and if you know what certain files do that helps too.
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
Thats great if building from source
but i think he is talking about porting roms that are not AOSP.
The problem with a porting tutorial is that all devices and roms are a bit different so there will never will be a tutorial to get this done 100%. They are great guides to give you a start but it can take a lot more to get things ported.
if the device architecture is similar
Ex... Evo 4g to Incredible
than porting is fairly easy
being able to logcat is very necessary when porting roms
getting that working is your first step.
I always gave up on porting just because i dont have the patients to do it.
Exactly. I've ported several roms from the E3D and Sensation to the Rezound, and they are easy because the processor is the same. All you really need to get it booting is the kernel in most cases.
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
Not that simple if you have to make a device tree from scratch like I'm doing
I've a question!!
I have an HTC Explorer (based on Qualcomm MSM7227) and I'd like to build a rom (AOSP or Cyano)...
I've downloaded Kernel Source Code but after hours of researches I haven't found a guide for merge a rom with a kernel..
can you help me?
thank you!
Can we port a rom from HTC desire to Motorola defy....is it easy??
HIT THANKS IF IVE HELPED
extremists said:
Can we port a rom from HTC desire to Motorola defy....is it easy??
HIT THANKS IF IVE HELPED
Click to expand...
Click to collapse
That's about as hard as it gets.
Unless building from source its not as difficult.
Sent from my PG86100 using Tapatalk
wes342 said:
That's about as hard as it gets.
Unless building from source its not as difficult.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Do u know how to port??
HIT THANKS IF IVE HELPED
The thing is there's also no real guide on how to make your own public repo for devices who don't have one .
E.g. Galaxy R
Herpderp Defy.
So I found out how to build from cm7 sources and it is a no go... I do not know how in the world you guys can port any roms. How do you get your files up on git hub any way? There is more to it then just compiling from cm sources..
Here's a slightly outdated one
EmoBoiix3 said:
The thing is there's also no real guide on how to make your own public repo for devices who don't have one .
E.g. Galaxy R
Herpderp Defy.
Click to expand...
Click to collapse
Just so its clear... this (slightly outdated) guide would be (the best I've found) for building a device tree (that you may elect to throw up on github) that can be used to build AOSP.. the same device tree probably could build CyanogenMod or MIUI fairly easily (minimal editing) but you are correct... no exact guide bc its not an exact science (lots of different devices out there with lots of different device configurations; even kernels different some are ti omap, some are qualcomm msm, etc.). Basically you build a tree to define your hardware.. AOSP, CM or MIUI will build themselves based on this definition (device) tree.
http://www.kandroid.org/online-pdk/guide/build_new_device.html
Now after you follow this guide, google the various build errors you get (one at a time) and perfect your tree until you get basic bring up... then perfect it some more until you get all your modules working (will take some aosp kernel cooking as well)... then perfect it some more... in a few months you should have something pretty decent (and learn tree building a bit more; we all learn by doing ) Best advice I have for you; going through the same thing myself.
Also wouldn't be a bad idea to download Hardware Info apk (Sleek Apps) and email yourself the info it spits out. That way you at least have a list of some of the hardware you are trying to define.
Rob
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
How exactly do you do this? How do you build it completely specifically for your device?
Sorry, I'm a complete noob on building from scratch and Linux. Could anyone shed some some light?
Thanks you guys
Hallo, I am a flash addict, yes I admit
the problem is that every rom I "test" have pros and cons,
so I'm wandering, how can I make one of mine?
not from sources (just yet) but lets say take an original aosp or samsung
and add different apks and patches
I tried to delete / replace apks like email, callendar etc in a running rom
and most of the times I get FC and non working apps.
Any help of what to read and how to start would be much appreciated!
and who knows, maybe in some time you test my releases
Find a ROM which lets you cook your own version.
And learn to edit things like the build.prop and system files.
postfatal said:
Find a ROM which lets you cook your own version.
And learn to edit things like the build.prop and system files.
Click to expand...
Click to collapse
Yes, any suggestion of where to start readind?
Tutorials?
pika456 said:
Hallo, I am a flash addict, yes I admit
the problem is that every rom I "test" have pros and cons,
so I'm wandering, how can I make one of mine?
not from sources (just yet) but lets say take an original aosp or samsung
and add different apks and patches
I tried to delete / replace apks like email, callendar etc in a running rom
and most of the times I get FC and non working apps.
Any help of what to read and how to start would be much appreciated!
and who knows, maybe in some time you test my releases
Click to expand...
Click to collapse
I like your interest in developing your own ROM.
As a beginner, you will have to start with android kitchen, it makes ROM development a breeze.
Visit here to learn more: forum.xda-developers.com/showthread.php?t=1227549
Most of the Rom developers started with, some are even still using kitchen to cook their own Roms.
You will also find links to useful tutorials on that page.
Look at this place too forum.xda-developers.com/showthread.php?t=1132724
Good luck
Swyped from my Samsung Galaxy SII
thank you! :laugh:
pika456 said:
thank you! :laugh:
Click to expand...
Click to collapse
You are welcome
Swyped from my Samsung Galaxy SII
Try compiling from source. Using the ROM kitchen is not really development. Problem is it does everything for you so you won't learn everything.
Sent from my Galaxy Nexus using Tapatalk 2
CdTDroiD said:
Try compiling from source. Using the ROM kitchen is not really development. Problem is it does everything for you so you won't learn everything.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I disagree with you.
I started with ROM kitchen, then started modding, then theming and now I can compile from source.
Everybody has got to start from somewhere.
Moreso, if you read his post well, he clearly said, "how can I make one of mine? not from sources (just yet) but lets say take an original aosp or Samsung"
One step at a time bro, that's the way to proper development in life.
Swyped from my Samsung Galaxy SII
Jokesy said:
I disagree with you.
I started with ROM kitchen, then started modding, then theming and now I can compile from source.
Everybody has got to start from somewhere.
Moreso, if you read his post well, he clearly said, "how can I make one of mine? not from sources (just yet) but lets say take an original aosp or Samsung"
One step at a time bro, that's the way to proper development in life.
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
More like cooking than developing but yea you are right everyone must start from somewhere, nothing wrong with modding stock ROMs to make them better. That's the whole aim I guess. It is very easy to download the source and its much easier to understand the code before its compiled for someone who has no experience with Java or anything.
Maybe extract the system and boot from a stock Samsung ROM and go from there as above.
Sent from my Galaxy Nexus using Tapatalk 2
I just got done initializing the AOSP JB_SOURCE for the Nexus 7, and am getting ready to attempt a first build, I'd also like to be able to compile CM10 and who knows maybe others but CM10 for sure. My question (although I'm pretty sure the answer is yes) is do I now have to make a new SOURCE directory for CM10 and repeat the process of downloading the whole thing locally for each build I'd like to attempt i.e. CM10, AOKP,MIUI
ect. If so the 150gb I used to create my virtual hard drive isn't going to be enough. I apologize in advance if this question is posted in the wrong place
and I did search first. Thank you.
Vektor67 said:
I just got done initializing the AOSP JB_SOURCE for the Nexus 7, and am getting ready to attempt a first build, I'd also like to be able to compile CM10 and who knows maybe others but CM10 for sure. My question (although I'm pretty sure the answer is yes) is do I now have to make a new SOURCE directory for CM10 and repeat the process of downloading the whole thing locally for each build I'd like to attempt i.e. CM10, AOKP,MIUI
ect. If so the 150gb I used to create my virtual hard drive isn't going to be enough. I apologize in advance if this question is posted in the wrong place
and I did search first. Thank you.
Click to expand...
Click to collapse
For each different ROM type (aosp cm etc.) you need different source code as they are different ROM
Sent from my LG-P350 using xda premium
Sorry it took so long, Thanks for the response. So it seems that for each particular flavor of Android I need the whole source repo synced to my machine.
That doesn't apply to different devices does it? I have an SGS 3 d2spr, and a Nexus 7 it would be fun to run a self built os for each.
Vektor67 said:
Sorry it took so long, Thanks for the response. So it seems that for each particular flavor of Android I need the whole source repo synced to my machine.
That doesn't apply to different devices does it? I have an SGS 3 d2spr, and a Nexus 7 it would be fun to run a self built os for each.
Click to expand...
Click to collapse
No it doesn't apply you just need different device folders and when you compile you use the folder you want.
Sent from my LG-P350 using xda premium