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?
Related
I had hear about cyanogenmod earlier and even tried to install it once when I was a rank noob without much luck. In my recent explorations of kernels and cifs I found myself at the cm site. It seemed pretty organized and I thought it might be interesting to have another go at it. I followed the instructions and installed it and it worked flawlessly. I restored my apps from Titanium backup and I'm up and running. I did some research in our forum and that, combined with some of my own observations, makes me wonder about the relationship between CM and some of the other roms like Vegan Ginger (which I really like) I get the impression that some or even all of our roms here are derivatives of CM that have been tweaked further by our devs. Is this correct? What is the difference between Vegan Ginger for example and CM7? I'm really puzzled because the kernels and the basic look and feel seem very similar. Someone even remarked that all of our roms are derivatives of CM. I'd be interested to know some of the background and the pedigrees of the various roms and their relationship with CM.
Cyanogenmod is one of the more known and talented group of Android ROM developers, developing for many devices and being a large team of dedicated coders, artist, etc...
They have taken the stock AOSP code and have modified, enhanced and added features far beyond the stock code. Most ROMs you see that have these additions are because they are forked from Cyanogenmod's github and then edited to look like their own (different graphic images, different text wording, etc..).
CyanogenMod was also one of the only ROM devs that I know of that got a Cease & Desist letter from Google early on and created the separated config of installing the rom.zip and Gapps.zip (Rom image and Google Apps).
As for how Vegan-Ginger relates...
Project Moving to Gingerbread
January 12, 2011 14 Comments
Just a quick update for everyone so you know where we stand at this point. Because of all the issues I have had trying to reverse engineer fixes into VEGAn, we have decided to move away from the actual VEGA system image. We have decided to move the project to a MODIFIED CyanogenMod 7 (aka Gingerbread) ROM with “inspiration from VEGA”. This will allow us to not only fix issues more easily but our work would also directly benefit the CM7 camp as well. This would give also give everyone the choice of a completely stock gingerbread like ROM as well.
THERE IS NO ETA AS OF YET FOR A RELEASE. When there is one…. you all will be the first to know! Exciting Times Ahead.
-GoJimi
Extreme GingerNerd
Click to expand...
Click to collapse
Hello XDA-Developers.
Some of my friends in the phone/wireless communications business (including a PhD) tell me that custom ROMs are unsafe and there could be written in the code spyware such as keyloggers that can steal your data and do other things of the sort in the background. Cyanogenmod (and AOKP maybe) seem to be pretty safe, and I am running it on my i897, but the Legend is not supported anymore and the latest official ROM I can get is Gingerbread on CM7, which is very slow and seems to have issues. However, I have found these UNOFFICIAL Cyanogenmod/AOKP ROMS made by others:
http://forum.xda-developers.com/showthread.php?t=2353659
http://forum.xda-developers.com/showthread.php?t=2222597
http://forum.xda-developers.com/showthread.php?t=1905588
http://forum.xda-developers.com/showthread.php?t=1562595
2.2 ROM
http://forum.xda-developers.com/showthread.php?t=866849
Note: Don't know if this matters, but all the ROMs save the last were not made by Recognised Developers.
These ROMs (I haven't tried some of them yet) run very smoothly on the Legend and are almost as good as a daily driver.
So can I trust these ROMs because they are based on CM/AOKP but are unofficial, or is the security compromised as it was unofficially done by a member? I would like answers from a technical point of view, not speculation such as 'devs usually have no intent', etc. Don't get me wrong, I may be paranoid, but I truly appreciate the amazing work that devs here are doing, but the possibility of security issues, especially with Linux and open source, is of my concern.
Before we begin: this thread is not about asking for users to comment which is the best rom or which is the worst! I am just asking for suggestions of which roms should I test in order to find out answer on my own.
So, I have had various roms, like neatrom, cm11, omnirom, whatever. The main problem with unofficial roms is instability. So, I am asking for your suggestions which roms should I test out in order to find a rom which is:
stable (very important since most of the roms are very unstable)
as new as possible (talking about android version, not rom's release date)
~good battery life (at least sort of good)
still has support (new releases, updates, etc)
Any ideas?
Recently I have tried android 4.2.2 CM 10.2 stable. It's far from stable: phone sometimes randomly freezed...
Also, tried various kitkat roms. Its obvious why I am no longer using them...
Neatrom / 4.1.2 is extremely laggy (comparing to, for example 4.2.2). So I sort of hate it too.
Rom suggestion threads are also forbidden.
Mod Edit
Word it in any way you like,it is still not allowed.
Please test these things for yourself.
This is the only way you will get an unbiased opinion,and then, you can decide for yourself if it meets YOUR needs.
Thread Closed
malybru
Forum Moderator
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
Is there a reason why every custom ROM seems to go treble? There's no real proven benefit when having unofficial treble. As one of the LineageOS devs said on their subreddit:
You don't get treble. You have it or you don't. All those "ported treble" are plain fake and they don't have the same capabilities of the "real" treble (the one that you have on your device out of the box or from your manufacturer as a stock ROM update).
This because treble requires appropriate changes to the proprietary files (those stored on the vendor partition) that a device without "stock/real" treble won't have
Click to expand...
Click to collapse
There's only one partition instead of both. The one for seamless updates is missing (I think).
As for treble ROMs, they are pretty much a gimmick unless devs actually make use of them. But I have seen reddit comments about people trying out generic system images via treble TWRP: https://www.reddit.com/r/Xiaomi/comments/8ac2gc/project_treble_is_amazing_and_because_of_this_my/
You can try it for yourself: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
What this could mean is, in 2 years if dev support drops for the Note 4, you may still be able to get the most recent version of AOSP or some other ROM as a generic system image. No need to wait around for devs to create ROMs or compile one yourself.