Do Android Users Still Use Custom Roms? (androidauthority.com)
"With all of the drama at CyanogenMod, Android Authority takes a look at the current state of custom ROM development," writes Slashdot reader Thelasko. From the article:
The future of CyanogenMod appears uncertain, after the open source ROM was forced to fork under the name Lineage OS. Fortunately there are already other remixed versions of Android available, with some of the most popular being Paranoid Android, Resurrection Remix, and Dirty Unicorns... [But] with each new version of Android, the gap between Android and popular custom ROMs has shrunk, which begs an interesting question: Are custom ROMs even necessary anymore?
To answer this, let's take a quick look at the state of custom ROM development as it exists today.
The article points out that mobile virtual reality is "on the verge of becoming mainstream and the wearable market has grown tremendously," asking whether custom firmware will also integrate these newer technologies. But the original submission also asks a question that's closer to home. What custom ROMs do Slashdot users have installed?
The article points out that mobile virtual reality is "on the verge of becoming mainstream and the wearable market has grown tremendously," asking whether custom firmware will also integrate these newer technologies. But the original submission also asks a question that's closer to home. What custom ROMs do Slashdot users have installed?
I have Cyanogen on two devices, and I will ALWAYS have a custom ROM just to eliminate all the damn bloatware. If there are programs on a new device that I can't uninstall without rooting (and there always are) it's time for a reflashing.
Let's begin by saying that the stock ROMs on certain devices have become very adequate. I own a Nexus 5X and a Moto X Pure smartphone, and their stock ROMs are basically a pure Android experience. The software is already lean without any carrier bloat. Everything works fine, except for the times when google's rushed updates may sometimes introduce a new bug. I also run a stock Samsung ROM on my Galaxy Tab S tablet.
On the other hand, there is a considerable cost to using a third party alternative ROM like Cyanogenmod. For one, those third party ROMs don't always support hardware as well as the stock. If you had read release notes for something like a Cyanogenmod release, you had surely run into statements like "limited camera functionality" or "fingerprint sensor, etc".
Another issue with third party ROMs is that some software builders actively block or sabotage them. For example, the AT&T's Uverse streaming service will detect whether you have a rooted or third party ROM and stops working. The Netflix goes only up to 480p resolution on a non-stock ROM. "Fixing" this probably involves editing build.prop and hiding your root, but I haven't tried it recently.
Unfortunately, custom ROMs are still necessary because phone manufacturers, carriers, and even Google itself washes their hands of any phone that is older than about 2 years. Often they stop offering system updates even sooner than 2 years. This forces people to install custom ROMs to keep their phone operating systems up to date.
I don't care what anyone claims -- a smartphone's useful life is way longer than 2 years, so it's unconscionable that these Android companies do this. Compare to iPhones, which are supported for up to 5 years. I have been using Android phones (Google Nexus models) for several years now, but I have seriously considered going back to iPhones because of this and because of app availability.
I rooted my phone to allow me to install apps with root access, then the phone wouldn't let me update while it was rooted, so I installed a custom ROM that would. If I have to unroot my phone every time I need to update it then I might as well just install a custom ROM.