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 ?

  • Eager Eagle@lemmy.world
    link
    fedilink
    English
    arrow-up
    53
    arrow-down
    1
    ·
    1 year ago

    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.

    • Gunpachi@lemmings.worldOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      You do have a point. I wish projects like GrapheneOS and CalyxOS supported non pixel devices as well.

      • smeg@feddit.uk
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        GrapheneOS’s reasoning is that Pixels are the only things secure enough for their needs

  • Someology@lemmy.world
    link
    fedilink
    English
    arrow-up
    39
    ·
    edit-2
    1 year ago

    In many cases, because manufacturers refuse to allow unlocking of bootloaders. In other cases, because manufacturers refuse to share drivers for proprietary hardware.

  • Takatakatakatakatak@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    31
    ·
    1 year ago

    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.

      • Takatakatakatakatak@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        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.

  • ѕєχυαℓ ρσℓутσρє@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    2
    ·
    1 year ago

    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.

    • NightOwl@lemmy.one
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      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.

  • Madnessx9@lemmy.world
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    1
    ·
    1 year ago

    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.

    • MasterBuilder@lemmy.one
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      1 year ago

      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.

      • Izmir@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        arrow-down
        3
        ·
        1 year ago

        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.

        • Willifire@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          Last I heard the person in question stepped down. Made me consider to switch to Pixel with grapheneos

        • smeg@feddit.uk
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 year ago

          Fortunately the lead dev is not the entire project and his tantrum won’t affect the stability of the project

          • Izmir@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Sure but the fact that anyone there could do it means fundamentally there is a risk present and that’s a bad position for a privacy centered organization. The others there MAY not do it, but they COULD.

            • smeg@feddit.uk
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Isn’t that the case with any project, open source or proprietary? Plenty of previously-respectable manufacturers have decided to just dump in a load of bloat/ad/spyware one release, at least with an open project there are security audits and the like so you know if something’s gone awry.

      • TrickDacy@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        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.

        • smeg@feddit.uk
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          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!

          • TrickDacy@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            Thanks for the info! Do you use maps for navigation while driving? If so, does it work as smoothly as normal? Also have you used the Google wallet for tap payments on graphene?

            • smeg@feddit.uk
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              1
              ·
              1 year ago

              I’ve not noticed any issues at all with navigation. Unfortunately contactless payments are one of the few things that don’t work.

              • TrickDacy@lemmy.world
                link
                fedilink
                English
                arrow-up
                2
                ·
                1 year ago

                I was afraid of that. Hmm, any other pain points that stick out? Are you able to use things like Google docs and voice? I know I’m probably wanting to have my cake and eat it too. It’s truly overwhelming how many Google services I rely on and I hate it.

                • smeg@feddit.uk
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  1 year ago

                  Google docs is fine, I don’t use any of the voice assistant stuff but I think they do still work. I think the NFC payments are a bit of an edge case, I can’t remember the reason they don’t work but they are the exception.

  • jet@hackertalks.com
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    1 year ago

    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.

    • jet@hackertalks.com
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      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

    • sheogorath@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      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.

  • lemmybenny@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    ·
    1 year ago

    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.

    • Gunpachi@lemmings.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      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.

      • jacktherippah@lemdro.id
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        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.

    • JetAnhyzer@ttrpg.network
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Been rocking these for years. I actually research the rom scene before buying a phone after being stuck with Samsung bloat for so long.

  • Eager Eagle@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    1 year ago

    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.

  • Zak@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 year ago

    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.

  • notthebees@reddthat.com
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 year ago

    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.

  • Resonant0838@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    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.

  • spiderman@ani.social
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    I have an android that has Mediatek Dimensity and I have found 0 custom roms that are good. I wonder why.

    • sheogorath@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      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.

  • fulano@lemmy.eco.br
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    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.

  • redcalcium@lemmy.institute
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    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.