I’m sorry but it’s true. Graphene OS sucks the big one… It’s absolutely janky when it comes to its Android app support, it’s UI is absolutely atrocious, and all around. It’s simply a wonky operating system.

Not only that but the whole premise of of making an operating system built only for Google pixel hardware on top of Android Open source project is just silly when it comes to the idea of “privacy”. That would be like trying to open up a gay nightclub in Qatar. Google could snap its fingers tomorrow and lock down the ability to unlock bootloaders.

What do you think? Am I wrong here guys?

  • ganymede@lemmy.ml
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    3 months ago

    Google could snap its fingers tomorrow and lock down the ability to unlock bootloaders.

    only valid point in the post afaict

    • other8026@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 months ago

      Well I suppose they could? But then how would that end for them? They sold devices with unlocked bootloaders. Changing that might get them in legal trouble. I’d think if a device is sold unlocked, it’ll remain unlocked.

      • ganymede@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        3 months ago

        i think they mean future devices, not previously sold.

        either way the thread is 99% invalid criticism of what is afaict one of the best projects of our generation

  • JustVik@lemmy.ml
    link
    fedilink
    English
    arrow-up
    50
    ·
    3 months ago

    It’s not their fault that they can’t make Graphene OS for more models. It’s the fault of the manufacturers of these smartphones who always put a stick in the wheel for anyone who wants to make a privacy oriented OS for their smartphone models.

    • ReversalHatchery@beehaw.org
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      edit-2
      3 months ago

      for a privacy oriented OS you don’t need a very specific security chip that only a single pije of phones have. that’s maximalism.

  • someacnt@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    26
    ·
    3 months ago

    As a user, I can definitely say that GrapheneOS is the single best project in the open source space. 99.99% of stuff works out-of-the-box, with de-facto feature parity. The remaining 0.01% is the one dumb investing app which I can only assume has sneaky spyware on it.

  • june (she/her)@lemmy.ml
    link
    fedilink
    arrow-up
    6
    ·
    3 months ago

    The UI is just AOSP android, simple and ugly (imo) as always. It’s not unique in that either, most OEMs have a skin based on AOSP in some way.

    As for the app support, I have had very little issues over the past year on GrapheneOS. Aside from some apps being exclusive to the play store (ie they don’t host them elsewhere and Aurora doesn’t have a copy), I have a pretty seamless experience. And yes, including banking apps.

    Tap to pay doesn’t work (they’re upfront about that) but NFC is still fully features in my experience.

    • fuzzzerd@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 months ago

      As a regular user, besides tap to pay what do you use NFC for? I get your point that it works, but what uses are there besides tap to pay for most users?

  • sic_semper_tyrannis@lemmy.today
    link
    fedilink
    English
    arrow-up
    13
    ·
    3 months ago

    I totally disagree. I’ve had very very minimal issues with anything on GrapheneOS and they use Pixel hardware because they have extra hardware security chips in them

  • FauxLiving@lemmy.world
    link
    fedilink
    arrow-up
    15
    ·
    3 months ago

    This isn’t even a bad opinion, it’s just ignorance.

    It only has a problem with some banking apps, the ui is stock android, the premise isn’t to make an operating system built only for Google Pixels it’s to make a secure OS and currently Pixels are the only hardware that meets the requirements and hypothetical futures can be imagined to make any product sound doomed.

    • Seraphim@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      3 months ago

      I’ve used banking apps in the browser with no issue. The ui being stock is a non-issue for me.

  • Mohamad20ZX@sopuli.xyz
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    3 months ago

    Don’t feel bad about your statement everyone should have high standards when it comes to criticism

  • CerebralHawks@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    3 months ago

    Different reasons, but I don’t really get the point of it either. It only works on Pixel devices, which means you gotta pay iPhone prices and reward Google’s bad behavior. If you’re fine paying that, you’re probably not too far against Google’s behavior and thus, why are you using Graphene? If you’re against Google’s boorish privacy practices, get an iPhone. Apple is sort of trying to take a stand against privacy invasion (at least to Google’s scaling; they aren’t perfect) but the fact remains, a lot of people don’t care about privacy. Pixel+Graphene is objectively better for privacy than iOS, sure, but there are tradeoffs and people who love Graphene are willing to accept them.

    The biggest problem with iOS is, it’s closed source and we don’t know what Apple will do tomorrow. As a Mac guy I don’t have a problem with Apple vis a vis my Macs. However the iPhone is kinda silly for a few reasons, but I still prefer it to the alternative because I don’t want to be playing around with custom firmware. That’s a younger man’s game. It was my game when I was a younger man and I don’t want to be in that scene anymore. My choice. I know it’s a good choice for others. Android isn’t really open source either, though. AOSP is — but forks of it, like the Android on Pixels, like OneUI (I still wanna call it TouchWiz), HTC Sense, and all the others, are not. Of course, if you’re running Graphene, or Oxygen (again, I still wanna call it Cyanogen), or something like that (I used to be sweet on an AOKP fork called LiquidSmooth), you’re playing with open source so you do have that. But you also give up a lot.

    I do think it’s a bit weird Graphene is only on Pixel. But I guess by keeping the device list small, they can focus on what they want to do, which isn’t support every phone, it’s supporting ones they know they can.

    At the end of the day, Graphene is a better option for privacy than iOS, which is better than any commercial Android OS by default due to not having Google Play Services.

    I’d say you have to really assess what kind of privacy you need. Maybe iOS is enough. If it’s not, Graphene is a good bet. I don’t need Graphene. Heck, I’d be fine with Pixel Android, but I have an iPhone so I can afford to claim the high road in privacy. Just not the highest road. I know where I stand. But I know where I need to be and I’m standing pretty close to it. If someone needs to be in another place, what works for me may not work for them.

    • WaffleWarrior@lemmy.zipOP
      link
      fedilink
      arrow-up
      1
      arrow-down
      7
      ·
      3 months ago

      At least with iPhone all your app compatibility will still work… I feel like Android isn’t too bad privacy wise because with the implementation of private space. There are some cool tricks you can do to essentially shut off apps when not in use completely

  • technocrit@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    4
    ·
    3 months ago

    That would be like trying to open up a gay nightclub in Qatar.

    It’s not just qatar. It’s many many allies of the fascist USA.