Google and carriers deployed changes to RCS which have been breaking it for many users on the stock OS including with certain carriers and in whole countries. The changes appear to have specifically impacted GrapheneOS users too. It's not related to our September 8th update. We're working on it.
You can find many recent threads about people having issues with RCS in Google Messages while using a stock OS with Google Mobile Services. There are articles about how some carriers and countries no longer have it. It still works for most people but the changes definitely regressed compatibility.
GrapheneOS users were impacted by these recent changes much more than other users. We don't know why yet but we're working on determining that and restoring compatibility with Google Messages for people who use it. We'll try to get compatibility with the new way it functions implemented very soon.
15 Comments
unexposedhazard@discuss.tchncs.de · 26 pts · 339d
RCS is worthless to me until there is a functional FOSS implementation.
Hominine@lemmy.world · 6 pts · 339d
Samesies, I just went back to Graphene on a new device and am back to the SMS/Signal/Discord combo for the time being. Oh, what I would donate for a self-hosted discord analog.
unexposedhazard@discuss.tchncs.de · 6 pts · 339d
Matrix for sure still has issue, but its getting better constantly imo. I havent used discord for 7 years so i dont know what i might be missing, but i dont feel like i am missing anything. I got instant messaging, voice/video channels, screen sharing, etc. I dont care about stupid bots and stickers and such so maybe that would be an issue for people.
SidewaysHighways@lemmy.world · 3 pts · 339d
xmpp is close ish. snikket is dockerized
Hominine@lemmy.world · 6 pts · 339d
Prose and Snikket in particular both look to have promise and I really like xmpp also, but the lack of group calls/screen-sharing remains the sticking point. I may still throw up a snikket server tho, hosting mollysocket is just as intensive and I may as well own the entire chain.
Ulrich@feddit.org · 3 pts · 339d
Even if there is one, everyone else would use Google's and they'd have all your metadata anyway.
jcarax@beehaw.org · 1 pts · 338d
Nothing is perfect here, but I think federation would be best. The concern is the same one that caused Signal to drop SMS support (to my knowledge), that people might improperly trust the services that their anonymous service are federated to. Especially when you're federated to a chat service that is run by a company that also handles the synchronization of it's users contacts with their names, phone numbers, and email addresses.
But still, in a sane world, federation of services should be the goal.
Ulrich@feddit.org · 1 pts · 338d
I mean yeah, that would be best. Just not in any meaningful way.
Tenderizer78@lemmy.ml · 1 pts · 339d
Does this mean I can't receive messages until it's fixed?
fodor@lemmy.zip · 2 pts · 338d
Tenderizer78@lemmy.ml · 2 pts · 338d
Nope. Tested it.
KindnessInfinity@lemmy.ml · 2 pts · 336d
regular mms/sms should still work
obsidianfoxxy7870@lemmy.blahaj.zone · 1 pts · 339d
Mabey if it's broken enough for stock Android it will get fixed sooner.
0xtero@beehaw.org · 3 pts · 339d
Except no one (except FOSS projects) really uses stock Android anymore
obsidianfoxxy7870@lemmy.blahaj.zone · 2 pts · 339d
Stock was the wrong word Google Android. If it's broken on what the majority of people use.
KindnessInfinity@lemmy.ml · 2 pts · 336d
Yeah hopefully