GrapheneOS could break Pixel exclusivity in 2026 with major OEM deal
10 months ago by baatliwala to c/android
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.
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.
That would make sense as Motorola is fairly supportive of custom roms
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.
What makes you think so? This (admittedly pretty vague) response indicates quite the opposite: https://grapheneos.social/...
I wouldn't bet on it. Lenovo is used across North American corporations, banks and government institutions.
How repairable are Motorola smartphones?
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
How repairable are Sony smartphones?
Samsung doesn't really rely on Snapdragon too much, so that might be out.
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.
True. But my S3 ran like a young racehorse when I installed Cyanogen back in the third age, when the orcs still roamed Rohan.
Not certain Sony counts as worldwide anymore since they seem to have retreated from the US.
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.
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.
Sony is sooooo expensive though…
They are called HMD now.
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
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!
Bixby! Bixby is on a fridge!
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
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
Let's hope so. This should be my last Pixel if it all plays out like that.
I paid $120 for each Pixel I own.
I refuse to pay a premium to have the "latest and greatest gadget"
How's the battery life so far on the phones you've had?
Pixels will be supported until EoL. You can get a used Pixel 8a or 9a, which will get supported until May 2031 and April 2032 respectively. Both feature modern, important hardware security features, such as the ARM memory tagging extension.
I wonder if this will have a significant negative impact on Pixel sales.
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 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.
Used Pixels are cheap.
I have three, paid about $120 for each one.
Using current phone rather than buying a different one to replace it is a lot less ewaste.
I am also going to see what happens with Graphene's new partnership. I don't really like the idea of being locked down to specific hardware.
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.
The phone market is very saturated
I doubt it will have any effect
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
Lol wut
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.
GrapheneOS has criticized Fairphone from a security perspective for a long time, long before any partnerships with OEMs were ever made. GrapheneOS chose to partner with this specific company (which they don't want to broadly disclose yet) because they have shown, that they actually care about security, and are willing to invest time and effort to meet the GrapheneOS device requirements, not the other way around.
Not really a 'Fairphone issue' and more a general 'smartphone issue'. The vast majority of OEMs don't invest into security and just use random parts with mostly stock Android. Sometimes they actually make it worse by replacing AOSP apps with their less secure ones. Which sadly will become more common with Google abandoning AOSP.
Fairphone simply isn't focused on security. Should that change? Are Fairphone users interested in improved security?
Brax?? Lol
Some are saying dude is a snake-oil saleperson. Idk always felt a bad vibe about that youtube channel.
oops all Xiaomi!
largest market share outside of Samsung and Apple.
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.
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.
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.
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.
Nothing needs to be disabled, since it isn't present in GrapheneOS in the first place. 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.
But the app might refuse to run without those checks being done. Or a new format, apkx2 I don't know, might only be able to be decrypted with the proper key and only once verification. It's not a new tactic. I'm very, very glad to see this type of development finally happening (though, admittedly, a couple decades later than of hoped), but it's now a new ballgame, and google owns the stadium, the seating pricing, and concessions, the parking lot, and ticketing counter. I'm concerned we've waited too long. What's GOS's plans for this? They're, essentially, going to have to create a new ecosystem, with most of the growing pains of new ecosystems.
I bet on Steam /hjk
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, as they could result in bugs: for example, many Samsung cameras only expose a 16:9 section of the 4:3 sensor in the open Camera2 API; other frequent issues with custom ROMs include VoLTE, Play Integrity and bootloader relocking).
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.
my hot take: while this is good for users in short term, in long term it just prolongs non-copyleft android OS hold for google.
my only hope for grapheneos is that they pointed that they may move from android too.
as I said in last post, I only see copyleft as a viable alternative. too many dev efforts forked and privatized. android should have been a warning. but many devs just think open source is enough. and they still think getting adapted by big corporation will not change the direction of projects.
I am personally going in the direction of testing and helping only copyleft projects. so I skipped RedoxOS. even-though I like rust and new microkernel OSes.
If I am going to give my time to a project (small as it is) I don't want it to end up like android.
I completely agree, and a strong copyleft licence is something that GPLv3 does much better than its predecessor, which is unfortunately why it has not been adopted by the Linux kernel. I foolishly assumed that GrapheneOS, given the values it professes, would be distributed under the GPLv3 licence, but I have now discovered that this is not the case, in a move that I frankly cannot understand. Hope that changes in the near future, but it's not very likely to happen I guess
yea, a lot of open source projects are done by people that don't see the point of copyleft software.
I think a lot of people just go with the 4 freedoms that RMS laid out.
when I read devs' reasons to use non-copyleft license, it boils down to "I don't want to limit freedom of later devs even if those devs are gonna fork it and make it private". even when they say "I don't care" they mean the same.
and they have the right to see it that way. my thinking is that humanity used to not have copyright at all. and the reason we are not living in caves is that knowledge mostly was spread (even when going from father to son only).
so I think software needs to go that way as much as it can.
I understand that developing software needs money and I even understand patents to an extent. but shit gone mad and patents are gone crazy. android is THE shining prime example of what happens even with a company that at least pretended not to go this way (that was naive to think they wouldn't)
that's why I going to write any software I write (even though I am just starting programing) in the most copyleft license ever I find.
maybe even more stalman than gpl3.
btw is there any site that explains the practical diff between gpl2 and 3? not tldr but not in details either, just maybe explain case base what happens?
Fairphone is very far from meeting GrapheneOS' requirements: https://grapheneos.org/faq#future-devices
They also openly supported harassment of GrapheneOS developers in the past.
A lot of their marketing is very misleading, or completely false. They're not the moral and ethical company they claim to be.
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
Anyone guessed Jolla? If not, I place my bet...
....good point...
Not sure I'd trust Graphene so long as Daniel is still involved
In all the time i looked online Ive never found a legitimate basis for these vague claims of drama around Graphene. See a lot of it in Louis Rossman circles (nothing against him, but he made a dramatic video on YT about leaving GrapheneOS) it’s reactionary at best. Someone got blocked people got mad, full story only the ones directly involved know.
Louis was directly involved with this. He's the one who exposed the whole situation and brought receipts.
Daniel is extremely paranoid (arguably part of why GOS is as secure as it is), but that paranoia can also lead to anxiety and assuming everyone is "out to get you".
Lots of people blocked. Rossman made excellent points.
Techlore and Rrossman both have excellent videos going into detail the long history of his negative impacts on the community
Because linking to the site itself rather than the video is useless - https://techlore.tv/w/auQigUjYTqkME1Bj7uPEPm
I don't know... Part of me thinks that someone overruled Daniel on this decision. He stepped down as the main dev years ago, but is still a director... maybe the other directors overruled Daniel?
But again, I don't know. I'm just shooting from the hip.
Sock puppets.
@lemdro.id
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Rules
Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
go to feed...
@lemdro.id
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Rules
Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
go to feed...
There aren't too many OEMs that sell worldwide. So that would be one of Samsung, Sony, Moto, OnePlus.
save