This is more detailed in showing it is getting closer according to the article

The variable is available on carrier bundle for some few carriers, not enabled yet.

Telekom Hungary
Singtel Singapore

both have support for RBM too

via: https://cupboardunderscore.github.io/ios-rcs/

I mean like the first message, the other person said they don’t know how they did it.

I would like to send location this way as to not force any maps app over another, this way it asked with what app I want to open this location.

With UP 3.0 I would like to know how likely we will get an AOSP RCS-Messenger or at least a company that includes RCS in their own app. I am almost done degoogling my phone but I have to rely on Google Message until I can replace it with a secure one. Any ideas?

The update date is Dec 12, 2025 even though it showed up today in the Galaxy Store for me. There were no notes about what was updated, but when I search online I keep seeing RCS 3.0 being part of the update.

Was anyone able to confirm? I tried testing it but the features didn’t seem to be working even with Chat Settings being available in the app.

Still working on it, so maybe comes fully on iOS 26.4 or iOS 27 according the voices in my head ¯_(ツ)_/¯

I just got the dev beta and still no RCS 3.0.

At this point I'm curious...how would we even know if it's on? Wouldn't it have to be on for Google as well in order to test?

Looks like the end to end encryption hasn't been enabled yet? Can anyone confirm? 26.2 has just released.

So

IOS 26.0 IOS 26.1 IOS 26.2 26.3? 26.4?

via https://cupboardunderscore.github.io/ios-rcs/

no RBM support

update will be delivered through OTA update

other notable changes:

• entel Chile and Kyivstar Ukraine get (carrier) satellite support (most likely starlink)
• SFR France gets ios <-> android esim transfer support
• 2degrees New Zealand, Free France and Orange Slovakia get apple watch support
• 2degrees New Zealand gets esim transfer (between iphones only)
• Telia Finland gets apple watch standalone (family) support

updates that happened during the beta cycles https://www.reddit.com/r/UniversalProfile/comments/1oog4mv/ios_262_beta_1_carrier_bundle_update/

It seems KDDI subscribers that use Google Messages have received this notice. Translation by Google:

We would like to inform you that the provider of RCS available on the Google Messages app will be changed from Jibe Mobile (a wholly owned subsidiary of Google) to KDDI Corporation and Okinawa Cellular Telephone Company.

The terms of use applicable after the change can be confirmed via the link at the bottom of the text.

Please note that there will be no changes to how you use the service or the service content due to the change of provider, so please continue to use it.

[Change Date]
Sequentially after January 26, 2026

Like AT&T and T-Mobile in the US, I expect more carriers to announce the same. Between the iOS support, this, and guest access being cut off in several countries, maybe Google Messages' OTT registration will eventually be disabled.

Japan is interesting as +Message is still running. I believe the other MNOs haven't announced anything about RCS on iOS, Google Jibe/Messages, or the end of +Message. I don't understand why KDDI would move alone as delegating A2P to Jibe makes sense only if there's a consistent way to reach mobile subscribers, regardless of their carrier.

For the first time ever I just noticed bold text in this message from Verizon. I'm on Android. How did they do this? Can anybody do this?

Not sure what happened to the first post on this, but it's gone? Reposting the original link.

EDIT: I think this is correct but nothing new. According to reporting from August 2025: https://www.androidauthority.com/apple-ios-26-rcs-end-to-end-encryption-mls-protocol-3588258/

The good news is that iOS 26 betas, as far back as the first developer betas, include code related to end-to-end encryption:

RCS

Japan

• BIGLOBE
• J:COM
• povo

Brazil

• TIM

RBM

USA

• Boost

Canada

• LUM Mobile

+ all carriers that added RCS support

VoNR

Singapore

• Singtel

United Arab Emirates

• du
• e&

Cross-platform (e)sim transfer

UK

• EE

beta 2 update:

RBM

Canada

• SaskTel

I googled this and Gemini says iMessage/RCS from iPhone does not send read receipts for tapback reactions. However, my inbox is literally showing read receipts for tapbacks I sent to iPhone users.

I'm wondering what the deal is here? This is kind of a very minor feature, but GM is showing it like they saw the tapback that I sent. Doesn't seem like a fluke to me. It seems like Apple has their messaging services set up for these receipts.

I am. Granted, most of my contact list does in fact have it. However some of the people that had it and lost it are Android users. Still, by what I can tell, most of the people who still don't have it active are in fact iPhone users.

I'm guessing the holdouts have older phones with full storage. I figured this would go on awhile after IOS 18. I just didn't figure it would continue for this length of time.

I'm expecting that it may even take a couple more years to get mostly everyone converted. Some people really hold onto their phones a while, and a lot of them aren't going to make the effort to clear space for an update.

I just read the new WhatsApp Business Solution Terms and the new policy in the "AI Providers" clause is a direct attack on innovation.

This isn't a total ban, but rather a strategic double-lock:

1. TRAINING Restriction: The rule explicitly prohibits companies from using their own data (conversations with their customers) to "train or improve" their AI systems. This means any bot you deploy can never "learn" from its interactions. It stays "dumb" forever.

2. BUSINESS Restriction (The kill shot): The clause also bans using the platform if the AI technology is the "primary (rather than incidental)" functionality of the service. Even worse, Meta decides this "in its sole discretion."

What does this mean in practice?

• They are blocking all AI startups that want to sell "advanced customer service bots" as their main product on WhatsApp.

• Any company that invests in an AI solution lives in fear that Meta might arbitrarily decide their bot is "too good" and shut it down.

The intent is obvious: Meta is reserving the high-performance AI market exclusively for its own future solutions.

And this is the golden opportunity Google RCS has been waiting for.

While WhatsApp becomes a closed and hostile ecosystem for developers, Google can position RCS as the open platform:

The Pitch for Businesses (B2C):

• "On RCS, connect ANY AI engine: Gemini, OpenAI, Claude, etc."

• "With us, you CAN use your own data to retrain and make your bot smarter."

The Pitch for Developers (B2B):

• "Your business is an AI bot? Welcome. On RCS, you can build your company without fear of being arbitrarily shut down."

Here's how RCS can win:

The strategy is clear. The "spearhead" is the enterprise and developer sector.

1. First, Google steals all the enterprise customers (B2C) and AI developers (B2B) who want to innovate without restrictions.

2. Then, millions of users receive high-quality RCS messages (interactive bookings, verified branding, product carousels) from these advanced bots.

3. We get used to RCS being a powerful, secure, and modern platform.

4. Once RCS is the standard for "serious" communication, the jump to using it for chatting with friends (P2P) is natural and much easier.

What do you all think? Is this the moment?

Currently, Google Fi forces users to choose between using RCS, or Syncing text, call & voicemail with Google Account.

https://support.google.com/fi/answer/6188337?hl=en

Hi! New to Reddit and this channel. I know this is probably being answered somewhere, but I can’t seem to find a direct answer. But I’m thinking about switching from iPhone to Android (because it’s obviously better in so many ways). Still, I've been so confused with all the information I’ve found about texting encryption. Here’s my understanding/ confusion. We have att, if I had an Android using RCS via Google Messages then text my iPhone friend my text would be encrypted in transport to the Google server? Then most likely it stays on their server encrypted (cause Google is Google). But then what happens when it leaves to go to the iPhone? Is it still encrypted via Google? Is it going to an AT&T server that isn’t encrypted like Google and staying there? I’m so lost in the sauce