jumpdeer I opted into the beta to install it
Why though, if it doesn't work why would you think that would fix it? The rest of your instructions sound like you're doing things in a different order.
TheExtremelyDirtyDan was able to use Aurora
Then it will work with Google Play version too, don't use Aurora it's an insecure mess.
Vuraze It seems that people who are on the T-Mobile network need to use an older version of Google Messages for RCS to initially connect Etouffee. Using a version from 2024 almost certainly is the incorrect answer and will lead to it simply not working.
Initially connecting isn't going to solve your problem if it fails to provision with Etouffee. That happens after the green "connected" thing appears. What I would do is have a look at the provisioning process in logcat to see if there's anything specific using locat with these filters:
adb logcat -v time \*:D | rg -i 'Bugle|RCS|Etouffee'
In any case I doubt carrier actually makes much of a difference especially as this application is not dependent on any carrier resources. (ie carrier apps preinstalled on phone etc).
I would give it a few days, with RCS actually properly disabled, including disabling it here: https://messages.google.com/disable-chat so that you can be sure you're free of any kind of rate limiting on both the verification and Etouffee provisioning.
Then simply clear the Google Messages data and set those permissions.
SillySaurus
Google Messages: Contacts, Network, Phone, SMS
- Make Google Messasges the default SMS application before running it.
Google Play services: Network, Phone
Carrier Services: not required
Instructions requiring "old versions" of the app are likely a red herring and not required. It also isn't sustainable for future users with newer phones etc or if Google changes something entirely so that doesn't work at all in the future (something which is inevitable). Perhaps Universal Profile 3.0+.