671–680 of 967 posts
Earlier quoted context omitted.
Graphene is supposedly working with a major OEM manufacturer to have future device support independent of google, on a flagship device. It's been in the works for awhile but it's very exciting. https://www.androidauthority.com/graphene-os-major-android-o...
I hope it's Fairphone.
Earlier quoted context omitted.
The whole reason why GrapheneOS is superior to its alternative is because they do all that. I also with they could support non-Google phones, but that's a problem coming from the manufacturers, not from GrapheneOS. My understanding is that there are close to half a million GrapheneOS users. And many potential users don't want to buy a Google phone. So it feels like it is starting to become worth considering for manuf…
> The whole reason why GrapheneOS is superior to its alternative is because they do all that. What is "its alternative"? > I also wish they could support non-Google phones, but that's a problem coming from the manufacturers, not from GrapheneOS. The manufacturers aren't blocking the installing of GrapheneOS...
I meant alternativeS, sorry. Well, anything AOSP-based that is not Android.
> The manufacturers aren't blocking the installing of GrapheneOS...
Of course they are not. But they produce hardware that is not secure enough for GrapheneOS to consider. I wish they saw value in GrapheneOS and produced hardware that met their requirements.
It's actually weird, because I'm convinced that it's completely worth it: just add those requirements to the design of one new model, and a potential of hundreds of thousands of people may buy it just for GrapheneOS.
Earlier quoted context omitted.
You can use labels for contact scope.
You might want to read my comment again. :) If you use labels, the app will have full access to the associated contacts, not just to their names & phone numbers.
This doesn't answer your question, but in case it helps for others out there: it's possible to use WhatsApp with no access whatsoever to your contacts and I used it that way for years. Connecting with people is slightly jankier but it still works.
Earlier quoted context omitted.
Graphene is supposedly working with a major OEM manufacturer to have future device support independent of google, on a flagship device. It's been in the works for awhile but it's very exciting. https://www.androidauthority.com/graphene-os-major-android-o...
I hope it's Fairphone.
It's just so damned convenient. And the recording of transactions on the phone saves me having to collect paper receipts.
Earlier quoted context omitted.
GOS has minimum hardware requirements and most of the available smartphones don't meet them
That's like saying Tulip blocked the installation of Vista because they didn't install enough RAM to run it The OS makers don't have to go out of their way to support a device they don't want to (that's the beauty of open source passion projects), but it's also not like any manufacturer (that allows bootloader unlocking or ships an unlocked bootloader) is blocking GrapheneOS or anyone else from doing it, which the qu…
I agree, but you are the one who talked about "blocking". I did not :-).
And once you are on GrapheneOS, break free from your proprietary watch ecosystem and switch to GadgetBridge ( https://gadgetbridge.org/ ) I run a Thinkpad with NixOS and KDE, a Pixel 9 with GrapheneOS, and an Amazfit watch paired with GadgetBridge on my phone. It's a testament to the hard work of the FOSS maintainers of these projects, and the spirit of open source, that everything works flawlessly together without a…
> And once you are on GrapheneOS, break free from your proprietary watch ecosystem and switch to GadgetBridge Then switch back to Google/Apple after half a year when you discover that you can’t run - your banking app - any government app - the app required to access large sports events - the pandemic tracking app without which you can’t enter an airport - various other random apps because they ALL detect that you’re…
Also, do not leave your bootloader unlocked. That is an incomplete GOS install and you will need to lock it to secure your device. Not locking it is both insecure and will make a much higher number of apps fail.
GrapheneOS needs at least the modem blob provided by the OEM. It runs as root, it has full network control. Same could go for other "drivers" like wifi+bluetooth. Privacy is more a dream than a real thing.
https://grapheneos.org/faq#future-devices
8th, 9th and 10th gen Pixels provide our full set of requirements with 7 years of support from launch. 6th and 7th gen Pixels are missing the ARMv9 security features including the extremely important hardware memory tagging (MTE) feature we heavily use to protect against exploitation. Even the first devices we supported back in 2014 including the Nexus 5 had isolation for the cellular radio but similar isolation for Wi-Fi/Bluetooth started with the Nexus 5X.
Earlier quoted context omitted.
You can lock the bootloader again with GrapheneOS and many banking apps work.
You won't pass Google Play hardware attestation that way, and you won't find a bank in Europe or the UK that doesn't require that to log on to their website within five years.
Earlier quoted context omitted.
GOS has minimum hardware requirements and most of the available smartphones don't meet them
This is a contradiction. There is nothing "minimal" about a requirement that excludes every device but one. Also some people (me) value independence from Google more than the highest degree of security (which relies on Google hardware).
I don't get your logic. Requirements are a choice. It's very easy to create requirements that exclude every device but one.
Example: "It has to be the Samsung Galaxy S23". Done.
Now you can disagree with those requirements, but that's completely different from saying that the requirements are wrong.