What to know
- SystemUIGoogle is building a USB authorization dialog that explicitly names connected devices by type and requires a 60-second sign-in to fully trust them.
- Advanced Protection currently blocks new USB data connections while a phone is locked; this code introduces a specific time window and granular device identification to the trust flow.
- The strings were found in SystemUIGoogle on Android 17 QPR2 Beta 6 (CP41.260831.007) and are not yet available to users.
Google’s Advanced Protection Program already includes a safeguard that blocks new USB data connections whenever a Pixel phone is locked. This prevents malicious peripherals from attempting data extraction via physical access. Now, a teardown of the latest SystemUIGoogle beta shows Google refining how you interact with and ultimately trust those peripherals.
Now, a teardown of SystemUIGoogle in Android 17 QPR2 Beta 6 (CP41.260831.007) reveals new code that names connected USB devices by their specific class and introduces a 60-second sign-in window to establish full trust.
Granular device identification
When a new USB device is plugged in, the system currently relies on generic identification. The new code points to a much more descriptive approach. SystemUIGoogle now includes a comprehensive list of strings that map USB interface classes to human-readable names. Instead of a generic prompt, the authorization dialog will be able to tell you exactly what kind of hardware you are connecting—whether that is a keyboard, a webcam, mass storage, or a printer.
The new strings, seen below, point to this granular naming convention:
The 60-second trust window
Beyond just naming the hardware, the teardown reveals a new temporal requirement for trusting peripherals. Code in SystemUIGoogle references a strict 60-second countdown. Once you tap “allow” on the authorization dialog for a new USB device, you must sign in to your phone within one minute to fully trust that hardware.
If the sign-in is not completed within that 60-second window, the trust process fails. The strings indicate that users will be instructed to physically disconnect and reconnect the devices to try again. This applies to both single-device and multi-device connections.
The strings that outline this new trust flow are:
This per-device-type naming and 60-second sign-in trust window is not yet available to users. We will watch future builds to see if this authorization flow rolls out to Advanced Protection users.
Leave a Reply