Multi-Network Lines Feature Limitations
What are the limitations to be aware of for Multi-Network lines on all three networks? (i.e. data usage, network priority, international, hotspot, etc.)
What are the limitations to be aware of for Multi-Network lines on all three networks? (i.e. data usage, network priority, international, hotspot, etc.)
Here are the things I would like to see come to US Mobile:
NOTE: I'm aware some of these are not likely and fully dependent on Parent Network making the features available for MVNOs. Like I said, just a wish list.
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?
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.