If RCS just broke on you, do this

ffuentek

original message (in Spanish):

he probado todo y mi telefono sigue con mensajes RCS que no funcionan, me arroja el mensaje de "No se detecta ninguna tarjeta SIM compatible con este dispositivo", no se que ocurre, he desinstalado la app Mensajes de Google, la volvi a instalar, borre los datos y cache, borre datos y cache de servicios y comunicaciones del operador...tambien los de PlayStore y de los servicios Google Play....y todo sigue igual, me encuentro perdido, y soy un usuario "avanzado"

Gracias a todos de antemano!

translation:

I've tried everything, and my phone still has RCS messages that don't work. It's giving me the message "No SIM card compatible with this device is detected." I don't know what's going on. I've uninstalled the Google Messages app, reinstalled it, cleared the data and cache, cleared the data and cache of the carrier's services and communications... also the Play Store and Google Play services... and everything remains the same. I'm lost, and I'm an "advanced" user.

Thanks to everyone in advance!

other8026

ffuentek ffuentek Sorry for this, but can you please post in English? I'm going to update your posts with translations.

BlingoDangoDingo

amuq Hey, I've been encountering this too. Did you ever find a solution or workaround?

ffuentek

original message (in Spanish):

hasta ahora nada.... sigo igual, imagino que alguna actualizacion lo resolvera, al igual que creo que una de las ultimas actualizaciones causo el error

translation:

So far nothing.... I'm still the same, I imagine that some update will solve it, just as I think that one of the last updates caused the error.

rebuild3593

+1, this solution fixed my issue.

To address some of the other questions/comments in this thread, a common problem I've seen is that your number won't verify if you have DCL via Memory disabled for Play Services.

To summarize:

Enable Phone Number Verification (Settings -> Apps -> Sandboxed Google Play -> Google Settings -> All Services (Top) -> Phone Number Verification)
- Note: Not sure if this one is always required. Someone can try without and report back if they want to.
Disable DCL via Memory for Play Services
Set the AOSP/GOS messaging app as your default SMS app
Clear Google Messages Storage (under storage and cache)
Give Google Messages it's required permissions (Phone, SMS, Contacts, Network, Notifications)
Open Google Messages, set as default SMS app
(Optional) Go back into Google Message's app settings and remove all the extra permissions it just gave itself.

Shrunk836

rebuild3593 this doesn't work for me, tells me the sin wouldn't work. After killing messages and open it again it tells me my device isn't supported.

cb474

rebuild3593 To address some of the other questions/comments in this thread, a common problem I've seen is that your number won't verify if you have DCL via Memory disabled for Play Services.

To summarize:
Enable Phone Number Verification (Settings -> Apps -> Sandboxed Google Play -> Google Settings -> All Services (Top) -> Phone Number Verification)
Note: Not sure if this one is always required. Someone can try without and report back if they want to.
Disable DCL via Memory for Play Services
Set the AOSP/GOS messaging app as your default SMS app
Clear Google Messages Storage (under storage and cache)
Give Google Messages it's required permissions (Phone, SMS, Contacts, Network, Notifications)
Open Google Messages, set as default SMS app
(Optional) Go back into Google Message's app settings and remove all the extra permissions it just gave itself.

I don't understand, you say at first that "your number won't verify if you have DCL via Memory disabled for Play Services," but then in step 2 of your suggestion you say that people should in fact disable DCL via Memory for Play Services. Did you mean enable? Also the only options I see are "allowed" or "restricted."

quaff

DeletedUser177 This worked for me. holy. What a journey to get it working. Really appreciating you doing the legwork to figure this out.

OfflinePuffin

Okay, I just want to ask, has anyone tried troubleshooting this with their carrier? Over the phone?

de0u

OfflinePuffin https://xkcd.com/806/

OfflinePuffin

https://www.youtube.com/watch?v=AmD_8cBqhW0

gheylien

Holy crap ... This seems to have worked. I've been going round and round with this for a month. I switched from Fi, and RCS was working fine, to US Mobile Warp. RCS either said the device wasn't supported or the SIM wasn't supported. Stumbled onto this after going down the device identifier rabbit hole with no success. Now it says I'm connected.

One thing I have noticed is that everything still seems to be SMS. So now that I'm actually connected to RCS, I'm hoping there's a bit of a backend lag time that needs to happen before my chats switch over. Fingers crossed.

BlingoDangoDingo

gheylien Did you just follow the large message with the numbered steps? I'm also on USM Warp. I get stuck on verifying my number/setting up

gheylien

BlingoDangoDingo
Correct. However, several days later, even though I'm connected to RCS, everything comes through as SMS.

gheylien

Decided to revisit this and redo the steps, now I'm stuck at setting up as well. I don't think it was ever actually connected for whatever reason.

ffuentek

Any news? I saw a post on some forum about this issue, and I understood it was also happening on PixelOS systems, and that Google was working on a solution.

We'll have to wait and see...

gheylien

Nothing new really ... It stays in "setting up" and doesn't move forward. I turned it off for 48 hours. Last night when I turned it back on, still in "setting up". I saw an article about a larger problem and a fix coming, but no idea when that fix is going to be implemented. For now I'm just living without it because I don't wanna take the time to reset the phone.

quaff

DeletedUser177 a month ago I did this and it seemed to fix my RCS. After today's GrapheneOS update, RCS is not sending again.

gheylien

Picked up a new Pixel 9 Pro XL from the sale USM was having. Out of the box RCS worked just fine. Turned off RCS, installed Graphene, followed the steps above and RCS worked for a couple days, then it stopped. Put the stock ROM back on and it's working right out of the gate. I don't feel it's a GrapheneOS issue per se, just something going on behind the scenes with GPS that breaks it after a while. So now I'm debating which OS I want to use. I wish RCS was more open.

cb474

gheylien Yeah, I'm having a similar experience. Was setting up a new Pixel 8 for my partner at the beginning of May. RCS worked out of the box with stock Pixel ROM. Then switched to GrapheneOS thsi week and now it's not working, it's just stuck at verifying. I've tried a lot of the tricks to no avail. Although on my own Pixel 8 with GrapheneOS, it works fine, I've even turned it off and on again (this was several months ago) and it always connected right away. It's very confusing why it should behave differently on identical devices.

JavaTheHutt

DeletedUser177 My RCS also broke a few days ago. Whenever I go to send a message, it tries to send, says "Message delivers when contact name is online" then it eventually sends as SMS/MMS. I am able to receive RCS message just fine, but cannot send them.

I've tried these steps, and also the standard turning RCS off, clearing cache/data, force stopping, etc but to no avail,

Has anyone else had an issue similar to mine?

OfflinePuffin

JavaTheHutt

I have had this issue Lately myself I would reach to your carrier it seems like an issue on their emd. That's what I am doing anyway

« Previous Page Next Page »