In recent weeks, Android users with rooted or bootloader-unlocked phones have noticed that RCS for Google Messages doesn’t work.
Specifically, users cannot send or receive RCS messages. According to one report, the phone number may pass verification, but the Rich Communication Services functionality will not actually work. Another example shows the message disappearing after tapping the send button.
Compared to when Google Wallet fails, there is no error message for the user to indicate that something has gone wrong. Therefore, users may not realize that they are missing chats.
Google today confirmed that the use of RCS is prohibited on some of these phones, and that it will prevent spam and He said it was necessary to prevent abuse.
Affected users have noticed that SMS/MMS continues to work on rooted devices or phones where the bootloader required for custom ROM installation is unlocked. Google noted that SMS is still available as a fallback if RCS is unavailable.
This RCS issue was particularly prevalent in late November and has occurred intermittently since then, including reports of the issue starting today.
That said, those savvy enough to root have found a simple enough fix that involves bypassing a safety feature (Play Integrity API) that appears to be responsible for preventing RCS access.
Blocking key communication features on an Android device is a step too far for many people, as rooting stops Google Pay, banking, and other similar apps from working. At the same time, while preventing spam is a legitimate concern, we wish there were more obvious ways to protect RCS users without compromising the customizability of Android. Google also needs to improve its communication to users when it is unavailable.
Google Messages details:
FTC: We use automated affiliate links that generate income. more.
