Google is silently blocking RCS messages on rooted Android phones and custom ROMs

ForgottenFlux@lemmy.world to Technology@lemmy.world – 718 points –
Google is silently blocking RCS on rooted Android phones and custom ROMs (Update)
androidauthority.com

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

You are viewing a single comment

I think after XMPP, Google Talk, Wave, Hangouts, Allo, etc... people should know better than to adopt a messaging service from Google.

Yes, I know RCS is theoretically an open standard, but if Google can keep me from using it, it effectively belongs to Google.

Theoretically? RCS is not an open standard. It requires a license from GSMA.

XMPP is not from Google. They just successfully pulled an EEE.

You'd think people would know better than to adopt anything from google.

It's not like everyone has a choice in the say. Given that many schools and workplaces rely on Google for something

There is a difference between adopting, and being forced to use, you know.

It's worse than that. Carriers have a say as well. For example, Samsung messages works with RCS in some markets but US providers currently lock it out. They only allow Google messages for RCS. Absolutely infuriating.

RCS is monopolised by Google. Theoretically open ("maybe, in the future, once it's secure…"), but practically not.

XMPP was ok for its time

Not only for its time! While flawed, I still see it as probably the best middle ground for messaging. It has evolved since then, its servers are easy to host and it has a variety of clients that support e2e.

Yeah, but I think that most of the clients are a bit dated in UX otherwise. There isn't really anything that I could suggest a friend to use

Yeah I was using ejabberd around 2006 to connect some high touch clients, and it certainly got the job done.

Yeah hard to call it an open standard when there's a single implementation that's closed source and goes off of spec.

It seems crazy that Google is in last place for providing messaging services. It’s like:

Various 3rd party apps > Apple > Microsoft > Google