Audio and video are out of sync: diagnostic checklist for Google Pixel Device
Audio and video are out of sync on Google Pixel Device: isolate the device, player, network and source with a clear test sequence and support checklist.
What this symptom means on Google Pixel Device
Speech and motion do not align, or the delay grows as playback continues. This runbook applies when you are already using a player or viewing method supported by the actual device. Begin with one reproducible example; the symptom by itself does not prove that a service, application or network is at fault.
Check the Google Pixel Device environment
Check the TV, phone or box input method and the installed player separately. A touch-oriented app can behave differently on a remote-controlled screen.
- Record the exact model, OS build and installed player version before changing settings.
- Use the device’s supported app source and system update process, then inspect free storage.
- Distinguish clearing temporary cache from clearing app data; preserve account and favorite recovery details before a reset.
Identify the full playback chain before testing: device, operating system, player, login format, local connection and destination display or audio route. For an external box, a television may be only the display. In that case, the app version and network measurements belong to the box.
Run a controlled diagnostic sequence
- Compare TV speakers with any wireless audio route.
- Pause and resume once, then note whether the alignment resets.
- Compare a live item with an on-demand item in the same player.
- If a player delay control exists, note its original value before one small test.
Carry out the steps in order while keeping other settings unchanged. Write down the initial result and the result after each change. If a test has no measurable benefit, restore its original setting before continuing. This gives support a history it can interpret and avoids ending with several unexplained adjustments.
Possible explanations to compare
- Wireless audio or receiver processing delay
- Player timing or decoder behaviour
- Source timestamps or a delivery interruption
These are hypotheses to test, not a diagnosis. A problem that follows an account across two otherwise working devices points to a different layer than a problem limited to one app. A failure seen only over one local connection needs a network comparison before an account reset.
What to record for support
| Evidence | Record | Keep private |
|---|---|---|
| Device | Google Pixel Device, exact model and operating system build | Serial numbers and account-linked identifiers |
| Player | Publisher, version and selected login type | Password, full playlist URL or portal token |
| Failure | Audio and video are out of sync, exact message and local timestamp | Customer or payment details |
| Comparison | Which single change improved or reproduced the result | Credentials for the comparison account |
A useful report includes what still works. For example, say whether menus respond, another item plays, or a second connection produces the same result. Avoid a screenshot of the full account page when a cropped error message is enough.
Work through the checklist
The checklist on this page is a temporary working aid. Record your final results in your own notes if you need to keep them or send them to support.
When to stop and escalate
A fixed delay may be manageable with a supported adjustment; a steadily increasing delay needs a different investigation. Include which pattern you observed.
Stop changing settings when you can reproduce the failure and explain the controlled comparison. Send the evidence privately to the relevant app publisher or service operator. If the feature is unsupported on this model, document that finding and use a supported alternative rather than repeating the same reset.
Related Google Pixel Device reference
Read the Google Pixel Device device guide for setup context, and use the community discussion area to share a redacted description of your test.