Model facts that change the troubleshooting path
Google lists a 6.3-inch 1080×2424 pOLED display with a 60–120 Hz Smooth Display range.
Google specifies a typical 5100 mAh battery and fast charging to about 50% in roughly 30 minutes with a compatible 45W USB-C PPS charger or higher under its test conditions.
Test matrix
What to test and what a pass actually tells you
Run the test closest to the symptom. A passing result narrows the diagnosis; it does not certify the entire device.
Use the result to narrow the next branch; browser visibility is intentionally limited to the subsystem exposed by the current API.
→Use the result to narrow the next branch; browser visibility is intentionally limited to the subsystem exposed by the current API.
→Use the result as a visual/timing reference. It cannot certify panel electronics or cable signal integrity by itself.
→Use the result as a visual/timing reference. It cannot certify panel electronics or cable signal integrity by itself.
→A pass proves this browser received live camera frames; app selection, permissions or capture mode become more important if one app still fails.
→A pass proves the selected input delivered audio into this browser session; app routing or processing becomes the next branch.
→A pass proves browser playback reaches the selected output path; it does not prove every codec, surround or app-specific route.
→Use the result to narrow the next branch; browser visibility is intentionally limited to the subsystem exposed by the current API.
→Diagnostic focus
Problems worth separating on this model
Model-specific problems
Start with the symptom people actually search for
These paths combine this model's documented limits with live evidence, instead of copying a generic troubleshooting checklist.
Exact specifications
Compatibility questions tied to this model
Evidence handoff
If the browser cannot reach the suspected subsystem
Keep the browser result as one observation, then move to the operating system or manufacturer diagnostic that can see the protected hardware state. Do not interpret an unsupported browser API as a failed component.
For model-specific firmware, drivers or service diagnostics, use the official Google Pixel source linked on this page.