Why do most newer phones other than pixels have little to no support for custom ROMs ?
I know that most customizability features that were once exclusive to custom roms are available for use right out of the box these days.
In the case of manufacturers like Samsung, I think,there are still no official builds of lineageOS for the newer phones after the galaxy s10 series.
I'm aware that GSI roms are available. My experience with GSI's have been kinda bad. Most of the time they lack a lot of features which makes the phone not viable anymore. Then there are also the random UI bugs, which frustrate the hell out of the user.
I miss the old days when there were lots of custom roms, even for budget devices. I used to flash them when my phones were out of warranty. I could use my phone however I saw fit.
Is there no way to bring back these good times ? Or will the whole custom ROM community just shrink to the pixels and a select few devices ?
In many cases, because manufacturers refuse to allow unlocking of bootloaders. In other cases, because manufacturers refuse to share drivers for proprietary hardware.
It just feels like I don't need custom ROMs anymore. Nowadays, most phones already do what I want them to do. I used to be pretty deep in the custom ROM community, but nowadays I don't even think about rooting my phone.
I guess the only use case for custom ROMs is the privacy aspect. But most people don't care about it, so the support is abysmal.
Biggest reason is prices of phones have gone up so people are holding onto them for longer with how much more expensive future replacements will be. But, the phones outlast the security updates,which is when roms come into play.
I used to install custom roms all the time back before knox on Samsung, now I cannot be bothered, usually something in the roms does not work among other bugs, it takes too long to keep up to date on rooting stuff etc, the support for roms is abysmal. I started to lose interest around the time banking apps started detecting root and not working, there were ways around it with magisk but it was complicated and could not find decent documentation on it.
It just became simpler to use what's out of the box and the newer phones I started buying had very little in the way of custom roms to start with.
And that is the goal - make it such a pain in the ass to go with something that won't track your every decision that we all give up because it is easier.
At least LineageOS with or without MicroG is fairly simple, with auto-updates in many cases. Once you get past Knox and install twrp, it's easier.
GSI builds are generally easy, too, if it's well maintained. I like Andy Yan's ROMs.
If the recent drama with the former lead dev of GrapheneOS is any indication, putting our trust in a singular entity in charge of custom ROMs is also risky.
Good to know that graphene OS is a good experience. I'm wondering how it is in practice. I just recently started thinking about leaving Google. I made a list of Google products I wanted to replace and frankly it's overwhelming. One I really cannot live without is Maps. It's just the damned best. And waze is owned by Google so afaik there is not much choice. Do you use the Google app sandbox thing on graphene?
Fairphone, they have instructions even on their site on how to flag your phone with different OS's. Think it's just been released in the states too. Android AOSP, Lineage, Ubuntu Touch, eOS to name a few.
I considered buying the fairphone and the pixel 7. Unfortunately, the former was not available in my country and the latter had no service centers in my region.
Then I got a good deal on a samsung galaxy s23 and bought it. Now I'm stuck with not being able to tinker with anything.
Samsung is probably the worst offender in that regard. No bootloader unlock on Snapdragon, bootloader unlock trips Knox on Exynos and disables basic features like the camera on Z Fold 3.
I'm not sure that is true, I don't remember device support being much better in the past. But assuming that is the case, part of the reason might be the fast evolution of devices and Android itself back in the day. Old devices quickly becoming obsolete and new Android versions being desirable made custom ROMs very attractive for a group of people, including myself.
I installed CyanogenMod on my first smartphone because I could get a more recent Android version when it actually made a difference. As Android evolved, an up-to-date install is not as different anymore than a 3 year-old one, not in features and even less in looks. The main motivations I see for custom ROMs nowadays is to improve your privacy and decrease bloatware, but I don't think most users would bother with going through the process and voiding their warranty to have these things.
I think there are fewer people working on them, more complexity involved in making a good one, and fewer end-users who want to use them.
It's disappointing that every device needs active effort to support it, unlike PCs where operating systems can be more generic and detect hardware during boot or install. It's my understanding that newer Android versions have improved the situation some, so we may see things turn around a little.
Unlockable bootloaders, having adb and fastboot support on the phone side, having a processor that has open source code, and not disabling cameras etc when the bootloader is unlocked are all needed to have a viable custom ROM community for a specific device.
Lots of modern phones don't do some or all of the above. Mediatek powered phones are a no-go, some phones don't support adb or fastboot (iirc some older LG phones have this issue), Sony would disable the camera if a bootloader was unlocked on some of their older phones.
I understand your bad experience with GSIs, but I think it's a step in the right direction. The way custom roms have been made through the years isn't sustainable for the long run. It's too much work for the few people involved, that goes obsolete so fast. But with GSis, the projects will one day be able to maintain just a few images, and the porting community will just have to focus on unlocking the devices.
GSIs aren't working 100% today, but it's something still new in the perspective of manufacturers, and the tendency is to have better support with time.
Just to put things into perspective, my experience, as someone poor from a third word country, is just the opposite. In the past, only the more expensive phones had custom rom support, and the cheaper ones I got access to, wouldn't even get results if I searched for the model on xda. Nowadays, even cheap chinese phones or the ones locally manufactured in here allow me to put a GSI and have a customized experience, up to date with security patches.
No kernel sources being published doesn't really help for custom ROM development. I've also seen that there's little regeneration of the custom ROM devs. Most of the guys making good custom ROMs now have been poached by the companies or basically got tired of the toxic custom ROM community (ETA when).
I still remember the heyday of the custom ROM development during the Nexus One days. Damn now I'm nostalgic all of the sudden.
For Samsung specifically, they flip a fuse if you unlock the bootloader which permanently disables many security features. That is a major issue for anyone wanting to do things responsibly.
There are still plenty of custom ROM communities out there, but mostly for those cheap Chinese brands, especially those with snapdragon SoC. Enthusiasts using those devices usually aren't too afraid of breaking their cheap phones, so the communities are still thriving. On the other hands, people with $1000+ flagship phones are usually less likely to do this and void their warranty, unless their phone manufacturers aren't voiding warranty when you unlock the bootloader such as on pixel devices.
No it's not. Check out xda, there hasn't been a custom ROM released for a OnePlus flagship since the 9 pro because they won't release the msm tool for newer phones