GoKawiilTL;DR Android users have been reporting some frustrating RCS problems with Google Messages.
Users suggested a number of fixes, but they don’t appear to work for everyone.
Google now confirms that it’s working with carriers to developer a proper solution.
RCS represents the next generation of text messaging, finally delivering many of the features users were craving for years, like threads and reactions. But all that complexity also feels like it’s made things a bit fragile, and sometimes it seems that we can’t go more that a few weeks without hearing about a new RCS glitch. Most recently, that’s one that’s involved error code 3100, and appears to largely impact users setting up new devices or switching carriers. Today, Google gives us an update on progress towards sorting things out.
As you may remember, we already looked at a number of potential solutions and work-arounds, and while some users did report success, it was clear that the same approach wasn’t working for everyone. Especially with something like RCS that can rely so much on external systems, that’s a situation that can feel incredibly frustrating. But that’s also why we’re relieved to now hear that Google’s on the case.
Google tells Android Authority that it’s working to deliver a proper solution, and has turned to the carriers for assistance: We’re aware of this issue and are working with our carrier partners to get it fixed as soon as possible. While that kind of open-ended timeline towards a fix arriving maybe isn’t what you were hoping to hear, we’re still really excited to learn that Google’s working to get to the bottom of what’s really going wrong here, so users don’t feel compelled to try a bunch of different multi-step solutions that may not even work.
For now, you may just want to wait for Google and the carriers to sort things out. We’ll update you if and when we finally get confirmation of the fix actually being deployed.
Follow