DeviceOK
SearchCheck my device
Home / Platforms / Android
Android

Use the browser test to identify the right troubleshooting layer.

Android can block camera or microphone at the device privacy-control level, the browser-app permission level, and the website permission level. Browser-visible tests are useful for media, touch and some sensors, while protected phone hardware needs OEM diagnostics.

High-signal checks

What to establish first

  1. 1

    Check Android Privacy controls if camera/microphone access is globally disabled.

  2. 2

    Check the browser app's Camera/Microphone permission and the DeviceOK site permission.

  3. 3

    Use the phone maker's native diagnostics for charging, NFC, SIM, battery and other protected hardware.

Live tests

Useful browser evidence on Android

Touchscreen TestDraw on the screen to verify touch/pointer coverage.
→
Webcam TestOpen your webcam locally to verify that the browser can access and display a live camera stream.
→
Microphone TestCheck whether your browser can detect your microphone and receive live audio.
→
Device Orientation TestWatch browser-exposed orientation angles change as you rotate a supported phone, tablet, or laptop sensor device.
→
Device Motion Sensor TestDisplay browser-exposed acceleration values while moving a supported device.
→
Browser boundary

What not to infer

  • A browser cannot test every phone sensor or charging subsystem.
  • Native app permissions and browser site permissions are separate layers.
  • Browser API support varies by Android browser and device.