That’s what I was thinking, but reading the article it’s apparently not related to sending messages. It’s simpler.
Google blocks RCS on rooted devices. And at the moment they don’t tell the user that at all, it just fails to work. So actively the worst way to handle it.
I mean, I’m on /e/os and RCS just sits there in “Setting up” eventually just uninstalled Google nessages. RCS is obviously key to their global spying program or something. E2E my ass.
Like everything else now, they no longer check any of that directly. It’s all handled via Play Integrity API. If the device fails the Play Integrity check it will fail.
When you find a suitable replacement for GBoard, let me know. Actually don’t, I’ve tried them all and they all fall well short of Google’s prediction algo.
If you have an iPhone and send a voice text to another iPhone and mention “Dave and Busters”, it will always fail silently. You can text the words “Dave and Busters” and it will go through, but if you say it in a voice text, it will never reach its destination.
That sounded too weird to be true yet it’s true. The problem seems to be that it generates some HTML to wrap the attached audio file, does voice to text, and doesn’t escape an ampersand, which trips a firewall.
It’s bad UX that it fails silently there too; at least the recipient should get some sort of explanation.
Sending a message should never fail silently, so that’s an improvement, but fuck whoever decided this.
That’s what I was thinking, but reading the article it’s apparently not related to sending messages. It’s simpler.
Google blocks RCS on rooted devices. And at the moment they don’t tell the user that at all, it just fails to work. So actively the worst way to handle it.
Now to see if they mean actually rooted devices, or anything with a non-stock OS.
I mean, I’m on /e/os and RCS just sits there in “Setting up” eventually just uninstalled Google nessages. RCS is obviously key to their global spying program or something. E2E my ass.
The hacky workaround is to send them via Beeper, which connects to Google Messages’ web client.
Like everything else now, they no longer check any of that directly. It’s all handled via Play Integrity API. If the device fails the Play Integrity check it will fail.
GrapheneOS stopped working years ago. Silently.
RCS works on GrapheneOS.
I’m glad it works for you but I don’t think it reliably works for a lot of Graphene users:
https://discuss.privacyguides.net/t/how-do-i-activate-rcs-on-grapheneos/23546/5
https://discuss.grapheneos.org/d/1353-using-rcs-with-google-messages-on-grapheneos/254
Graphene OS works outside of Google’s phone (Pixels)? If no, I am not considering it ever
Don’t use Google apps
I don’t trust any of them honestly
When you find a suitable replacement for GBoard, let me know. Actually don’t, I’ve tried them all and they all fall well short of Google’s prediction algo.
If you have an iPhone and send a voice text to another iPhone and mention “Dave and Busters”, it will always fail silently. You can text the words “Dave and Busters” and it will go through, but if you say it in a voice text, it will never reach its destination.
That sounded too weird to be true yet it’s true. The problem seems to be that it generates some HTML to wrap the attached audio file, does voice to text, and doesn’t escape an ampersand, which trips a firewall.
It’s bad UX that it fails silently there too; at least the recipient should get some sort of explanation.