Google Clock Live Updates Bring Timers to Lock Screen and AOD

Google Clock v9.0 is rolling out support for Google Clock Live Updates, surfacing active timers and stopwatches in the status bar, on the lock screen, and on the always-on display, Android Authority reported today. The update also fixes a specific bug: timers shown on the always-on display previously appeared frozen mid-count even while running in the background. Both changes arrive together.

One thing to know before updating: the rollout is server-side, meaning installing v9.0 does not guarantee the feature activates on your device. Google has not published a timeline for when it reaches full availability, Android Authority noted today. So if the feature does not appear after updating, that may reflect distribution pace rather than a compatibility problem with your device.

How Google Clock Live Updates work across the status bar, lock screen, and always-on display

Once a timer or stopwatch is running in Google Clock v9.0, leaving the app no longer hides it. A highlighted icon appears in the status bar as a compact chip, capable of showing either an icon, up to seven characters of text, or a specific time value, according to Google's documentation cited about a year ago. Tapping that chip opens an expanded view with playback controls, including pause, resume, and stop, without returning to the app, Android Authority reported today.

The same Live Update carries through to the lock screen and always-on display. The timer follows the user rather than sitting idle inside the app.

The AOD fix is the most concrete change here. Previously, a timer displayed on the always-on display showed a static number: the clock icon was present, the time was visible, but the count did not move. The timer ran fine in the background; the display just never reflected it, Android Authority confirmed today. That disconnect is now resolved, with the always-on display updating in real time.

For anyone timing a workout interval or monitoring something from across a room, that distinction is the whole point. A frozen display is worse than no display, since it suggests nothing is changing when time is actively running out.

Google also notes that if a user swipes away a Live Update, the app should recognize that and not resurface it, 9to5Google reported about a year ago. That design principle matters for Clock specifically: a dismissed timer Live Update should not keep reappearing uninvited.

Why timers fit the Live Updates model and where Android 17 comes in

Google's guidelines for Live Updates are specific about what qualifies. The feature is reserved for activities that are ongoing, user-initiated, and time-sensitive. Equally important is the exclusion list: ads, promotions, chat messages, alerts, upcoming calendar events, and ambient background information are all prohibited, 9to5Google reported citing Google's documentation about a year ago.

A running countdown satisfies all three required criteria and violates none of the prohibitions. The user started it. It is actively changing. The outcome matters within a defined window.

Google's guidance also describes the right escalation model: a notification should become a Live Update only when the user has a pressing need, then step back down when that need passes. The flight boarding pass example Google uses is instructive show a normal notification hours before departure, escalate to a Live Update only when boarding begins, 9to5Google reported about a year ago. Clock's behavior appears to follow this same logic: start a timer, it surfaces as a Live Update; the timer resolves, the update clears.

Android 17 formalized this pattern at the API level with the MetricStyle notification template, built specifically for timers, health and fitness apps, and travel use cases. The template supports up to three simultaneous data points displayed across the always-on display, lock screen, and status bar, with format adjusting dynamically based on device state, Android Authority reported about two months ago. Android's official developer documentation uses a clock app as the primary reference example for MetricStyle implementation, Android Developers noted about four months ago.

One caveat: available reporting does not confirm whether Google Clock v9.0 wires into the MetricStyle template specifically or uses an earlier Live Updates layer. The platform supports this pattern at the API level and a clock app is the documented reference, but whether the shipped app uses MetricStyle precisely has not been verified by current reporting.

Who gets the Google Clock v9.0 update, and when

This is where the rollout gets complicated.

Live Updates support ships with Google Clock v9.0, available now on the Play Store. But the rollout is also server-side, which means Google enables the feature per device independently of the installed app version, Android Authority confirmed today. A user can update today, start a timer, and see no Live Update appear. Google has not published a timeline for when the server-side switch reaches all eligible devices.

On platform compatibility, Android Authority confirmed the feature working on a test device running Android 17 QPR2 Beta 1, and expects it to function on stable Android 17 as well, Android Authority reported today. That is the only confirmed test environment. Available reporting has not confirmed a minimum Android version requirement, and whether the feature functions on non-Pixel Android 17 devices, manufacturer-skinned interfaces, or Android 16 builds remains unestablished.

Android 16 is relevant context here. That release launched the initial Live Updates framework but did not make the feature fully available in its stable release, 9to5Google reported about a year ago. The platform infrastructure arrived first; application support is catching up now.

What's confirmed, what isn't, and what to do:

• Confirmed: Live Updates work in Google Clock v9.0 on Android 17 QPR2 Beta 1
• Expected but unconfirmed: Stable Android 17 support
• Unconfirmed: Support on Android 16, non-Pixel devices, or OEM skins
• Not established: Minimum Android version requirement
• No timeline: Google has not indicated when server-side rollout reaches all eligible users

The practical takeaway: update to v9.0, and if you are on Android 17, the feature could appear at any point. If it does not show up immediately, that reflects the server-side distribution model. For users on older Android versions or manufacturer interfaces, the picture is less clear, and no reporting currently settles it.

What this signals for Live Updates on Android

Google Clock is not a third-party experiment. It is a first-party Google app shipping the feature on Android's own platform, which makes its behavior a reference point for what Live Updates are supposed to look like in practice.

Google's Live Updates documentation uses a clock app as the MetricStyle example, Android Developers noted about four months ago. The production implementation in Google Clock v9.0, arriving today, is the tangible version of that. Developers building timer, fitness, or interval-tracking apps now have a live, shipping example of how the feature behaves across the status bar, lock screen, and AOD not just documentation describing it.

Two things worth watching as this matures: whether the server-side rollout model gives way to something more predictable, and whether available reporting eventually clarifies Android version requirements and OEM support. The feature works. The gap between "it works" and "it works for everyone" is a distribution problem, and Google has not yet said how long that gap will last.