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.
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.
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.