• Avid Amoeba
    link
    fedilink
    English
    3
    edit-2
    2 years ago

    Wow, I thought it was more than that. I guess among other things that shows how much less shitty stock OEM Android ROMs have gotten.

  • LoboAureo
    link
    fedilink
    English
    82 years ago

    Will be +1 when have official support for the poco X5 pro. (If I can pay with mobile)

    🤓

    • @janguv@lemmy.dbzer0.com
      link
      fedilink
      English
      22 years ago

      (If I can pay with mobile)

      Correct me if I’m wrong, but so long as you root with Magisk and configure the denylist, installing the SafetyNet Fix and changing the Props if you need to spoof a device ID, then you’ll always be able to use Google Pay/contactless, regardless of whether on Lineage or another custom ROM.

    • Keith
      link
      fedilink
      English
      12 years ago

      Buy one from someone who does the installing on sites like Ebay

    • @emli42@lemm.ee
      link
      fedilink
      English
      22 years ago

      Put simply, you don’t. If your phone is supported and the documentation is there, the installation is a breeze.

      • @Mio@feddit.nu
        link
        fedilink
        English
        12 years ago

        No. If it was easy to install then there would be a installation guide on the phone. Not even a installation program available on the computer to assist.

        • @emli42@lemm.ee
          link
          fedilink
          English
          22 years ago

          This is 100% unofficial. Phone makers don’t want you to install third party roms (they cease having any control, won’t receive analytics, can’t push ads etc). Why should they help you out? They’ll do the bare minimum (or less) that is required for you, the owner, to be able to use third party roms.

  • @perniciousanteater@lemmy.world
    link
    fedilink
    English
    102 years ago

    I’ve been using LineageOS on my OnePlus 8, after a couple buggy updates from the manufacturer. I haven’t looked back once.

    I use my phone pretty averagely and never run into bugs or problems, and the added features make it a no brainer.

    I’ve rarely run into app compatibility issues, but there’s usually a simple solution available. Or a different app!

      • I like the filtering this site has got but it’s missing an option for the one thing I want most that is becoming increasingly more difficult to find: a 3.5mm audio jack. Other than that, though, this is pretty slick even for just finding a new phone in general.

  • @Spoilt@jlai.lu
    link
    fedilink
    English
    42 years ago

    And some applications still refuse to launch on it, preferring an outdated version of Android because Google does not send its security updates after 3 years.

  • Oha
    link
    fedilink
    English
    42 years ago

    Lineage is fucking Awesome. I fucking love android without google crap

    • @Fisch@lemmy.ml
      link
      fedilink
      English
      12 years ago

      Depends on your bank. My bank’s app (Sparkasse) has always worked, even when I had Magisk installed.

    • @Unreliable@lemmy.ml
      link
      fedilink
      English
      142 years ago

      It’s a constant cat and mouse game with Google. You can use Magisk with Zygisk enabled, Shamiko, and Play Integrity Fix (there’s also a few other combos that work) to get baking apps to work. I have no issues on my rooted Pixel 8 Pro, but it’s always a gamble if Google updates their end and then you get locked out of Google Wallet for a day once you update your fixes (not banking apps).

    • Mike
      link
      fedilink
      22 years ago

      @bort @ijeff As long as you don’t root it, yes… and if you root it there is workarounds that might work.

      • @Kusimulkku@lemm.ee
        link
        fedilink
        English
        12 years ago

        Unfortunately GPay / Google Wallet has been borked on most ROMs since the recent Google shenanigans about a week ago. Even those not rooted. I got hit by that, running ArrowOS and not being rooted.

        My bank’s app works though so eh, lost some convenience but can get things done.

  • @TheMadnessKing@lemdro.id
    link
    fedilink
    English
    632 years ago

    Honestly, Custom ROMs have been in decline of usage since few years. There are also Other ROMS like Pixel Experience, PixyOS, Havoc, evolutionX, PixelOS, Paranoid, Derpfest, CrDroid and lot more.

    The reason for the drop is due to a combination of reasons like better OEM UI, unpublished Kernel code (Chinese OEMs, Mediatek), locked bootloaders and Safetynet issues.

    I’m currently rocking CrDroid it has currently ~85K active devices (https://stats.crdroid.net/).

    • @CoderKat@lemm.ee
      link
      fedilink
      English
      32 years ago

      Do custom ROMs still have issues with some apps not allowing them? It’s been an eternity since I tried one and I don’t know if it’s a hard requirement, but at least when I did try it, I had (?) to root my device and my bank apps refused to work after that.

      • @TheMadnessKing@lemdro.id
        link
        fedilink
        English
        12 years ago

        I haven’t encountered such a thing yet (been using for 5 months).

        There are lot of methods to bypass those checks even now, and often many ROMs do this by default. (LineageOS doesn’t do that afaik)

      • Gunpachi
        link
        fedilink
        English
        12 years ago

        Some banking or payment apps can detect root and won’t let you use them.

        When I used to run Custom ROMs I just used magisk to hide the root and these apps would work fine afterwards.

      • @sv1sjp@lemmy.world
        link
        fedilink
        English
        22 years ago

        Many applications especially banks require Google Safetynet to be functional, even without root. I am running DivestOS, a hardened version of LineageOS without gapps, and I can’t have access on my bank because I chose freedom. Democracy at its finest…

    • deweydecibel
      link
      fedilink
      English
      72 years ago

      better OEM UI

      Very subjective.

      Unpublished kernel code

      Don’t use those phones.

      Locked bootloaders

      Plenty of OEMs allow bootloader unlocking, stop buying Samsung.

      Safetynet issues

      It’s Google Play Integrity checking now, and as someone who has been using LinageOS on unrooted phones for a while, I’ve never had these issues. Not to say people out there aren’t having them, but it’s not as bleak as people seem to believe it is.

      I have one phone that’s rooted, and I have to use magisk to hide it, and that occasionally has issues, but not the non-rooted ones running custom roms.

      • @sv1sjp@lemmy.world
        link
        fedilink
        English
        12 years ago

        Now try to use most of Banking applications (even McDonalds app lol) Most of these application require Google Play Integrity. So practically, you are enforced to use Google Play Services or buy a second device to run android with gapps and then power it off (that’s what I did)

      • @TheMadnessKing@lemdro.id
        link
        fedilink
        English
        1
        edit-2
        2 years ago

        I’m talking from a general user perspective who often can’t even differentiate between chipsets let alone look for such details.

        People used to got to Custom ROMs because OEMs were really doing shit job, that’s not the case now given now.

        • @FutileRecipe@lemmy.world
          link
          fedilink
          English
          42 years ago

          People used to got to Custom ROMs because OEMs were really doing shit job, that’s not the case now given now.

          Yep. I used to use custom (ROMs, kernels, etc) for the extra features and playing with my phone like a shiny new toy. Now I use GrapheneOS because OEMs and Google don’t do security and privacy anywhere near as good as GOS. And I can live with the minor inconvenience of apps that use Play Integrity API, though I do encourage the app devs to switch to hardware backed attestation because: “Android’s hardware attestation API provides a much stronger form of attestation than the Play Integrity API with the ability to whitelist the keys of alternate operating systems. It also avoids an unnecessary dependency on Google Play services and Google’s Play Integrity servers.” https://grapheneos.org/articles/attestation-compatibility-guide

      • @Kusimulkku@lemm.ee
        link
        fedilink
        English
        32 years ago

        It’s Google Play Integrity checking now, and as someone who has been using LinageOS on unrooted phones for a while, I’ve never had these issues. Not to say people out there aren’t having them, but it’s not as bleak as people seem to believe it is

        Maybe a week ago they borked the integrity of custom ROMs. GPay/Wallet doesn’t work anymore with Magisk shenanigans. Happened to every ROM I checked.

      • @NRoach44@lemmy.ml
        link
        fedilink
        English
        52 years ago

        Where are these OEMs that allow proper bootloader unlocking on most of their range?

        Google, Sony …? Huawei stopped doing it, Oppo & Samsung doesn’t last I checked.

    • @nexusband@lemmy.world
      link
      fedilink
      English
      24
      edit-2
      2 years ago

      Before i got my Pixel 6 Pro, i’ve been running Custom Roms on everything. The Pixel 6 Pro is probably the first device, i’m actually okay running Stock. It just does what it should. And i’ll be honest, the hassle of getting it to work properly (Banking, Netflix, etc) is just too much for my everyday phone…Google really did a number on that one, both positive and negative. I kind of hate it…

      • @adavis@lemmy.world
        link
        fedilink
        English
        102 years ago

        I used to turn to custom roms to extend the life of my phone. My first smartphone didn’t get an official update after I purchased it for example. The custom roms often made the phone snappier too.

        These days I’m on a mid range Samsung phone released almost 4 years ago and it’s still getting updates.

      • BiggestBulb
        link
        fedilink
        42 years ago

        Ditto on a Pixel 6 Pro. There were a ton of people with issues when this thing came out, but I was lucky enough to dodge all the issues.

        • @nexusband@lemmy.world
          link
          fedilink
          English
          12 years ago

          I had none over the last 2 years…which is funny, because i fully expected to have them - and put a custom rom on it. There are just two things that irk me…you can’t disable IPv6 and the adaptive charging is still not enough for me personally, i would have liked to have a hard limit…

      • @0ops@lemm.ee
        link
        fedilink
        English
        272 years ago

        Ironically that’s one of the only phones that you have the choice of not running stock

        • deweydecibel
          link
          fedilink
          English
          32 years ago

          Not it isn’t. Plenty of OEMs let you unlock the bootloader.

          • @0ops@lemm.ee
            link
            fedilink
            English
            82 years ago

            That isn’t the only factor though. Take OnePlus, for example. You can still unlock their bootloaders, but if you check out XDA you’ll see that their hasn’t been any custom roms for a OnePlus flagship since the 9 pro because they stopped publishing the MSM tool, so the risk of bricking the phone is too great.

            • Gunpachi
              link
              fedilink
              English
              22 years ago

              I guess the same thing is happened with samsung after the s10 series. No new roms for the newer ones apart from 1 or 2 oneui based roms.

      • deweydecibel
        link
        fedilink
        English
        32 years ago

        Google really did a number on that one, both positive and negative. I kind of hate it…

        And yet you bought a Pixel and supported them in this.

  • bufalo1973
    link
    fedilink
    English
    42 years ago

    I’ve changed thanks to not having any update on my Moto G7 Power since 2021.

    • lemmyvore
      link
      fedilink
      English
      292 years ago

      And it could’ve even been useful, had they not chosen to show the code names instead of the make and model…

    • @Simpletim@lemmynsfw.com
      link
      fedilink
      English
      32 years ago

      I don’t know the exact modus operandi, but usually this is achieved by using some “phone home” mechanism which sends a device identifier (to ensure uniqueness) along with an OS version (and maybe some other fingerprints to ensure integrity of the data - like a hash of CPU hardware, etc).