I think you meant it the other way around - "why custom ROMs have little device support" - right?
because for me it's clear that companies just want to ship their own spyware and bloatware.
I think you meant it the other way around - "why custom ROMs have little device support" - right?
because for me it's clear that companies just want to ship their own spyware and bloatware.
You do have a point. I wish projects like GrapheneOS and CalyxOS supported non pixel devices as well.
GrapheneOS's reasoning is that Pixels are the only things secure enough for their needs
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.
Support is by far the most popular then it has ever been
I am presently using a super niche device. SUPER niche. So niche that I have been dealing really closely with the manufacturer, who worked with Qualcomm and made a specific firmware just to get wifi calling working for me in Australia.
I have quizzed them so many times on why they won't support rom development. You can unlock the bootloader, but the rom files are heavily encrypted. There's no way to extract the boot IMG so we're dead in our tracks.
The manufacturer basically say that they have to fight so hard to gain google certification that they won't do a single thing to risk losing it.
They've been pretty generous with their warranty policies so probably another reason is they don't want to risk anyone doing overclocking etc and then having to cover device repairs or replacement.
Ok now you've just made me curious on what's the super niche hardware.
It's a Nokia 3310.
AGM G2 Guardian. It's a pretty exclusive club mate. AGM gambled big and I don't think it's really payed off for them - they haven't shifted enough units and their profit margin was super small.
I work outdoors and live a pretty weird life, I was super super excited to find a decent snapdragon in a ruggedized device like this. The long-range thermal is legit, battery life is insane and it feels like a super high quality thing to hold. They've had a few little teething problems - some issues with fingerprint sensor for a few people, some screen flickering issues for others. I've been pretty lucky so far and I believe they are switching things up in manufacturing now.
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.
It must be a long time since you ran a custom ROM. I use GrapheneOS and that is far from the case.
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.
Last I heard the person in question stepped down. Made me consider to switch to Pixel with grapheneos
Fortunately the lead dev is not the entire project and his tantrum won't affect the stability of the project
What drama
That's a hell of a username...
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?
Ps. Your username is terrifying.
I can definitely recommend GrapheneOS. Interestingly Google Maps actually runs fine without Google Play Services, but if you do need other Googly stuff then installing the Sandboxed Play Services is pretty trivial. Happy to answer any more questions about it if you want!
Snap... being able to use my phone to pay for stuff, outweighs having a custom rom.
It's mostly a function of an unlockable bootloader. If the device manufacturer does not allow the bootloader to get unlocked then putting a ROM on it is extremely difficult.
Pixel devices tend to be unlocked, unless the carrier locks the bootloader. So it's always a good idea to buy pixel directly from Google so you get an unlocked bootloader.
The same can be said for fair phone.
The other devices are really hit and miss. Basically if you can't control the software it's not your hardware even if you paid for it.
I feel like this is a basic human right thing. Probably going to wait for the EU to make legislation unlock hardware you own. I look forward to that
Other manufacturers basically crippled the device if you decide to unlock the bootloader doesn't really incentivize people to develop Custom ROMs. As open as Pixel are, its market share is small compared to the juggernauts like Samsung. If you unlock a Samsung phone bootloader, say goodbye to your camera quality, HD streaming on streaming apps, your banking apps, Knox, and many more.
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.
Xiaomi phones with Snapdragon SoCs have very good custom ROM support.
Been rocking these for years. I actually research the rom scene before buying a phone after being stuck with Samsung bloat for so long.
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 have an android that has Mediatek Dimensity and I have found 0 custom roms that are good. I wonder why.
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.
Yeah, the wallet doesn't work anymore if you unlock it... that's what stopped me. Pretty shitty thing for them to do imo.
Let's say a person relocks the bootloader somehow... is it possible to get back those lost features ?
From my understanding no
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.
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.
I can't see many advantages to the manufacturers.
If people were screaming out for this I'm sure plenty of marketing departments would jump on it.
I also imagine as hardware gets more complicated so does the process of making ROMs. Which is already a pretty niche skill.
Most manufacturers have made it more difficult to both make and install custom ROMs for their devices.
Pixel is the one big exception so far.
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities: