vixaex
After it working for a couple weeks consistently, the second APK from @Turtacular 's method just stopped working for me today (T-Mobile). And I can't make it work anymore.
The APKs they referenced were com.google.android.apps.messaging_messages.android_20241120_00_RC07.phone_dynamic-262371063_minAPI26(arm64-v8a,armeabi-v7a,x86,x86_64)(nodpi)_apkmirror.com.apk as the first, and then upgrade and stay on com.google.android.apps.messaging_messages.android_20250311_04_RC01.phone_dynamic-273168063_4arch_7dpi_24lang_0fa6bd6ebbb40b6d0d8682c5d4f6453d_apkmirror.com.apkm.
I did manage to get RCS working again, but I suspect I'm going to be stuck resetting every 24-36 hours now.
Unlike before, when I didn't have to clear any data or do any reboots with Turtacular's method, this time I had to:
- Uninstall the old version
- Reboot
- Install the first version (do not open it yet)
- Wipe storage for it
- Try to set it as the default SMS and fail initially (because it's the ApkMirror version, this makes the Allow Restricted Permissions 3-dot option appear on the main settings page for the app)
- Enable the Allow Restricted Permissions
- Set it as the default SMS app
- Enable the Allow Alarms a nd Timers option (separate from the other Permissions settings)
- Open the app
- Verify the RCS status is Connected (RCs says not supported unless you do the above sequence for me now, unlike before)
- Install the second APK (bundle)
- Open the app and check the RCS status (still connected)
- Enable the debug menu and ch3ck Etouffee status
- Stuck on Etouffe: false, and RCS doesnt work. Rebboting and waiting don't work for me anymore.
- Install the latest Google Messages available (Debug menu on the last few versions no longer includes the option that list Etouffe status, and it's not present in any other info either)
- Wait a few minutes and open a conversation with someone that has known working RCS. Your Messages box should switch to "RCS" instead of "Text Message" after a second or two.
So for me maybe I didn't wait quite long enough on Turtacular's second version, but I do now have to reboot after uninstalling the version I was running when it stopped working, and I have to actually wipe my app's storage after installing it now too.
Given the sudden burst of people experiencing problems, I'm guessing all carriers have finally switched to their own implementations. From the GitHub Issue description, it seems the only limitation from GOS is that it doesn't yet support IMS Single Registration, so I'm guessing the different carriers have different levels of backward compatibility support for the prior IMS multi-Registration, and the limitations are in flux.