RCS "Connected" but stuck on SMS/MMS. RCS State: 0.

[HippieMitch]

Issue type

Feature not working as intended

Device

I am on a clean install of crDroid 12.9 on a OnePlus 13R in NA. I had the RCS "Connected" status on first boot, but it doesn't seem to be working, stuck on SMS/MMS. I've tried retrying while passing all three integrity checks using a keybox, but am getting the same result.

crDroid version

crDroid 12

Exact version / Build date

12.9/2026-05-03

Bug description

RCS isn't functioning in Google Messages.

Steps to reproduce

Step 1.) Perform a clean crDroid install.
Step 2.) Install Google Messages after logging into Google.
Step 3.) See green "Verified" status in RCS settings.
Step 4.) Send a message to someone with RCS and see that it's stuck as SMS/MMS.

Relevant log (logcat/build log)

Google Messages Debug info: 

RCS Connection State: CONNECTED
RCS State: 0

Screenshots or videos

Solution

No response

Additional context

No response

Acknowledgements

• I've checked device is officially supported and that no support is provided for unofficial devices (for device specific reports and not source related).
• I'm running latest version available on crdroid.net for this device and that the device is still maintainer supported (not flagged unsupported on download page)
• I have searched the existing issues and this is a new and no duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this issue properly and understand that not doing so will automatically result in closing of ticket.

[306bobby-android]

You need a PIF, (from canary). For me, the built in one hasn't been working. I use PIFork instead, but try the built in one first with canary. If the built in one doesn't work for you, report back so I can confirm this as a bug

[HippieMitch]

I've tried a few of the built in PIF's, including Canary, and I can't pass Basic Integrity without a keybox. The keybox has me passing all three by itself. I'm trying to use this phone without root if possible 🙂. I'm sure PIFork would likely work.

[306bobby-android]

I've tried a few of the built in PIF's, including Canary, and I can't pass Basic Integrity without a keybox. The keybox has me passing all three by itself. I'm trying to use this phone without root if possible 🙂. I'm sure PIFork would likely work.

Thanks for the info. And integrity isn't technically required for RCS as long as the PIF is there and working (correctly ;))

[HippieMitch]

Thank you. That's good to know. Please let me know if you need anything else from me. I wasn't sure how to capture a relevant log for this outside of Messages debug info.

[HippieMitch]

UPDATE: I was able to get it with a different PIF, just not any of the ones from the built-in downloader. This could be closed as it isn't technically a bug. All we would need to do is ship a different PIF to get ootb RCS. Thanks again.

[306bobby-android]

UPDATE: I was able to get it with a different PIF, just not any of the ones from the built-in downloader. This could be closed as it isn't technically a bug. All we would need to do is ship a different PIF to get ootb RCS. Thanks again.

So you took a different PIF .json and imported it? Do I understand correctly?

[HippieMitch]

UPDATE: I was able to get it with a different PIF, just not any of the ones from the built-in downloader. This could be closed as it isn't technically a bug. All we would need to do is ship a different PIF to get ootb RCS. Thanks again.

So you took a different PIF .json and imported it? Do I understand correctly?

Yes, that is correct. I still can't pass Basic without a keybox. After importing the *.json file RCS started working again. The weird thing is the keybox went from passing 3/3 to 1/3 after importing the PIF *. json file. It seems that RCS only needed the *. json file to work even without a keybox, like you suggested previously.