If you see the Development board, you can see the same developer creating "XXX ROM", and releases a couple of updates for it for a while, and then abandons it, and then creates "YYY ROM", and releases a couple of updates for it for a while, and then abandons it, too, and then creates "ZZZ ROM", and so on. Of course, those ROM's are incompatible so you cannot just update from "XXX ROM" to "YYY ROM".
I know that creating a ROM and maintaining it for free is a time consuming, laborious task, and I can completely understand it if developers abandon a ROM and no longer create updates. But why create a new YYY ROM, instead of updating an existing XXX ROM from 1.1 to 1.2? Isn't that a more difficult & time-consuming work to create a new YYY ROM than updating XXX ROM 1.1 to 1.2?
Diversity. Each ROM offers a different set of extrafeatures. Another question could be, why don't rom developers join into a master project for creating a unique rom with all the pros and none of the flaws
Related
HD2 new rom finished? Any new ROM will build?
Window Mobile is no longer being worked on.
If you are a keen user of this OS I would just install one of the great custom WM ROMs & just enjoy it while you have hardware to support it.
Hopefully given time Windows Phone or Android will get down to making serious user innovation of a OS rather than usual hassle with minimal configuration, lacking obvious simple functions & constant UI changes that benefit no one ...
Moved to proper forum.
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
Hey guys, I was recently installing a new ROM and kernel on my Nexus 6 when I happened upon something interesting. Franco makes an AMAZING kernel for Nexus devices, and he has an awesome app called FKUpdater which checks his server for new updates to the kernel, provides the user with the changelog for that update, then allows the user to either a) download the zip file for the kernel, or b) download and auto-flash the kernel zip.
I thought this was especially smart because it works regardless of what ROM you're on, since we all know how difficult it can be to stay up to date on both the ROM and the kernel, not to mention any other mods that we like for your phones (thinking back to the pre-Lollipop mods like Xposed, etc).
So, what if there was a way to make a ROM OTA manager, which could check for new versions of your ROM using something as simple as an RSS feed that developers could reference using the build.prop.
Here's the way I imagine this working:
A ROM developer doesn't want to go through all of the unnecessary hassle and costs associated with implementing the OTA features (it's not as easy as it might sound), so instead the developer simply adds a line to the build.prop:
ro.customROMversion.rss=http://www.example.com/rss
This build.prop line would be universal for all ROMs, with the actual RSS link being associated with each specific ROM (so if a development team builds ROMs for multiple devices, they would have one feed per device).
Then the app would check the build.prop for that line, and regularly check the RSS feed for updates. The RSS feed would have a standardized format. It would include the necessary information for the app to detect a new version (version number, build date, etc) as well as including the changelog for the new version (if the ROM developer includes this).
In reality, this wouldn't be difficult at all, and the best part is that the feature could be added in a heartbeat to practically every ROM out there. The ONLY issue I could see running into would be that the download links for the ROMs would (potentially) need to be direct downloads, with no redirects. I don't know how important that would be to implementation, though.
Does anyone see this as being something particularly difficult to do? I would love to build/release this (I REALLY wish I could contribute more to the Android community at large), but I don't know how to program something like this. If anyone thinks they could do this, I would really love to help put this in motion!
Hi! I have the Nexus5X and even though there are a lot of ROMs for the 5X, I don't really like any of them, so I was wondering how I would go about creating my own ROM. To start this off, I want this ROM to be a viable option for 5X users, a "legit" ROM, and I do not want to use a kitchen.
I do have previous Android building experience. Since I can do that, I want to know a couple specific things about making a ROM suitable for daily use.
First of all, how do I include the latest security updates from Google?
Secondly, how do I get OTA updates for my ROM(like AICP has an AICP OTA app)?
Thirdly, how do I know which revision to sync (r1, r2, r13) etc.
Fourth, are there any other things that I need to keep in mind when building this ROM and making it like other ROMs in the sense of stability, professionality etc (I can't really explain it, just that it's not simply someone adding random features)
Thanks
Hello, so this is a developer oriented thread, so please refrain from answering if you aren't well informed on the subject matter as to avoid cluttering it up.
I've been wanting to ask what the reason of using FBEv1 still in most ROMs is instead of FBEv2 (Starting Android 11). FBEv1 is less secure and is no longer recommended by Google starting 11. Most ROMs are AOSP based anyways, so preserving compatibility with the stock MIUI ROMs in my opinion isn't a valid excuse. Lineage has shown that FBEv2 works just fine on the device. This also creates segmentation between user groups as now part of people are on FBEv1 ROMs and the other part is on v2 making any simple transition impossible without a wipe and making recovery compatibility hell.
Shouldn't we be adopting the newer more secure standard on any non MIUI based ROM for obvious reasons? Especially since going further, newer and newer android versions will eventually leave FBEv1 deprecated.
I'm not meaning to attack or defame anyone here with this, moreso raise the question and hopefully get some developers to switch to FBEv2 in their next release.
+1 I have the same question too. Why not adopt FBEv2?