Your iPhone RCS chats with Android are encrypted in iOS 26.5: How to verify E2E is enabled


Encrypted RCS text messaging on an iPhone

Lance Whitney/ZDNET

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • iOS 26.5 will encrypt RCS text messages between iOS and Android.
  • The encryption supports the iPad, Mac, and Apple Watch.
  • The update brings new Pride wallpaper to iPhone and Apple Watch.

iPhone owners who exchange texts with Android users should now find that their messages are safe and secure from prying eyes. Released on Monday, Apple’s iOS 26.5 finally brings end-to-end encryption to RCS (Rich Communication Services) messages. Thanks to the latest iOS updates, that protection also extends to the iPad, Mac, Apple Watch, and Vision Pro.

Also: How to send RCS messages from your iPhone to your Android user friends

This type of end-to-end encryption means that your messages can’t be read while they travel between devices. For now, the feature will be in beta mode as it rolls out. Though the encryption is enabled by default, its actual use depends on a couple of factors.

How to check if E2E encryption is enabled

First, your carrier needs to support the technology. Though all the major carriers should already be on board, smaller regional ones may not have completed the necessary steps yet. Apple’s web page on Wireless Carrier Support and Features will tell you if your carrier has adopted the encryption by listing “End-to-end encrypted RCS messaging (beta)” as one of its features.

Second, Android users must be running the latest version of Google Messages. Assuming those two conditions are met, iPhone owners will see a new lock icon in their RCS chats as a sign that the end-to-end encryption is working.

To ensure that your RCS messages are encrypted, you’ll need to update your iPhone to iOS 26.5. To do that, head to Settings, select General, tap Software Update, and then tap the Update Now button.

Also: 12+ iPhone settings you can change to noticeably improve its battery life (iOS 26 and older)

After the update has been installed and your phone has restarted, you can double-check the encryption option. Go to Settings, select Apps, and then tap Messages. Swipe down the screen to the Text Messaging section and tap the entry for RCS Messaging. Make sure that End-to-End Encryption (Beta) is turned on.

You’ll also want to perform the same steps on an iPad, Mac, Apple Watch, or Vision Pro. You can then send and receive texts with your Android contacts knowing that the messages will be encrypted on both ends. To confirm this, swipe to the top of the screen of a text conversation with an Android user. You should see the lock icon followed by the word Encrypted.

“Encrypted RCS is a real privacy win, and the cross-industry work with Google and the GSMA is the harder achievement worth acknowledging,” Adam Boynton, Senior Security Strategy Manager for Apple device security provider Jamf, told ZDNET. “The honest caveat is that encryption secures the pipe, not the person on either end. The fastest-growing threat on mobile is no longer interception, it is impersonation. AI-cloned voices and deepfake messages pass every technical check because nothing was ever compromised. We have solved for the transit. We have not solved for the human.”

Other iOS 26.5 features

Aside from the encryption, the iOS 26.5 update is a minor one but does kick in a few new features. 

You’ll discover new Pride Luminance wallpaper for the iPhone, iPad, and Apple Watch. A “Suggested Places” option in Apple Maps will steer you to spots you may want to visit. Apple developers can now sell you annual subscriptions but charge you monthly. On the downside, though, Apple Maps may also start to show you local ads based on your location.

Also: Google Maps vs. Apple Maps: I compared two of the best navigation apps – here’s my pick

Of course, the usual bug fixes are also baked into the latest update. 

For the iPhone and iPad alone, version iOS 26.5 resolves more than 60 security vulnerabilities affecting a variety of features. The encryption and the security fixes both make this otherwise minor update worth installing.

“The headline number of fixes matters less than the pattern behind them,” Boynton said. “A concentration of WebKit vulnerabilities alongside kernel memory issues and an App Intents sandbox escape reflects the types of components commonly chained together in modern mobile attacks. None of the vulnerabilities disclosed by Apple are reported as actively exploited, but the update offers a useful look at the current mobile threat landscape. One kernel issue was credited to Google’s Threat Analysis Group, which focuses on state-backed threats and high-risk users, while a separate WebKit flaw was credited to Anthropic researchers working with Claude.”





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


When you pick out a phone, you’re also picking out the operating system—that typically means Android or iOS. What if a phone didn’t follow those rules? What if it could run any OS you wanted? This is the story of the legendary HTC HD2.

Microsoft makes a mess with Windows Mobile

The HD2 arrives at an unfortunate time

windows mobile 6.5 Credit: Pocketnow

Officially, the HTC HD2 (HTC Leo) launched in November 2009 with Windows Mobile 6.5. Microsoft had already been working on Windows Phone for a few years at this point, and it was planned to be released in 2009. However, multiple delays forced Microsoft to release Windows Mobile 6.5 as a stopgap update to Windows Mobile 6.1.

Microsoft’s plan for mobile devices was a mess at this time. The HD2 didn’t launch in North America until March 2010—one month after Windows Phone 7 had been announced at Mobile World Congress. Originally, the HD2 was supposed to be upgraded to Windows Phone 7, but Microsoft later decided no Windows Mobile devices would get the new OS.

This left the HD2 stuck between a rock and a hard place. Launched as the final curtain was dropping on one OS, but too early to be upgraded to the next OS. Thankfully, HTC was not just any manufacturer, and the HD2 was not just any phone.

The HD2 was better than it had any right to be

HTC made a beast of a phone

HTC HD2 Credit: HTC

HTC was one of the best smartphone manufacturers of the late 2000s and 2010s. It manufactured the first Android phone, the first Google Pixel phone, and several of the most iconic smartphones of the last two decades. Much of the company’s reputation for premium, high-quality hardware stems from the HD2.

The HD2 was the first smartphone with a 4.3-inch touchscreen—considered huge at the time—and one of the first smartphones with a 1 GHz Qualcomm Snapdragon processor. That processor, along with 512GB of RAM, made the HD2 more future-proof than HTC probably ever intended. Phones would be launching with those same specs for the next couple of years.

For all intents and purposes, the HD2 was the most powerful phone on the market. It just so happened to run the most limiting mobile OS of the time. If the software situation could be improved, there was clearly tons of potential.

The phone that could do it all

Android, Windows Phone, Ubuntu, and more

The key to the HD2’s hackability was HTC’s open design philosophy. It had an easily unlockable bootloader, and it could boot operating systems from the NAND flash and SD cards.

First, the community took to righting a wrong and bringing Windows Phone 7 to the HD2. This was thanks to a custom bootloader called “MAGLDR”—Windows Phone 7.5 and 8 would eventually get ported, too. The floodgates had opened, and Windows Phone was the least of what this beast of a phone could do.

Android on the HTC HD2? No problem. Name a version of the OS, and the HD2 had a port of it: 2.2 Froyo, 2.3 Gingerbread, 4.0 Ice Cream Sandwich, 4.1/2/3 Jelly Bean, 4.4 Kitkat, 5.0 Lollipop, 6.0 Marshmallow, 7.0 Nougat, and 8.1 Oreo. Yes, the HD2 was still getting ports seven years after it launched.

But why stop at Android? The HD2 was ripe for all sorts of Linux builds. Ubuntu—including Ubuntu Touch—, Debian, Firefox OS, and Nokia’s MeeGo were ported as well. The cool thing about the HD2 was that it could dual-boot OS’. You didn’t have to commit to just one system at a time. It was truly like having a PC in your pocket, and the tech community loved it.

Do a web search for “HTC HD2” now, and you’ll find many articles about the phone getting yet another port of an OS. It became a running joke that the HD2 would get new versions of Android before officially supported Android phones did. People called it “the phone that refuses to die,” but it was the community that kept it alive.

The last of its kind

“They don’t make ‘em like they used to”

HTC HD2 close up Credit: TechRepublic

The HTC HD2 was a phone from a very different time. It may have gotten more headlines, but there were plenty of other phones being heavily modded and unofficially upgraded back then. Unlockable bootloaders were much more common, and that created opportunities for enthusiasts.

I can attest to how different it was in the early years of the smartphone boom. My first smartphone was another HTC device, the DROID Eris from Verizon. I have fond memories of scouring the XDA-Developers forums for custom ROMs and installing the latest Kaos builds on a whim during college lectures. Sadly, it’s been many years since I attempted that level of customization.

It’s not all doom and gloom for modern smartphones, though. Long-term support has gotten considerably better than it was back in 2010. As mentioned, the HD2 never officially received Windows Phone 7, and it never got any other updates, either. My DROID Eris stopped getting updates a mere eight months after release.

Compare that to phones such as the Samsung Galaxy S26, Google Pixel 10, and iPhone 17, which will all be supported through 2032. You may not be able to dual-boot a completely different OS on these phones, but they won’t be dead in the water in less than a year. We will likely never see a phone like the HTC HD2 from a major manufacturer again.

HTC Droid Eris


A Love Letter to My First Smartphone, the HTC Droid Eris

No, not that DROID.



Source link