Android 17 QPR 2 Beta 3 takes cell network security to the next level

Robert Triggs / Android AuthorityTL;DR Android 17 QPR 2 Beta 3 introduces a SIM security timeline to track and store records of modem-detected threats, such as IMEI/IMSI access by the cell network. A new SIM security info screen outlines active encryption ciphers across calls, SMS, emergency alerts, and data streams. We’ve also spotted new notifications that would alert users to a wider variety of cellular attacks, such as DoS, jamming, imprisonment, downgrade, and location tracking attacks. Google released Android 17 QPR 2 Beta 3 over the weekend, and with it, the company is significantly beefing up defense mechanisms for cell networks. Google first introduced the “Mobile Network Security” feature in Android 16, and the latest Android 17 QPR 2 Beta 3 release upgrades it to include a tracking timeline, cipher encryption details, and a broader array of cellular attack warnings.You’re reading an Authority Insights story. Authority Insights brings you all the latest exclusive reports, app teardowns, leaks, and in-depth tech coverage from the Android Authority team that you won’t find anywhere else.Through the “Network notifications” feature within “Mobile network security,” Android 16 alerts users in real time when connected to an unencrypted network or to a potential “stingray” (a fake base station). This is what the feature setting looks like on a Pixel:While the heads-up was appreciated, those warnings were easy to miss once dismissed (unless you toggled on Android’s notification history feature, which most people don’t know about).The new “SIM security timeline” feature within Android 17 QPR 2 Beta 3 solves this by maintaining a persistent, timestamped log of modem-detected security events. If a rogue cell tower or network attempts to record your unique IMEI or IMSI identifiers, the event is saved to the timeline. Users with multiple active SIMs can also filter these logs by specific cards to see exactly which carrier line was targeted.You’ll also notice a new option right above the “2G network protection” toggle. This pertains to “SIM security information,” which, in our screenshot, shows “BSNL MOBILE” as the name of our active network. Tapping on this new option opens the following page:AssembleDebug / Android AuthorityThe page description states that it provides an “overview of encryption ciphers for the current connection over this SIM.” Further, it mentions that “if a connection using certain network generation was never established, ciphers may be missing.”Based on the connection, this section can show ciphers for: Calls & SMS (CS) Call initiation (SIP) Call data (RTP) Data authentication (NAS) Data (PS) Data transfer (AS) Emergency call data (RTP) Emergency call initiation (SIP) These terms represent the different protocols and network layers a mobile phone uses to make calls, send messages, and connect to the internet.Strings within the beta also reveal that Google is preparing granular network notifications for specific cellular threats. Beyond basic identifier requests, the system is adding warnings for: Downgrade attacks: Forcing devices onto older 2G/3G/4G protocols to bypass encryption. Imprisonment attacks: Trapping a device in connection loops to cut off legitimate carriers. Denial-of-Service (DoS) and jamming attacks: Flooding of frequency or signaling channels to disrupt reception. Location tracking attacks: Exploiting cellular protocols to secretly triangulate your position. Unauthenticated SMS and emergency alerts: Spoofed local broadcasts not sent by your carrier. Here are the new strings related to these upcoming network notifications: CodeDowngrade attack DOS attack Imprisonment attack Jamming attack Location tracking attack Unauthenticated emergency message Unauthenticated SMSThese additions transform Android’s cellular security warning system from a basic warning pop-up into a comprehensive audit log, offering privacy-conscious users much better visibility into modem-level surveillance.⚠️ An APK teardown helps predict features that may arrive on a service in the future based on work-in-progress code. However, it is possible that such predicted features may not make it to a public release.Thank you for being part of our community. Read our Comment Policy before posting.