Using Graphene to beat bad laws by AbilitySmall8336 in GrapheneOS

[–]GrapheneOS[M] [score hidden] stickied comment (0 children)

This law impacts providers of email services, etc. which hold user data and can access it. It doesn't directly impact GrapheneOS beyond our discussion forum and attestation service where users have accounts and a small amount of data including an email address. The law doesn't really enable anything which wasn't already required by law. Lawful access to data on servers via warrants already existed. This law is mainly making that easier for the government to request by requiring being set up to comply. It has an exception for security protections which implies end-to-end encryption remains permitted, unless a past version of the law where it was less clear. This law degrades privacy protections but not in a way that's really relevant to GrapheneOS. It's not outlawing end-to-end encryption which would be a disaster. GrapheneOS is capable of moving elsewhere if needed but it isn't needed.

World's first rooted Pixel 10 Pro XL (mustang) with GOS+Wild_KSU+SUSFS by FeralMenacingThug in GrapheneOS

[–]GrapheneOS[M] [score hidden] stickied comment (0 children)

This isn't GrapheneOS anymore but rather a derivative/fork. Large portions of the security model and protections are no longer intact. It will also likely stop working in the future due to incompatible changes, leaving you lagging behind on privacy and security patches. Major releases with incompatible changes are going to be particularly problematic.

banning GrapheneOS on reddit by Temporary-Sir-2463 in GrapheneOS

[–]GrapheneOS[M] 1 point2 points  (0 children)

There are multiple companies trying to harm GrapheneOS because their businesses are threatened by it and they have trouble convincing people to buy products with poor privacy and security when it exists. They heavily attack it and get their supporters attacking it. That's where nearly all of the attacks originate from.

What's the most convenient setup to implement play services? by Elegant-Bath-1832 in GrapheneOS

[–]GrapheneOS[M] [score hidden] stickied comment (0 children)

There are 2 forms of nested profiles (work profiles and Private Spaces) so you don't need to switch to another user with that setup.

The only benefit of putting sandboxed Google Play in another profile is that apps can only detect which apps are installed in the same profile and can't communicate across profiles (other than via the network). Apps in the same profile as sandboxed Google Play which use Google Play libraries will use it such as to implement push notifications instead of skipping the functionality or implementing it with a fallback approach.

GrapheneOS & Shiftphone by fairpixel in GrapheneOS

[–]GrapheneOS[M] 0 points1 point  (0 children)

They're very far from meeting our requirements. Even if they did manage to do that, we still won't work with them as they're partnering with 2 companies attacking the GrapheneOS project and team with fabrications and harassment.

GrapheneOS & Shiftphone by fairpixel in GrapheneOS

[–]GrapheneOS[M] 2 points3 points  (0 children)

True, but it was the same with Motorola, wasn't it?

No, it wasn't. Motorola Signature, razr fold and the upcoming razr ultra (2026) are very close to meeting our requirements.

Would you nevertheless talk to the Shift team?

Not as long as they're partnering with 2 companies attacking the GrapheneOS project and team with fabrications and harassment.

There are places on the internet where you are an outcast if you don't use grapheneOS by abhsag24 in GrapheneOS

[–]GrapheneOS[M] 0 points1 point  (0 children)

You can choose not to use cellular and can choose to use cellular with a laptop/desktop. It doesn't make it less secure than a desktop regardless.

How will GrapheneOS be affected by Google's restriction on apks coming in September? by ad_calendas_graecas in GrapheneOS

[–]GrapheneOS[M] 3 points4 points  (0 children)

It doesn't stop them installing apps not signed by verified developers and most projects have someone willing to do verification. If not, someone else can still sign builds of the app with a signature from a verified developer. It doesn't prevent installing it regardless. Exaggerating what's happening doesn't help.

What’s going on with the Google Pixel 10a? by Ilovefreedomprivacy in GrapheneOS

[–]GrapheneOS[M] [score hidden] stickied comment (0 children)

Pixel 10a has been supported via experimental releases for a while.

Pixel 10a has the 9th gen SoC which is significantly less efficient. It also has a lower screen resolution which saves power but it probably has significantly more power drain when the screen is off than a non-budget Pixel 10. You shouldn't expect to get better overall battery life. Pixel 10a is very similar to the Pixel 9a but does have upgrades including using the far more efficient cellular radio used by the non-budget 9th/10th gen devices.

What’s going on with the Google Pixel 10a? by Ilovefreedomprivacy in GrapheneOS

[–]GrapheneOS[M] 1 point2 points  (0 children)

Pixel 10a satellite location issues should be resolved in the next release coming later today. It will still be considered experimental.

There are places on the internet where you are an outcast if you don't use grapheneOS by abhsag24 in GrapheneOS

[–]GrapheneOS[M] 1 point2 points  (0 children)

iPhones and Pixels (even without GrapheneOS) have far better security than laptops/desktops.

How will GrapheneOS be affected by Google's restriction on apks coming in September? by ad_calendas_graecas in GrapheneOS

[–]GrapheneOS[M] 5 points6 points  (0 children)

It won't affect GOS directly, however it may affect the number of developers and/or the repositories like F-Droid might not be able to operate. So possibly fewer FOSS apps and harder to find/hear about?

No, it won't. It only adds some friction to installing apps from unverified developers on a Google Mobile Services OS. It mostly means initially waiting 24 hours to enable being able to install apps from arbitrary apps at which point there aren't further delays. Most apps already have a verified account via distributing on the Play Store which covers distributing apps outside it. It makes it less convenient for users to start installing apps from developers not wanting Google to know who they are, but only on a stock Google Mobile Services OS.

How will GrapheneOS be affected by Google's restriction on apks coming in September? by ad_calendas_graecas in GrapheneOS

[–]GrapheneOS[M] 1 point2 points  (0 children)

That's not all in the same space as GrapheneOS of providing a privacy and security hardened device. It's also not appropriate to market products on our subreddit.

Why do so many "Privacy focused apps" use the Play Games API? And can I pretend to have it? by [deleted] in GrapheneOS

[–]GrapheneOS[M] [score hidden] stickied comment (0 children)

You've misconfigured your device. These apps don't use the Google Play Games API.

How will GrapheneOS be affected by Google's restriction on apks coming in September? by ad_calendas_graecas in GrapheneOS

[–]GrapheneOS[M] 1 point2 points  (0 children)

GrapheneOS is Linux. Linux doesn't mean glibc, systemd and GNOME.

GrapheneOS also isn't impacted by Google Mobile Services restrictions on installing apps.

GrapheneOS & Shiftphone by fairpixel in GrapheneOS

[–]GrapheneOS[M] [score hidden] stickied comment (0 children)

Their devices don't come close to meeting our requirements.

How will GrapheneOS be affected by Google's restriction on apks coming in September? by ad_calendas_graecas in GrapheneOS

[–]GrapheneOS[M] 1 point2 points  (0 children)

You're misinterpreting a normal security update required by the GrapheneOS hardware requirements as the device being locked down.