Re:Google Messages end-to-end encryption is now out of beta
by izacus on Wednesday June 16, 2021 @04:46AM
(#27526324)
Yeah, RCS is also broken on my Samsung phone and keeps deregistering itself. The dual-SIM support is also non-existent (which shows how every single of our comms services are built by Americans where dualSIM phones have been blocked by carriers for years).
In general it's a completely trash fire situation where we're pretty much forced to use proprietary services without APIs to communicate.
Re:Google Messages end-to-end encryption is now out of beta
by dcomp on Wednesday June 16, 2021 @04:33AM
(#27526232)
Probably some weird carrier RCS registration issue. My wife uses a s10e on EE (UK) and I use a Pixel 4 XL on Vodafone (UK) and I get RCS messages between us. Only use it for the delivery and read notifications but it works.
I do remember having loads of problems with RCS registration failing on the Samsung side, or just disabling itself.
Edit: Specifically I think it won't register whilst on WiFi and requires the correct mobile APN. I used to switch APNs to get a public IP address/ unfiltered internet
Re:Google Messages end-to-end encryption is now out of beta
by hocuspocus on Wednesday June 16, 2021 @04:51AM
(#27526352)
It's not an issue on the device, I asked my carrier, Google won't let them interconnect RCS to Jibe.
To my understanding, carriers were encouraged to either implement Universal Profile on their own or use a Google-operated "Jibe as a service" infrastructure. The former are now completely isolated from Google's network.
To me it looks like British carriers are simply using Jibe.
I cannot send an RCS message from my Pixel to my wife's carrier-provisioned RCS app on her Samsung phone.
Google doesn't seem to be interested in a federated and interconnected RCS infrastructure anymore.