Samsung Galaxy owners who rely on caller ID to screen incoming calls now have a new line of defense: a feature that detects when a scammer spoofs a phone number already saved in the user’s contacts. The protection works through a device-level digital handshake rather than carrier-side filtering, and it ships turned on by default for eligible phones running Android 12 or later. The timing is pointed. INTERPOL has flagged increasingly sophisticated global financial fraud in its 2026 threat reporting, and the Federal Trade Commission has highlighted a wave of enforcement actions against impersonation scams earlier in 2025.
Why a device-level handshake fills a gap carriers cannot close
U.S. voice service providers have been required to authenticate caller ID through the STIR/SHAKEN framework since a June 30, 2021 compliance deadline set by federal caller ID rules. Those regulations force carriers to sign and verify the origin of calls at the network level, making it harder for mass robocallers to hide behind fake numbers. Yet STIR/SHAKEN was designed primarily to stop bulk operations, not to confirm whether a specific person is actually on the other end of a call that displays a familiar name. Once a spoofed call clears the network and lands on a handset showing “Mom” or “Your Bank,” the carrier’s job is effectively done.
Google’s fake call detection addresses that remaining blind spot. The feature uses an end-to-end encrypted RCS channel to perform a device-to-device handshake between the caller’s phone and the recipient’s phone. If the handshake fails or never occurs, the recipient sees a warning that the incoming call may not actually be from the contact it claims to be. Because the check happens on the device itself, it can flag spoofing attempts that network-level authentication lets through, especially when scammers piggyback on legitimate numbers or exploit gaps in international routing.
This split between network verification and device verification has practical consequences. Carriers authenticate the originating line; the handshake authenticates the person behind it, or at least the specific device associated with that person’s account. As RCS adoption grows across Android phones, the handshake could become the primary trust signal for contact-specific calls, in the same way that blue checkmarks and verified badges evolved in messaging and social apps. That would shift some accountability for spoofing prevention away from carriers and toward handset makers and the app ecosystem that supports RCS messaging.
How fake call detection works on Samsung Galaxy phones
Eligibility is specific. A phone must run Android 12 or later and have Phone by Google, Google Contacts, and Google Messages installed with RCS turned on, according to Google’s support guidance. Samsung Galaxy devices that meet those requirements receive the protection automatically because it is default-on for eligible hardware. Users do not need to toggle a setting or enroll in a beta program; the feature is baked into the calling experience for those who rely on Google’s dialer and messaging stack.
Samsung already operates its own call-screening layer. Smart Call, built into the Samsung Phone app, labels suspected spam and fraud callers, lets users report numbers, and offers one-tap blocking. That system draws on crowd-sourced databases and carrier partnerships to flag unknown numbers that match known spam patterns. The new fake call detection is different in kind: it verifies whether a call claiming to come from a saved contact is genuine, rather than scoring an unfamiliar number for spam likelihood. The two layers now work in parallel on qualifying Galaxy phones, covering both unknown-number spam and known-contact spoofing.
In practice, that means a Galaxy owner might see a spam label on a call from a random toll-free number thanks to Smart Call, and a separate warning banner on a call that appears to come from a friend or family member if the digital handshake fails. The distinction matters because users tend to treat contact-name calls as inherently safe. By inserting a verification step into that trusted category, Samsung and Google are trying to blunt some of the most emotionally manipulative fraud tactics, such as fake emergency calls from relatives or impostors claiming to be from a customer’s own bank.
Google’s documentation discloses that certain call information may be sent to Google as part of the feature’s operation, but no independent audit or effectiveness metrics have been published. Samsung has not released a separate technical brief detailing how its Smart Call system interacts with Google’s handshake at the software level, leaving open questions about how conflicts are resolved if one system flags a call and the other does not. For now, users must rely on on-screen indicators and their own judgment rather than a transparent scoring methodology.
Enforcement pressure and the fraud threat driving adoption
The FTC published a press release in April 2025 outlining recent enforcement work on impersonation, signaling that spoofing remains a top priority for regulators. The agency emphasized that scammers increasingly pose as government officials, tech support staff, and financial institutions, often using caller ID tricks to make the ruse more convincing. Separately, INTERPOL’s 2026 reporting warned that financial fraud is growing more sophisticated globally, with voice-cloning and caller-ID manipulation among the techniques gaining traction across borders.
These warnings help explain why Google chose to enable fake call detection by default rather than burying it in a settings menu. Scammers who spoof a trusted contact’s number exploit a psychological shortcut: people answer calls from names they recognize without questioning the caller ID. No amount of carrier-level STIR/SHAKEN signing can override that instinct once the spoofed number reaches the screen. A visible on-device warning, delivered before the user picks up, interrupts the pattern at the moment it matters most and gives the recipient a chance to pause, verify, or let the call go to voicemail.
The broader enforcement climate also creates incentives for device makers to show they are not passive conduits for fraud. As regulators scrutinize how platforms handle impersonation, features like fake call detection offer a concrete, consumer-facing response. For Samsung, integrating Google’s handshake technology into Galaxy phones allows the company to point to layered protections without having to build a parallel RCS verification system from scratch.
Open questions for Samsung owners and the wider Android ecosystem
Several gaps remain. No public FTC or carrier dataset quantifies how often scammers successfully spoof numbers that are already saved in a victim’s contacts, so the real-world scale of the problem the feature targets is unclear. Google has not published detection-accuracy rates or false-positive benchmarks for the RCS handshake method, leaving consumers and security researchers to infer effectiveness from anecdotal reports rather than hard data. Without independent testing, it is difficult to know whether the system meaningfully reduces successful scams or primarily adds friction for edge cases.
There are also coverage limits. Because the feature depends on both parties having RCS enabled through Google Messages, calls from contacts using iMessage, older SMS-only phones, or third-party dialer apps will not trigger the handshake at all. International calls may face additional constraints if local carriers or devices do not fully support RCS. In mixed ecosystems where families and businesses span Android and iOS, that means the protection will apply inconsistently across a user’s contact list.
For Samsung owners, the immediate takeaway is that fake call detection is a helpful but partial safeguard. It strengthens the security of calls between compatible Android devices while leaving traditional phone traffic largely unchanged. Users who want the most benefit will need to keep Google Messages as their default texting app with RCS turned on, even if they prefer Samsung’s stock messaging interface for other reasons.
For the wider Android ecosystem, the feature marks a shift toward treating caller identity as an application-level problem rather than solely a carrier responsibility. If handset makers and app developers continue down this path, future protections could combine device handshakes, behavioral analytics, and user reporting into a more comprehensive trust layer for voice calls. Until then, fake call detection on Samsung Galaxy phones is best understood as one more tool in a still-evolving defense against impersonation scams, not a guarantee that every familiar name on the screen is who it claims to be.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
