I originally posted this on its own in this forum, but not a single person responded to it since i posted it about a month ago.
Hello, I use US Mobile as my phone service and one of the perks to using them is they have access to all three major networks in the US. I had Google Messenger loaded and RCS was working great on my P9P while I was on the T-Mobile network of US Mobile. Then US Mobile launched a great deal on there AT&T network and I transferred to the AT&T network. After transferring about 2 months ago, I've never gotten RCS to activate again. I've tried just about everything short of Factory resetting my phone with a fresh version of GOS.
I think the issue is in the throw-away google account I had to create to get RCS to work (which worked perfectly on the T-mobile network), it says my P9P is not auto-verified (and when i try to auto-verify it says this might take a while). I remember back when i was on the T-mobile network, my phone was auto-verified. And because my phone won't auto-verify now, the RCS process can't get past "setting up..."
I even created a new throw-away google account and have the same exact issue with auto-verifying my phone. It just says Auto-verification in progress, this might be a while. (or something like that).
I've turned on and given google messenger and google carrier services more permissions then i remember giving them when I got RCS to work on T-mobile (although according to this forum T-mobile don't even use Carrier services, so i don't think i had to have that installed at all). I've switched to a beta version of google messenger because there was a bug in the public release that told me that RCS wasn't compatible with my phone or with my SIM card. I've gone through the massive RCS thread on this forum and tried most of it. It's possible i missed a step somewhere.
Has anyone found a solution to this auto-verification issue?
It is certainly not the end of the world that RCS don't work, but it was really nice when it did, since normal people don't use Signal for everything and you can't talk them in to it.
Yesterday I tried DeletedUser177 original post to the T on my pixel 9 Pro, waited 2 hours and nothing changed. So I decided to prove my point that something with google's auto-verify is causing the issue and therefore it won't connect to RCS. Using my old Pixel 8 with a brand new, up to date version of GOS, I logged in to the same throw-away google account and downloaded beta google messenger and beta carrier services. Now, I did not follow all of DeletedUser177's steps on my pixel 8, but I thought since it was a fresh OS, it might work. It didn't work. And the google account gave me that same message about auto-verification could take a while to complete. So I deleted GOS off the pixel 8 and loaded up Stock Android 15 and plugged in my SIM card. After it finished with all of its updates, I checked the RCS status and it instantly connected to RCS and I was able to RCS message my dads iPhone with no issues. I checked that google account and there was a second instance of my pixel 8 on there and it was auto-verified. I though great, so now that my phone number is fully registered on RCS servers, it should be a simple matter of plugging my physical SIM back in to my pixel 9 Pro and i'll be good to go.... Nope, as soon as i plugged my SIM card back in and checked the RCS status, it was the exactly the same as before.
At this point I've ruled out any issues with my phone carrier, US Mobile isn't the issue. I can try DeletedUser177 steps again now that i know my phone number is active on RCS servers. But i don't understand why all of this worked on my pixel 9 pro before when i was on the T-mobile network and GrapheneOS and now it don't. And I'm pretty sure the google auto-verify is the issue.
Any suggestions or advice would be greatly appreciated.