- cross-posted to:
- graphene_os@lemmy.sdf.org
- googlepixel@lemdro.id
- cross-posted to:
- graphene_os@lemmy.sdf.org
- googlepixel@lemdro.id
You must log in or # to comment.
Not sure I’d trust Graphene so long as Daniel is still involved
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.
manufacturer will offer GrapheneOS support on future versions of their existing models, priced similarly to Pixels.
Great, so I still won’t afford it…
Finally, some good news!
Let’s hope so. This should be my last Pixel if it all plays out like that.
I can’t wait to hear more. Please just make a phone that I’ll want to buy. My phone is 4 years old and there’s just nothing I want to replace it with yet.
It has become less and less of an issue over time though. Not only have I gotten used to using my phone FAR less with positive health results, but I have set myself up to have access to my Linux PC during the “chill with the family on the couch” times in the evening when one might zone out on their phone for a bit. That’s what I’m using right now!
Disappointed to learn about Fairphone lagging behind in terms of security… I really wanted to get one. But still good news I guess.
I’m not saying the information about Fairphone is wrong, but you shouldn’t assume it’s all as bad as they made it out to be. You’re reading a marketing pitch from one group that works with one vendor saying why another vendor isn’t that good.
Not too surprising as they don’t have the same company size, it’s hard to keep up.
Qualcomm isn’t exactly the best vendor to choose either. They’re US-based, closely-aligned with the US government as a military contractor, and the baseband/processor are heavily integrated on many chipsets, even sharing memory. That means a compromised carrier network could twiddle bits that the operating system sees, if they so wanted. Among many other issues.
There’s something about a Samsung Exynos designed to spec by Google that is actually more desirable even with the lack of compute performance. More fingers in the pot, less chance of some sneakiness working its way in.
Fuck Samsung.
Bixby! Bixby is on a fridge!
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 has more people working in Android then GrapheneOS does, it’s not possible for them to go completely independent.
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.
And edit72: I’m not just saying “hey magic people do this” - I’ve done this shit. I’m down to help, and I will. But the project owners need to step up for some actual work instead of just putting potpourri on something someone else built. Annoying side-story, I figured out how to cross-compile/rebuild/fix dependencies on a CPAP app called Oscar so it would be ARM-native on ARM Macs. Couldn’t figure out how to contact the devs after much digging to let them know, so. I have 1 of 1 copy of that app running ARM-MacOS native. Would be neat to help them replicate it though.
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.
deleted by creator
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
My money is on Motorola.
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.
The only way a graphene is phone gets major adaptation is if you could use pay with it.
I can pay with NFC and my GrapheneOS phone.
Where is this/ what app do you use?
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’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.
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.
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 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
I think you underestimate it. Where I live, 39% of card transactions used a mobile wallet last year.
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.
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
Oh man, please. My current Motorola could use replacing, official Graphene support would be fantastic
That would make sense as Motorola is fairly supportive of custom roms
It’s not going to be a Chinese company.
I wouldn’t bet on it. Lenovo is used across North American corporations, banks and government institutions.
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.
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.
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.
About fucking time.
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’d love an HTC again
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’
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.
Yeah, but the cpu sucks…. How can I justify to myself going from an iPhone 11 to something with a worse cpu
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.
Thank Microsoft.
Nokia just extended their existing contract with HMD for several years. Doesn’t seem like they’re going anywhere in the foreseeable future.
I wonder if this will have a significant negative impact on Pixel sales.
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.
The only reason I bought a Pixel is for GrapheneOS and the only reason my SO has one is also GrapheneOS.
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.
Yes it well. Their chips are pathetic and they seem to have no motivation to do anything about it.
The phone market is very saturated
I doubt it will have any effect
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.
I thought the exclusivity was because of Googles superior chip security?
Lol wut
Partially. It’s more that Google’s overall architecture was better for security, inclusive of many different features.
You can find a big ass list here: https://grapheneos.org/faq#future-devices
So far all I have seen them say is that the new device meets their requirements. Considering that this company has a lot of power over them I would be very tight-lipped about details in case they start throwing curveballs
