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
Related
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.
Hi,
I work in the security and privacy field and would like to start development of a new lightweight ROM with strong security and privacy controls but to be honest I don't have a clue where to start. I am experienced in flashing ROMs onto Android devices (currently have CM on my Nexus 4 and Galaxy Tab 2 as well as Beanstalk on my old HTC Desire Bravo) but have not yet built a custom ROM.
Ideally I would like to build the lightest possible ROM for HTC Desire (as this is my device for experimenting) but there are a number of features/restrictions I would like to include.
I see a lot of ROMs on this site (which I am sure are very good) and some generic guides on how to build ROMs but I need some more specific information. I need to know how to build a kernel which disables access to certain things (such as regular voice calling - this ROM should only permit VOIP calls) - how to strip out all the apps and services I don't want or need, how to include the apps I want installed by default (such as droidwall) and I have yet to come across such a resource.
Ideally I would like to strip the ROM down to the bare minimum required to allow a functioning device with data connectivity and then build it back up with the functionality I need.
Could anyone point me in the right direction?
Hi
I can Need you. You can Port roms .i have a project with Android 5.0 for Mid and Low End devices please join US We can work together but i Need more Rom porter and Kernel builder
Link:http://forum.xda-developers.com/che...oid-lollipop-5-0-rom-low-mid-devices-t2925685
Thanks from Germany
Ok, so let me tell you some information about my situation first.
I recently have made a deal with a manufacturer of Android Tablets.
I want to be able to develop and add features & fix bugs and push the updates to my customers Tablets and have them be able to easily download & install them. The Tablets currently run stock KitKat 4.4 but I can always ask my manufacturer to install certain modded software (roms?)
Thanks,
Ollieorange
Hello!
I have been following annual Google I/O 2017 and heard about all the benefits of Google's Project Treble.
I cannot help but wonder how are developers (for example here at XDA) able to create custom roms or unofficial Android updates. Why Google can't make official Android Nougat update for Nexus 7 2013, but you here at XDA can. What is different between your work and Google's when it comes to these things, as far as neither has access to hardware manufacturer's code support.
I have to say I am not a professional software developer, so I understand if this topic is beyond my comprehension.
Thank you!
"Why Google can't make official Android Nougat update for Nexus 7 2013"
Planned obsolescence.
"neither has access to hardware manufacturer's code support"
Google is obliged to release kernel source code because Linux(the kernel powering Android) is released under the GPL. The kernel is responsible for letting Android "talk" to the hardware. Developers at XDA can then modify the open-source kernel to "fit" newer versions of Android.
I'd like to chime in on this.
Let's use the Nexus 7 2013 as an example. The difference between what an official build of Nougat from Google would be and what a build of Nougat from XDA is that the Google released one will have updated devices drivers that are made specifically for Nougat, while the XDA released one simply uses the older device drivers and hope they work. In some cases they work flawlessly (mostly on Nexus devices), however other times there are things that don't work so they either need to be disabled or worked around. So essentially a Google released OS has everything updated and tested to work with the new OS, while XDA releases are more 'hacked' together to work (simply because the device drivers aren't Open Source). Google may not have access to the hardware drivers, but they still get them updated.
Now let's touch on Project Treble (and why I am so excited about it). Instead of each and every device driver needing to be upgraded and tested for each new OS version, the OS version will specify which version of the drivers (HAL's) will work with the OS. This means there will be a separate space where all the device drivers will reside, and the OS will simply load those when booting (no more proprietary binary blobs to include in the ROM! hopefully...).
This means on any Project Treble compatible device (all phones that ship with Oreo, and some that update to Oreo) with an unlocked bootloader, a user can simply compile AOSP and flash it directly to the device with no modifications and have the device work. I believe this is actually a requirement to pass Google's certification process for new devices with Oreo. That means, say, with the LG v30 if the bootloader is unlocked, there can be an AOSP ROM on day one of its release.
So instead of Android being strictly a per device compile, it is just a general compile (sans device specific features). However, this doesn't remove the old driver issue. If the drivers in their respective partition no longer are updated by the manufacturer, the later AOSP code will need to be modified to work around these (and accept them). This is still easier in my opinion than the binary blobs.
As for official updates, Project Treble allows device hardware manufacturers to work on updating the device drivers while the OS Dev (Samsung, etc) works on updating their OS. So it is a parallel development instead of a serial one (hardware AND os instead of hardware THEN os).
A question.
Do the Nexus 5X devices have the Treble system or project incorporated with Oreo?
I do not understand the other manufacturers that cheaper excuses are giving, it is true that they are not obliged but I think it would be good practice, maybe they think as before that you will not buy them a phone.
Does someone make a Change.org or similar campaign to ask all Android manufacturers to make a minimum effort?
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