Google Messages RCS Breaks for Some Galaxy Users After Samsung Smart Switch Transfer

Samsung Galaxy users are experiencing RCS failures in Google Messages after transferring data to a new device with Samsung Smart Switch. Some see error code 3100 when trying to enable RCS or send messages on their new phones.

Google says it is aware of the problem and believes corrupted cache files from Smart Switch may be to blame. In an August 21 update, Google said it is working with carrier partners to address the issue.

The problem appears after using Smart Switch to transfer data to a new Galaxy device.

Google Messages RCS Failures After Samsung Smart Switch Transfers

These reports come after Samsung discontinued its Messages app in the US, which led both new and existing users to switch to Google Messages. Since Google Messages is the only app on Galaxy phones that supports RCS, it has become the default choice. Some users, however, are having trouble getting RCS to work after setting up their new devices.

Android Authority notes that several Reddit users report RCS stops working after moving to a new Galaxy phone and transferring data with Smart Switch. Those affected see error code 3100 when trying to enable or send RCS messages.

Google believes the issue may be linked to corrupted cache files transferred during the Smart Switch process.

Some users also report RCS problems after switching carriers instead of devices. Google says these cases may be due to the number-porting process not being fully completed.

Google Messages RCS Workaround and Fix Status

Google suggests several steps to try to restore RCS, but these do not work for everyone:

1. Update to the latest version of Google Messages.
2. Turn off RCS in the app settings.
3. Clear the Carrier Services app data.
4. Restart the phone.
5. Enable RCS again.

Android Central notes this workaround does not appear to work for all affected users. Some say they were only able to restore RCS after factory resetting their Galaxy phone, and even then there is no guarantee it solves the problem, making a factory reset a drastic step to attempt.

Google says it is aware of these reports and is working with carrier partners on a solution. There is currently no guaranteed fix for everyone. Google has not given a timeline for a broader fix, so affected users may need to try the suggested workaround and wait for a carrier-side solution instead of relying on a factory reset.

Thank you for being a Ghacks reader. The post appeared first on gHacks.