• shortwavesurfer@lemmy.zip
    link
    fedilink
    English
    arrow-up
    8
    ·
    8 hours ago

    This is why my next phone will be running Nura. I have been saying for years that Google was going to attack AOSP based projects, and here it is.

    • custom_username@reddthat.com
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 hours ago

      I’m pretty confident it would just be newer device releases. They might be able to start locking bootloaders on older devices via updates (I think it’s possible), but something already running graphene would be fine.

    • Sina@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 hours ago

      The only reason for you and me, but not for most people. Most just wanted a stock android phone that’s similar to iphones in terms of integration.

    • Tehdastehdas@piefed.social
      link
      fedilink
      English
      arrow-up
      11
      ·
      edit-2
      14 hours ago

      Sloppy use of terms in the article. Locked down bootloaders should be illegal.

      All new phones come with a locked bootloader, but unlocking codes are delivered on (a few) maker’s website by IMEI. Then the user unlocks it, installs a new OS, some of which can re-lock the bootloader with a new signature, re-enabling verified boot = secure boot, which stops malware from making itself reboot-resistant, and blocks evil maid attacks through the USB port.

      • Blisterexe@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        The problem with the codes being on the website is that it gives the company control over who can unlock the bootloader

        • bumblebeer@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 hours ago

          Eh. It’s a bit more complicated than that. Most of the carrier phones are locked because they are given to customers on a financed plan. Unless and until the phone is paid off and all other contract terms are satisfied, then the customer doesn’t actually “own” the device. It sucks, but it does make sense in the context. If you don’t like it, then don’t enter into such agreement. Either buy your device outright or use alternative means of financing which do not impose such restrictions.

  • bitjunkie@lemmy.world
    link
    fedilink
    English
    arrow-up
    36
    arrow-down
    2
    ·
    24 hours ago

    make non-spyware alternative OS

    target hardware is made by same company as spyware OS

    What could go wrong?

    • ɔiƚoxɘup@infosec.pub
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      20 hours ago

      I remember a conversation from a while back where it was discussed that the graphene devs were asked why they didn’t go all in on a Linux OS instead.

      I wonder how much regret they have over making their choice.

      • lentildrop@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        5 hours ago

        Nobody would use it if they used a Linux OS because the whole point of GOS is that it’s a drop-in replacement for Android. Using a Linux phone even in 2026 is a huge commitment.

        • ɔiƚoxɘup@infosec.pub
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours ago

          Yeah, and that’s a fair criticism, but the point is, if they had been working on it all this time, then it may not be such a commitment anymore.

      • theparadox@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        7 hours ago

        didn’t go all in on a Linux OS instead

        This is extremely difficult to do without open hardware or support from major chip manufacturers. You can’t make an open source operating system if you don’t have drivers for the hardware that the operating system is supposed to run on.

        You can install non-android Linux on quite a few phones… assuming you don’t need it to work like an actual phone. Things like the modems (the hardware that communicates with cell towers) won’t work without drivers. If they do work, they are usually binary blobs - something akin to black boxes.

        • ɔiƚoxɘup@infosec.pub
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 hours ago

          Yeah, I agree, the hardware is not there yet.

          Hopefully this new bullshit from Google will create a large enough market that it’ll be viable.

      • Jako302@feddit.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 hours ago

        What exactly would a Linux phone do better for them? The two main problems for the GOS project are 1. Finding hardware that is up to their security standards, and 2. Google putting increasingly more restrictions into their “security” APIs.

        1. On the hardware side, the OS doesn’t matter at all. The main hurdle was their overly strict requirement for security. Whether that standpoint is reasonable or not is not the point here, cause it doesn’t change with the OS.

        2. On a Linux OS they would’ve been hit even harder by safety net and hardware attestation checks. They certainly could get basic functionality like calls and SMS to work, but 99.5% of users want to use apps, not just have a dumb phone. Since there is absolutely no marked for Linux phone apps, even with the entire GOS crowd added to the userbase, the only viable solution would be running everything in an emulator like waydroid. Other Linux phone projects already do this, but its worse in security, privacy and usability than even a fairly plain AOSP implementation.

        I get the wish for a Linux phone, but AOSP is a fully functional OS even without the Google shit tacked on. There is nothing wrong with using it as a base. The main problem with it is that google stopped adding new features and instead keeps them proprietary. But that doesn’t matter since a Linux phone wouldn’t have these features either, so the development would have to be done either way.

        • ɔiƚoxɘup@infosec.pub
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours ago

          Yeah, I understand the decision that they made and why they made it. I’m just saying hindsight is 20-20, and we would all be in a better place if they had chosen Linux back then.

  • DaddleDew@lemmy.world
    link
    fedilink
    English
    arrow-up
    89
    ·
    edit-2
    1 day ago

    I’m so glad Linux phones are becoming a thing. The day my GrapheneOS device dies, I want to keep the same level of control over my phone’s settings, the software that runs on it and what on it is allowed to access the internet or not.

    Stock android phones are nothing but thoroughly locked down, enshittified tracking and data mining devices that use your own battery power and data plan to constantly upload data about you and sometimes allows you to use them as smartphones.

        • Auli@lemmy.ca
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          3
          ·
          1 day ago

          Shoes going to pay for it? Even Linux is paid for by IBM and others, we just get the benefits.

          • Sturgist@piefed.ca
            link
            fedilink
            English
            arrow-up
            3
            ·
            13 hours ago

            Shoes going to pay for it?

            No, probably not shoes, but there’s likely a corp that’d be interested in funding something like that.

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

        preferably multiple different ones.

        Multiple devices/OEMs: Yes. Fragmented choices of operating systems and app stores: Hell, no

        • uen3@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          16
          arrow-down
          1
          ·
          1 day ago

          People who would install different OSs on their phone don’t need “app stores”. Monopolistic companies that want to control the OS on your phone need them.

          I still remember how hard it was to find and install software on a Mac for the 25 years before Apple made an App Store.

          ...

          Not hard at all. Not even a little bit.

          • i_am_not_a_robot@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            5
            ·
            1 day ago

            It’s still easier to install software on a Mac without using the app store. But now Apple charges developers even if they’re not using the app store.

            • woelkchen@lemmy.world
              link
              fedilink
              English
              arrow-up
              5
              arrow-down
              2
              ·
              24 hours ago

              It’s still easier to install software on a Mac without using the app store. But now Apple charges developers even if they’re not using the app store.

              But running unsigned and unverified apps on macOS requires jumping through hoops.

          • woelkchen@lemmy.world
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 day ago

            People who would install different OSs on their phone don’t need “app stores”.

            People who would buy a preconfigured phone that happens to run something else than Android or iOS (like Jolla) wouldn’t be the ones installing a different OS.

  • pulsewidth@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    10
    ·
    16 hours ago

    I use Graphene OS and have donated to them, but feel like the Graphene main dev (Daniel/thestinger) is the boy who cried wolf at this point. I don’t doubt that Google may want to diminish or end Graphene, but claiming there is a campaign to interrogate OEMs and warn them against supporting Graphene is something else.

    I’ve read the news story and the Graphene forums threads and once again can’t see a single shred of evidence.

    A screenshot, an attributed quote… Nothing. Just all the claims of one person, again.

    • Firelord@lemmy.zip
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      6
      ·
      7 hours ago

      Ah, the classic american pasttime of giving mega corporations that have already proven to screw over their user base over and over again the benefit of the doubt.

      • pulsewidth@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        2
        ·
        7 hours ago

        Literally said right in my comment that I don’t doubt Google’s may have such motives, I don’t see how that is possibly “giving them the benefit of the doubt”. All I asked for was proof.

        If your whole response to someone asking for proof is to attack their character then you really don’t have much to add, especially as you can’t even do it right (I’m not American).

        • Firelord@lemmy.zip
          link
          fedilink
          English
          arrow-up
          5
          ·
          6 hours ago

          The problem is that if you have proof of Google trying to fuck you over, it’s already too late. I’m saying we prevent said fucking by killing google with anti-trust. Google doesn’t need any defence.

    • FG_3479@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      3
      ·
      16 hours ago

      They’re saying that they expect Google to lock Pixel bootloaders, not that they have hard evidence of it.

      • pulsewidth@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        11 hours ago

        If you’re going to make claims as to what they’ve said, at least read the article.

        Where’s all the evidence that they’ve been reaching out to OEMs? Zero so far.

        • FG_3479@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          8 hours ago

          The terms are true, and they say that an OEM will lose GMS if they sell Android phones without it.

  • GreenKnight23@lemmy.world
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    14
    ·
    19 hours ago

    I’d feel bad for Graphene but they were the ones adamant that “pixel phones were the only phones we could support”.

    how’s that working out for you guys?

    not so good, huh? guess you stomped on your corpodaddy’s balls a bit too hard and they cut you off.

    diversify or die.

    • undrwater@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      19 hours ago

      Motorola.

      It’s hard for an open source project to maintain multiple hardware lines without maintainers.

      I’m honestly not sure this is Google’s plan, regardless. One segment of the company is complaining, while another is supportive. We’ll have to wait till it gets to legal.

    • pucker4676@lemmy.ml
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      6
      ·
      18 hours ago

      They didn’t just choose the Pixel. It was the only phone that met their requirements. You sure sound like a fool.

      • KrunAndDun@lemmy.today
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        5 hours ago

        They chose to create requirements in which the only option was the Google Pixel. Its completely their choice. They could have had different the requirements, but they didn’t.

        I don’t know why the language surrounding this debate always gets twisted. GrapheneOS wants to continue following their own requirements which point to Google Pixels only, more than they want to open up and support other platforms, some more ethical/moral, open, and not crafted by a company directly opposed to their goals.

        • Senal@programming.dev
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          2 hours ago

          They chose to create requirements in which the only option was the Google Pixel. Its completely their choice. They could have had different the requirements, but they didn’t.

          Yes, like airplane manufacturers could have less stringent requirements for the materials with which they build their planes, doesn’t make it a good idea.

          I don’t know why the language surrounding this debate always gets twisted. GrapheneOS wants to continue following their own requirements which point to Google Pixels only, more than they want to open up and support other platforms, some more ethical/moral, open, and not crafted by a company directly opposed to their goals.

          So your argument is to lower security requirements so they can provide a less secure system in favour of more phone options.

          To what end ? Their whole schtick is maximum security possible, there are plenty of alternatives if you want less security (for a given idea of security).

          Lowering their security requirements is also directly opposed to their goals, so what is it that you are suggesting as a solution?

          It sounds like you know the answer so stop complaining around it and just tell us.

          • KrunAndDun@lemmy.today
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 hour ago

            So your argument is to lower security requirements…

            I made no such argument. My comment plainly explains my issue with the language around this discussion. It doesn’t take a side nor propose a solution.

            • pucker4676@lemmy.ml
              link
              fedilink
              English
              arrow-up
              1
              ·
              41 minutes ago

              They would have to lower standards in order to support a different phone. That’s the whole point. They’re not sticking it to anyone. Just trying to provide as secure of an OS as possible.

              • KrunAndDun@lemmy.today
                link
                fedilink
                English
                arrow-up
                1
                ·
                33 minutes ago

                They would have to lower standards…

                Except that some context around security is threat model. There are people who view it as a significant security issue to be using Google hardware.

                Security cannot so simply be boiled down to a one dimensional axis of more or less secure.

    • Krudler@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      21 hours ago

      Really?

      I cannot wait to get rid of the steaming lump of shit known as the pixel 9, perhaps this will increase its saleability or resale value?

      Edit I was very curious about what you said about it’s illegality so I did some research and as far as I can see, there’s nothing illegal about their plans. And they said out right they’re going to roll this shit out in January in Canada 🙃

  • _haha_oh_wow_@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    53
    arrow-down
    3
    ·
    1 day ago

    Oh no, there goes my last reason to buy a Pixel as my next upgrade. Hello Moto!

    Google just can’t stop shitting the bed, can they? At this point you might as well buy an iPhone…

  • dan1101@lemmy.world
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    1
    ·
    1 day ago

    Google has gone full evil now, they want 100% control of our apps and data.