Unfortunately all it does is crash. I'm guessing there's something they changed in the system that it needs. Thanks for the file though.— Matthew (@LinkofHyrule89) March 9, 2019
Short Message Service aka SMS is still present since its inception in the 1990s. Before the widespread availability of cheap mobile data and instant messengers, SMS single-handedly bootstrapped an independent ecosystem of text messaging.
The first SMS message was sent in 1992, thus the technology is already more than 25 years old. Despite the emergence of high speed data connectivity, SMS is still available as an integral part of smartphones.
While designing iMessage, Apple carefully implemented the SMS fallback option. That strategy ensures seamless interoperability of messaging while using the ecosystem of Apple.
However, the journey of Android users has not been as smooth as Apple people in the world of native messaging. Google is heavily mocked by the tech communities for their confusing strategies while designing a standardised messaging platform.
Hangouts, Google Allo, Android Messages…. I don’t want to reiterate the painful saga.
The arrival of Rich Communication Services (RCS) has brought a new hope amidst this chaotic backdrop. RCS is a next generation communication protocol which aims to enhance the cellular messaging by bringing features like MMS-esque photo/video sharing, delivery/read receipts etc.
RCS is meant to replace the current texting standard, i.e. SMS. The Universal Profile of RCS is regulated by the GSM Association (GSMA), who describes it as a “single, industry-agreed set of features and technical enablers”.
RCS is backed by Google-owned Jibe, who is pushing major carriers to adopt their backend cloud services that are necessary for the universal profile. The thing is, US cellular providers like T-Mobile and Verizon already have their proprietary enhanced messaging protocols.
Told you, things are complicated! ?
T-Mobile markets their tech as ‘Advanced Messaging‘.
Advanced Messaging is T-Mobile’s next generation messaging service that allows you to send high-resolution photos and larger video files. You can also see when your messages have been delivered, when they are read, and even when others are typing a response! There is no app to download, no separate account to configure, and no password to enter.
Only a handful of phones are whitelisted for this Advanced Messaging thingy. Fortunately the carrier is also adopting the RCS Universal Profile 1.0, albeit in a slow pace.
As a matter of fact, the T-Mobile exclusive OnePlus 6T was initially launched without RCS/Advanced Messaging support. The carrier enabled it with the recent most OTA update.
The stock OnePlus messaging app is updated with RCS support, but sideloading it on non-T-Mobile firmware won’t bring similar support automagically.
People have found the implementation half-baked, as RCS only works with stock OnePlus messaging app, but not with Google Messages. Also, cross-carrier RCS support seems finicky.
I got the T-Mobile OnePlus 6T. However after the latest update, I can no longer receive pictures attached to a text message. The senders phone will say “RECEIVER CANCELED”. T-Mobile tech support offered me a replacement phone and OnePlus tech support started a repair session. They re-flashed my phone and the problem still exist. OnePlus finally said wait until the next update and see if that fixes the problem. I f I use Textra or another messaging app it works fine. I happen to like the default app that came with the phone.
Anyone else have ths problem?
Several users have noticed weird glitches while sending or receiving text messages after the update.
In addition to the above problem, I noticed another issue. My wife and I both have TMobile OnePlus 6ts. She uses the default messaging app, and I use the Google messages app. I no longer receive texts from her in the Google messages app, but I do receive texts in the default app. I assume this is because of RCS. Is there any fix to this?
Having the exact same issue with my OnePlus 6T. Please fix this issue. Restarting the messenger app does nothing. Only restarting the phone will bring the limit up to 1000 characters. But it seems to revert to 100 after a bit.
OnePlus and T-Mobile are, in fact, aware of the situation. Tom B., Global Service Strategy Operations of OnePlus, started a new thread and shared a handful of instructions to capture logs and send them to OnePlus for diagnosis purpose.
How to capture log:
1. Input *#800# from dialing interface, enter “oneplus logkit”, delete history log.
2. Move log path to “built-in SD card” and then Click “save log”, reboot device.
3. Click “get QXDM Log”, choose “modem-common”, and then click “open device log”.
4. Reproduce the issue that text message till error happens and take a screenshot to record the time, then stay for a few minutes. (better above five minutes)
5. Enter “get QXDM log” and choose “close device log”, and then click “save log” again to stop it.
6. Enter File manager >Internal storage > oem_log >diag_logs to check if the subfolder date was the latest.
7. Finally, send us the whole oem_log folder (file manager-storage) along with the screenshots.
8. Enter into the logkit where you enable QXDM log, click the “close device log”, and then “delete history log”.
Tom also posted a basic troubleshooting guide.
The logs and feedback need to be submitted at the Feedback section of the official OnePlus forum. The event will be closed on April 7, 2019, 6 AM ET.
At the official OnePlus subreddit (r/oneplus), members have already started to participate and share their experiences after the RCS update.
FYI, US unlocked Galaxy S10 users are facing some weird problems with RCS on T-Mobile. You may take a look at this article to know more.
Are you a user of OnePlus 6T on T-Mobile? Do let us know your opinion regarding the RCS support and obviously share the logs with OnePlus.
PiunikaWeb is a unique initiative that mainly focuses on investigative journalism. This means we do a lot of hard work to come up with news stories that are either ‘exclusive,’ ‘breaking,’ or ‘curated’ in nature. Perhaps that’s the reason our work has been picked by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and more. Do take a tour of our website to get a feel of our work. And if you like what we do, stay connected with us on Twitter (@PiunikaWeb) and other social media channels to receive timely updates on stories we publish.