I have tried googling this and also searching the forums and have found many helpful guides for setting up build environ for building CM/AOKP/AOSP and so on. I am new to this obviously and dont totally understand linux and what not but have successfully built CM from source for my S4. Now I would like to start building KitKat from googles source. I mostly like everything about the google stock rom and seeing as their are fewer things in it then I would want to change in the stock CM builds and whatnot that I would really like to just get the google repo and build from that source. When following the guides I have seen they all refer to the repo's for the AOKP or CM or whatever and not AFAIK googles source. Is this so simple that beccause I dont understand how to do it maybe it means Im not supposed to be or is it just an unusual desire? Anyway if someone could direct me to the proper guide or the proper command to init the google 4.4 repo for the Nexus 7 2013 Deb/razorg I would greatly appreciate. Not sure if this should have gone in dev section or here or what but figured not clutter dev forum with such a simple thing. Thanks in advance. Any guidance on any of this source building design stuff would be appreciated as well.
McOpCo 5528
I think I just posted to soon. Finally found googles site and looking through it I think I am getting there. Still would appreciate any help or suggestions on guides to read or anything that helped any of you build your first few builds via source. Thanks.
repo init -u https://android.googlesource.com/platform/manifest -b android-4.4_r1.1
Related
Hi,
Apolgies if this is in the wrong place, but this is the only forum I would expect to get my answer.
I need someone to point me in the right direction please. I'm thinking of compiling an ASOP for personal use from source. I have looked at the google tutorials and even though Linux isn't my weapon of choice, being an IT systems engineer I do not feel following the tutorial will be too difficult.
However, is there a more specific guide for the desire?
The tutorial builds for the development handsets eg Nexus one. Is it just a case of supplying the correct drivers, RIL and editing the product code, or is there a bit more to it than that?
Any help / direction greatly appreciated.
You could start with building ROMs from Oxygen or CM source. That way you can familiarize yourself with the AOSP project without worrying about drivers etc. (DevNull source is completely stock AOSP with drivers for the Desire etc.)
Later on, when you know how everything works, you can start your own project.
If you want to start building AOSP from Google source, you might want to read the tutorials over at Google for a couple of times + checking the wiki's over at CM. They pretty much explain everything that there's to it.
If you're looking for a guide specific for the HTC Desire, then I think you're out of luck. Most dev's over here start off with the tutorials over at android.com and even with tutorials etc. at CM.
Is DevNull definitely 100% AOSP + drivers? If so, then it would be pointless compiling from source anyway.
I already ran that through dsixda, but the options there are quite limited.
What I had hoped I could do was make a tiny tiny AOSP. DevNull is pretty small though, so maybe it can't get much smaller.
rootSU said:
Hi,
Apolgies if this is in the wrong place, but this is the only forum I would expect to get my answer.
I need someone to point me in the right direction please. I'm thinking of compiling an ASOP for personal use from source. I have looked at the google tutorials and even though Linux isn't my weapon of choice, being an IT systems engineer I do not feel following the tutorial will be too difficult.
However, is there a more specific guide for the desire?
The tutorial builds for the development handsets eg Nexus one. Is it just a case of supplying the correct drivers, RIL and editing the product code, or is there a bit more to it than that?
Any help / direction greatly appreciated.
Click to expand...
Click to collapse
Hi Dan, for a start, the best place to start would be building a Cyanogen Rom from source as per Cyanogen's guide here. This guide is specific for the Desire
My suggestion is to build/modify this source first, since it's actively supported by a community. Once you get a fair idea, you could move on to the vanilla source..
Btw..Linux knowledge isnt crucial for building it, and you can easily follow the guide
Edit: Oops, just reallized that I just mirrored Pyr0wl's advice
Hi,
this weekend I decided to give it a go and compiled my first ever rom. Of course just a basic one, build from the latest source (4.0.3). All went fine, got it working. So I do understand the basics for now. However, regarding the source and building 'material' I have some questions. I could not find a proper answer with google, so maybe someone here could help me. I'm not asking for a complete guide, just a pointer in the right direction would be great!
1) How do I clean up my previous build. Is it really as simple as 'make clean'?
2) Right now I've synced the 4.0.3 branch. Let's say I want to build just the kernel. Do I set up a new directory where I sync the kernel sources, or can I do it from within my current directory, but without building the full rom?
Thanks in advance. Right now I focus on the basics, my next step would be to use GIT. But for now, if anybody could help me with the above (or knows a good -tutorial/beginners- site with some tips on building a kernel) that would be great! Thanks!!
I found a guide for compiling AOSP for 4.0.3, but I'd like to do it for 4.0.4. I'm more interested in learning about roms and stuff, but I don't want to use the rom kitchen. I have a working dev environment (ubuntu 10.04, followed the setup procedures on the AOSP site).
I have my repo sync'd and ready to build, but I read that I need proprietary libraries for my phone. Unfortunately I don't see anything about the cdma G nexus on this page (only maguro):
https://developers.google.com/android/nexus/drivers
So.. where do I find these? I've been doing a lot of searching but unfortunately I can't find any information on this. Thanks in advance.
The bottom of the page you linked has a few binaries for the CDMA Nexus. Other than those, use the extract-files.sh script in the device folder (device/samsung/toro) and if you run that with your phone attached and adb enabled/setup, it will pull the rest of the files that you need off of the phone.
Thanks! The files in that guide were from 4.0.3, would these be different from 4.0.4?
Okay so with the help of a lot of people and hours of work I have successfully built a kernel for the sg3. I want to take the next step to roms however (I know, big step).
Using the xda-university thread I have setup a repo and am currently pulling the latest 4.3 AOSP source (will let it sit overnight, my internet isn't too amazing and I have HDD not SSD *sadface*)
As far as I understand it so far, I need to find suitable device tree sources to get AOSP sources working on the sg3 (at&t for now). I have been doing a lot of searching and reading, but as usual when you get started, its like a sea of information. If anybody could give me some reading material or direction on taking on this venture, it would be much appreciated. Feel free to be as technical or nontechnical, I will read til I get what you mean.
Thanks
EDIT: so I did some reading and decided to go with cm's d2 device tree and see if it works. I created a new directory in /root/devices/samsung called android_device_samsung_d2-common
Unfortunately when I use the lunch command, it is not one of the selectable options. I read that I need to edit my .repo/manifest.xml to include it but upon examination I tried adding the following line but it didn't help
Code:
<project path="device/samsung/android_device_samsung_d2-common" name="device/samsung/android_device_samsung_d2-common" groups="device,d2" />
any ideas?
Anyone?
If you want to build cm, look here
http://wiki.cyanogenmod.org/w/D2att_Info
It has a very good tutorial on how to build cm
mrhaley30705 said:
If you want to build cm, look here
http://wiki.cyanogenmod.org/w/D2att_Info
It has a very good tutorial on how to build cm
Click to expand...
Click to collapse
Thanks, wanted to build from source directly and just use cm device trees but I guess I should make smaller steps and try basing off of cm first. Thanks for the link, will try
It's also a good way to test your build environment. If you can build cm straight up, then you'll know if something you did broke it. And believe me, trying to chase down build errors is a pita.
hello,
I've noticed that there is a guide for building CM14 for the oneplus 3. Myself and others have been able to use it to make personal builds and to learn some things along the way.
I would imagine that the next step to progress to would be to make builds of ROMs that don't have a nougat/CM14 branch in their repo for our device. Its pretty easy to brunch, select your device, and wait for the build to finish. But I am very interested in learning how to build a ROM using a device tree from another repo.
I've noticed that @Eliminater seems to be very proficient at this, as he has built and posted unofficials of various ROMs.
I've been trying to teach/learn this myself through searching for guides, but havent been able to find anything that helps me get there 100% of the way.
I've been able to get as far as forking the device tree, editing the .mk and .dependencies files to match the format needed for the ROM I'm trying to build. I've also added the forked device tree and additional repos to the local_manifest. This has gotten me far enough that I have been able to do a successful "lunch", but I haven't gotten a build to finish. In fact, they fail pretty early on.
Is anyone able and willing to explain the process further?
Are there additional steps that I'm missing?
Or do you just need to be proficient enough to troubleshoot error after error when building?
Thanks in advance