News |
By Brian Tristam Williams
Google has started rolling out fake call detection for Android, using an RCS-backed device verification mechanism to warn users when a caller may be spoofing one of their contacts.
The feature is part of the June Android Drop and is aimed at a very specific weakness in phone security: caller ID can say a call is from a known person, while the call itself may be routed through internet-based spoofing tools. With AI voice cloning now widely available, that can turn a familiar name on a screen into a convincing fraud attempt.
Google has outlined the new call-warning mechanism, which works when both the caller and recipient are using Phone by Google. Instead of trying to decide whether a voice sounds synthetic, Android checks whether the call is actually coming from the contact’s device.
The system acts like a silent digital handshake. When a genuine contact calls, the caller’s device sends a real-time confirmation signal to the receiving device. Google says this is built on end-to-end encrypted Rich Communication Services (RCS), which gives the system a route to verify the device without exposing call content.
Google’s fake call detection checks whether a call is coming from a verified contact device before warning users about possible spoofing.
If that initial confirmation signal is missing, Android can check with the contact’s actual device. If the real device is not placing a call, the recipient sees a warning that someone may be pretending to call from that contact’s number, with the option to end the call.
This is a more practical defence than trying to detect a cloned voice after the call has already started. Voice analysis can be useful, but it is also a moving target. A device-origin check gives Android a stronger signal before the victim has to judge whether the caller sounds right.
Fake call detection is rolling out globally this month to Android 12+ devices, starting with Pixel devices. It requires Phone by Google, Contacts and Google Messages to be installed, and both people on the call must use Phone by Google. RCS capability in Google Messages is also required.
That set of requirements is the main limitation. The protection becomes more valuable as more Android devices and apps adopt the mechanism, and Google says it built the feature on top of RCS so that other device makers and calling apps can implement similar checks.
The update also reinforces Android’s broader move into platform-level security and interoperability. As previously reported by eeNews Europe when Google readied Android for RISC-V, the operating system continues to expand beyond a simple handset software stack into a wider ecosystem layer for devices, silicon and services.
The June Android Drop also expands Quick Share support for Apple AirDrop on selected Android devices. Google says compatible Android phones can now send files to iPhone devices using AirDrop, provided the iPhone is within Bluetooth range and its AirDrop visibility is set to “Everyone for 10 Minutes”.
The current compatibility list includes recent Samsung Galaxy S, Z Flip and Z Fold models, recent Pixel devices, and selected phones from Xiaomi, OnePlus, OPPO, Vivo and Honor. Google’s Quick Share compatibility page also lists several additional devices as coming soon.
For users, the two updates solve different problems, but they point in the same direction. Android is trying to reduce friction where phones still behave like isolated ecosystems, while adding stronger default protections against scams that exploit trust in contacts, caller ID and increasingly convincing AI-generated speech.
If you enjoyed this article, you will like the following ones: don't miss them by subscribing to :
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。