Sorry to piss off all the Apple shills on here, but sounds like an opportunity to me. I think there’s enough of us that want something better and some traction with Graphene and some Linux options. This should be a spark to ignite some fires. I’m disappointed but unsurpised by this news, but also a little excited about the window of motivation and opportunity this opens.
Honestly, I’m worried. Current Linux options are expensive and or shitty. IDK if Sailfish is still a thing. I can’t use Apple. If I keep taking good care of my not-so-shitty Xiaomi phone, maybe I have a couple more years until I’m pwned.
If you care about using third-party Android apps, I have good news for you, but grim news for the ecosystem. You will still be able to use third-party apps. But it’s going to be harder. You’ll probably need to use something like Shizuku or an ADB tool. The first wave of those affected won’t be you and me; it’ll be people who aren’t quite as technically competent. Then, slowly, a chilling effect will echo across independent development.
Its a version of android OS that can be installed on Google Pixel phones. Its a relatively easy switch if you’re technically inclined, but the device needs to be carrier unlocked.
No. As long as the base remains opensource (AOSP), they can remove the bad parts. Graphene has made numerous contributions to AOSP, I’m confident they can manage that. And if the user base growths, I hope their fundings will follow.
It would be a good thing for the world if AOSP was forked with big resources behind an open project with an open governance. But that needs lot of resources.
It’s Android with all of the Google removed where possible and sandboxed where not. You can choose to install the Google Play services and use it like any other Android phone or use it without any Google software.
Some things won’t work, namely things like some banking applications and NFC payments, because they require on hardware attestation that Google will not allow Graphene to pass. Essentially everything that isn’t banking/payment related works exactly like any other Android phone.
It is just a secure phone (though you can still install Facebook on it if you want) that is designed around mitigating attacks that could violate your privacy and security.
Very easy to install, you just buy a Pixel directly from Google (don’t buy from the carriers, they’ll be locked). Enable OEM Unlocking in the Developer menu and then plug it into USB and you can install it directly from the Graphene site via WebUSB. It takes about 5-10 minutes, then your phone will reboot (It’ll give you a scary looking screen about not running a Google OS that you’ll see every time it reboots but it’s just informational, it doesn’t affect anything and the system will boot into GrapheneOS in a second or two).
The more complete instructions and WebUSB install process:
My thinking is that the part of Google that I think is bad is their advertising and algorithmic recommendation systems which are built on private data that I no longer wish to divulge.
The Pixel is made by a company that used to be called HTC before they were consumed by Alphabet. That company produced good hardware that was smartly designed and innovative. That legacy continues with the device that Google has sells as the Pixel.
There are a few things about the phone that Alphabet has tainted, such as the inability to use NFC payments because hardware running GrapheneOS isn’t allowed into their secure hardware attestation chain. Not for any real technical reason, only because it allows Alphabet to disincentivize people away from a competitor by abusing their many monopoly powers.
GrapheneOS takes advantage of the excellently designed HTC hardware to create an operating system that is designed from the ground up to be secure. It then leverages the complete control over your hardware to put Alphabet’s other software inside of a little box where it constantly lies to the software in a way that lets your applications work without them actually being able to access everything on your device.
Yes, it is technically an Alphabet product and giving them money can feel distasteful. However, in this case by buying their hardware you can cut off their software, which is the actual thing that is negatively affecting everything.
Until then, I’m less worried about giving HTC money than I am about having a device that I know is under my control and that works to protect my privacy.
Why do banks need a hardware attestation, out of curiosity? I’d assume that banking apps are just clients so all that matters is if they have creds or not.
The banks don’t want their payment systems being accessed by devices that are compromised by malicious actors.
The attestation chain allows for Google to tell the apps ‘Yep, this system is running a known safe image that has been crytographically verified using the secure hardware on the device’. The apps will only allow their payment systems to be accessed (like, to send an NFC payment) if this check can verify that.
They don’t NEED it for NFC payments to work, this is a way of limiting attack vectors on their payment infrastructure (or, cynically, a way for Google to ensure that no competing OS can exist because people would rather give Google all of their privacy so they can pull a phone out of their pocket rather than a credit card.
Sorry to piss off all the Apple shills on here, but sounds like an opportunity to me. I think there’s enough of us that want something better and some traction with Graphene and some Linux options. This should be a spark to ignite some fires. I’m disappointed but unsurpised by this news, but also a little excited about the window of motivation and opportunity this opens.
Honestly, I’m worried. Current Linux options are expensive and or shitty. IDK if Sailfish is still a thing. I can’t use Apple. If I keep taking good care of my not-so-shitty Xiaomi phone, maybe I have a couple more years until I’m pwned.
PostmarketOS seems promising, though.
If you care about using third-party Android apps, I have good news for you, but grim news for the ecosystem. You will still be able to use third-party apps. But it’s going to be harder. You’ll probably need to use something like Shizuku or an ADB tool. The first wave of those affected won’t be you and me; it’ll be people who aren’t quite as technically competent. Then, slowly, a chilling effect will echo across independent development.
I look forward to LibrePhone coming online. I hope it comes soon …
“Librephone — Free Software Foundation — Working together for free software” https://www.fsf.org/campaigns/librephone
Could you go over what Graphene is for phones? Is it easy to switch to an alternative to android?
Its a version of android OS that can be installed on Google Pixel phones. Its a relatively easy switch if you’re technically inclined, but the device needs to be carrier unlocked.
If it’s just a fork of Android, doesn’t that mean 194 days from now they either need to branch off entirely and write their own code from here on out…
Or…
Never advance the base code?
No. As long as the base remains opensource (AOSP), they can remove the bad parts. Graphene has made numerous contributions to AOSP, I’m confident they can manage that. And if the user base growths, I hope their fundings will follow.
It would be a good thing for the world if AOSP was forked with big resources behind an open project with an open governance. But that needs lot of resources.
deleted by creator
I’ll switch in a heartbeat if they support a nonGoogle phone
They’re working on it. Unfortunately most phones have poor security hardware, which is why its limited to Pixels at the moment.
Good news!
Isn’t carrier locked phones exclusive to America? As far as I know, no other country lock their phones to a specific carrier.
It’s Android with all of the Google removed where possible and sandboxed where not. You can choose to install the Google Play services and use it like any other Android phone or use it without any Google software.
Some things won’t work, namely things like some banking applications and NFC payments, because they require on hardware attestation that Google will not allow Graphene to pass. Essentially everything that isn’t banking/payment related works exactly like any other Android phone.
It is just a secure phone (though you can still install Facebook on it if you want) that is designed around mitigating attacks that could violate your privacy and security.
Very easy to install, you just buy a Pixel directly from Google (don’t buy from the carriers, they’ll be locked). Enable OEM Unlocking in the Developer menu and then plug it into USB and you can install it directly from the Graphene site via WebUSB. It takes about 5-10 minutes, then your phone will reboot (It’ll give you a scary looking screen about not running a Google OS that you’ll see every time it reboots but it’s just informational, it doesn’t affect anything and the system will boot into GrapheneOS in a second or two).
The more complete instructions and WebUSB install process:
https://grapheneos.org/install/
What really bugs me about it: The first step from “how to ungoogle your phone” is “go, give money to Google” by buying their hardware.
It bugs me also.
My thinking is that the part of Google that I think is bad is their advertising and algorithmic recommendation systems which are built on private data that I no longer wish to divulge.
The Pixel is made by a company that used to be called HTC before they were consumed by Alphabet. That company produced good hardware that was smartly designed and innovative. That legacy continues with the device that Google has sells as the Pixel.
There are a few things about the phone that Alphabet has tainted, such as the inability to use NFC payments because hardware running GrapheneOS isn’t allowed into their secure hardware attestation chain. Not for any real technical reason, only because it allows Alphabet to disincentivize people away from a competitor by abusing their many monopoly powers.
GrapheneOS takes advantage of the excellently designed HTC hardware to create an operating system that is designed from the ground up to be secure. It then leverages the complete control over your hardware to put Alphabet’s other software inside of a little box where it constantly lies to the software in a way that lets your applications work without them actually being able to access everything on your device.
Yes, it is technically an Alphabet product and giving them money can feel distasteful. However, in this case by buying their hardware you can cut off their software, which is the actual thing that is negatively affecting everything.
I’d buy any other phone that fully supported GrapheneOS’s requirements for future devices.
Until then, I’m less worried about giving HTC money than I am about having a device that I know is under my control and that works to protect my privacy.
Why do banks need a hardware attestation, out of curiosity? I’d assume that banking apps are just clients so all that matters is if they have creds or not.
The banks don’t want their payment systems being accessed by devices that are compromised by malicious actors.
The attestation chain allows for Google to tell the apps ‘Yep, this system is running a known safe image that has been crytographically verified using the secure hardware on the device’. The apps will only allow their payment systems to be accessed (like, to send an NFC payment) if this check can verify that.
If you want technical details: https://developers.home.google.com/matter/primer/attestation
They don’t NEED it for NFC payments to work, this is a way of limiting attack vectors on their payment infrastructure (or, cynically, a way for Google to ensure that no competing OS can exist because people would rather give Google all of their privacy so they can pull a phone out of their pocket rather than a credit card.
What kind of traction? Is it missing something? Or do you just mean more developers behind it?
It’s missing a robust user base imo. More developers too.