The ROMs section of this forum for Z3C has like 3 unofficial CM12 threads, but none of them have been updated in months. I found the freexperia project website but I can't see where there's any discussion about how close that is to working.
I used CM on my last phone (Galaxy S) since GB and I loved it. I guess I'm just wondering if anything is happening for CM on Z3C and I'm not seeing it because I don't know where to look.
Maybe late but I just open a cm-12.1 thread for z3c.
If possible, open one in our forums, instead forcing z3c-people to go the the z3-forums
Your are totally right, it is a bad way. But I didn't plan to maintain it for a long time. (until Lineage 14.1 get ready) that is why don't open it.
As of every hour and every minute now we seeing new ROMs popping up for various devices now and but seems that the development for our ghost has come to end??
Well something requested by us is simply rejected by the senior members with all due respect.
For example:I recently demanded for a stock like Marshmallow based rom coming with all the special moto features like display,voice,etc.. but they rejected and recommended to try the cm 13 which loses all the Moto functionalities!?
Hence I finally put a request for one more time to build special type of ROMs for our moto devices just like the XOSP(Xperia open source project) and honourable name it as "MBOSP"(MotoBlur Open Source Project).
As much as i would love to have such rom, Moto X is 3 years a old device and I don't think anyone will work this much for an older device. I am using official CM13 by @Megatron007 and it is great. Maybe you should request the devs of existing roms to add Moto functionalities in their roms.
There can't be a Marshmallow stock rom, because there isn't a Marshmallow stock rom to start with.
There can be if built from aosp
LOL no
There can be atleast a stock like!
At this point I just want to have my verizon 1060 bootloader unlocked. I got it after it had been updated with no chance of putting cyanogen on it
I demand a working Nougat rom right now!
Those damn developers should do something to earn those salaries paid by XDA.
minimum a donation xD by users
"For example:I recently demanded for a stock like Marshmallow based rom..."
What are you paying?
Is there a kind of LTS (long term support) ROM that regularly backports kernel and OS security patches? Kind of like a 6.0.1 with January 2017 patch level? I know I can install most ROMs without GApps (Slimroms is probably my favorite) but most of these ROMs base either off AOSP or CM/LOS which also base off AOSP, so when Google stops patching AOSP, these downstream ROMs stop getting security patches.
I don't really care for Android N as I'm perfectly happy with M but would like to squeeze another year or two out of it.
Just curious if such a thing exists; I'm sure it's no small feat to backport security patches, but it's something I'm very interested in to get the most life out of what's still an excellent device. This likely applies to many other devices as well (N4, N5, OPO, others who have been retired for reason other than money).
Edit: I should add that I'm aware of new tags, such as https://android.googlesource.com/platform/build/+/android-6.0.1_r78 but these seem to stop roughly two years out and don't really seem to have a guarantee of when they'll stop being updated. I'm looking to extend that two year mark to three or four years.
Android doesn't do LTS like Ubuntu. If you want to have the most current security updates, you'll have to update to Android 7.1.1. Security updates will continue for another 12 months.
It would be cool if there was a custom ROM that implemented something like this; not necessarily android per se, but sometimes, especially in an enterprise environment this would be a great idea.
mituzora said:
It would be cool if there was a custom ROM that implemented something like this; not necessarily android per se, but sometimes, especially in an enterprise environment this would be a great idea.
Click to expand...
Click to collapse
This was more what I was thinking of. I know Android officially doesn't go beyond ~2 years but that's what I'd like to see changed. Desktop OSes and software sometimes have these long-life versions (as pointed out, Firefox and Ubuntu to name just two) so it would make sense to start doing this for mobile OSes, certainly in an enterprise environment but a "would be nice" is also for older units or people who really don't care about bleeding edge but don't want to be left behind.
I imagine a model similar to Redhat and it's Enterprise Linux distribution which is open source (and then released by the CentOS folks), though in that case Redhat themselves are doing the backporting and patching. Since Google doesn't do that (pretty much the opposite if you look at their rolling releases for Chrome/Chromium) it would have to be a third party responsibility.
It would be a pretty big undertaking and wouldn't solve any issues that would lie in binary blobs typically used for most the hardware, but it could be a base for others to use if they had something a little more open (or as open as a smart phone can realistically be). In case any security research students are looking for a capstone...
Edit: regarding the "not necessarily android" note; I was thinking about this while I was working on an Ubuntu Touch port. I like how polished Android is and that I can even use it sans-Google apps but being strong-armed into the latest version of the OS is pretty silly. I really don't care about anything N brings from M. The step from L to M was huge and M has been rock solid for me, so I would like to see M used as an LTS base. N is just too weird and buggy, even half a year into it. For me at least.
But why would you stay on 6.0.1 which is noticeably slower than 7.1.1 on N6?
I've not had that experience myself; performance has been either the same or slightly worse but that's very subjective. It's not terribly important if 6.0.1 were used as a base or 7.x, I just picked 6.0.1 as an example because of its maturity and my perceived stability over 7.x.
Nope! Google has stopped pushing security updates to Marshmallow so the latest security patch level you will have is December 2016 on any Marshmallow ROM. Gotta switch to Nougat to continue to get security updates.
The only two ROMs I'm aware of that still push M builds are Mokee and AOKP. But again, just because they have compile dates in January of this year, they are still going to have either the November or December security patch. Backporting is too much work and would be stupid for any dev to waste time on.
Nothing is a waste of time if you're learning.
retro486 said:
Nothing is a waste of time if you're learning.
Click to expand...
Click to collapse
Yes, but as a developer you learn more from the latest version, so it makes more sense to focus on it.
Android is not conceived as a LTS OS, it is made for devices which are meant to be used for two years, so it doesn't makes sense to provide security patches for older versions.
If you're really up to the challenge, you should start a LTS ROM project yourself, because based on your response, I think you like to learn, and I think you'll learn a lot by doing it yourself.
Fair enough. And considering my original question about an LTS edition was answered (several times) I'll leave it at that. Thanks!
Well, while not officially that, but I am on MOB31S, which is a 6.0.1 January security patch official ROM. It is currently the official T Mobile ROM. I'm not sure how you would get it if not on T-mobile.
I'm looking for a newer tablet to replace my original Tab Pro 8.4 (mondrianwifi) which has almost no ROM support left and only very flawed 7.1.2 ROMs. How's the ROM support for this tablet? Looking around, it looks like there's mostly lineage and resurrection, with a few others. But since there's official nougat, I'm assuming these ROMs are fairly stable and not too hacky/buggy? This seems like better hardware than the Nexus 9, but I'm concerned about dev support.
This isn't a ROM request. But it's purely a discussion of what users think of this idea for a custom ROM.
I've had a recent discussion and thought of a possible new idea for a custom ROM with a friend.
The Idea
Ever since I've been switching to a custom ROM, the look of it makes me miss OOS 10 before OnePlus changed it to look like OneUI.
Is there a way in which a custom ROM can be based on Oxygen OS 10 or at least a custom ROM that has the same UI and feel? It could also be OOS 11, but there's a reason why OnePlus hasn't released it to older devices as it could still have bugs, but at least OOS 10 which many fans loved.
It doesn't matter if we can't exactly replicate it, but at least have a similar UI and feel. Unlike most custom ROMs that are based on Lineage OS which looks similar to the Google Pixel UI. I just feel that the classic OOS UI is still better.
Implications
Because it's a custom ROM it can have additional features and monthly updates of course. Also, within those updates, it could include monthly security patches which would be better maintained and consistent, unlike OnePlus which some feel that they have lost their touch in recent years. If this idea is developed to become a real ROM, it would be a full ROM and hopefully be better maintained.
What is the impact?
The impact this custom ROM could bring is that, if successful it can be developed for other or older devices and bring the version of OOS that everyone loved to many people. Developing a custom ROM that's like OOS10 that supports and updates older OP devices(OP3/3T, OP5/5T, OP6/6T) would better than how OnePlus supports and updates them.
Conclusion
This is just an idea proposal to all ROM developers and fans of the OP6/6T. I just believe that this could help all those people who love the stock look and feel of OOS but is better maintained with a bit more features with monthly updates and security patches. Plus they can continue to enjoy it for many more years to come. If this does come to fruition it can bring OOS we love back to us and to many more.
Please add any comments, criticisms, and thoughts.
Voting in the poll or adding a like will be great. Thanks.
Credits:
@rayray07
@Extreme_Ninja2099
First comment