TL;DR
- Users who have rooted their phone, have their bootloader unlocked or are using some custom ROMs report that their RCS messages are not being sent, even though RCS shows them as connected.
- The Google Messages app does not show any error messages when blocking RCS messages of these users and does not send the messages out as SMS or MMS either.
- Google famously campaigned for Apple to include RCS messaging in iMessage but is now blocking it for certain Android users.
It’s apparently the Google Messages app, not Android itself. Good to know.
it’s the only OEM-independent, RCS-compatible app for now, so it’s not like you can work around it by installing another client.
It suggests that apps without this problem can be developed, which means more paths to a workaround than if we had to modify the operating system.
Sure but specifically with RCS, Google has to allow devs to use it in their apps. And they won’t.
How is Google going to stop them?
Forbidding an app from the Play Store is unlikely to stop these users, who already use rooted devices and custom ROMs. They’ll just get an app from their ROM provider, F-Droid, or elsewhere.
Does RCS depend on Google services integrated with the mobile network operator? If Google tried to use that position to forbid alternative apps, it would seem likely to run afoul of the Digital Markets Act.
I don’t know a lot about RCS specifically, though. Is there another issue I haven’t considered?
well, so far none of the third party SMS apps have implemented RCS support, and when asked, every developer replies that they need Google to open their standard for other clients to use, so I guess they’ve been doing a pretty good job at stopping everyone else.
Have they given a reason why the specifically not able to do it, or do they just not want to do it because it’s “unlicensed” or “out of spec” if it’s just the second option then it’s a problem of having unwilling people and not a real entry barrier.
If there’s an actual barrier to developing something like that it’s important to understand what it is.
yes, every time the reason given was Google not opening their API to the public.
Oh good i dont use that