AI Search
Google is pushing a surprise software update to the first-generation Pixel Watch even though the model has exited its official support window. The release targets the watch’s modem stack and addresses a critical flaw tied to emergency calling, an area where reliability isn’t optional.
The new build focuses on improving E911 emergency dialing behavior on the original Pixel Watch. While Google isn’t detailing the exact failure mode, the description points squarely at the watch’s cellular modem handling of emergency calls and network handshakes. This is a high-stakes corner case: according to the Federal Communications Commission, roughly 80% of 911 calls in the United States originate from wireless devices, and the National Emergency Number Association estimates well over 240 million 911 calls annually. A small reliability gap can translate into many real-world incidents.
Pixel devices have faced isolated emergency-calling issues in the past, some tied to interactions with third-party apps or network routing peculiarities. The decision to deliver a one-off patch beyond the watch’s support horizon suggests the bug could compromise core safeguards like direct emergency dialing from the wrist or handoff to a paired phone when cellular isn’t available.
Google is distributing a single global build labeled BW1A.260305.003 for the first-generation Pixel Watch. The company describes it as a modem update and says it will reach all eligible units in a phased rollout that depends on carrier and device. In practical terms, expect LTE variants to see it first, though Google indicates broad coverage across first-gen configurations.
Importantly, this release does not advance the platform version. The original Pixel Watch remains on Wear OS 5.1, based on Android 15, with no path to Wear OS 6. This is a surgical reliability fix rather than a feature drop or security bundle.
Emergency calling spans hardware, firmware, carrier provisioning, and location technologies such as Advanced Mobile Location and Emergency Location Service. Even a small inconsistency can interrupt call setup, delay location transmission, or mishandle network fallback. By shipping a modem-level patch after the official window ended, Google is signaling that life-safety functions sit outside routine support timing—a stance consumers and regulators will welcome.
Other ecosystem players occasionally do the same. Apple and Samsung have both deployed limited patches to older watches for critical reliability or security issues after major updates stopped. These exceptions are rare, but they build trust—especially as more wearables add fall detection, crash detection, and SOS features that users rely on in high-pressure moments.
To look for the update on a first-gen Pixel Watch, open Settings on the watch, tap System, then System updates, and follow the prompts when it appears. Keep the watch on its charger, ensure a stable connection to Wi-Fi or LTE, and leave Bluetooth enabled if it’s paired to a phone. Because this is a staged rollout, it may take time to show up depending on carrier configuration.
If you own the LTE model, confirm that your carrier plan is active after installing the update and place a standard test call to verify connectivity. Avoid placing test calls to emergency services; if you must validate emergency dialing, consult your local non-emergency line for guidance first.
A first-gen Pixel Watch getting a fresh build after its support period ended is unusual—and telling. Google is prioritizing a critical path where there’s zero room for failure, and doing so without moving the watch to a new OS version. For owners who still rely on the original model, this quiet modem update could be the most important one they install.
