this post was submitted on 06 Oct 2025
342 points (98.9% liked)

DeGoogle Yourself

14516 readers
18 users here now

A community for those that would like to get away from Google.

Here you may post anything related to DeGoogling, why we should do it or good software alternatives!

Rules

  1. Be respectful even in disagreement

  2. No advertising unless it is very relevent and justified. Do not do this excessively.

  3. No low value posts / memes. We or you need to learn, or discuss something.

Related communities

!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml

founded 5 years ago
MODERATORS
 

Fuck Google with a stiff wire brush.

you are viewing a single comment's thread
view the rest of the comments
[–] Arghblarg@lemmy.ca 63 points 2 months ago* (last edited 2 months ago) (5 children)

I read somewhere that GrapheneOS devs have a strategy which they believe will work -- they strip out something or other about app/device attestation (?) from APK files before installing occurs, or the enforcement code itself from their spin of the OS, so sideloading (ie., user-controlled installation) can still work.

I sure hope so... I think everyone in their respective country needs to scream at their local regulators about this.

Of course, this will only help those whose devices GrapheneOS can run on.

[–] Truscape@lemmy.blahaj.zone 52 points 2 months ago (2 children)

The GrapheneOS team is already in communications with an Android OEM to see if they can make a device that meets their specs, hopefully that bears fruit in a year or two.

[–] MrSoup@lemmy.zip 9 points 2 months ago (2 children)
[–] other8026@lemmy.ml 11 points 2 months ago (1 children)

Just check the project's X account. The OEM partnership is mentioned very regularly.

[–] jnod4@lemmy.ca 5 points 2 months ago (1 children)
[–] 211@sopuli.xyz 10 points 2 months ago

Hope it's Fairphone.

[–] Truscape@lemmy.blahaj.zone 2 points 2 months ago

It's a bit of telephone, I originally heard it from this user.

https://lemmy.blahaj.zone/comment/16087016

[–] Scolding7300@lemmy.world 2 points 2 months ago (1 children)

Wdym a device that meets theur specs, as in a replacement for the Pixel? Or straight up a GrapheneOS device, standalone?

[–] Truscape@lemmy.blahaj.zone 7 points 2 months ago* (last edited 2 months ago)

A device that meets GrapheneOS's requirements to be installed on. I don't think it will be exclusive or anything.

[–] other8026@lemmy.ml 24 points 2 months ago (3 children)

Google has already shared how apps' developers will be verified. They're adding another app that will have access to block installing apps or disable them. That won't work on GrapheneOS because 1. the app won't be installed and 2. the app won't have that kind of privileged access.

[–] Truscape@lemmy.blahaj.zone 11 points 2 months ago

ROFL we got redstarOS on mainstream phones before gta6

[–] BCsven@lemmy.ca 7 points 2 months ago (1 children)

I think the issue is new hardware and google starting to close source android, so that Graphene devs don't have the open source to work with. They'll probably get binary blobs

[–] other8026@lemmy.ml 1 points 2 months ago (1 children)

It's my understanding that the changes that were made didn't make things more or less proprietary. Some drivers are still open source, others are still closed source. The device trees mostly have other things in them like configuration files and stuff like that.

[–] BCsven@lemmy.ca 1 points 2 months ago

It sounds OK for now, but it seems Google is on a path of closing things up like Apple.

[–] shaggyb@lemmy.world 3 points 2 months ago (1 children)

Soooo we just block that app, right?

[–] other8026@lemmy.ml 1 points 2 months ago

It just won't work on GrapheneOS. Not sure if disabling it will work on the stock OS. We will have to wait and see on that one.

[–] ExtremeDullard@piefed.social 15 points 2 months ago (2 children)

And how long is it going to work?

Do we really want to play cat and mouse with Google? I don't.

[–] other8026@lemmy.ml 15 points 2 months ago

The way Google will block apps with unverified developers won't work on GrapheneOS. The change won't be part of AOSP. On the stock OS, the functionality will be handled by another Google app that has privileged access. GrapheneOS won't be affected directly.

[–] WhatGodIsMadeOf@feddit.org 11 points 2 months ago (1 children)

Right... I want to see Linux distros.

[–] orbituary@lemmy.dbzer0.com 7 points 2 months ago (3 children)

I hope so as well. This debacle with RCS not working on GrapheneOS has been a real dick-punch. I really don't want to go back to a stock OS.

[–] other8026@lemmy.ml 3 points 2 months ago (1 children)

It's my understanding that RCS was fixed for most users after this update: https://grapheneos.org/releases#2025092700. You may need to grant permissions to Google Play Services first, then clear Google Messages' storage, grant permissions to Google Messages, then try setting it up again.

[–] orbituary@lemmy.dbzer0.com 3 points 2 months ago* (last edited 2 months ago) (1 children)

It was not. I have been on the Discord #Testing channel working with others to troubleshoot. Those steps do not work.

It seemed to be fixed on the 20251003 release, a lot of people got it working for a while, including me. It died within 24 hours.

[–] other8026@lemmy.ml 0 points 2 months ago

I said "most users". There are some who are still experiencing issues, which is being looked into. Other people have had issues that were fixed by clearing the storage for Google Play, Google Play Services, Google Messages, then granting all necessary permissions before launching Google Messages again.

[–] Chulk@lemmy.ml 3 points 2 months ago (1 children)

I thought the RCS thing was also happening on stock Android? Wasn't it more of a carrier thing?

[–] orbituary@lemmy.dbzer0.com 6 points 2 months ago (1 children)

It's been largely fixed for stock with select regions still being affected. RCS is failing on GOS because the correct device ID isn't getting reported and the verification services won't authenticate the OS.

It'll work for about 24 hours, give or take, from a fresh installation, but after that RCS dies and no longer works. Any groups you were in will see you as departed and you will lose any future messages to that group.

It's pretty fucked.

[–] Chulk@lemmy.ml 6 points 2 months ago (1 children)

Thanks, I had no idea of the severity. I wonder if they'll be able to fix it.

I convinced my fiance to switch over to GOS because I've had moderate success with it for about a year now. So of course this happens as soon as she made the switch. Now she's talking about getting an iPhone.

[–] orbituary@lemmy.dbzer0.com 3 points 2 months ago

Ain't that how it always goes? Best I could do with mine was to get her to use Signal. Better than nothing, I guess.

[–] rhythmisaprancer@piefed.social 3 points 2 months ago (1 children)

I have accepted no RCS. I miss some of the features, sure, but until I can get more than one person to use something like signal I'll stick with insecure SMS thru a FOSS provider I guess.

[–] orbituary@lemmy.dbzer0.com 4 points 2 months ago (1 children)

I have like 40 people on Signal and regularly chat with a dozen of them there. Some people see the benefits, others don't. I am lucky.

[–] rhythmisaprancer@piefed.social 3 points 2 months ago (1 children)

That sounds great! So far, after five years, I have won a single person. Even back when Signal worked as a more regular messenger. Happy for you 🙂

[–] orbituary@lemmy.dbzer0.com 2 points 2 months ago (1 children)

Hopefully we can all get more people on it. I adopted Signal almost ten years ago, so that helped. Keep spreading the word and it'll grow.

[–] rhythmisaprancer@piefed.social 1 points 2 months ago (1 children)

Thanks for the encouragement! The one person is a key player in that network so maybe! Hard to fight with the apple folks.

[–] orbituary@lemmy.dbzer0.com 1 points 2 months ago

The kool-aid is sugary.

[–] bold_atlas@lemmy.world 1 points 2 months ago* (last edited 2 months ago) (1 children)

Shouldn't they be keeping bypass strategies a secret right now?

[–] rumba@lemmy.zip 6 points 2 months ago (1 children)

Shouldn’t they be keeping bypass strategies a secret right now?

They're up against a company with more money and developers than they know what to do with. This is, at most, a game of cat and mouse. Secrecy will buy them a sprint or so.

If Google wants to go nuclear, they can do some rolling encryption bullshit or put a million calls all over the OS to check app validity and stop open source altogether.

[–] FEIN@lemmy.world 2 points 2 months ago

and bloat default android devices even more! 🎉