Gemini on Wear OS: Pixel Watch 5 Offline Limits and Watch Actions
See which Gemini watch actions depend on your phone, how Pixel Watch 4 and 5 controls differ, and what Pixel Watch 5 can do offline.
- Gemini is available on eligible Wear OS 4 or newer watches paired with an Android phone that uses Gemini as its digital assistant; language, region, account, and app setup still matter.
- Raise to talk is documented for Pixel Watch 4 and 5, while limited offline Gemini actions require Pixel Watch 5 and Gemini on Wear OS 1.36 or later.
- Wear OS 7 platform improvements do not make later Gemini Intelligence or early-access AppFunctions available on every watch.
- A watch result is not proof of a completed phone action. For a supported FoneClaw task, open FoneClaw on the phone and start a separate, reviewable request.
What Gemini Can Do From Your Watch
Gemini can handle selected voice requests on an eligible Wear OS watch, including quick questions and supported app actions. The important distinction is where the result comes from. A timer can be a watch action; a request involving messages, an account, or another app may depend on the paired Android phone, a connected service, permissions, and network access. An answer on the watch does not, by itself, prove that an action happened on the phone.
| What you want | Where to check the result | Key limit |
|---|---|---|
| Set a timer or alarm | Watch timer or alarm screen | Offline Gemini support is model-specific. |
| Control media or use a connected app | Watch and the device or app being controlled | The target app and connection must support the action. |
| Send or change something on the phone | Paired phone and target app | Watch invocation is not general phone authority. |
Choose a small, observable request first. Check that Gemini opens, then confirm the timer, playback state, or app result where it should appear. For a wider device-by-device view, Gemini Intelligence Supported Devices: Phones, App, Chrome, Wear OS, and FoneClaw covers eligibility beyond this watch workflow.
Check Compatibility and Start Gemini
Google's Gemini smartwatch guidance describes support for eligible Wear OS 4 or newer watches paired with an Android phone. Gemini must be the phone's default digital assistant, and availability depends on language, region, and rollout. On Pixel Watch, Google's watch setup guidance also specifies a personal Google account, the Gemini assistant app on the phone, and updated watch apps. Check those requirements on the exact watch and account before troubleshooting an individual command.
Start with the watch's supported button or on-screen assistant entry point. If you use “Hey Google,” wake the watch first. Raise to talk is documented for Pixel Watch 4 and Pixel Watch 5; it is not a gesture to assume on every Wear OS model. Button assignments and settings can differ by manufacturer, so use the controls shown on your watch rather than looking for a universal menu path.
Once Gemini launches, ask a simple question before trying a connected-app action. If the assistant responds but the action does not happen, check that app's settings, account, permissions, and phone connection separately. The phone may supply the missing state even when the request began on your wrist. For more detail on the paired phone's voice controls, see Gemini Voice Control on Android: Actions, Fixes, Live Help, and Phone-Agent Limits.
What Pixel Watch 5 Can Do Offline
Offline Gemini is narrower than general watch support. Google documents it for Pixel Watch 5 with Gemini on Wear OS 1.36 or later, not for Pixel Watch 4 or all Wear OS 7 watches. The documented basic actions include setting a timer or alarm, using Water Lock or Wi-Fi controls, opening an app, starting a workout, and controlling music. A supported gesture on Pixel Watch 4 does not imply the same offline capability.
To check an offline action without relying on a spoken answer alone, enable Airplane mode on Pixel Watch 5, then make sure Wi-Fi and Bluetooth are off. Ask for a low-risk timer and inspect the timer screen. Restore your normal connections afterward. If the action fails, check the watch model and Gemini app version before concluding that every watch feature is unavailable offline.
Opening Maps while disconnected is not proof that navigation works offline. Likewise, an offline timer does not establish offline cloud research, connected-app work, or phone execution. Test the specific action you need and look for its actual result.
Separate Wear OS 7 From Later AI Features
Wear OS 7 and Gemini Intelligence are related but not interchangeable. The Android Developers overview of Wear OS 7 describes platform changes including Live Updates and enhanced media controls. It describes Gemini Intelligence for select devices later and AppFunctions as an early-access developer path. Neither statement makes multi-step AI automation a current feature on every Wear OS 7 watch.
When a feature is described as planned or limited to select devices, check its current status for your watch rather than treating the operating-system number as proof. The practical question remains specific: can this model, account, app, and paired phone perform this action now, and where is the result visible?
Fix a Missing or Failed Watch Action
Work from the first point that fails instead of repeating a broad request. A missing assistant, a gesture that does nothing, and an app action that never completes have different causes.
| What you see | What to check | Next step |
|---|---|---|
| Gemini does not appear | Watch eligibility, phone pairing, default assistant, account, language, region, and app updates | Launch it through the watch's available control, then try a basic question. |
| “Hey Google” or raise to talk does nothing | Whether the watch is awake and whether that model supports the gesture | Try the button or screen entry point; check gesture settings on Pixel Watch 4 or 5. |
| An offline request fails | Pixel Watch 5 model, Gemini on Wear OS version, and whether the requested action is on the limited offline list | Try a timer and inspect its screen before testing another action. |
| Gemini responds but a connected app does not act | Phone connection, target-app setup, account, and permissions | Open the target app or phone to confirm its state before retrying. |
For a message or other consequential request, inspect the target app before trying again. A response that sounds successful is not a substitute for a visible result, and an uncertain state is a reason to pause rather than risk repeating the action.
Continue a Larger Task on Your Phone
The watch suits a brief request or glanceable result. Move to the Android phone when you need to inspect a recipient, review a longer message, resolve an ambiguous date, or see an app's permission and result screens. If you want FoneClaw to handle a supported SMS, calendar, memo, or device task, open FoneClaw on the phone and start that task separately. There is no verified native FoneClaw Wear OS app or Gemini-watch-to-FoneClaw handoff.
Our FoneClaw Features page describes supported Android actions. FoneClaw uses a configured model for reasoning and governed phone tools for execution; actual permissions and the configured approval policy still apply. A compatible online model may receive context supplied for the task. Check the phone's visible result rather than assuming a watch request or model reply completed it.
For example, an SMS request in FoneClaw requires approval before the visible draft. Pure-text sending can complete automatically only when accessibility is connected and the default messaging app shows a verified recipient, complete body, and one stable Send control. If those conditions are not met, including an ambiguous dual-SIM or attachment flow, finish manually on the phone. Do not tap again after a result reports the message as sent. For the broader distinction between intent and confirmed Android execution, see AI Agent Phone Control on Android: Intent, Confirmation, Action.