Google has announced expanded phone-scam protection for phones running Android 15 and earlier. The change appears in its October 19 release notes for Google Play services v26.41 and targets apps that request accessibility permissions while a call is in progress.
For someone keeping an older Android phone, the appeal is straightforward: a useful security improvement can arrive without a major operating-system upgrade. It addresses a particularly dangerous moment in a scam, when a convincing caller talks you into giving an app more control over your phone. There are still limits to what owners can confirm, however, and receiving this feature would not restart a phone’s manufacturer support clock.
Why a caller wants accessibility access
Consider a caller claiming that your account needs urgent attention. They persuade you to install an app, then stay on the line to walk you through its setup. The consequential step may come after installation, when they direct you into Accessibility settings and tell you to enable a service. An apparently routine setup task can become permission for software to observe and operate parts of your phone.
Google’s explanation of restricted settings describes the underlying risk: accessibility access can let an app read content on your screen and interact with other apps on your behalf. That makes a request for this access substantially different from asking to send you notifications. In the wrong hands, those capabilities can expose sensitive information and help a malicious app carry out actions you did not intend.
Those same capabilities also make phones usable for people who need assistance. Android’s accessibility-service documentation describes screen readers, switch controls and voice controls, along with the ability to inspect interface content and perform actions such as clicks and gestures. The practical question is whether you deliberately chose and trust the service requesting access. A caller’s insistence that you enable it is no substitute for that decision.
Android already restricts some sensitive settings for certain app installations. Google advises against allowing restricted settings unless you trust the developer. If an unfamiliar app needs you to override a warning before it can supposedly help, stop and verify the app independently through the organization’s official website. Do not disable assistive tools you rely on simply because they use accessibility access.
What changed since Android 16
Google described this approach in its May 13, 2025 Android security announcement. It said scammers coach people into changing security settings and granting powerful permissions, and introduced in-call restrictions designed to interrupt those actions. At that announcement, the protection against granting accessibility permissions was associated with Android 16.
Google described the original protections as operating on the device during conversations with people outside the user’s contacts. That history explains the design: introduce a barrier while another person is applying pressure. It does not establish every operating condition of the newer implementation on older phones.
As of October 21, 2026, the new release entry gives no minimum Android version, country or model list, rollout-completion date, or exact warning screen. It also does not specify which calling apps are covered. Owners should therefore treat the announcement as an expansion of protection, without assuming every phone below Android 16 already has identical behavior.
Why it can reach a phone that is staying on an older OS
Google Play services updates independently of operating-system and manufacturer updates. It supplies background capabilities across Android, so Google can deliver certain improvements without a new Android release from the phone maker. That is why the delivery channel matters to someone whose phone is staying on its current Android version. This route requires Google Play services to be present on the phone.
Keep the names straight when checking Settings. Google Play services is the component named in this announcement. The Google Play system update date and the Android security update date are separate status entries. Updating the Play Store app is another distinct action. None of those dates or app versions can stand in for the Play services version.
This improvement also cannot tell you whether the manufacturer still fixes vulnerabilities elsewhere in your phone. If that is the decision you face, check how much security-update support your phone has left. A new defense against one scam technique is useful; it is not evidence that an expired support commitment has been extended.
This protection has a different job from AI scam alerts
The accessibility safeguard concerns a sensitive action taken during a call. Google Messages’ AI scam protections assess suspicious messaging conversations. Scam Detection in Phone by Google looks for signs of fraud during calls and has its own Pixel and country requirements. Receiving one feature does not establish that the others are available. Their settings should not be used to judge whether this permission safeguard is active.
What you can actually check on your phone
Check for a Play services update
Google’s current Play services update instructions point to Settings, then your profile picture and All services. Under Privacy & Security, open System services, select Google Play services, and tap Update or Install if offered. On some phones, you first enter Google Settings through Settings > Google; labels and entry points vary.
Use the normal update route. Clearing Play services data is a troubleshooting measure with consequences, not a documented way to activate this protection. Google warns that clearing its storage can remove saved information and require you to authenticate accounts or payment methods again.
Inspect the component version without treating it as a guarantee
Open Settings > Apps > Google Play services, using See all apps if needed. The installed version is available in the component’s App info page, a location also shown in Google’s Play services version example. This lets you check the installed component rather than looking at the Play Store’s version.
The installed version does not, by itself, establish whether this safeguard is active on your phone.
Check the phone’s other update status separately
Google’s Android update guide directs you to Settings > About phone > Android version for the Android version, Android security update and Google Play system update information. Record those separately and install the updates offered through the phone’s supported update process.
Review apps with powerful access
You can also review access already granted. Look under Settings > Accessibility for Downloaded apps or Installed services. Google documents those labels in its guidance for removing suspicious accessibility access. Review unfamiliar entries, turn off access for suspicious apps, and remove apps you installed at an unverified caller’s direction. Keep trusted accessibility services you intentionally use.
Keep Google Play Protect enabled as well. In the Play Store, tap your profile icon, then Play Protect > Settings, and check Scan apps with Play Protect. Google says it checks apps during installation and periodically afterward, and can warn about, disable or remove harmful apps. That scanning is useful alongside permission safeguards; a clean scan does not establish that the new in-call protection is active.
Do not let a caller turn a warning into another setup step
If someone unexpectedly asks you to install software, enable accessibility access or work around a security warning, end the conversation before changing settings. The FTC’s guidance on alarming account-security calls recommends contacting the organization independently through its official app or website, or a number on your statement or payment card. A caller knowing your name or account details does not establish that they are legitimate.
If you have already granted access, review the suspicious app rather than waiting for a future update to solve the problem. Keep passwords and verification codes private, and contact the organization’s real fraud department if account information may have been exposed. Treat a request to hand over control as a reason to stop, even if the phone displays no alert.