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
Related
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.
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
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
green2005 said:
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
Click to expand...
Click to collapse
It's actually fairly simple... an "official" ROM is one that is authorized, and often supported by, the development team of that ROM and the device is considered an "officially supported device".
But since the source code for these ROMs is open source, anyone can build or compile them for their device or another device that isn't officially supported. The ROM is not supported by the development team, but by the ROM maintainer/builder only. These types of builds that are either not officially supported devices, have modified the source code outside of the original developers guidelines, or not authorized by the development team are called "unofficial". They may even be by the same maintainer as the official version, but they modified (perhaps used a different toolchain) from the original guidelines for the ROM and it cannot be considered official any longer.
Really, it's boils down to: is the device supported and authorized by the core ROM development team... if yes, it's official... if no, it's unofficial.
Android Original Development is supposed to be for ROMs, kernels, and other projects that are completely original by the author, or authorized originals... Cyanogenmod/LineageOS is a good example of this... ROMs like Resurrection Remix are not considered "original" because they are based on Cyanogenmod, thus they just go into the Android Development section.
If in doubt about what the forum groups are for, read the sticky posts in each group.
Thanks now it's more clear
Hi! I own the Nexus5X and I am interesting in creating a custom ROM for the device. I have synced the AOSP source tree, gotten everything set up and flashed a build on to my device.
How can I start creating a ROM for the device? What are some general guidelines? How do I start tweaking apps, adding features, etc.
Also, if someone could take a look at these errors I am getting with my AOSP build that would be awesome: https://forum.xda-developers.com/nexus-5x/help/issues-aosp-built-source-bullhead-t3555439
Thanks
NateDev said:
Hi! I own the Nexus5X and I am interesting in creating a custom ROM for the device. I have synced the AOSP source tree, gotten everything set up and flashed a build on to my device.
How can I start creating a ROM for the device? What are some general guidelines? How do I start tweaking apps, adding features, etc.
Also, if someone could take a look at these errors I am getting with my AOSP build that would be awesome: https://forum.xda-developers.com/nexus-5x/help/issues-aosp-built-source-bullhead-t3555439
Thanks
Click to expand...
Click to collapse
Hello,
If you have interest in develop a custom rom, i suggest you start at XDA University to learn a bit of everything about Android.
You have some great guides on Android Software Development (look at stick posts)
I have my own guide which is not finished but I will teach everything you need to know about build a custom ROM from source, how to use github, git, mergetool etc... You can follow my progress HERE
FSadino said:
Hello,
If you have interest in develop a custom rom, i suggest you start at XDA University to learn a bit of everything about Android.
You have some great guides on Android Software Development (look at stick posts)
I have my own guide which is not finished but I will teach everything you need to know about build a custom ROM from source, how to use github, git, mergetool etc... You can follow my progress HERE
Click to expand...
Click to collapse
OK thanks, I will take a look at that. If possible, could you take a look at the errors I am getting with my AOSP build? I posed the link in the original post. Also, do you have to run extract-files.sh or can you simply download the vendor binaries from Google and run the extracting script? (AOSP)
NateDev said:
Also, do you have to run extract-files.sh or can you simply download the vendor binaries from Google and run the extracting script? (AOSP)
Click to expand...
Click to collapse
If you fork/download vendor binaries you don't need to run extracting script
It would be great if any developer shares his/her work procedure about building any ROM for Oneplus 6 (enchilada).
A lot of new ROMS are there in the market and for people like me who want to learn custom ROM developement and have only this phone at the moment to test, not a lot of resources are present in the web market to help us.
Therefore, it's my humble request to any DEV who can share with us the procedure for building custom ROMS like from scratch. This can include, getting ROM sources, device tree, kernel tree or vendor tree to be used and other modifications. It will help the community a lot. Discussions can be made based on various issues people encounter and it would be appreciated a lot.
Closed at the OP's request.