#GrapheneOS
Final
10/15 1:03:52
π
What I can say for now:
- #GrapheneOS has partnered with a major Android OEM. One of the top ten.
- We aim to have a device by H2 2026, but potentially 2027.
- We have early source access for patches and, soon, major releases through our partner.
- We are aiming to get their next generation flagship devices able to support installing GrapheneOS.
- The device will have the flagship Snapdragon 8 Elite 2 (SM8850) SoC.
- We will continue to support Pixels if they continue to release with support. We will also aim to have Pixel 10 support once Android 16 QPR1 sources are available.
nostr:nevent1qqsd530424tlznva20dwhx4ypvjhenavulscljl86njedc2qen85kusppemhxue69uhkummn9ekx7mp0qgstamq7hv6fjwexll9g6wrs2q678ctm0ns7r7qy3vgxdl74lhv06gqrqsqqqqqp8p3p3p
ava
10/14 22:23:22
π
GrapheneOS is finally ready to break free from Pixels, and it may never look back
https://www.androidauthority.com/graphene-os-major-android-oem-partnership-3606853/
TL;DR
The makers of GrapheneOS have confirmed they are partnering with a major Android OEM to bring the privacy-focused Android fork to Snapdragon-powered smartphones.
The project has confirmed itβs bringing support for Pixel 10, but is unsure whether support will continue for Pixel 11.
GrapheneOS didnβt reveal the name of its new partner, but said that those devices will be priced in the same range as Pixels.
---
Saw this coming. It would have been nice to see more transparency and less "everything is fine, we've got it covered" when I engaged with them about the recent Google updates just two months ago. The technical realities I was asking about clearly pointed here, and the dismissive responses didn't inspire confidence.
nostr:nevent1qqsrnwcn5nlhs00nycrtvjf2d7g0qcudua6l3x47yr38tzparffuvxsprdmhxue69uhhyetvv9ujumn0wd68yurvv438xtnrdakj7q3qf6ugxyxkknket3kkdgu4k0fu74vmshawermkj8d06sz6jts9t4ksxpqqqqqqz68manv
Either way, this kind of partnership was supposed to happen years ago before that deal fell through. Let's hope all those who recently bought Pixels specifically to run GrapheneOS will get the years of updates they expected before needing to migrate to this new device.
I stopped using GOS as a primary device months agoβit was a pain getting my data off, and Google's Play Integrity API is making it harder for apps to install on custom ROMs.
I still recommend them to most people for secondary devices. The privacy fundamentals are solid, but GrapheneOS has always relied on Pixel's superior hardware security (Titan M2, verified boot, etc.).
Finding an OEM partner with comparable hardware security has been a bottleneck all along. I'm genuinely interested to see what they come up with.
#IKITAO #Privacy #GrapheneOS #Pixel
Zaikaboy
7/29 16:01:52
π
In any case, as it's our government imposing this, it won't work and your average 3 year old will be able to bypass it!
#GrapheneOS #IVPN #Runyourownserver
β¬
4ba01911f5d9a4d545ceab52dc6a267f12381d057bc22c87e4983bfd7b79eef3
β¬
β¬
Zaikaboy
7/29 15:50:35
ππ€
Moaning Nostrians. They say a good woman moulds her man π€. She's definitely a keeper!
Final
7/2 2:10:19
π
#GrapheneOS Android 16 builds are now available in the Alpha channel. We did it.
Zaikaboy
3/21 19:31:29
π
Time for people to ditch the fruit, degoolag the droid. #GrapheneOS for the win
β¬
The Fishcake (nostr.build)
3/21 19:29:50
π
HTTP-402 exists, itβs only a problem with clients and its support. I think Amethyst or Snort had some support for it, but many clients will be blocked from App stores due to payments without cut to the phone OS maker π
β¬
mike
3/21 19:24:33
ππ π€ π€£ π§
I still think building platforms on NOSTR to emulate Patreon and OnlyFans are compelling propositions.
Paying directly for content on NOSTR is native and doesn't require a trusted third party.
Do we need a paywall NIP?
ava
1/6 16:46:39
ππ§‘
One thing I do not miss from running #GrapheneOS on my main device is the "Optimizing apps" process after each update that significantly slows your phone down and cripples its usability for up to 40+ minutes.
#IKITAO #Privacy #Tech
