r/UniversalProfile
Same phone number, two people attached to it
One person I can reach by phone. She’s had the same number for decades. When
I try to text her to the exact same number I’ve used for years, someone else responds saying I have the wrong phone number. Any ideas what is going on?
Has anyone seen MLS encryption for a conversation between Google Messages users?
reddit.comMore Android RCS contacts are becoming E2EE with iOS
my RCS was broken for a few weeks (iOS 27b4 activation stuck bug, b5 fixed it) and I've noticed more conversations now appear as E2EE
I went through my contacts and roughly 1 in 5 contacts appear as E2EE now
none of the newly encrypted contacts are necessarily tech savvy, which means that Android x iOS E2EE is rolling out to stable GM
No changes with iOS 27 DEV Beta 5
Unsending a message and editing still does not work.
Just an update.
iOS 27.0 Beta 5 - Dual-SIM Bug
I had RCS Activation errors in iOS Beta 4 for all three US Mobile Networks (Warp - Verizon, Dark Star - AT&T, Light Speed - T-Mobile). RCS Activation was successfully working, however, with other carriers.
iOS 27.0 Beta 5 fixed the RCS Activation issue, I'm now able to activate RCS on all three networks. But....only when there is one eSIM active at a time. RCS Activation now consistently fails when there are multiple eSIMs enabled. This includes other carrier non-US Mobile eSIMs, which were working in a Dual-SIM configuration in Beta 4.
I suspect Beta 5 has introduced a new Dual-SIM bug. Anyone observing the same?
Have anybody been able to utilize E2E Encryption via RCS yet?
I’m not sure if my friend’s android phone need to update for it to work but it seems like the conversation is not E2E Encryption yet.
Looking for 2 volunteers for a quick RCS group chat test (Testing a backup app)
Hey everyone, I'm currently testing an Android backup app I'm working on to make sure it properly backs up and processes RCS group messages. To test this, I need to be in a live RCS group chat with at least two other people who have RCS enabled on their devices (Android or iOS 18+). If you're willing to help out, please send me a Direct Message (DM) with your phone number, and I'll add you to a temporary group. Once we send a few test messages to verify the backup capture, we can disband the group. Thanks in advance for the help!
US Mobile - Potential RCS Activation Bug (iOS 27.0 Beta 4)
UPDATE: iOS 27 Beta 5 (released today) surprisingly fixed my RCS activation issue on all three US Mobile networks. They are all working now post-upgrade. But only when a single eSIM is enabled at a time. If I enable Dual-SIM, RCS continues to fail to activate on both eSIMs. From one bug, to another.
-----------------------------------------
Are there any US Mobile subscribers here with RCS successfully activated on iOS 27.0 Beta 4? All three of my new lines are failing to activate, "waiting for activation...", (Lightspeed, Warp, Dark Star).
What is super interesting is even though my activation is failing for each line, I have one Android contact running Google Messages Beta. When he sends me a message, the conversation always switches to RCS (encrypted). But when I reply it switches back to SMS. It is almost like my line is partially activated, enough that his phone can detect I am RCS enabled with encryption enabled. But my iPhone doesn't have server confirmation it has fully registered with Jibe servers. I've confirmed it is an actual RCS message getting delivered because he can send me a large video file without SMS compression, and in-line replies are also working.
IMS Status show "Voice & SMS", and RCS state is "waiting for activation...".
I can't tell if this is related to server-side RCS cache issue with the previous carrier before a line transfer or an RCS bug in iOS 27.0 Beta 4 with US Mobile subscribers. RCS was working when I was on T-Mobile (same iOS version) before moving to US Mobile. RCS is properly working on all the other iPhones running iOS 26 on my account after transferring from T-Mobile to US Mobile.