[Q] Need advice on choosing a ROM - Galaxy S 4 Q&A, Help & Troubleshooting

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.

Related

[Q] Note 3 drivers & CyanoGenMod

Dear Note3 users,
I am wondering about buying the Note 3 - however, I am afraid it will turn out the same as with my Note 1 - lack of proper drivers for newer AOSP/CyanoGenMod and the resulting problems (especially - phone reboting when taking pictures and occasional UI stuttering etc.). I remember devs blaming Samsung for not releasing the source-code for the Exynos-based devices back then..
I suppose the current CM KitKat builds are fine with N3 - what about future builds, especially when moving beyond KitKat? Has Samsung done a better job at supporting the N3 and AOSP/CM thus far (when compared to the N1)?
Thanks for all your replies..
Jan
I can't answer your question directly - I don't use CM/AOSP - but I'm interested in the way you asked your question.
I don't see that Samsung have any onus or responsibility all to "support" CM and/or AOSP. As I understand it, they release the source codes for all drivers that they are legally obliged to and no more.
I'm sure the rest is a PITA for CM/AOSP devs, but is that unique to Samsung? Don't Sony, HTC etc do the same?
Personally the only thing I like about CM is the theme choices, and now there are Xposed modules to port many themes to TW based ROMs. If I wanted CM/AOSP, I'd buy a Nexus.
I've nothing against TW framework, it's never let me down, and I've had the SGS/2/3 and Note 2 previously. I don't use the TW launcher, stock icons or stock kernels. I have tried a fair few CM ROMs over the years, and never had a single one that was 100% bug free.
Put it this way - I like stability in my phone, and by definition any ROM that needs nightly builds isn't going to supply that "need".
My 2 cents. Whatever floats your boat is fine, that's why we don't use iphones

Is rapid Upgrades killing Android Development?

Coming from the Epic, and then from the S3, I have noticed the fragmentation of Android with just the dilution of good development.
With that said, I acknowledge I am a user, not a Developer. I've tried to get interested in development, it is just not where my passion lies.
This is one of those useless posts you see on XDA, however, I feel like there is not much going on in this forum so maybe this is the best discussion we could have.
Take Apple, they have one product to focus on, no one to share the spotlight with. Android on the other hand has several, I have no idea how many, to share the spot light with. S3, S4, S5, Oppo, One, name your poison.
I say all this because I remember back to the Epic... It was Epic. The phone was amazing when it came out, the development was even better.
Now that I'm on the S4, while I don't want to take away anything from what the developers on this phone have done, it is not their fault, but developers will flock to where the demand is. And it just doesn't seem to be here.
Maybe this is Sprints fault? I stay with Sprint because they're the cheapest option I have. Certainly not the best, but definitely the cheapest.
Just trying to promote a discussion, not a flame war. Start now.
socos25 said:
Coming from the Epic, and then from the S3, I have noticed the fragmentation of Android with just the dilution of good development.
With that said, I acknowledge I am a user, not a Developer. I've tried to get interested in development, it is just not where my passion lies.
This is one of those useless posts you see on XDA, however, I feel like there is not much going on in this forum so maybe this is the best discussion we could have.
Take Apple, they have one product to focus on, no one to share the spotlight with. Android on the other hand has several, I have no idea how many, to share the spot light with. S3, S4, S5, Oppo, One, name your poison.
I say all this because I remember back to the Epic... It was Epic. The phone was amazing when it came out, the development was even better.
Now that I'm on the S4, while I don't want to take away anything from what the developers on this phone have done, it is not their fault, but developers will flock to where the demand is. And it just doesn't seem to be here.
Maybe this is Sprints fault? I stay with Sprint because they're the cheapest option I have. Certainly not the best, but definitely the cheapest.
Just trying to promote a discussion, not a flame war. Start now.
Click to expand...
Click to collapse
With unified builds, awesome devs are still contributing to our device! Its cool that a talented dev who builds aosp but is with verizon can build for us too. There is no shortage of great development going on, but I'll admit the sprint s4 forums are not as active as I remember the e4gt forums being.
To address your other point, sure - the sheer amount of android devices available will mean the pool of talented devs are spread more thinly across the spectrum of devices, but this community rocks and with a little google-fu (xda helps those who help themselves) I don't think development has really stalled. The forums are just a little less active. What IS a shame is that users here will drive talented devs away from releasing their work publicly on the forums by driving them insane with questions that have been answered 100s of times, petty politics, and flame wars, etc.
But at the end of the day, I would rather have an open OS with a vibrant (or dull) community than a locked down device I can never truly have full control over. But frequent upgrades have always been pushed by manufacturers, at the end of the day profits are the bottom line for them. Thats what is so great about this community, is that the devs here do work that would have gotten them a decent commission or wage elsewhere, FOR FREE. God bless :good::highfive:
All good points, and I would have to say I agree with you, especially with the shame that developers sometimes are driven away by lazy users.
mxmr said:
With unified builds, awesome devs are still contributing to our device! Its cool that a talented dev who builds aosp but is with verizon can build for us too. There is no shortage of great development going on, but I'll admit the sprint s4 forums are not as active as I remember the e4gt forums being.
To address your other point, sure - the sheer amount of android devices available will mean the pool of talented devs are spread more thinly across the spectrum of devices, but this community rocks and with a little google-fu (xda helps those who help themselves) I don't think development has really stalled. The forums are just a little less active. What IS a shame is that users here will drive talented devs away from releasing their work publicly on the forums by driving them insane with questions that have been answered 100s of times, petty politics, and flame wars, etc.
But at the end of the day, I would rather have an open OS with a vibrant (or dull) community than a locked down device I can never truly have full control over. But frequent upgrades have always been pushed by manufacturers, at the end of the day profits are the bottom line for them. Thats what is so great about this community, is that the devs here do work that would have gotten them a decent commission or wage elsewhere, FOR FREE. God bless :good::highfive:
Click to expand...
Click to collapse
I'm not a developer either (well of any roms/android mods at least). But as a long time computer power user and burgeoning programmer (3rd year comp sci major) the development on the S4 is very lack luster. We could get into comparing S4 vs development on older platforms, but I'd rather just discuss the generally bad development in the sprint S4 non-original android dev. forum. Most roms are not suited for daily drivers. I have personally tried 2-3 different versions of Sac's Rom and negalite's rom( as well as 1 try on various other roms) and none was with out major flaws.
The problem as I see it is this: The demand is for the newest rom with the most up to date android features. So as rom developers are getting closer to making a stable working version of their roms, Sprint releases an update at which point most developers switch and start working on new release with out ever making a fully functioning rom. To make matters worse most Rom's are presented as a finished product. Some have a known issues section in the first post ,but I challenge any one who disagrees with me to find a known issues section on a rom that actually contains all the know issues. It doesn't exsist. Instead each user is left to download an unfinished product and only after discovering an issue and digging though 10 pages of forums you find others have the same issue and that there may or may not be a soultion. How f'ing hard is it when a god damn issues is reported to update the orginal post?????? I understand these developers are doing this out of the good of their hearts, but anything worth doing is worth doing correctly. If it is to much work to keep an up to date list of ALL known issues, have one of the roms users do so. Not much work for one fan of a rom to keep list of issues if dev cant be bothered.
You help no one when custom roms break things working in the stock version and present it as a working rom. Custom roms used to add fucntion to a device now, it adds somethings and breaks others. Till this trend changes, the best rom is stock rooted + w/e mod a user desires. When a bunch of things dont work label your Rom alpha when most things work call it beta and only when everything works call it stable. This kind of common sense would improve everyone's experience greatly.
mysongranhills said:
I'm not a developer either (well of any roms/android mods at least). But as a long time computer power user and burgeoning programmer (3rd year comp sci major) the development on the S4 is very lack luster. We could get into comparing S4 vs development on older platforms, but I'd rather just discuss the generally bad development in the sprint S4 non-original android dev. forum. Most roms are not suited for daily drivers. I have personally tried 2-3 different versions of Sac's Rom and negalite's rom( as well as 1 try on various other roms) and none was with out major flaws.
The problem as I see it is this: The demand is for the newest rom with the most up to date android features. So as rom developers are getting closer to making a stable working version of their roms, Sprint releases an update at which point most developers switch and start working on new release with out ever making a fully functioning rom. To make matters worse most Rom's are presented as a finished product. Some have a known issues section in the first post ,but I challenge any one who disagrees with me to find a known issues section on a rom that actually contains all the know issues. It doesn't exsist. Instead each user is left to download an unfinished product and only after discovering an issue and digging though 10 pages of forums you find others have the same issue and that there may or may not be a soultion. How f'ing hard is it when a god damn issues is reported to update the orginal post?????? I understand these developers are doing this out of the good of their hearts, but anything worth doing is worth doing correctly. If it is to much work to keep an up to date list of ALL known issues, have one of the roms users do so. Not much work for one fan of a rom to keep list of issues if dev cant be bothered.
You help no one when custom roms break things working in the stock version and present it as a working rom. Custom roms used to add fucntion to a device now, it adds somethings and breaks others. Till this trend changes, the best rom is stock rooted + w/e mod a user desires. When a bunch of things dont work label your Rom alpha when most things work call it beta and only when everything works call it stable. This kind of common sense would improve everyone's experience greatly.
Click to expand...
Click to collapse
To a degree, I definitely am with you on this. I have been with this forum since the days of my old HTC thunderbolt. There are AT LEAST 5 popular daily drivers that worked worlds better than the stock rom for that phone. My particular phone glitches out on the dialer/phone app for all Original Android ROM's meaning I am automatically limited to a TW rom. I've tried everything to fix this but nothing seems to. However, there is one that works flawlessly, Triforce 5.4. It's perfect, so far as I can tell, but is starting to show its age. It may be the only perfect ROM for our phones but is almost completely without bells and whistles, unlike the Thunderbolt, which you could save multiple working images to SD and restore if you felt like using sense one day, CM the next, and I do recall a few completely custom ones loosely based on CM that worked awesome. Anyway that's my say on it. I am sad NAE firmware capabilities don't have a nice Triforce release to go with it, but the PRL and firmware seem to work great with the ROM, so I guess I'll stick to it, even if it is boring. It definitely does everything I need for it to do. Still, finding the issues with each one and helping the developers is part of the process. It's fun and part of the reason why I do what I do. Take my ASUS Transformer. That thing is old as the hills, but has multi window, android 4.4.3, windowed apps, and all manner of other things and it runs super smooth. timduru is the dang wizard of that device and refuses to let it die peacefully.
arikdahn said:
To a degree, I definitely am with you on this. I have been with this forum since the days of my old HTC thunderbolt. There are AT LEAST 5 popular daily drivers that worked worlds better than the stock rom for that phone. My particular phone glitches out on the dialer/phone app for all Original Android ROM's meaning I am automatically limited to a TW rom. I've tried everything to fix this but nothing seems to. However, there is one that works flawlessly, Triforce 5.4. It's perfect, so far as I can tell, but is starting to show its age. It may be the only perfect ROM for our phones but is almost completely without bells and whistles, unlike the Thunderbolt, which you could save multiple working images to SD and restore if you felt like using sense one day, CM the next, and I do recall a few completely custom ones loosely based on CM that worked awesome. Anyway that's my say on it. I am sad NAE firmware capabilities don't have a nice Triforce release to go with it, but the PRL and firmware seem to work great with the ROM, so I guess I'll stick to it, even if it is boring. It definitely does everything I need for it to do. Still, finding the issues with each one and helping the developers is part of the process. It's fun and part of the reason why I do what I do. Take my ASUS Transformer. That thing is old as the hills, but has multi window, android 4.4.3, windowed apps, and all manner of other things and it runs super smooth. timduru is the dang wizard of that device and refuses to let it die peacefully.
Click to expand...
Click to collapse
I just recently got off heavily modded stock and flashed Super S4 and so far it is awesome. Ktoonz's Kernel is baked in and after using recommended recovery to flash I've had no problems. It isn't heavily modded (mostly other mods baked in and some init.d tweaks) but is fast and stable and is one of the very few TW roms I'd recommend.
When I was on HTC Inspire 4G, There were easily 10 Roms (ASOP and Sense) suitable for a daily driver. For the S4 I'd be hard pressed to find 3 stable usable TW roms at a time.
I think android as a platform is changing a lot philosophically, as well. Older custom roms used to be a must have and were the main reason most users wanted root. Now everything is much more framework centric. Now root is used to add functionality through Xposed framework modules,or audio mods like Viper. Previously each and every mod had to be rom specific.

BEST Galaxy S2 ROMS (GT19100)

Hi Friends.
I have a 3 yr old Galaxy S2 (GT19100) and I must say this is the longest running phone in the history of my Mobile Phone usage. I have been using Mobile phones from the year 2000 and I must say the technology has advanced so far on the last decade or so that at times I find it difficult to match up with it.
The purpose of this thread is to help Galaxy S2 users to find the best custom ROM's for S2 users. (Dev's and testers your feedback is the most valuable)
Personally, I am a fan of Samsung's Touchwiz skin and I have used Wizzedkat, Jellysnap, Revolution Rom etc and I would like to know your views on which Touchwiz based Rom you find the best and why.
I am yet to try the Fusion and I know there are many more Touchwiz based Roms.
I would appreciate your contribution as this will help all those who are looking for a stable Touchwiz based Rom which works great and gets the most out of our S2.
Sorry, but Best ROMs threads are usually not allowed.
So a mod is likely to freeze this thread.
Discussion might be possible if a thread is framed differently than "Best ROM".
That said, particularly with an older device like the GT-I9100 is now, I prefer AOSP ROMs. I prefer KitKat or Lollipop before older stock ROMs most of the time.
And despite what I, or many others, might feel about the situations about CM and CM Inc, CM11/12 and ROMs derived from it are still in the lead as far as popularity goes, though that lead has diminished over the last few years.
I currently have 18 active Android devices I use for testing my Android apps. And all of them has CM or CM derived ROMs available, except possibly for some Sony's if FXP is considered distinct from CM.
Of course my perspective is that of a developer, mostly doing app testing. Individual devices may have ROM's available that appeal more to people who like UI and other "extra whiz-bang" features.
Neat ROM!! Its awesome, just moved over to the 4.4.4 version if neat ROM and its good.
jr866gooner said:
Neat ROM!! Its awesome, just moved over to the 4.4.4 version if neat ROM and its good.
Click to expand...
Click to collapse
+1
you have lost neatrom

funny thing that older moto g's got cyan 14.1 but moto g4 plus didnt

Ok so cyanogenmod.org got all moto devices listed and they said moto g series getting cyanogen 14.1 but moto g4 plus not anywhere in cyanogenmod.org list:crying:
I hate unofficial buggy ROMs
mayank.bhola1 said:
Ok so cyanogenmod.org got all moto devices listed and they said moto g series getting cyanogen 14.1 but moto g4 plus not anywhere in cyanogenmod.org list:crying:
I hate unofficial buggy ROMs
Click to expand...
Click to collapse
Official roms are buggy too if you ever tried nightlies or snapshots. And we will see, maybe official will come until cm statet it comes not
They didn't say all G family, they post this list:
falcon, peregrine, titan, thea, osprey
They are 1st 2nd and 3rd Gen.
FlaminisRex said:
They didn't say all G family, they post this list:
falcon, peregrine, titan, thea, osprey
They are 1st 2nd and 3rd Gen.
Click to expand...
Click to collapse
If it's not in the list, it will be added, thats possible.
@mayank.bhola1:
No need to scared and say it will never come. If you didn't have a proof, don't open such scaring threads "no official cyanogen 14.1" that's really annoying to others, because some people trust it and won't buy the device maybe(just an opinion)
I avoid anything cm based. Always worse on battery life.
trsix said:
I avoid anything cm based. Always worse on battery life.
Click to expand...
Click to collapse
That's not true that all cm based has "always" worse battery life. On my galaxy's I got more battery compared to Samsung roms(official or mod) and also on my other devices cm gives me more battery life then stock, even to aosp! Maybe you encountered bad experiences, but it totally depends on the device tree, drivers, modem, source, etc etc... And the knowledge of the dev :angel:
My experience with CM was that a lot of the features added where useless to me and they just added battery drain and new bugs. And when a bug was fixed in a nightly, there was a good chance that another two bugs would pop up.
Not cool if you really need to use your phone as a phone. Maybe OK if you don't have a job or you stay at home all the time.
SoNic67 said:
My experience with CM was that a lot of the features added where useless to me and they just added battery drain and new bugs. And when a bug was fixed in a nightly, there was a good chance that another two bugs would pop up.
Not cool if you really need to use your phone as a phone. Maybe OK if you don't have a job or you stay at home all the time.
Click to expand...
Click to collapse
So you concluding that we must stick to stock ROMs ??
Depends of what you do for living... and if need a reliable phone line for that.
SoNic67 said:
Depends of what you do for living... and if need a reliable phone line for that.
Click to expand...
Click to collapse
I knew a device which stock cos rom is the hell on earth(random reboots, bugs, freezes) compared to cm and nearly all people saying wow after flashing cm instead of staying on stock. CM is widely available for devices and always a chance to get more out of your device when the manufacturer gives up the development after launching the device or won't fix bugs in acceptable time.
Not the case here. Moto firmware is stable and not bloated.
CM is best after OEM leaves device support. I had Asus Zenfone 5 earlier but no official CM so developers made unofficial one but Asus had serious issues with bootloader unlock as no developer was able to resolve screen freeze issues. So running custom ROMs on that device was hell bad.
If you think making cm and make it official is easy then do it urself, we really want to see. Things are not same as 1st,2nd &3rd. The chipset are way different than the previous gen. So stop posting useless things. Dont open thread for you own satisfaction.
Just my $0.02 : The premise behind getting a custom ROM is that it's for those who have an above average idea about OS, customizations, working on a system level and such.
The whole argument about stability, and what one does for their living is a bit too far fetched in context of using a device that is dependable. Stock ROMs are made by OEMs keeping a novice end-user in view, who may or may not have sufficient time, knowledge or inclination of going beyond what the device came shipped with.
Custom ROMs and development is undertaken almost completely as a voluntary exercise by the devs, mostly on cost of their own resources and go far as to offer their work off forum threads which they'd personally support. Those flashing and modding devices are ones testing the work undertaken by devs, and even after a ROM gets official status, work on development continues with feedback from users and updating security, porting features from other devices, expanding customization et al.
Battery use, smoothness of UI, connectivity, stability, obviously are essential to one's experience of using their phone, but are highly dependent on how well one's put to use the abilities of their custom ROM, apart from what applications or settings one's gotten on, and that would come about only with experimenting, learning and keeping oneself updated with their device's software.
Stock ROMs, barring the few odd ones which run stock Android are almost always crammed with bloatware, uncustomizable UI/features and locked in to a mesh of regulatory compliances, OEM/vendor/third party interests and above all marketing the device as a product - which means you're good to go for just about as long as the OEM cares, and that isn't usually long enough given they'd obviously be focused on selling newer products.
So, it's just that mileage may vary but if you're willing to stick around to learn and experiment, customizing is the only way to truly own your phone.
Sent from my Moto G4 Plus using XDA Labs
Frances91 said:
...
Stock ROMs, barring the few odd ones which run stock Android are almost always crammed with bloatware, uncustomizable UI/features and locked in to a mesh of regulatory compliances, OEM/vendor/third party interests and above all marketing the device as a product - which means you're good to go for just about as long as the OEM cares, and that isn't usually long enough given they'd obviously be focused on selling newer products.
So, it's just that mileage may vary but if you're willing to stick around to learn and experiment, customizing is the only way to truly own your phone.
Sent from my Moto G4 Plus using XDA Labs
Click to expand...
Click to collapse
I think the G4 is close to AOSP. Using Xposed you can get many fancy features found in custom roms. GravityBox gives you much of what CM offers.
Security features make it much more difficult to customize a phone. Pay by phone, i.e. "Wallet" will become important.
Custom roms are used more now for keeping old phones current. Not that much happening with new phones. Look at CyanogenMod https://download.cyanogenmod.org/ to view this.
king200 said:
I think the G4 is close to AOSP. Using Xposed you can get many fancy features found in custom roms. GravityBox gives you much of what CM offers.
Security features make it much more difficult to customize a phone. Pay by phone, i.e. "Wallet" will become important.
Custom roms are used more now for keeping old phones current. Not that much happening with new phones. Look at CyanogenMod https://download.cyanogenmod.org/ to view this.
Click to expand...
Click to collapse
If you're considering using Xposed for the 'fancy features' and use wallet, and yet vouch for stock Roms I'm not sure what you're on to. You'd need for more mods running on a stock ROM which would anyways take months or even years to get updated to run latest Android versions. Some times you'd just stick around with frequent updates which are still two SDK versions behind the current official release, basically cycling through bloat, partner apps and constant rooting, modding to just keep your phone worth it's use.
As for new phones, it takes a fair amount of time, effort and understanding to access available sources and build a device tree from which custom ROMs are built.
Besides, not many users, unless they've specifically bought the new device to work on development, adopt customization till about several months after their purchase. As for CyanogenMod site they list the official ROMs, which are painstakingly built after months of testing. What you see on there are mostly devices which are either usually a year old or are stock Android - both being fitting scenarios for system level modifications to drive both performance and customization. You'd be hard pressed to find Android OEMs updating devices or even offering security patches for long.
Also, do remember MIUI, Oxygen and several other OEM ROMs that run across some of the most successful phones evolved from the custom ROMs community development.
And yeah, there's the custom kernels as well which almost always need a custom ROM.
Unless you've hit upon a groundbreaking counter claim to all the benefit of custom ROMs you would be among a tiny minority of informed users who ascribe to that idea. I would really like to benefit from what you can share about it, I am sure I can hit up the devs in my subscribed threads and help them make better decision with their time and efforts.
Sent from my Moto G4 Plus using XDA Labs

[Dumb Question]

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.

Resources