Greetings Everyone.
I've searched this forum, but I didn't found any post related to this theme. My aim is to compile non "kernel/common" android's source code, in order to replace the applications inside the Android device (such as SG sIII). I've seen that "kernel/common" will wuild a Kernel Image but, by the way, I don't think that this code (ie. the one you could find in "frameworks/base/core", "dalvik", "bionic") could be put inside my image. My question is: how to compile this source code? In particular, I've seen that there is an Anrdroid.mk: should I use ndk-build? Or better, Is there a way to associate the build image generated with this ulterior build?
Thanks in advance.
Related
Hi all, I've been googling around but didn't find any useful information, so I'm asking just in case. Is there any guide to compile the full Android sources (kernel+userspace) for the Sapphire?
I found information for the Dream, and I guess it will be similar, but android's kernel source doesn't even have the sapphire files (though I have a copy elsewhere), but I don't know which libraries I might need to add by myself to the destination images, or something else I need to have in consideration...
Thanks in advance!
Hi there,
Now, I understand that there's a thread or two and a few web pages directed at compiling Android and its kernel from source.
However, the thread in question is months old, and didn't fully explain the process.
As for the web pages, they are mostly outdated and don't include enough information, not to mention desire specific instructions.
I think that, properly explained, building Android shouldn't be daunting, and everyone should be able to attempt it, if they wanted to.
So, I hope to compose a comprehensive guide on how to do just that.
The problem is that I myself have not been able to put enough instructions together to be able to complete a build. And there is no point digging up old threads.
So, If anyone who knows the ropes (that is, compiling android and a kernel from source) would be willing to lead the way, I'd happily turn it into an easy to understand guide.
Josh.
fllash said:
Hi there,
Now, I understand that there's a thread or two and a few web pages directed at compiling Android and its kernel from source.
However, the thread in question is months old, and didn't fully explain the process.
As for the web pages, they are mostly outdated and don't include enough information, not to mention desire specific instructions.
I think that, properly explained, building Android shouldn't be daunting, and everyone should be able to attempt it, if they wanted to.
So, I hope to compose a comprehensive guide on how to do just that.
The problem is that I myself have not been able to put enough instructions together to be able to complete a build. And there is no point digging up old threads.
So, If anyone who knows the ropes (that is, compiling android and a kernel from source) would be willing to lead the way, I'd happily turn it into an easy to understand guide.
Josh.
Click to expand...
Click to collapse
I followed this guide here and successfully compiled a modified HTC Kernel and I had very little Linux and Android experience.
Obviously instead of cloning the Cyanogen git, you just use the gits you wish to compile
Mekrel said:
I followed this guide here and successfully compiled a modified HTC Kernel and I had very little Linux and Android experience.
Obviously instead of cloning the Cyanogen git, you just use the gits you wish to compile
Click to expand...
Click to collapse
Thanks for the link
Though i don't fully understand the whole 'git' thing. Where do i find them? And how to i know which ones are the ones i want to use?
Josh
EDIT: Also, how do you 'edit' the kernel (i imagine it is somewhat like make menuconfig?). Also:
- Are these sense kernels?
- How do you add modules like OC and UV?
fllash said:
Thanks for the link
Though i don't fully understand the whole 'git' thing. Where do i find them? And how to i know which ones are the ones i want to use?
Josh
EDIT: Also, how do you 'edit' the kernel (i imagine it is somewhat like make menuconfig?). Also:
- Are these sense kernels?
- How do you add modules like OC and UV?
Click to expand...
Click to collapse
A git is a repository for source code, developers upload their source code there and can commit changes. The commit can allow descriptions of what was changed and also details the files changed.
The git system allows other people to add to the source if they have permission, or allows others to read the changes and download the source code.
Git links are usually posted by people who release software, as Android is GPL licensed so people have to release their source code if they're distributing their work.
Editing the kernel, take a look into the git and the commits and it will show you which files were changed and how exactly they were changed. That will give you the best understanding.
UV/OC is done by changing the acpu table in the architectures files and changing the minimum/maximum voltage figures in the board_bravo.c file.
The Cyanogen kernels are not Sense kernels no, it's a modified Google Kernel.
Thanks for the explanation. I followed the guide and built the rom, and it works (always a plus )
Now, the next thing is the kernel. How do I build a kernel with the CM tweaks integrated? I understand that all i would be doing is rebuilding the same one that is already installed, but im doing it to learn.
So, if i synced the GIT, does that include the CyanogenMOD kernel source? If it does, where is it and how do i rebuild it. If not, where do i find it?
Thanks,
Josh.
Ok this may be a stupid question but if
https://android.googlesource.com/platform/ contains the AOSP source code
https://android.googlesource.com/kernel/ contains the kernel source code
what does https://android.googlesource.com/device/ contain?
Aside,
1) In the https://android.googlesource.com/device/, what does the branch ics-plus-aosp contain?
2) When I download https://android.googlesource.com/device/generic/goldfish/ ics-plus-aosp it only contained a single folder, audio, why is that so? I would have expected something like the aosp, etc...
Can a mod help me to move this to android Q & A, thanks.
bump
I believe it is device specific code
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.
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