I tried it once a year ago, message was delayed. Immediately switched to another App (QKSMS).
this post was submitted on 21 Nov 2024
16 points (94.4% liked)
Technology
59498 readers
3579 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Haven't used RCS since Google intentionally caused it to silently fail on rooted devices
can be fixed with play integrity spoofing but not a true fix
It can be, but you can't tell it's broken until you try to send an RCS reply. Otherwise, it appears to be working.
Last night I noticed they broke again, so I just said hell with it and disabled Google Messages and went back to Fossify. Screw RCS. Google has inserted themselves into what should be a carrier service, and they're gatekeeping it to only Google-blessed configurations.
Apple is doing insane stuff with iMessage making SMS useless with Android. It is intentional manipulation. I've only seen it on some Apple kernels with the latest iPhone. My old man's phone absolutely will not send or receive an SMS unless I message is manually turned off and then it won't get iMessages. Apple has always been a shitty company, but this is next level insane. Just get and use the Signal app and ditch all the proprietary garbage and manipulative bs IMO.
SMS, iMessage and now RCS have been working well for me and I've been (primarily) using iPhones for the past 8 years now.
The Messages app shows what type of message (iMessage/SMS/RCS) you're about to send in the text field and displays which (sent or received) messages are what as well.
One thing I could see going wrong is that a given phone number is registered with iMessage and it hasn't been disabled after switching to an Android phone for example.
Another (imo more likely) thing is that if it's using RCS, some carriers don't seem to work too well with it as of now. iOS seems to have implemented the base standard, while Google added proprietary extensions to said "standard" in Android, like end-to-end encryption. I never had issues sending or receiving RCS messages from/to Android devices, but there might be some hiccups for some people as RCS - even though it's called a "standard" - isn't really standardized.
Not sure what's so insane from Apple's side about any of that.
Not sure of the exact issue but the best answer from Apple so far is that the issue is kernel related. I've tried every setting I can find and no luck. It could also be related to actual dual sim use. It could be carrier related, but it is less likely Android as I use Graphene OS.
Doesn't even have to be Apple, the wife and I are on different carriers and I saw the same shenanigans happening.
Signal app or Threema or really any other independent messaging app (except whatsapp, strangely) solved the issue.
I have a pixel with T-Mobile and my wife has iPhone with Verizon. RCS has worked great for us.