What’s happened? Google‘s latest Android Canary build (an early pre-release version of an Android update) quietly hints at a smarter Always-on Display for Pixel phones.
- Android Authority spotted code changes with new text referencing a tool called “Turn off display on inactivity.” It also has a summary about saving power when no activity is detected.
- “Doze” appears in the naming, Android’s internal label that also covers ambient display, so this clearly targets AOD.
- You should find the option under Settings > Display > Always-on display if the feature ships in a future update.
This is important because: AOD is handy, but it nibbles at battery all day. Pixels don’t offer schedules or much fine-grained control, so an inactivity cutoff adds a simple way to reduce waste without losing quick-glance info.
- It trims unnecessary screen time when your phone sits on a desk for hours, instead of glowing until Bedtime Mode.
- Pixel’s lack of AOD scheduling makes a single “turn off on inactivity” setting the clean fix, no micromanaging required.
- Samsung already adapts AOD to conditions like face down or in the dark, so this helps Pixel catch up without cluttered menus.
Recommended Videos
Why should I care? Idle drain adds up, so keeping Pixel’s Always-on Display on by default is great for info at a glance, but it shouldn’t keep shining when you’re nowhere near your phone.
- Fewer wasted minutes of screen-on time during idle stretches means lower background battery loss over the day.
- No schedules to build. Leave AOD on and Android quietly turns it off when you’re inactive.
- It pairs with newer touches like AOD wallpapers on Pixel 10, so you keep the look with less battery cost.
Okay, so what’s next? Google is laying the groundwork in Canary. It typically enables user-facing switches in later Canary or Beta builds once the code hardens.
- Watch upcoming releases for a new setting under Settings, Display, Always-on display.
- It could also appear via a server-side flag, so you might see it without a full system update.
- Expect Google to test more features that didn’t make it to Android 16, which might just end up on Android 17.
