TL;DR
- Global Rollout: Google is rolling out fake call detection for Pixel devices first, before broader Android 12 support follows globally.
- Device Handshake: The feature uses RCS signaling to check whether a trusted contact’s device is actually present during a call.
- Eligibility Limit: Users need Phone by Google, Google Contacts, Google Messages, RCS capability, and Phone by Google on both sides.
Google has launched an Android fake call detection feature globally this month, starting with Pixel devices, to flag suspected spoofed calls used in AI voice scams. Fraudsters can display a contact’s name or number while a cloned voice pressures the recipient for money or sensitive information.
Pixel devices get the first wave, with global availability expanding to Android 12 and newer devices running Phone by Google. Rather than trust caller ID alone, the system checks whether the contact’s device is present in the call path.
The warning appears when the trusted contact’s device does not return the missing confirmation signal: “If a scammer tries to impersonate your contact, that initial confirmation signal will be missing.”
How Google’s Device Check Works
Fake call detection on Android uses a silent real-time confirmation signal between devices when both the caller and recipient use the app. If that signal is absent, the recipient’s phone can check the contact’s real device and warn the user to hang up. Spoofed calls exploit the gap between the displayed identity and the real caller, so the feature tests the device relationship behind the contact name.
Rich Communication Services, or RCS, supplies the encrypted signaling path behind the check. RCS confirmation works like a digital handshake between devices: the phone checks whether the expected device participates in the exchange, not whether a voice sounds familiar. RCS also underpinned Verified SMS in Android Messages, while this rollout applies the signaling path to contact-device verification during calls.
Practical protection depends on the software stack around the call. Fake call detection requires Google’s official phone calling app Phone by Google on both sides, Contacts, Google Messages, and RCS capability in Google Messages. Users who rely on another dialer can install Google’s app and make it the default, but the warning works only when both participants meet the app and RCS requirements.
Google’s existing Android defenses also include scam detection and sender verification in Messages, Phone by Google, RCS for Business, and STIR/SHAKEN. By narrowing that identity work, the new warning focuses on trusted-contact calls rather than trying to score every suspicious voice.
Why Trusted-Contact Verification Matters
Recent voice-cloning fraud risks help explain why trusted-contact impersonation is becoming a mobile security problem. An earlier Android security update added verified financial calls, while the new approach sits beside tools already filled with caller ID, spam blocking, scam alerts, call handling, and AI call-scanning features.
Third-party call-protection apps such as Truecaller, Hiya Protect, and RoboKiller compete from the app or network-service layer. Google’s fake-call warning works inside the default-phone path when the required apps and RCS services are present.
Other apps and device makers could adopt the same method because the feature is built on top of Rich Communication Services (RCS), an open standard. Wider adoption would let fake-call warnings reach more dialer surfaces without turning every warning into a voice-analysis problem, although the first rollout remains centered on Phone by Google.
How Fake Call Detection Fits Google’s Scam Defenses
Earlier work on Google Messages scam protections already put more warnings inside Android communication apps. Personal-contact scams create a different pressure point because a spoofed number and a familiar voice can be harder to challenge during a stressful call.
Synthetic audio remains central to that pressure. Android’s new call check does not authenticate the voice itself; it tries to verify the device relationship behind the call.
Pixel owners get the first wave, Android 12 and newer devices follow through the global rollout, and the strongest protection still depends on both sides using Phone by Google with the required Google apps and RCS capability. Other dialer apps and device makers must implement the RCS verification method before fake-call warnings reach users outside Google’s first Phone by Google path.
