Please be Motorola and put it on my Razr+…
Hope for Motorola but for some reason I want to put a guess in for LG
LG who exited the smartphone market in 2021?
FR?
Yeah mate, long gone. Real shame that, loved their V-series.
oops all Xiaomi!
largest market share outside of Samsung and Apple.
I’m hoping for motorola too.
Add Nokia, Brax, and other smaller phone companies that actually value privacy, open-source, repairability, linux, and consumer-friendly then we got a deal
Brax?? Lol
Hey I don’t know a whole lot about it but it seems kinda interesting
Some are saying dude is a snake-oil saleperson. Idk always felt a bad vibe about that youtube channel.
Don’t know if that’s an existing phone because from what I read the new integration will be for a new/next gen device. So not anything that’s on the market now
Yah, a guy can dream though, can’t he?
I bet on Steam /hjk
I wonder if this will have a significant negative impact on Pixel sales.
I would assume it will, if the SoC performance is in the same ballpark. Pixels have good NPU specs but their CPU, GPU and RAM feel like mid range options compared to snapdragons. So I don’t think that’s a high bar to hit. I don’t run graphene because I’m not buying a google phone, but I would consider running it on something else.
The only reason I bought a Pixel is for GrapheneOS and the only reason my SO has one is also GrapheneOS.
I can’t see how it would. Techies are the only people who know what GrapheneOS is, and even then it’s a small percentage of us. The average person still asks if you have an iPhone or a Samsung.
I hope it takes off, but even if it does the dent will be small.
I want to try GrapheneOS. But my current Samsung phone still works. If I ever do switch, I would be looking for a Pixel on the local resale market so as to avoid giving Google money, anyway.
It’s what I did. I bought a used pixel 8 and only regretted it after the recent strong of Google shenanigans. I’m still looking for a proper Linux phone solution in the meantime. I’d rather not have to be reliant on anything Google does in the future.
Used Pixels are cheap.
I have three, paid about $120 for each one.
Yes it well. Their chips are pathetic and they seem to have no motivation to do anything about it.
Every cell phone manufacturer has some interest in diversifying the operating systems. Because Google develops Android and sells its own cell phones, it has an unfair market edge. And now Google is threatening to filter out apps that it doesn’t like which makes the risk even higher.
So we can be sure all of the other major manufacturers of Android phones have considered if they’d like to support other distributions.
Maybe they will make deal with other distributors to ship their exclusive app stores and so that would be a good economic move for them
According to details shared on Reddit, the partnered manufacturer will offer GrapheneOS support on future versions of their existing models, priced similarly to Pixels. These initial devices will feature flagship Snapdragon processors, which GrapheneOS notes provide significantly better CPU and GPU performance compared to Google’s Tensor chips. The Snapdragon platform also bundles high-quality wireless connectivity, eSIM support, and decent image processing capabilities directly into the system-on-chip.
Oh thank you. Let’s hope for something nice for a change.
This might be it. This might be the alt phone to defeat all others. Flagship chip + graphineOS features and long term support is a killer killer deal.
There aren’t too many OEMs that sell worldwide. So that would be one of Samsung, Sony, Moto, OnePlus.
I hope Sony simply because I want a headphone jack and an MicroSD card reader. Their phones are already pretty bloat free and their custom apps, usually focused on the camera system, would mesh very well with GrapheneOS. Would be a great way for them to become relevant again.
Hot take, but no alt phone will reach critical mass without those features. They need support from even the most stubborn users
If the Graphene phone wants to presents itself as a consumer-first phone, I agree.
How repairable are Sony smartphones?
Samsung doesn’t really rely on Snapdragon too much, so that might be out.
The US-based flagships do.
Yeah, but European ones don’t (or at least last time I checked). I guess that would be a hassle for them to keep compatibility.
Samsung is also a synonym for useless bloat, locked boatloaders, intrusive ads, and every other hostile feature ever. They are the last one to open up their phones.
My money is on Motorola.
That would make sense as Motorola is fairly supportive of custom roms
I agree, Motorola is owned by Lenovo. They have found middling success with the return of their Razr line and with phones in the lower to mid tier range. But they really want something super flagship. Something like the Think Phone would have probably sold really well with a Graphene option.
Device hardware, firmware, and software are integrated to protect your most sensitive data from mobile threats. With Moto KeySafe, PINs, passwords, and cryptographic keys are isolated from other device data for an added layer of high-level security.
Yeah this sounds like what Graphene insists on.
That sounds like a fancy speak for a Trusted Platform Module. Isn’t some kind of TPM mandatory to obtain a google certification for a new device?
Yeah, a TPM or secure element. I don’t think it’s required.
It (unfortunately) isn’t required. Most current Android devices on the market have serious security issues (most notably, full disk encryption can easily be bypassed due to a lack of effective unlock attempt rate limiting) due to their lack of a secure element.
Are you sure there’s no rate limiting? My phone definitely does rate limit the on-boot disk decryption prompt. Do you mean there’s no rate limiting if someone detaches the NAND and brute-forces it off-device?
The only way a graphene is phone gets major adaptation is if you could use pay with it.
Not really. The kind of people this ROM caters to are exactly the kind of people who don’t use Google Pay to begin with.
There’s other pay features in the world like Wero and MobilePay
I can pay with NFC and my GrapheneOS phone.
We need details please
I’m in the UK and use Curve. I’ve used it locally, of course, but also in Singapore, Australia and Japan and it worked without incident.
Where is this/ what app do you use?
I’m in the UK and use Curve. I’ve used it locally, of course, but also in Singapore, Australia and Japan and it worked without incident.
Not OP, but my (German) bank supports the Digitales Bezahlen App with GrapheneOS. I used it exactly twice, both times because I forgot my wallet at home.
There are several supported apps, such as Curve Pay, PayPal, and banking apps that have their own tap-to-pay implementation.
https://shkspr.mobi/blog/2025/06/contactless-payments-with-grapheneos/
https://grapheneos.social/@GrapheneOS/115295538501760765
You can also use the
contactless payments supportedtag when searching the GrapheneOS banking app compatibility list on GitHub. https://github.com/PrivSec-dev/banking-apps-compat-report/issues?q=is%3Aissue+label%3A"contactless+payments+supported"
I think people overestimate that feature. Where I live you still have to hand your card to the teller most of the time and nobody is handing their phone over for tap to pay.
I think you underestimate it. Where I live, 39% of card transactions used a mobile wallet last year.
I pay with a normal card but I’d say the majority of people around me pay with their phone.
Also, I need to use my bank app to pay for things online. I scan a QR code and confirm the payment with a pin or fingerprint. Correct me if I’m wrong but I think many bank apps also don’t work properly with graphene.
Edit: maybe I’m getting confused, I thought bank apps normally needed google play services and that because of that they don’t work on grapheneOS, but I don’t know if that’s correct
hmm how bout round the world?
Like Germans prefer cash but tons go all digital—yuge in China for example, Apple Pay’s big stateside (USA)…
Curious your region btw to expand my knowledge on this
I live in the US and I also just got back from a 10 day trip that had me in 6 different airports around the US and saw basically nobody using their phones to pay. I saw a bunch of people using the translate app, the camera, FaceTime, Apple wallet for boarding passes, but no tap to pay.
I think it’s because the places that use it also have their own apps, like Starbucks. You can order and pay in the app and if you are likely to setup Apple Pay you are probably fine going all the way with the app too. The same is true of Walmart and other major retailers who also specifically don’t take Apple or Google pay because they want you to use their app.
So random that the USA is lagging behind in this regard, travelled Europe - everyone using phone pay, and in Australia my home country, it’s pretty much the only way people pay nowadays.
It’s heavily used everywhere else in the world, the US is well-known to lag behind on payment technology. It’s like travelling back in time when you go there.
I pay with my phone literally everywhere in Canada, haven’t opened my wallet in months. I was in the US last year and they didn’t have mobile payment terminals at restaurants so you always had to pay for sit down service at a counter, always wanted me to sign for tap, kept calling it Apple Pay instead of tap or contactless, had places that would only swipe a physical card which isn’t even allowed in other countries anymore, it’s crazy.
Walmart takes tap in Canada, they were one of the last holdouts. The “individual app for each service” thing is very American, even American companies abroad don’t do it because they’ll lose business. It’s the same thing with cash transfers. There are 100 different private ways to send money in the US. PayPal, CashApp, Facebook Pay, Apple Pay, Venmo, etc.
None of those exist in Canada because we just have Interac e-transfers. Hard to compete with free & automatic support by every bank account in the country. Other countries have similar systems. The US has Zelle but as far as I know that was implemented way later and doesn’t have the mindshare.
How repairable are Motorola smartphones?
I have had several versions of the Moto G family and they’re pretty easy to repair. Usually under $30 for a screen. Trickiest part is glueing the back panel back on.
Oh man, please. My current Motorola could use replacing, official Graphene support would be fantastic
It’s not going to be a Chinese company.
How come? I’d bet they’d be the most easiest “oem” to get started with.
All western ones will be on the mercy of google licencing, so I’d guess no one wants to burn bridges.
I’m quite sure no one would consider Chinese company as safe option for privacy and clearly security focused phone.
Also as Sony already has the Sailfish support the company is likely going to be Sony.
I wouldn’t bet on it. Lenovo is used across North American corporations, banks and government institutions.
What makes you think so? This (admittedly pretty vague) response indicates quite the opposite: https://grapheneos.social/@GrapheneOS/115118480213473033
Ooh yeah let’s get a 6" 2025 take on the OG Motorola Droid with the slide out keyboard, to make it more linux-phone-y.
Not certain Sony counts as worldwide anymore since they seem to have retreated from the US.
Genuinely wish it’s a Chinese OEM, I’d love to run Graphene on something like the Xiaomi 17 Pro
Chinese phone cameras are far superior than anything else. It would be cool tbf
Finally, some good news!
But if google goes on with locking out the app store with the developer verification bs, how would would this play into that? If Aurora won’t install the app or the app won’t run, then we’ve accomplished little in that area. I’m really hoping I’m missing something.
Custom ROMs should be able to disable the checks. My bigger concern is what it does to the open app ecosystem as a whole.
TBH I would actually expect GrapheneOS not to disable these checks. GrapheneOS devs pride themselves to have the best implementation of the official Android security model, and enforcing signature checks is likely part of that…
They might add additional certificates I guess, to allow their own apps, and maybe a selected few others.
This is incorrect. The sideloading checks are implemented in Play Protect, which needs elevated privileges to function. On GrapheneOS, Google Play services run with normal privileges, just like any other user-installed app. This means, there are no Play Protect checks in GrapheneOS, and there will never be. It would only be possible on ROMs, such as LineageOS with Gapps, where Play services are installed as system apps, running with higher privileges than all other apps.
Well, good to know.
I was thinking more about the way of Android security models, and that it would make sense for GOS to restrict available storefronts to stay consistent with their way to implement them. But good to know that it will not automatically happen just by updating the google services.
And I would also think that people would likely complain if they where to implement it in a different way.
Except this ‘signing’ is more of a control feature than a security feature. Just because Google markets it as a security feature doesn’t mean it is.
Well… The Android security model, as it is implemented in stock android and GOS, is about top down control, the full trust is given to the system vendors, not the end users. No rooting for instance. From this perspective not allowing installation of apps that cannot be blocked by the system vendor, fits well with that model.
TBH, I am not a fan of that security model. And this is my critique of GOS. It doesn’t allow the user full access to their device, so that they can check and control what each application is storing or sending to third-party servers. Instead it is on full security and allows apps to store and transfer information to which the user has no access to.
But the system vendor/developers would have that access, because they control the whole base system.
The focus of the Android security model and in turn of GOS is on security, at the cost of privacy or freedom.
Whats that?
A HW manufacturer (aka OEM) will share specs and interfaces with the GrapheneOS team, who will develop an official port for the hardware, with support and everything. The OEM will allow bootloader unlocking and maybe even ship some of these phones with Graphene preinstalled, depending on what their contract with Google allows. To this day, only Pixels have officially received GrapheneOS releases because Google has documented their hardware interfaces in AOSP. Now, AOSP is no longer developed with the Pixel as a target but a virtual device, putting the future of GrapheneOS on Pixels into question (the team refuses to use reverse-engineered hardware interfaces, which may result in bugs).
Thanks for the detailed explanation.
thank you for explaining
the team refuses to use reverse-engineered hardware interfaces
Small correction: Current and future GrapheneOS releases for Pixels are produced by reverse-engineering Pixel OS releases. adevtool was developed together with the developer of ProtonAOSP back then, to automate extracing several components from the stock Pixel OS.
Thx
Anyone guessed Jolla? If not, I place my bet…
Do they count as major?
Certainly not
took their time
I’m skeptical. Even knowing how paranoid Daniel is about, well…everything.
Who remembers the last time a custom ROM got an OEM deal? It is the reason Lineage OS exists today…
With everything Google is doing with Android, they might not have a choice. It’s either this or possibly one day no longer being able to work on Graphene.
Graphene would be better off cutting themselves off from Google’s OS future entirely and pivot the fork as quickly as possible to remove all dependencies. Probably too arrogant to consider it, though. Also becomes much more work.
Google will forever control Android. I would prefer if he just worked on Linux (phone & desktop) to the benefit of all.
You’re under-thinking it.
In pseudo-correct but probably not order:
- Step 1: Collect underpants
- Step 2: Keep receiving Google security updates but stop updating Google mainline
- Step 3: Start replacing the underbelly to just raw Linux (or BSD or whatever) and slowly shift the “Android” portion to a VM/container
- Step 4: RIL and other stuff (probably should happen first) have to be packaged up and become their new entity on the modem side (also probably the biggest challenge, but manufacturers and ODMs provide dev kits)
- Step 5: ???
- Step 6: Once the Android side is safely firewalled away from the core OS, start embracing something like PostmarketOS
- Step 7: GUI/graphics are built out with the Android pieces still running in a container
- Step 8: Start writing applications that replace the Android applications, go one by one, remove dependence on each Android application as you go while still maintaining compatibility (I mean the core OS ones that make the device at least basically functional, the F/OSS devs will have to each rewrite/change their apps, or some other magic can be inserted here that isn’t really magic.)
- Step 9: Once the OS itself is beefed up enough, retain Android container for the needs of some for some uncomfortably long frustrating time to maintain, but not too long
- Step 10: Have Obtainium/F-Droid/etc. all simultaneously pivot and start providing apps for the native OS as well as maintaining backwards compatibility with the Android apps in the container
- Step 11: Once some magic point, forced or otherwise happens, sunset the Android portion of the app stores. Keep the containerized Android around a little longer
- Step 12: Sunset the Android container, at this point the phone should be running 100% “native” OS and apps and store
- Step 14: Profit!
There are industry blueprints for this. Apple is probably the best example of how to implement these shifts, from OS 9 (co-op MT proprietary OS)->OS X (BSD-NextStep-based Unix OS), 68k->PPC, Replacing Unix underpinnings with Apple Frameworks, PPC->Intel, OS X->iOS, Mac from Intel->ARM, etc. etc. They frequently used containerization to keep the old running while the new was built up around it and replaced. It is a solid proven design pattern.
I think that sounds like a damn solid plan, personally. Not sure if the GrapheneOS devs would go for it. The lead dev (who I thinked stepped down, so may not be a factor now) had some strongly negative opinions towards a Linux phone due to all of its security holes compared to Android, but like… It’s not as if those things couldn’t be addressed like you describe. It would just take time.
Google has more people working in Android then GrapheneOS does, it’s not possible for them to go completely independent.
I dearly remember my OnePlus One with CyanogenMod, if that answers your question?
But do you remember the clusterfuck that was Cyanogen Inc?
Nope, only from what I’ve read about it more recently. Back then I was just hyped about getting an even smarter smartphone with a better OS and all the new possibilities it brought to me. It was by no means my first smartphone, and I had already explored using my phones in interesting, useful or smart ways, but the OnePlus One felt like a very big upgrade in my daily life, especially since things were moving pretty fast on that area 10-15 years ago. CyanogenMod was definitely an important part of that improved Android experience, and I don’t think the corporation clusterfuck affected that, really, as I did not at all notice what was going on over there.
That situation destroyed CM and its team. Lineage OS was the proverbial phoenix that rose from the ashes of CM.
I’ll hold off on a new phone to watch for this. Android could be great without Google’s nonsense. An OS that has high end hardware support and continues to work on convergence with desktop Linux both by the communities development and Google’s
Exactly. Google is evil, and I don’t want Google-related things on my phone.
So who do we think? It’s not Fair phone and it sounds like it’s not oneplus. I’ll be needing a new phone within the next couple of years, if they roll it out soonish
I mean those are the first two I’d suspect too. Maybe Sony or Pico? They’re both pretty dev friendly.
I hope it’s Sony
Sony is sooooo expensive though…
They said it’d be on par with a Pixel, so either a reasonable Sony or not Sony…
The Sony xperia 10 VII has a micro SD slot and a 3.5mm port so I’m hoping Sony too.
Edit: looks like the OEM selected doesn’t have compatible phones today but would in 26’
Yeah, but the cpu sucks…. How can I justify to myself going from an iPhone 11 to something with a worse cpu
I’ve completely forgotten that Sony makes phones also, but this phone is great on paper. So much so that, next year, when I will be switching back to Android from an unfortunate ios hiatus, I will definitely consider one (maybe viii? ). Thanks for reminding me.
Praying from this end of my Sony xperia
I hope Nokia
They are called HMD now.
I actually think this could be it. Nokia has always been a little adventurous with their operating systems, and I think they are eager to claw back their old reputation.
It’s not.
Have a friend who works at a decently high position here in Finland and they actually are considering exiting the smartphone market all together because the margins are too small and they make easy more money on other things, like 5G equipment. They kind of want to move past being associated with phones basically.
I’d love an HTC again
