Sorry if this question doesn't belong here.
I need to know where i can start to make a Custom Rom. I was searching a lot but i was not able to find anything else than the method to make roms for HTC devices using a kitchen, but i need a more general look to know what i need to know to start this project. I was reading on source.android.com but i'm not shure if that's the only material that's actually out there on this topic.
Thanks for the help.
Hey everyone, so I think this would be the right forum for this specific question. I used these steps:
http://source.android.com/source/initializing.html
So I'm not sure if the AOSP questions go here. Anyway, I just had a question. How do you know when the AOSP is done compiling? I had a few errors along the way that I fixed but I didn't see any "success, build complete" or anything. Just sort of stopped. Any specific lines that determine a successful build?
Thanks in advance
Question, I am getting the One S eventually and I want to just have Android AOSP on it for now. But I reckon there's more to the process than simply compiling it from source. What device specific challenges must I figure out first? Ive got plenty of experience with Android development but I havent really messed around with device specific stuff.. Any help much appreciated
Thread moved with a clean start
Or find answer here
Hello everybody
Recently, I found this thread http://forum.xda-developers.com/showthread.php?t=2233282. After a while testing it with the new method, I found out I had some bugs. I then wanted to test the old method, aka compiling the kernel + module from the debian image. The problem is, even with http://oldwiki.cyanogenmod.org/wiki/Building_Kernel_from_source I don't understand what to do. Do I have to type every single line, replacing the source with the debian image, with botbrew, or am I missing something (I surely am).
tl,dr how do I compile a kernel for this
I'm really new to all this stuff, but curiosity makes me want to go further. I hope somebody can help me a little bit.
Thanks in advance.
My phone is a s2 i9100, cm10.1
HI! I'm wondering how I would get started creating a custom ROM for Android. Not necessarily a ROM as big as CyanogenMod, but a custom ROM nonetheless, that can evolve and get bigger. Thanks
NateDev473 said:
HI! I'm wondering how I would get started creating a custom ROM for Android. Not necessarily a ROM as big as CyanogenMod, but a custom ROM nonetheless, that can evolve and get bigger. Thanks
Click to expand...
Click to collapse
Hi,
Check out this thread http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
Art Vanderlay said:
Hi,
Check out this thread http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
Click to expand...
Click to collapse
That mentions needing the device tree, vendor and kernel, and says that is on GitHub, however my device, the BLU Energy X 2 isn't very well known so there is no device tree or vendor. All I could get was the kernel source from BLU. I saw that there might be no device tree because the kernel version is only 3.10.74+, but there must be a way.
If I want to use CyanogenMod as a base, would having a CM ROM for my phone that I ported (copying over files from stock to port) help with the process? Because the original CM ROM that I used to port was for a phone with the same kernel version of mine, so there was a way that they got it, without device tree or vendor, right?
Sorry for this long + confusing wall of text, I'm just trying to explain my situation here. If you need me to clarify something, just ask.
Thanks,
Nate
NateDev473 said:
That mentions needing the device tree, vendor and kernel, and says that is on GitHub, however my device, the BLU Energy X 2 isn't very well known so there is no device tree or vendor. All I could get was the kernel source from BLU. I saw that there might be no device tree because the kernel version is only 3.10.74+, but there must be a way.
If I want to use CyanogenMod as a base, would having a CM ROM for my phone that I ported (copying over files from stock to port) help with the process? Because the original CM ROM that I used to port was for a phone with the same kernel version of mine, so there was a way that they got it, without device tree or vendor, right?
Sorry for this long + confusing wall of text, I'm just trying to explain my situation here. If you need me to clarify something, just ask.
Thanks,
Nate
Click to expand...
Click to collapse
If you want to work on a ROM then you need to have a device tree and vendor blobs. There's no way around this, its very different to porting a ROM. Try making a new thread in http://forum.xda-developers.com/android/help
Maybe some experts can help you there
Art Vanderlay said:
If you want to work on a ROM then you need to have a device tree and vendor blobs. There's no way around this, its very different to porting a ROM. Try making a new thread in http://forum.xda-developers.com/android/help
Maybe some experts can help you there
Click to expand...
Click to collapse
Ok, I will. Just wondering, how are these files usually acquired? I know they can usually be found on GitHub, but who originally puts them there? Where are they originally acquired from? The phone manufacturer?
NateDev473 said:
Ok, I will. Just wondering, how are these files usually acquired? I know they can usually be found on GitHub, but who originally puts them there? Where are they originally acquired from? The phone manufacturer?
Click to expand...
Click to collapse
They're built by developers. Since no ones developing for your device someone with some knowledge of ROM building would have to work on. I'm no expert so my advice would be to make a new thread in the section that I linked you.
Art Vanderlay said:
They're built by developers. Since no ones developing for your device someone with some knowledge of ROM building would have to work on. I'm no expert so my advice would be to make a new thread in the section that I linked you.
Click to expand...
Click to collapse
I've just done that