Urgent.News

What's breaking now, across thousands of outlets.

Editions

Tech

Google Messages RCS breaks with ‘3100’ error for some, especially Galaxy switchers

An issue with Google Messages appears to be breaking RCS for some users, with much of the problem tracing back to Samsung Galaxy devices.

Google Messages RCS breaks with ‘3100’ error for some, especially Galaxy switchers

Google Messages is reportedly experiencing issues with its RCS feature, particularly affecting Samsung Galaxy device users. The problem has been traced back to these devices, especially for those who have recently switched to a new device or network. Users on Google Messages have been reporting error code "3100," which translates to "Trouble connecting. Awaiting retry," indicating a failure to properly connect to RCS servers.

The issue seems to be more prevalent for users upgrading to new devices, such as the Galaxy Z Fold 8, or those moving to a new carrier. One possible cause could be errors during the porting of phone numbers, or corrupted cache files transferred by Samsung's Smart Switch. However, the exact cause remains unclear at this point.

Google has provided troubleshooting steps for users experiencing this issue. These include turning RCS off, clearing data for "Carrier Services," rebooting the device, and then turning RCS back on. Another user suggested a six-step process that includes temporarily turning off 2-step verification and clearing Play Services data. However, success with these methods appears to be inconsistent.

Google has confirmed that this issue is a carrier problem and is working alongside partners to resolve it as quickly as possible. They have issued an update to 9to5Google, stating, "We’re aware of this issue and are working with our carrier partners to get it fixed as soon as possible." Readers who are experiencing this problem are encouraged to share their device details and the issue they are facing.

Written by urgent.news from 9to5Google's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at 9to5google.com →

More in Tech

npm v12 silently skips install scripts — here's how to check if that breaks you

npm v12 shipped on 2026-07-08 with a real security-motivated change: preinstall , install , and postinstall scripts are now disabled by default.

  • npm v12 disables preinstall, install, and postinstall scripts by default
  • npm ci silently skips blocked install scripts with 0 status code
  • Online tool identifies dependencies affected by npm v12 changes

More from Thursday 20 August →