Google’s June 2026 Android Update Adds Wardrobe Scan and Scam Detection

Your phone already knows your face, your location and your heart rate. Now it wants to catalogue your wardrobe. Google’s June 2026 Android update includes an AI feature that scans your photos to log what you own and wear, and that is just one of several capabilities that show how deeply AI is now embedded in the devices most of us carry everywhere.

Google’s June 2026 AI Features: What’s Actually New

The headline addition is the “Digital Wardrobe,” a feature within Google Photos that uses AI image recognition to scan a user’s existing pictures and build a catalogue of their clothing and style. The analysis runs entirely on-device, processing photos held in the phone’s own memory rather than sending them to a server. That is a genuine privacy improvement over cloud-based alternatives. It also means the phone constructs an increasingly detailed, locally stored model of a user’s appearance and habits, one that sits outside the normal transparency of cloud-backup disclosures.

The second significant addition is “Fake Call Detection” for Pixel phones. When a call arrives, the Phone by Google app checks whether the incoming number carries an encrypted RCS verification signal from the originating device. If that signal is absent, because the number has been spoofed or a real-time AI voice clone is in use, the app flags the anomaly and warns the user before they pick up. The analysis runs locally, so call content is not monitored by external servers. The effect is that the burden of authenticating a call shifts from human judgement to the device itself.

The Sensor Layer Most Users Don’t Think About

Most people think of a phone’s camera and microphone as the main data collectors. The full list is longer. Modern smartphones contain accelerometers, gyroscopes, magnetometers, ambient light sensors, proximity sensors and barometers. Health-focused devices add photoplethysmography (PPG) sensors, optical sensors that measure heart rate by detecting blood flow changes under the skin. Each feeds a constant stream of data into the operating system and the apps running on top of it.

Microphones stay in a low-power listening state to catch wake words for voice assistants. Cameras run background AI processes that detect whether you’re looking at the screen, adjusting brightness accordingly. Location services blend GPS, Wi-Fi and cellular signals to track position continuously. When all of this sensor data is processed together by on-device AI, it produces a detailed picture of habits, movements and daily routine, without any of it necessarily leaving the phone.

Health Data: The Most Sensitive Layer

Samsung is taking a similar on-device approach with health data. A major update to its Samsung Health app, rolling out alongside an upgrade to the Galaxy Watch, introduces a Heart Health Score, Daily Cardio Load and a Fitness Index. These translate biometric readings from PPG sensors, accelerometers and sleep tracking into plain-language health summaries. The appeal is preventative health monitoring without a clinical appointment. The trade-off is that the phone and watch are now continuously processing cardiovascular readings, sleep patterns and activity levels using algorithms that run in the background whether or not the health app is open.

Powerful mobile chips, System-on-Chips, or SoCs, make this possible by handling enough processing locally that sensitive data never needs to leave the device. That changes the privacy calculus compared to cloud-dependent features, but it does not eliminate it. A local vulnerability can still expose locally processed data, and on-device AI can build detailed inferences about behaviour and physiology that users may not realise are being generated.

Fake Call Detection: How the Verification Works

AI voice cloning has reached a point where a convincing imitation of a family member or colleague can be generated from a short audio sample. That makes phone-based social engineering, where a caller manipulates someone into transferring money or revealing personal information, considerably more effective. Fake Call Detection addresses this directly by checking call authenticity before the user picks up, rather than relying on the user to spot the deception mid-conversation.

Because the analysis runs locally, call content is not routed to external servers for assessment. That matters for calls involving financial or personal information. Whether users are comfortable delegating that verification to the device is a separate question. For a closer look at how AI agents can behave unexpectedly when given autonomous access to systems, the Claude Opus 4.5 production database incident is instructive.

Apple’s Reported Approach: On-Device and Gemini

Ahead of its Worldwide Developers Conference, reportedly scheduled for June 8, Apple is expected to position on-device AI processing as a core differentiator, according to reports. The company’s custom silicon is designed to run AI queries locally rather than routing them to cloud servers. Apple is said to frame this as both a privacy measure and a cost advantage.

The most notable reported detail is that iOS 27’s Siri is set to use a distilled version of Google’s Gemini model, optimised to run on Apple hardware. Apple is said to have negotiated terms preventing Siri queries from being used to train Google’s models, with most processing handled on-device or within Apple’s Private Cloud Compute infrastructure. For more complex queries, Apple reportedly uses Nvidia’s confidential computing technology within Google Cloud, encrypting both the data and the model during processing. iOS 27 is also expected to let users auto-delete Siri conversation history after 30 days or a year, or keep it indefinitely. That kind of granular retention control is uncommon in mainstream AI products and is the sort of concrete option users can actually act on.

Regulation: The EU AI Act’s August 2026 Deadline

The EU AI Act’s transparency rules take effect in August 2026. Users must be informed when interacting with an AI system such as a chatbot, and AI-generated content must be clearly labelled. The Act’s primary focus is high-risk AI, but its transparency requirements directly affect smartphone features involving generative capabilities or biometric analysis, which includes the tools Google and Samsung are now rolling out.

On-device processing reduces some risks: data that never leaves the phone cannot be intercepted in transit or exposed in a server breach, but it does not resolve the concern entirely. The June 2026 Android update itself includes a patch for an Android Framework security flaw, a reminder that local processing is not the same as secure processing. The Act’s labelling requirements are expected to push manufacturers toward clearer privacy dashboards, disclosures that explain not just what data is collected, but what the on-device AI is doing with it.

The Trade-Off: Capability Requires Access

The honest version of the pitch for all of these features is straightforward: the more useful the phone becomes, the more it needs to know about you. A Digital Wardrobe that organises your clothes requires AI that has analysed your photos. Fake Call Detection that works in real time requires AI that has assessed your incoming calls. Health monitoring that catches early warning signs requires AI that tracks your body around the clock. None of that is inherently problematic. All of it is worth understanding before you agree to it.

The practical problem is default settings. AI features are typically switched on by default, with privacy controls buried in settings menus that few users navigate unprompted. Apple’s reported option to auto-delete Siri history is a step toward making that control visible, but it still requires users to seek it out. The gap between what the phone is doing and what users understand it to be doing has not narrowed with these updates. The heavier responsibility sits with manufacturers to surface these controls at the point where users actually encounter the features, not three menus deep.

What to Watch Next

On-device model distillation, compressing large AI models to run efficiently on a phone’s chip, will advance further. Apple’s reported use of a distilled Gemini for Siri and Google’s on-device approach for Fake Call Detection both point in the same direction: more capable AI running locally, with less cloud dependency. That requires better AI chips inside phones and more efficient compression techniques, both of which are active development areas across the industry.

The EU AI Act’s August 2026 transparency rules will likely set a template beyond Europe. When manufacturers must label AI interactions clearly for EU users, building a separate, less transparent experience for other markets becomes harder to justify and harder to maintain. Clearer in-app disclosures and more standardised privacy dashboards across Android and iOS globally are a plausible consequence.

Health monitoring will go further. Samsung’s updated Health app, with its Heart Health Score and continuous biometric tracking, points toward a device that acts as a persistent health monitor, flagging changes before symptoms become obvious. That is a genuinely useful application of always-on sensing. It is also a device continuously processing physiological data, which sits in a different category of sensitivity from location history or browsing behaviour.

Cryptographic call verification, the mechanism behind Fake Call Detection, is likely to extend beyond phone calls. The same principle of verifying the authentic origin of a digital interaction could apply to video calls, messages and AI-generated content. As deepfake audio and video improve, the infrastructure for verifying what is real will need to keep pace. Stay up to date with the latest AI developments at Auton AI News.