GrapheneOS (@[email protected])
grapheneos.social
We could continue supporting future Pixels such as the Pixel 11 and Pixel 12 after we have another option available but we won't depend on them continuing to provide alternate OS support. It's good that the Pixel 10 still provides it since our alternative is a year or two away.

We’ve received the Pixel 10 we ordered and have confirmed it supports unlocking, flashing another verified boot key and locking again.

Our Pixel 10 support will likely only be possible to complete after we finish porting to Android 16 QPR1 which is being released in September.

A second Pixel 10 we ordered has arrived at a package forwarding service in the US to be shipped to a country without Pixels available.

We’ll order a Pixel 10 Pro (XL) and Pixel 10 Pro Fold for our main device testing farm today too since we’ll supporting all 4 variants of them.

Previously, we likely would have been able to implement support for the Pixel 10, Pixel 10 Pro and Pixel 10 Pro XL in the next 48 hours. However, we likely need to wait for Android 16 QPR1 and our port to it since we don’t expect a Pixel 10 device branch will be pushed to AOSP.

We’ve received confirmation that Android is switching to having quarterly releases across devices. There will be 3 quarterly and 1 yearly release of Android and the Android Open Source Project. Monthly releases are Pixel exclusive and will have far fewer changes than before.

Previously, only Pixels shipped the quarterly releases in practice. Other OEMs will now be pushed to ship those, but not the monthly releases which are now officially Pixel exclusive. Please note monthly Android Security Bulletins are a different thing from the monthly releases.

Android Security Bulletins are backports of a subset of patches deemed High/Critical severity to older Android releases. That currently means the initial yearly releases of Android 13, 14, 15 and 16 without the monthly/quarterly updates for those. This will need to change now.

The changes are acceptable for us and we can deal with it. We’re currently working with a major OEM towards future generations of their devices meeting our requirements and providing official GrapheneOS support. GrapheneOS on both Pixels and these future non-Pixels will be fine.

Pixels are still the most secure Android devices and the only ones combining a high level of security with proper support for an alternate OS. However, it’s clear they don’t value alternate OS support and won’t remain the best devices for GrapheneOS once we have official ones.

We could continue supporting future Pixels such as the Pixel 11 and Pixel 12 after we have another option available but we won’t depend on them continuing to provide alternate OS support. It’s good that the Pixel 10 still provides it since our alternative is a year or two away.

  • mmmac@lemmy.zipEnglish
    4·
    1 day ago

    Sweet! Looking forward to finally upgrading to the pro. Been with graphene OS since the 6 launched and have always been with the baseline model (6 - > 9, to the 10 pro now)

    Looking forward to the optical zoom the pro line provides, as well as the reported efficiency gains of the new TSMC tensor 5

  • eelectricshock@lemmy.worldEnglish
    6·
    2 days ago

    Big up for the GrapheneOS team for building a very secure operating system despite Google software developers trying their hardest to lock down the system!

  • muntedcrocodile@lemmy.worldEnglish
    171·
    2 days ago

    Working with a major OEM that’s awesome absolutely incredible and what GrapheneOS needs. I see Linus from LTT is also running GrapheneOS at the moment so that’s going to be interesting. Hopefully the OEM ur working with will also provide GrapheneOS out of the box as an option that would be absolutely incredible.

  • Heliumfart@sh.itjust.worksEnglish
    113·
    2 days ago

    I really want to switch to graphene. I’m just so addicted to my tap and pay. Especially in summer, I can leave the house with nothing but my phone.

    • ColeSloth@discuss.tchncs.deEnglish
      1·
      4 hours ago

      I contemplate getting a phone case with just my cc in it, and still using my phone like tap to pay. If it’s not an rf prtected case I think it should be able to read the card straight through.

    • berrodeguarana@lemmy.eco.brEnglish
      1·
      11 hours ago

      I’m on the same boat. I’ve been thinking of getting one of those Garmin smartwatches with Garmin Pay to circumvent this issue but we’ll see.

      Much better to go to the beach/pool/BBQ with just your watch to buy foods and drinks

    • typhoon@lemmy.worldEnglish
      19·
      2 days ago

      I’m still old fashioned. I need a wallet with my driver license, some cash and some cards

      • xploit@lemmy.worldEnglish
        5·
        2 days ago

        That’s why I use a phone wallet case - bonus point for being almost impossible to smash my screen.

    • jobbies@lemmy.zipEnglish
      14·
      2 days ago

      I loved tap and pay and relied on it heavily. Its amazing how quickly you get over this. If I can do it anyone can! Its worth it for the peace of mind Grapheneos provides.

    • Darren@sopuli.xyzEnglish
      6·
      2 days ago

      I bought a MagSafe case for my Pixel 9, then one of those MagSafe wallets. It’s not quite as fluid as regular phone payments, but it works.