Hello XDA!
I want to create a ROM which is aimed at those developers out there. It will be fast, have lots of Linux commands, and have a nice UI. It will also have a Package Manager that comes with it.
The reason i am asking for help is because I've never made a ROM before. I can code the apps for the ROM, the Linux commands, and some of the core Android code but i will need somebody else to do most of it.
The ROM will be for either KitKat or JellyBean, I'm not sure yet.
Github: GitHub.com/GNU-Droid
Related
I know Its pretty dumb to ask after seeing a lot of tutorial here, But I really can't understand! My Device is a huawei ascend y300. I have lots of custom rom on various forums. So I wanna built one myself! One of the developer built cm 11 from source and he is rolling out nightly on a daily basis. My interest is to build the cm11 too on my own computer based on his device specific changes he has done. and he has done a lots of changes for our device. Also if I can make any other rom from its source based of his work like mokee rom, or slimbeam etc. ANy help is appriciated. thnk you
I want to learn how to build a rom for an new device that no one has created a custom rom for. I am kinda new at this. But I want to learn how. I is there a full on guild or something on how to do it... I want to know. There are devices out there that have to custom roms yet that I would like to build for. I would like to use AOSP to build a clean fresh pure Android rom. Those devices I want to build for have the right specs to run a newer Android version but the developers did not realse an update for. I really would like to learn how to build/create my own Android rom from scratch... Learn how to build a kernel, bootloader, etc. to help the rom run right. Can anyone help?
http://forum.xda-developers.com/showthread.php?t=1272270
Thanks me if it helps you
@jakeh9777
Read this http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
Especially post #4 and below
Thanks!
My only problem is where do I get a device tree and all the files for the device? I am wanting to build roms for devices that no one else build roms for yet. So it is going to be hard to customize roms for those devices without any roms in the first place. I know how to download source but I can't build it a rom from it. I just want to support devices that no one else has but the ones people want still... And some of them aa silde out qwerty keyboards. Can I get some more easier instite... I better at learning physically, so a video will be good too.
P.S. I can't get a device tree from CM if the device is not been added... That is why I said these devices don't have roms yet.
Hi,
I wanted to ask this in other subforum, but this is my first post and I don't have permission there. Do you have a guide to recommend for creating custom roms?
I know a lot about Linux, I can compile kernels, patch, I know C a little. I programmed couple of Android apps, in Java and Go, so I guess I have some basic knowledge.
What do you guys do, with what source do you start? Is it a stock android source but you modify kernel and modules or you need first to find exact source for that phone?
For example, I own a Lenovo A560, and would like to try build custom rom for it. What would be the first steps?
Thanks,
Milan
Hey guys . I'm new to Android development...but i have a good idea about developing a custom rom and kernel using ubuntu..
But one day i was thinking that,
everyone who are interested in rom development goes through the AOSP website and tries it. And atlast after so many confusions and so many new learnings they compile it..
Bug fixing and adding features is next job.... Let's keep it aside
My thought was to build a software using java or c++ , which will automatically compile the rom for any device according to the user's input.
The inputs are device's code name (eg:-hammerhead)
And type of os(lineage based or aosp based etc...)
In the background of this software, all the rom compiling codes, source downloading codes, setting up environment codes etc,.. will be feeded using c++ or java.
After getting inputs from the user via a simple interface, the process will start. Downloading source, choosing directory,compilation, and finally the flashable rom will be the output of this software which will be stored in the given directory folder...
What do u guys think about this. Will this work???
i also know there are many troubles making this software
Pls comment abt ur thought guys..
I also need help in this case..
My vote is for is for a interactive GUI for android kernel development. One to allow easy modification to the kernel source and compilation. Kinda like Link+ Kernel Ide for Eclipse but for android
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
XdaNeko said:
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
Click to expand...
Click to collapse
It has been a looong time since I knew about those things but if I remember your base ROM should have that same Android version as your port ROM.
And if you want an advice, please consider building a ROM from source. Troubleshooting is hell with ported ROMs. Building ROM is scary because it has commands that you don't know yet, but it's way more easy than porting. Trust me.
Here is a guide on how to build ROM from source :
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
@XdaNeko
It's NOT the version of Android what does matter. If that would be the case then an upgrade via OTA never would be possible.
A Stock ROM always at 100% matches phone's hardware ( CPU, GPU, RAM, storage memory, etc.pp ) - it's built by OEM's / Carrier's R&D department, the guys who know best of.
Whereas a Custom ROM necessarily does NOT because it gets built by 3rd-party companies/programmers associations - who think they can do it better, but don't always have the specific Android device at hand.