Product1 publisher2 min readPublished
Google pauses the Home widget's polling when the phone screen is locked
Google shipped fifteen separate fixes to the Home app and Gemini for Home on September 16, ten of them in the app itself. The most consequential pauses the widget's polling while the phone screen is locked, where no user will ever see it happen.
The Product Desk · Product desk
What happened
- Device tiles for sensors, cameras and smoke and carbon monoxide detectors no longer appear grayed out after a user returns from device controller screens, so the screen does not have to be reloaded.
- Google says it eliminated stalls during Wi-Fi pairing when adding new smart devices, and made multi-account switching more reliable after "Home not found" errors and preference resets.
- Three camera fixes cover Android live-stream tiles turning black after full-screen view, Android timeline scrolling freezing across recording gaps, and an iOS Live button that left playback paused.
- Five Gemini for Home changes dated September 16, 2026 address unnecessary follow-up questions, broadcast errors, Live Mode self-interruptions, playlist identification and TV streaming on smart displays.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- cost Households running the widget were spending phone and camera battery on refreshes taken while the screen was locked. That cost arrived as more charging, and no user would file it as an app bug.
- constraint An agent can only act on devices that finished joining the network, so a pairing stall caps what any of Home's newer automation can reach in that house, whatever the feature list says.
- exposure Smoke and carbon monoxide detectors were among the tiles that went gray. A household looking at a stale gray tile cannot tell a cleared alarm from a rendering fault.
- precedent Itemising fifteen repairs at this granularity sets the expectation that the next Home release note will be equally specific. Skipping a known bug next time becomes conspicuous.
A battery doorbell does not know why it is being asked for a frame. It answers. Google's release notes say the Home widget now pauses background updates and polling "whenever your phone's screen is powered off, locked, or running a screensaver" [1], and that the change saves battery on the phone and on connected cameras [2]. Turn that sentence around and it describes the old behaviour: the widget kept polling while the phone lay face-down on the counter.
People unlock the phone, look at one tile, and put the phone away. Google's fix matches that, with widgets that now "refresh immediately the moment you unlock your phone" [2]. A team tells itself something else: a widget is a live surface, a live surface has to be current, so it polls on a timer whether or not anyone is looking.
Fifteen items are enumerated in the release, ten in the app and five in Gemini for Home [14]. Sensor and camera tiles could "appear grayed out after returning from device controller screens" and now do not [3]. Stalls during Wi-Fi pairing were eliminated [5]. A startup crash on Google TV devices was resolved [6]. The same day, Google began rolling out Home MCP [13].
Sort the fifteen by what each bug does to a person. Some block the task outright: the pairing stall stops a device from joining at all [5], and the Google TV crash stops the app from opening on the television [6]. Some are recoverable irritations, like the gray tile that a reload cleared [3] or the Android live-stream tile that went black until someone scrolled it [9]. The polling loop was invisible to the user and billed to something else [1].
I would fund the blockers and the invisible drain ahead of the irritations, and the tradeoff is that the irritations are most of what a support queue contains, so the queue reads worse for a while before anything else improves. A household that abandons Wi-Fi pairing never appears in a usage chart, because it never became usage. A camera that dies at noon gets logged as a hardware defect. No count of affected homes appears in the release notes [15], so the ordering argument rests on where the bug sits in a person's day.
The item worth copying verbatim: smoke and carbon monoxide alarm notifications now show current device status in the app after an alarm has already been cleared [8].
What to watch
- Whether owners of battery cameras report longer runtimes after the widget change, since Google did not quantify the saving.
- Whether the next Home MCP change ships with per-item release notes, or only the app does.
- Whether setup stalls reappear as new device categories are added to the onboarding flow.