Related
Last night, +Steve Kondik took to twitter to vent a little bit:
"CM has been getting a lot of crap lately for taking so long with a release. Guess what? It's not that easy. We don't just call something stable unless we mean it. *Also, RC1 is soon!* The most stable devices will get the RC first. The system we've put in place should allow other devices to catch up quickly. More details later this week "
Now to combat the obvious questions:
# As Steve stated, this will not be for all CM9 supported devices. The Nexus S and Galaxy Nexus can be considered safe bets, but the final list won't be available until release day.
# As always, the proper day of release is difficult/impossible to predict, but we anticipate a code freeze going in place tomorrow at the earliest.
# Yes, this means we will actively be running two separate RC phases (CM7 and CM9). Bug's should be reported to the issue tracker once the release is made, not in the comments on our posts.
# There has been a lot of talk surrounding Linaro in CM. While CM 9.0 won't ship with all the patches on gerrit, quite a few of them are already incorporated and others are sane enough that they will likely be there. There are still some issues surrounding the updated gcc used for the Linaro patches that don't play nice with AOSP.
# Nexus One: For the time being, the N1 will not be supported. We can get it to build/boot/run, but the hacks required break Google's CTS, so until that is rectified, you won't see any build with CM's official stamp of approval.
CM9 News
And from a followup a few hours later:
******
+Ricardo Cerqueira sat down with XDA recently for a developer interview
To piggy back on our comment about the N1 and CTS, Ricardo describes why we don't just shrug off that requirement.
Because it opened a can of worms that can’t be closed again. Getting it to work needed some very ugly workarounds that directly go against Google’s compatibility document for ICS. An app developer targeting ICS as a minimal version for his apps has the right to expect some functionality to be guaranteed on a device that claims to be ICS, that wasn’t (and isn’t) true for ICS builds with these hacks. That’s one the main reasons CM9 does not officially include a bunch of devices that are “working.”
...and some users understand that, but a lot don’t, and they’ll submit error reports on those apps, or they’ll rate it badly at the Play store. This is not a hypothetical scenario, it has happened whether we like it or not, asked for it or not, CM’s userbase is large enough to matter, even if you don’t count derivatives. We have a responsibility not to cause that kind of grief to app developers and we did. With all the mostly bull**** talk about fragmentation, we actively contributed to a break in the platform, no matter how small. That’s not a good thing :X People SHOULD know these builds contain hacks, but you’ve surely realized by now that they don’t
******
dookie23 said:
....so until that is rectified, you won't see any build with CM's official stamp of approval.
Click to expand...
Click to collapse
so.... is that ever gonna get rectified
charlie_su1986 said:
so.... is that ever gonna get rectified
Click to expand...
Click to collapse
I wonder what are the hacks he mentioned in the post. Was it the hboot hack, m2sd hack or swap partition...etc?
what is all the fuss about CM9 not releasing a rom officially when we have quite a few talented devs that have already given us the choice of running a near perfect ICS Rom on our nexus one?
EDIT: BCM offers CM9 features, AOKP offers us users the choice of AOKP features and texasice rom has a twist of its own features to. I do not see a problem with CM not releasing an official rom
Kannibalism said:
what is all the fuss about CM9 not releasing a rom officially when we have quite a few talented devs that have already given us the choice of running a near perfect ICS Rom on our nexus one?
EDIT: BCM offers CM9 features, AOKP offers us users the choice of AOKP features and texasice rom has a twist of its own features to. I do not see a problem with CM not releasing an official rom
Click to expand...
Click to collapse
Don't get me wrong, I love seeing the talented devs make awesome progress on kang'ing CM9 and things are coming together nicely. What I am getting at is not whether Cyanogenmod is releasing a CM9 rom officially for the Nexus One, but it's what Ricardo Cerqueira said about the hacks breaking Google CTS. This could mean that apps might not run or worse yet, FC's for no reason.
Now, the real questions are, what are these hacks Ricardo was talking about and is that gonna get rectified?
the hacks they talk about could be small stuff like ta camera fix etc since vendors do not always release new drivers.I would say that the nexus one is using a few hacks for drivers in order to make everything work better
I suspect it's a combination, both messing with HBOOT partition sizes (which is not a *bad* thing, but involves a lot more risk than just flashing a new ROM) and the nasty driver hacks that the poor dev's have had to do to try to working around the lack of a Broadcom driver, since they saw fit to release neither a driver nor sufficient documentation. It's hard to see how either could be overcome for an "official" CM9 release. I feel like it's a bit of a chicken and egg problem; with sufficient dev attention things could probably be brought into acceptable shape, but unofficial ports will never have sufficient dev attention.
Disclaimer: I really appreciate all the work that's been done by everyone on all the community ROMs. It's a hard, often thankless job, whether you're debugging mystery driver issues on an older phone or trying to coordinate a release for dozens of different devices with angry, impatient fans. While I'd love to have an official, flawless ICS ROM, at least we get more love from the community than we did from Google
decoherent said:
I suspect it's a combination, both messing with HBOOT partition sizes (which is not a *bad* thing, but involves a lot more risk than just flashing a new ROM) and the nasty driver hacks that the poor dev's have had to do to try to working around the lack of a Broadcom driver, since they saw fit to release neither a driver nor sufficient documentation. It's hard to see how either could be overcome for an "official" CM9 release. I feel like it's a bit of a chicken and egg problem; with sufficient dev attention things could probably be brought into acceptable shape, but unofficial ports will never have sufficient dev attention.
Disclaimer: I really appreciate all the work that's been done by everyone on all the community ROMs. It's a hard, often thankless job, whether you're debugging mystery driver issues on an older phone or trying to coordinate a release for dozens of different devices with angry, impatient fans. While I'd love to have an official, flawless ICS ROM, at least we get more love from the community than we did from Google
Click to expand...
Click to collapse
I agree with this post i would put the blame on google for not pushing the vendors for the broadcom drivers since android is open source after all but once again great works by our devs and thanks for letting us experience the latest versions of android on our devices
EDIT: i must admit that i have better devices to use than the nexus one but the community keeps me coming back for more
Sent from my Nexus One using xda premium
Hello.
I need advice/suggestions on choosing a Rom for my Samsung Galaxy S 4 (I9505/jfltexx). What I am looking for is a ROM that is stable and actively maintained with regards to bug and security fixes, preferably AOSP based. I have no need for neither all sorts of bells and whistles, fancy eye candy nor bleeding edge features. Rushing to the latest major android version is not a priority, having my phone fully working is, though.
Here is some "background data" om me in the hope of providing a more complete picture of what I am looking for based on my previous use/experience.
I have owned 3 android capable devices. HTC Legend, Samsung Galaxy SII and Samsung Galaxy S 4. One can argue these have been poor choice of devices but it is what it is. I have been running mainly Cyanogenmod since 6.1 I believe on all devices. Fact is, flashing CM has been one of the first thing I have done after buying a new device as I tend to "gag" on HTCs and Samsungs firmware. The first few years I used to tinker about with the devices a lot, flashing stable, RC, milestone and nightlies, different ROMs/kernels frequently but always found my way back to fairly default CM. It has been a bumpy ride on CM (yes, I realize this is in part due to my choise of devices) and while I am not here to lash out at CM in general, recent choices from the CM team and increasingly inconsistent support for my current device leads me to looking for alternatives while really appreciating the sheer amount of great work the CM team have done over the years.
So, what drew me towards CM in the first place? Well, mostly the flexibility/customizability of the ROM and the power/control I felt I had of it, the openness of it and what once was an active, positive community around it. Admittedly, SenseUI and TouchWiz probably pushed me towards it as well. The most recent year or two I have moved a bit away from tinkering and have had a higher need for a stable and maintained ROM that "just works".
I had decided to go for OmniROM, it seemed to be a decent alternative but I am under the impression that my device is no longer supported. Have been considering CopperheadOS as well.
Anyway, I am open to suggentions.
Cheers.
Slimsaber and Slim roms are constantly updated. They are also mantained by the same developer.
Resurrection Remix. I use this rom for some time and I have no issues. But this depends from phone to phone.
It is pretty feature rich.
The GPE rom is also a good choice. But GPE 5.1 is still pretty new and may not offer a stable and bugfree experience. You might want to try GPE 5.0, but it is not mantained anymore, since the move to 5.1.
There is a pure AOSP rom. It's basically the same thing you find on a nexus device.
Hello Guys,
welcome to the world of Team-Exodus.
What is Team-Exodus ?
We are a small group of entusiasts that like to learn more about Android and the Android-ROM developement.
We aren't exactly beginners But there is still room to learn more (you never end learning).
What is Exodus-Rom ?
Maybe, we better should start, what Exodus-Rom isn't: It isn't a (semi)professional mainstream ROM like CyanogenMod,AOKP or similar Roms. We don't focus on buzzword features, nor are we into "bling bling" options. We don't need a "change clock color" option, just because we can do it. These are "low hanging fruits", something nearly everybody can do, who has a computer to compile Android.
So what is Exodus-Rom, what is our focus on ?
We mainly focus on learning how things can be done. We are more into "quality over quantity". We prefer to have 4 or 5 real good and stable working features and not 20-30 features that work... somehow... sometimes...
We want performance, a fast, smooth fluid UI, a real good user experience, not a overbloated kang rom.
For instant that's the main reason why we currently don't have a Marshmallow Rom online, but I will give you a little more information regarding Exodus-6.0 (marshmallow) later.
But before that, who are we, who is "Team-Exodus" ?
The core team of "Team-Exodus" consists of the following guys:
@PrimeDirective - Dave, a very talented developer from the US, founder and Team Leader of Team-Exodus, specialist in App developement (for instant our Exodus Updater or the Drop Wallpaper App) and also our specialist for in deep functionalities of the Android Rom (like a complete rewritten Navbar customization). He currently uses bacon (Oneplus One) and Flounder (Nexus 9) for developenemt
@Raja.M - Raja, a real nice guy from India, he is our java specialist, he started Android developement something link 6 month ago but his knowledge is fast growing. He developes on the bacon (Oneplus One)
@TheCrazyLex - Alex, a kernel specialist from germany, he joined Team-Exodus like 3 month ago, mainly responsible to optimize and unify our kernels where possible. He also uses the Bacon (Oneplus One) as developement device.
@usmcamgrimm - Adrian, our graphics and theme specialist. Beside his amazing wallpapers, he is also responsible for all our LGE G3 devices. He mainly developes on the VS985.
@Martin_Ro - myself, Martin, also from germany, mostly responsible for the server with the build system, gerrit and download page. I'm also developing here and there if I find some time as I'm a married guy with to young boys. I'm developing on shamu (Nexus 6).
But beside this core team, there are a lot more ppl that help us making the Exodus Rom as amazing as possible, I will add some more of them step by step
So, now, back to Marshmallow and why it takes so much more time to bring an Exodus-6.0 to you guys:
For this to understand, you need to know more about where we come from.
On late 2014 we (Dave and Me) parted from VanirAOSP (that wasn't really AOSP but also used CM as base at that time btw) because we feeled like it started to get more and more into that mainstream "feature count is everything".
With 5.1 we started to directly use CyanogenMod (cm-12.1) as base, but was somewhat annoyed by upcomming issues because they used their open source branch as testfield for unfinished stuff, so for 6.0 we decided to go as near as possible back to strict AOSP.
But a matter of fact is: With strict AOSP you aren't able to support every device, and not as many devices as we want to support. So we have had to make some decisions and try some stuff. In the end we started developing Exodus-6.0 with a Mixture of strict AOSP and CAF as base, with the really amazing wide support of CyanogenMod regarding devices.
But with this, we got back to one of our main concerns: CyanogenMod is doing a fantastic job regarding device support (nobody can beat them in that department) but they are cluttering their stuff more and more. In the past few month, they started to create their own SDK, their own framework. And their SDK started to grow like a octupus, sticking his arms into every aspect of android. But we don't want to use their sdk, so we needed to remove it from everywhere.
And that was, what took so long. We wanted the device-tree and their hardware layer, but not their feature, and for sure not their SDK. And removing that stuff from everywhere inside the device-trees and Hardware layer.
Also we needed to use some of their code stuff in various places to make the connection between our AOSP/CAF based ROM and their hardware/device stuff.
So that took us nearly a month to finish up, but now we have first working experimental builds for bacon, shamu and VS985 so we can go into the real developing stuff.
There is still a lot to do (bring back all the features we want to, make the rom that fluid that you might be used to from EXODUS-5.1 etc.) But the real hard part is done now and we are way neared to a first public beta. Depending on the time Dave can find for Exodus (he is really really busy currently because of a new job), we expect to have a public beta by the end of the month...
So stay tuned and be patient
Made sticky
Hello! I enjoyed the 1/2 of the core team's and the new teams work since JB VanirAOSP to Exodus .
Just wondering, it would be cool to say what you do to seperate you guys from the rest. I know you guys build with jdk8 instead of jdk7 for the lollipop builds and use Linaro with some optimization flags.
I'd like to know if you do more than that and also I am wondering how JDK8 especially helps with optimization.
If you need a tester for bacon. I'm here very big fan of 5.1.
Nice to hear the updates... waiting patiently...
Sounds like the beta will become a christmas present.
Gesendet von meinem Nexus 5 mit Tapatalk
big fan/user of Exodus 5.1 on falcon. out of all the LP ROMs i've tried this has to be one of the most stable and lean ROMs out there. love the amount of essential customization catered here and skipping of cliche features that no one bothers to use (atleast me).
big thanks to @sachoosaini for introducing me to the ROM.
Well here it goes on
@PrimeDirective always a great human and great developer who supported Falcon despite the fact that i can never able to contribute the device to you. I find a best buddy out there who will always be my friend... Now @koshikas thanks Dave for supporting this phone, i never did anything for exodus.. But i am committed for future. If Dave continues the journey for exodus i will be with him in all way... Well what he told me around 6-7 months back is now coming to the real world. Now they support falcon or not. But I am honored by Dave for being there with all the silly questions people ask in community, falcon has great life indeed now its upto the team they develope for it not. I will donating device as soon as I am getting my salary which i am for sure going to get soon..... Wish Luck to exodus....6.0 is on the horizon
If you need a tester...
Hey, if you guys need an experienced tester for bacon, look no further. :good:
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I'm with this guy
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Coolkid90 said:
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Click to expand...
Click to collapse
Hm, ok, might be, because english is not my mother language, but for me this sound like "too much drugs and not enough sleep"....
Oh, and by the way:
we just prepared the open source manifest so you can start contribute
I will write a short Facts thread for Exodus-6.0 so you know how to build, and what we changed regarding device-support...
Excelente
Looking real forward to Exodus MM!
sir I am with you here.
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I m new here and wish to get some knowledge from senior member.
Thanks for this great rom
Exodus seems cool... hyped for MM release!
delete : found it
"err on the side of kindness"
Hi guys
Only to keep you informed: We started publishing official release builds for Exodus-6.0.
Look into your devide Android Developement sections for more information or on our g+ community: https://plus.google.com/communities/106801227383087889476
Dear Devs,
@TheDarkStrix @TheStrix @Umang96 @poad42 @thinhx2 @srisurya95 @Santhosh M @psndna88 @dadi11 @xyyx @abhishek987 @Sudeep Duhoon @warlord_rk @minz1 @Ashish0077 @Bitti09 @Vatsal @rocknegi @AmolAmrit @Shivam Kumar Jha
Tens of thousands of RN3 users owe a big thanks to you. You are the reason why many of us buy a new device and unlock it the very next day, root it and flash TWRP. You are the reason why we get the latest software. (Using assistant on RN3, nougat, DT2W, Quick Charge, CPU Governers etc).
I dont disrespect you. I cant cook ROMs, I cant force you to make anything for me.
I have owned 3-4 devices in last few years and have been a diehard fan of custom ROMs.
My observation is that in case of all the devices, its a common theme over XDA that each team is developing their own ROMs. But from a users point of view, it is a dilemma. . You choose one ROM and loose some features of another ROM.
In case of RN3, with Linage & AOSiP, Volte is working out of the Box.
RR is the best ROM in terms of customization, but its a nightmare to get VOLTE working on RR (Flash MIUI, get your phone wiped, wait for 30 minutes to boot it up, use some 26/11 build).
You pick up AOSP and you again miss out on customization.
RR is based on CM but still very different from Linage.
Linage is pretty much barebone.
The problem right now is Lack of XPOSED, with xposed, it was very easy to get the customizations. To name a few, network speed indicator xposed module, Download Progress Bar, Block Google Ads etc.
So without XPOSED, we depend on you for the customizations.
Someone has VULKON, Someone has OMS, for some camera works better.
AOSiP gives the best LTE signal strength,
with linage, you cant turn off fingerprint sensor vibration (I use VibraFix app from play store to disable fingerprint vibration and make it snappy).
So its a thought, from an end user. (Always people start making negative comments and ask moderator to take the thread down, dont do that, positive feedbacks help sometime).
My request is, why dont you guys collaborate in a better manner on a common GIT. You can build your own ROMs, and yes you use each other's fix, and yes you compete with each other at one level, that see, my ROM is best.
I see comments like, camera is buggy, use Google Camera, so why not include Google Camera in the original build along with Snap Camera).
We can get a very good ROM if you guys work together. Why cant we have this forum to share your views, roadmap, issues summary here along with on GITs & REPOs as normal user never goes there.
Some people say they need source code from xiomi, but with same resources available to everyone, why the outcome is different.?
For example, if vulkan is better then why cant every rom can have it.. why not everyone can have OMS. If one DEV can get it working with same available resources then why cant the other one..
What is the fun in making a new custom rom where the only difference is a few names in build.prop and a different boot animation.
Xiomi is using multiple camera and fingerprint sensor, but there must be some way to figure out sensor names.. eg for fingerprint one can check if its goodix or FPC.
So dear devs.. you are superman and batman in individual capacity.. but come together to form the justice league.
Please build a larger team, work together to include all possible features in a single package.
Regards.
-A fan of XDA ecosystem and a user for whom you work so hard.
hi, i using kenzo with goodix fp, only have 4,5 custom rom, i want make rom for it but my server i bad, it make rom about 7 hour for 64 bit devices, 32 bit is normal, i no have time to make some rom for it
1, rr,aosip,... i dont care features of it, simply i love sony ui- xosp i make it for kenzo
2, i dont know c,java,android launguage, i dont make apk, i no use mod
3, i hate redmi devices many camera company, fp company this is reason why camera f.c, only camera font work, dont connect to camera,...
4, i like vibrant when i touch to fp
5, if we are make i github with all repo, i will like trash, really
6, now,i want comeback miui to take picture with my girl friend but setting f.c because dont find device(few mounth ago, i enable find device)
7 i dont care camera, i just use kenzo for play game
sorry, my english very bad
Nice effort.
Read the complete post, NIcely written. I agree with what you've written. Let's see what happens. I would be really happy to see a ROM that has the best of all roms combined.
I would also appreciate if somehow someone can bring MIUI Apps to our custom roms as some of the apps like CALC, MiRemote and all are really good. Especially the default MI file explorer which has hidden folder. I know CM Explorer also has a secure storage but I feel that MI's explorer is better. :Excited:
All roms and kernels here have open sources and all devs try to make Kenzo better all the days, in relation at the possibility of each, try to ask the at xiaomi to open open their sources the reverse engineering is not simply to do...After you can build your rom with all features that you want
Weeeew
A good move!
gynsharma said:
Dear Moderator, I understand that it is in a wrong section, but this is the only section which has the visibility, I hope it stays, its high time when we stop removing positive requests from XDA.
Dear Devs,
@TheDarkStrix @TheStrix @Umang96 @poad42 @thinhx2 @srisurya95 @Santhosh M @psndna88 @dadi11 @xyyx @abhishek987 @Sudeep Duhoon @warlord_rk @minz1 @Ashish0077 @Bitti09 @Vatsal @rocknegi @AmolAmrit @Shivam Kumar Jha
Tens of thousands of RN3 users owe a big thanks to you. You are the reason why many of us buy a new device and unlock it the very next day, root it and flash TWRP. You are the reason why we get the latest software. (Using assistant on RN3, nougat, DT2W, Quick Charge, CPU Governers etc).
I dont disrespect you. I cant cook ROMs, I cant force you to make anything for me.
I have owned 3-4 devices in last few years and have been a diehard fan of custom ROMs.
My observation is that in case of all the devices, its a common theme over XDA that each team is developing their own ROMs. But from a users point of view, it is a dilemma. . You choose one ROM and loose some features of another ROM.
In case of RN3, with Linage & AOSiP, Volte is working out of the Box.
RR is the best ROM in terms of customization, but its a nightmare to get VOLTE working on RR (Flash MIUI, get your phone wiped, wait for 30 minutes to boot it up, use some 26/11 build).
You pick up AOSP and you again miss out on customization.
RR is based on CM but still very different from Linage.
Linage is pretty much barebone.
The problem right now is Lack of XPOSED, with xposed, it was very easy to get the customizations. To name a few, network speed indicator xposed module, Download Progress Bar, Block Google Ads etc.
So without XPOSED, we depend on you for the customizations.
Someone has VULKON, Someone has OMS, for some camera works better.
AOSiP gives the best LTE signal strength,
with linage, you cant turn off fingerprint sensor vibration (I use VibraFix app from play store to disable fingerprint vibration and make it snappy).
So its a thought, from an end user. (Always people start making negative comments and ask moderator to take the thread down, dont do that, positive feedbacks help sometime).
My request is, why dont you guys collaborate in a better manner on a common GIT. You can build your own ROMs, and yes you use each other's fix, and yes you compete with each other at one level, that see, my ROM is best.
I see comments like, camera is buggy, use Google Camera, so why not include Google Camera in the original build along with Snap Camera).
We can get a very good ROM if you guys work together. Why cant we have this forum to share your views, roadmap, issues summary here along with on GITs & REPOs as normal user never goes there.
Some people say they need source code from xiomi, but with same resources available to everyone, why the outcome is different.? For example, if vulkan is better then why cant every rom can have it.. why not everyone can have OMS. If one DEV can get it working with same available resources then why cant the other one..
What is the fun in making a new custom rom where the only difference is a few names in build.prop and a different boot animation.
Xiomi is using multiple camera and fingerprint sensor, but there must be some way to figure out sensor names.. eg for fingerprint one can check if its goodix or FPC.
So dear devs.. you are superman and batman in individual capacity.. but come together to form the justice league.
Please build a larger team, work together to include all possible features in a single package.
Regards.
-A fan of XDA ecosystem and a user for whom you work so hard.
Click to expand...
Click to collapse
U have made a really good move by posting this! Everything u have written is really appreciable! I'm waiting for response of developers on this!
Good message. I really wish for a world like this. However, I do know a tiny bit more than you although I cannot code or build ROMs. Correct me if I am wrong but AFAIK, The "Official builds" have to be official and so must come from the lineage team or from the slim team etc. You take the code base, put on your blobs and other stuff and compile it. So, there are going to be differences in the code base and so the build varies from ROM to ROM. Lineage is built on CM which had a policy that build them the minimal independent self-sufficient system that works. So, you get CM apps and thats it. Slim says give them a bootable system. They leave it to the users to add the apps they like. Resurrection Remix says that you want features, I have dumped them all here. So, you can't ask them to have a uniform codebase.
On the other side, there are the blobs which they source from different places and so once a dev tests one blob and finds it amazing, he can share it with all the others and things will be awesome. But that is where the good news ends. Once the dev uses a blob and it has some conflicting code with some package, he makes modifications and the chain of things he did is hard to keep a track of. The other dev was approaching a different way and so he will not agree to all the chain of modifications as it breaks things for him.
Bottom line:- It is a messy world out there. But the idea is still plausible to a great extent. My two cents of advice is that, one dev please volunteer and make a fully featured ROM with features and reviews cherry picked and stuffed. And while you are at it, please include AROMA installer so that people who like substratum or Vulkan or other things may choose it and the others leave it.
@aveemashfaq
i have too thought one month ago about aroma customized post installation toolkit .i made it for my personal use as it has included all vulkan,volte,hd icon diseabler(thanks to sudeep duhoon),custom popular kernels ,osmosis scripts (wonderful person)selected gapps ,user apps ,agni toolbox stuffs and many more like a cherry picked boot animations,ringtones ,fonts etc but i cant post it publically with some reason .
I have been on cyanogenmod slash lineageos since "day one" galaxy s3 (for me). So now I studied information technology by myself and asking myself: Which "fork" of lineage/cm makes sense with this device, i love this community with all the diversity of roms and stuff - actually waiting for that los15 release :3
anyway, what rom do you recommend for security, stability and not that much customizability (as in: a overall slim rom)
I want to elaborate this question: I always felt quite "insecure" giving an unknown developer the "control of my device"; I simply relied on that "master"-cm/los-community since its the biggest and all other roms kinda "depend" on them.
Thank you in advance guys, you rock! x
What's wrong with stock?
See this is what I don't get. People just flash away without giving stock a go, but then will complain this or that doesn't work.
Sometimes you have to. Oppo is a good example. ColorOS is always so out of date and they have so many bugs but the Axon is on Nougat with the possibility Oreo will come. You can leave it un-rooted and encrypted and not fiddle with it. Android pay will work, it's Google Certified and you can apply updates when you like.
I agree but what's with those zero day exploits? With cm/los I essentially just flash the latest nightly straight away which is "latest android"+fancy ****+open source. Yes, at the end of the day I might unroot my smartphone, encrypt it and that's it.
I just panicked with all those zero day exploits which may take months for OEM to get fixes certificated, affecting "essentially 99 percent of android devices"[sic!].
jojofreddy said:
I have been on cyanogenmod slash lineageos since "day one" galaxy s3 (for me). So now I studied information technology by myself and asking myself: Which "fork" of lineage/cm makes sense with this device, i love this community with all the diversity of roms and stuff - actually waiting for that los15 release :3
anyway, what rom do you recommend for security, stability and not that much customizability (as in: a overall slim rom)
I want to elaborate this question: I always felt quite "insecure" giving an unknown developer the "control of my device"; I simply relied on that "master"-cm/los-community since its the biggest and all other roms kinda "depend" on them.
Thank you in advance guys, you rock! x
Click to expand...
Click to collapse
LineageOS and ResurrectionRemix are the best 2 ROMs for this phone in my opinion.
Keep in mind you can use the stock camera to not lose picture quality.