Hi all, i've read other threads about this argument but any of them satisfied me.
I am curious about the steps to do for developing a custom ROM for an unmodded device, so for example taking the android source code and make it work on a device.
In my case, I will use a Samsung Grand Neo (GT-I9060).
How do developers manage to port a ROM to a new device? How do they make device features working? Do they use camera drivers and other drivers to reach this goal?
How to upgrade the firmware to a newer version if no newer version is released by the manufacturer?
Sorry for these nooby questions
Waiting for your answers
Related
I was going through the xdadevelopers forums when I saw that the process of installing ROMs seems of be device dependent. Can someone please explain me why it is so?
More specifically, shouldn't the process of installing a pure Android ROM (AOSP) be the same on every device since all of them are based on the ARM architecture.
I haven't installed an android ROM before, but I am trying to understand why the process isn't similar to installing a Linux based OS on my computer.
I recently bought an Android tablet (HCL ME X1) to experiment with ROMs but later realized that there aren't ROMs for this device. Can someone let me if I can use the ROMs of any other device for this?
Because all different models have different hardware so the rom has to be specific to that device.
Sent from my GT-I9100 using Tapatalk
Thanks for the reply stylez.
So I guess if I want to develop a custom ROM (say an AOSP ROM) I will need the device drivers which my vendor wrote.
Is there any way of identifying the vendor specific drivers of my device? I am using an HCL ME X1.
Hi,
I was wondering if it's still an issue that Samsung isn't releasing their drivers source code and so we can't develop fully functional roms with latest version of android for our Galaxy s3?
What drivers do current roms for the Galaxy s3 are using?
I came across the http://opensource.samsung.com/ site and I'm trying to downlad the source code for a JB build.
Won't I be able to take the drivers from that build and use it with the latest version of android?
I realize this is a basic question and I'm sure I'm not the first to think of this, I just want to understand what's hloding us back.
Thanks!
I am really confused! I went through a lot of threads and forums. Unfortunately i can't get some of the concepts....
Can someone give me a roadmap on how to get started with compiling android roms(not custom roms)
How do OEMs like Samsung, HTC compile their ROMs??? I mean where do they learn that the particular process should be done this way regarding Android firmware???
In Repo Sync, is it possible to pause and resume that huge download? If i want to reinstall linux, is it possible to backup that 30-40GB download???
I have Asus Fonepad 7 and has kernel sources here: http://www.asus.com/support/Download/28/7/0/7/K0zj5cW6VJEzTjQR/32/ My question is am i able to create stock Android ROMs like those in Nexus devices and fastboot images for flashing on to this device??? Also do x86 devices have a different way of compiling ROM???
I want to do things the original official way... Please help me, I am very eager to learn!!!
I would be more than happy if someone could help!!!
Hi,
This is my first post on XDA, so please let me know if I violated any rules of this forum.
I have observed that there is a dearth of custom ROMs for Samsung devices with Exynos chipsets in general. Since the manufacturer doesn't provide much support/update after ~2 years, i think it there should be a way to increase the life of the device.
As an example, I have a Samsung Galaxy Note 5 (SM N920G) running Android Nougat and i couldn't find any ROM with Android Oreo supporting this device.
I have no knowledge of Android ROM development, so please forgive me if my questions are stupid or too basic.
1. How difficult is it to create a custom ROM in general and does Samsung make it difficult for developers by not releasing the kernel sources?
2. If the devices share a common chipset, how difficult is it to port the custom ROM to make it work for another device? Ex: If there is a custom ROM working for Samsung Galaxy S6, how much work does it require to make it work for Galaxy Note 5 as well?
I was desperate to try Android Oreo on my device and i have some time to burn this weekend. So i was wondering if i could try and create a custom ROM for myself.
I've also searched XDA and found some guides which were written for Marshmallow/Nougat. I am not sure if the same methods can work for Android Oreo as well.
I am looking for any inputs/suggestions and any sources you could point me to in my attempt to learn.
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.