How to compile aosp source code for specific devices? - General Questions and Answers

Hi guys, I'm a total noob to android custom roms, so please don't abuse me if I've just asked something very obvious to devs...
Please don't reply giving links to the aosp project, I've already seen them.
Assume I have the system needed to build from the source code.
How do I exactly configure the toolchain for a particular device(say moto g xt1032)?
Do I get configurations with the 9gb download, or do I have to download it separately? And will I be able to successfully compile a working ROM for that device?
I just wanted to know more before diving into my new project.

Related

[Q] Downloading kernel source code from custom ROMs

I want to download the source code for the kernel in my custom ROM because I want to compile something that may have dependencies with it.
So, I own a HTC Desire en lets say, I am using the following ROM:
http://forum.xda-developers.com/showthread.php?t=1863780&highlight=download+source
De binairies I can simply download and flash, no big deal.
But I cannot compile anything on my phone.
I have found a site where it is explained that I need to point the compiler to the source of the kernel, and then I can compile it on a Linux computer.
Thus, I need the source.
I've tried posting in the thread mentioned, but it giving me a message that I cannot post there because I am a new user
Btw. The thing I am trying to compile is C code.

[Q] Can I upload the nexus binaries to github for my rom?

Hey there!
I started a new project for a new ROM based on AOSP with some friends and wanted to know if I am allowed to upload the vendor binaries from here: https://developers.google.com/android/nexus/drivers?hl=de#hammerheadktu84q to my github for including it in the build?:silly:
CouldnĀ“t find an answer in the license myself but I saw that it has been uploaded already in some git repos.
Thanks for your help again!
yes
Why wouldn't you be able to?

What is necessary if I want to compile a ROM?

Hi guys. 2 months ago I've came into Android World deeper than before and now I'm very fascinated. I downloaded linux, all the necessary files to compile a rom but I still don't understand some things.
My device is Redmi Note 2 and I use stock MIUI 7. As we all know mtk and/or xiaomi haven't released kernel sources (6795) so developers have to think hard how to make a rom. And there are my questions. Does kernel source is really necessary? What if I compile rom successfully and then port boot.img from stock? Will it work? However developers made some roms based on LP for this device. And I read that I need device tree and vendor, which doesnt exist for redmi note 2 or I still can't use github.
Second question which I have is: does compiling for 64 bit CPU differ from compiling for 32 bit CPU (like 6592)? If yes, could you give me some tips?
Ohh I think you can understand what I wrote
Thanks in advance and please dont blame me for silly questions
If you are looking to compile roms then you picked the wrong device to do it. They are the worst with kernel source. You can't completely compile a rom but use a patch system that does most of the work.
Yes it is different. There are some Tuts around but they are few as most don't use that type of chip.
If you really want to learn to develop then I would suggest getting a different device. One that respects the copyright and gpl laws.
zelendel said:
If you are looking to compile roms then you picked the wrong device to do it. They are the worst with kernel source. You can't completely compile a rom but use a patch system that does most of the work.
Yes it is different. There are some Tuts around but they are few as most don't use that type of chip.
If you really want to learn to develop then I would suggest getting a different device. One that respects the copyright and gpl laws.
Click to expand...
Click to collapse
Thank you for your advices. I have HTC desire 310 and I found the kernel sources. I know what I'll do in my free time
Monsterlevel said:
Thank you for your advices. I have HTC desire 310 and I found the kernel sources. I know what I'll do in my free time
Click to expand...
Click to collapse
To compile a rom u need kernel source, device tree and proprietary, bye

Porting B2G to moto g3

Hi Folks,
I'm trying to port B2G to my moto g3. I was referring to this doc (https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Porting_B2G_OS/basics). However some of the things mentioned in this doc are not clear to me. Could you please help me with the below issue.
I'd like to build the AndroidKernel from source. So where should I include the below lines? Is it in this file?
https://github.com/LineageOS/android_device_motorola_osprey/blob/cm-14.1/rootdir/etc/init.target.rc
HTML:
on early-init
start ueventd
import /init.b2g.rc
Also if I understood correctly. building the kernel from source doesn't require to unpack , edit the init.rc file and repack the kernel from the device. Could you please confirm this?
Thanks,
Arun
Hi Arun,
I totally understand your frustration with this. You'd like to contribute to the Servonk project but first you need to port B2G to your phone or buy a new phone. Since the only other supported phones are the Z3 compact and Nexus 5, both of which are still relatively expensive secondhand, you want to use your Moto G3 which means first porting B2G to it.
So, I think there are two options you have:
1. Port direct from the AOSP code
2. Port from the CM12 code.
As Gerard said in telegram, porting from CM to B2G was never finalised so may actually require more work. However there may actually be more people here who can help you since people seem more familiar with CM than AOSP (in general, I know some people are very knowledgeable in both).
I see you've posted in the AOSP 7.1.1 kernel thread. Unfortunately, for the Servonk project you currently need a Lollipop based build, so 5.x AOSP kernel or CM12.x.
It might be worth asking a mod to move this thread into one of the development sub-forums.
As you know, this is the limit of my knowledge, but I really hope you find some success, if would be great if you could contribute to the Servonk project.
Your last option is to use the desktop build of Servonk, based on Glutin instead of Gonk, but I understand that you really want to get Servonk working on your phone.
Best of luck

[Android Development] How The Developers Make The Custom Rom?? (not buildboting)

My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
(t.me) is a good place, they use SDK and Android Kitchen etc.
JaswanthTeja said:
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
Click to expand...
Click to collapse
Custom ROM sources require that the stock source code be made available to the public by the manufacturer/carrier of the device. If the stock source code for a specific device has not been made available to the public, developers can not create custom ROM source code for that specific device. Developers use the stock source code to create the custom ROM source code and then ROMs are built using the custom source they created. I think that is the answer you were really looking for. You want to know how the source code itself that the ROMs are built from is created. You aren't asking about the fruit that comes from the tree, you are asking where the tree that bears the fruit comes from. Am I right?
The only way to get custom ROMs on devices that do not have stock source code made available is to port custom ROMs from a similar device with the same architecture that does have available source code and custom ROMs made for it.
OldNoobOne said:
(t.me) is a good place, they use SDK and Android Kitchen etc.
Click to expand...
Click to collapse
I don't think that is what they are asking.
Droidriven said:
I don't think that is what they are asking.
Click to expand...
Click to collapse
Yeah, I Want To Know About Android Arc
JaswanthTeja said:
Yeah, I Want To Know About Android Arc
Click to expand...
Click to collapse
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Droidriven said:
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Click to expand...
Click to collapse
cool

Categories

Resources