[Q] Decveloping android to other devices? - Android Q&A, Help & Troubleshooting

Porting Android - Did I thinking that this modifying custom ROM from one device such as CyanogenMod for the Nexus 5 and move it to another completely different device? I have an idea for the Nokia N9 developing ended with android 4.1, I would like to create a ROM, for example, 4.4 (higher than 4.1) for Nokia N9 as KitKat has a lot of optimization and was run even on slower devices. Could someone explain how to do or advise what to do, or give a link to the guide. Linux commands aren't unknown to me. I'm new on xda.

Related

[Q] Device dependency of Pure Android ROMs

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.

[Q] Android Porting. Why device specific?

Hello all!!
I'm new to Android and i'm interested in learning a bit and maybe get involved with it but there are some things that i don't get about android and can't find the answers.
My main question is why Android which is based on Linux is so hard to get updates for all devices at once?
For example we got ICS lately why it's only available for Nexus S and not for all devices that support android?
In pcs if there is a new Ubuntu version every pc can get it no matter the hardware it uses as there are drivers for it.
Is it so hard to have drivers for all the android devices?
Why do we need to wait forever for the X company that makes the phone to build a new kernel?
Is it about the libaries?The drivers?
Say i got a device that is not supported by ICS what would i need to make it supported? I got my libs from 2.3.5 can i toss them to overlay compile and works? If not y not?
Thanks in advance for your answers and sorry if my questions are too noobish, everyone has to start from somewhere
Serafym said:
Hello all!!
I'm new to Android and i'm interested in learning a bit and maybe get involved with it but there are some things that i don't get about android and can't find the answers.
1. My main question is why Android which is based on Linux is so hard to get updates for all devices at once?
2. For example we got ICS lately why it's only available for Nexus S and not for all devices that support android?
- In pcs if there is a new Ubuntu version every pc can get it no matter the hardware it uses as there are drivers for it.
3. Is it so hard to have drivers for all the android devices?
4. Why do we need to wait forever for the X company that makes the phone to build a new kernel?
5. Is it about the libaries?The drivers?
6. Say i got a device that is not supported by ICS what would i need to make it supported? I got my libs from 2.3.5 can i toss them to overlay compile and works? If not y not?
Thanks in advance for your answers and sorry if my questions are too noobish, everyone has to start from somewhere
Click to expand...
Click to collapse
1. Manufacturers don't release updates for all their devices all at once (some not at all).
2. It's ready (most stable so far) for that device (SDK ports; (almost) official update)
- Not true. If you tried to place Ubuntu 12.04 LTS on a PC with a 368 MHz and 32mb ram, it would not run .
3. Yes. Android is on devices from many different manufacturers with many different designs and hardware.
4. See here: http://en.wikipedia.org/wiki/Linux_kernel (to know what it is). Different hardware will require different commands, etc. If the manufacturer doesn't release the kernel source, development cannot be done on that device (properly).
5. Yes and yes (much more too).
6. Create a working port from some other device (with similar hardware) which is supported. Sometimes. Some versions of android have backward compatibility of those files but ICS isn't really backward compatible which is why many ports of ICS (for various devices) don't have a working camera, etc. See the 2nd paragraph here: http://www.cyanogenmod.com/blog/cm9-progress-update.

[Q] Is there a possibility to build a universal android ROM

Hello
Here is a little question, is it possible to create a universal android rom.
Today, cyanogenmod allow us to have different flavour of android for many devices. But cyanogenmod is not universal and requires specific hacks for each device.
I know that Android is based on a linux kernel, that kernel should beallow an automatic detection of the devices specifications....
Moreover, Motorola initiates its Ara project. This new concept should be linked to an evolutive version of Android.
Is there anyway to see one day an android repository to upgrade and costumize your phone/phablet/tablet. With an essential package (OS) and options (launcher/Touchwiz....).
An universal evolutive OS should be a way to solve
- android fragmentation.
- security update
- Easy update without formatting your device
- OTA update for all devices (Samsung, Cube, HTC....) even for olders or chinese models
bart47 said:
Hello
Here is a little question, is it possible to create a universal android rom.
Today, cyanogenmod allow us to have different flavour of android for many devices. But cyanogenmod is not universal and requires specific hacks for each device.
I know that Android is based on a linux kernel, that kernel should beallow an automatic detection of the devices specifications....
Moreover, Motorola initiates its Ara project. This new concept should be linked to an evolutive version of Android.
Is there anyway to see one day an android repository to upgrade and costumize your phone/phablet/tablet. With an essential package (OS) and options (launcher/Touchwiz....).
An universal evolutive OS should be a way to solve
- android fragmentation.
- security update
- Easy update without formatting your device
- OTA update for all devices (Samsung, Cube, HTC....) even for olders or chinese models
Click to expand...
Click to collapse
I'm not going to be the one to say its impossible but its very unlikely. Different devices use different modems, kernels, and other system requirements. The CM team may be able to come up with something like that but you won't see it anytime soon if it happens. There are some ROMs out there that are in 1 big AROMA zip file and they all have the same features but the bases meet the requirements of the specific device.
bart47 said:
Hello
Here is a little question, is it possible to create a universal android rom.
Today, cyanogenmod allow us to have different flavour of android for many devices. But cyanogenmod is not universal and requires specific hacks for each device.
I know that Android is based on a linux kernel, that kernel should beallow an automatic detection of the devices specifications....
Moreover, Motorola initiates its Ara project. This new concept should be linked to an evolutive version of Android.
Is there anyway to see one day an android repository to upgrade and costumize your phone/phablet/tablet. With an essential package (OS) and options (launcher/Touchwiz....).
An universal evolutive OS should be a way to solve
- android fragmentation.
- security update
- Easy update without formatting your device
- OTA update for all devices (Samsung, Cube, HTC....) even for olders or chinese models
Click to expand...
Click to collapse
I doubt it's possibility. Different phones have different kernels/coding for hardware. All Android phones uses Linux kernel, but are coded differently, and that's why we have different/custom kernels. Phones/phablets/tablets have different UIs, which will result in larger updates. Furthermore, u said "essential package" which is hardly possible due to large file size and company issues. For example, Samsung has TouchWiz (and all it's bloatware ), while HTC has Sense (and the bloatwares ), and to stuff everything in a single ROM /Update, it's simply too much. (A update from Samsung would cost 100-300mb, and if what u say is true, OTA updates would cost 600mb~. (Take into account the stock Android launcher.)) I doubt Samsung would like this idea too. Companies like Samsung and HTC have their own launchers to differentiate themselves from others, and if consumers have a choice, they might use other launchers other than their own. (E.g. a Samsung user wants to use Sense, while preserving the Samsung hardware.) Though I would very much like to see this in the future, this is technically impossible. Hoped this explained your question.
Smack that thanks button If I helped!
Always make a nandroid backup before trying anything risky
Sent from my fabulous N7105 powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
This is literally impossible, All devices would need to be designed to perform for that rom. Not only that but not a single one of those companies would agree to it. They'd actually attempt to make their own os before doing that, and the reasoning is simple, each company is in this race for themselves not as a team effort. For this to happen would be going the route of IOS, which android is not.
Sent from an Xposed LG-G2/LS-980

Becoming Android ROM developer

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!!!

A bare operating system

Hello... Since I'm not very familiar with cell phones I'm curious about something. With a desktop computer, one can build their own or have a manufacturer type ( Dell, HP and so ) Now if you take the custom build system you basically can decide which OS you want, why can't cell phones be similar to that be able to install whichever OS you like, Or can you? Like in Android is it possible to install just a basic OS onto a phone? one that doesn't have let's say Google ( Google store)? Is there an Android build without Google? Also, does Android have an OS with its own browser, if not, why not? thanks
Dude905 said:
Hello... Since I'm not very familiar with cell phones I'm curious about something. With a desktop computer, one can build their own or have a manufacturer type ( Dell, HP and so ) Now if you take the custom build system you basically can decide which OS you want, why can't cell phones be similar to that be able to install whichever OS you like, Or can you? Like in Android is it possible to install just a basic OS onto a phone? one that doesn't have let's say Google ( Google store)? Is there an Android build without Google? Also, does Android have an OS with its own browser, if not, why not? thanks
Click to expand...
Click to collapse
You're thinking about it along the correct route. There are plain, unbranded Android builds known as Vanilla Android. These are the builds you see on Nexus and Pixel devices, built from the AOSP (Android Open Source Project) and have no carrier or OEM bloat.
If you're looking for a lightweight Android OS with no GApps (Google Apps), there are a ton of custom Android builds available, the most popular in the world being LineageOS. However, it should be noted that you can't simply flash a vanilla or custom Android build to your device and expect it to boot and function properly. Android ROMs need to be ported to a specific device. This is due to the vast hardware differences between various manufacturers and models.
To see if any custom Android builds are available for your particular device, search your model device in the Search Plus option. If any custom ROMs, kernels, recoveries, etc., are available for your device, you'll find them here on XDA.
MotoJunkie01 said:
You're thinking about it along the correct route. There are plain, unbranded Android builds known as Vanilla Android. These are the builds you see on Nexus and Pixel devices, built from the AOSP (Android Open Source Project) and have no carrier or OEM bloat.
If you're looking for a lightweight Android OS with no GApps (Google Apps), there are a ton of custom Android builds available, the most popular in the world being LineageOS. However, it should be noted that you can't simply flash a vanilla or custom Android build to your device and expect it to boot and function properly. Android ROMs need to be ported to a specific device. This is due to the vast hardware differences between various manufacturers and models.
To see if any custom Android builds are available for your particular device, search your model device in the Search Plus option. If any custom ROMs, kernels, recoveries, etc., are available for your device, you'll find them here on XDA.
Click to expand...
Click to collapse
Thank you for your input it gave me more of an understanding and I will do as suggested

Categories

Resources