Use case · Support
Turn “it does not work” into one failing layer.
A clean diagnostic flow checks hardware access first, then browser permissions, then the destination app.
01 / FIELD NOTE
A repeatable isolation workflow
- Reproduce the issue in the smallest matching Device-Test module
- Confirm the browser sees the correct device and permission state
- Try a second supported browser to separate browser configuration from hardware
- Close apps that may hold exclusive access and test again
- If the isolated test passes, inspect the original app’s selected device and policy settings
02 / FIELD NOTE
Useful evidence for support tickets
Record the browser and operating-system version, the exact test page, permission state, selected device name, and whether the same test passes in another browser. Avoid sending camera frames, microphone recordings, location coordinates, or other sensitive output unless support explicitly needs it.
03 / FIELD NOTE
Know when to escalate
If a device fails across browsers and native operating-system tools, update drivers or firmware and contact the device manufacturer. Physical damage, intermittent power, and USB hub faults cannot be repaired by a web test.
FAQ / DIRECT ANSWERS
Frequently asked questions
Can Device-Test repair a device?+
No. It helps isolate symptoms; it does not change drivers, firmware, operating-system settings, or hardware.
Why does a device work here but not in another app?+
The other app may have a different selected device, permission, account policy, audio processing path, or exclusive-access conflict.
NO SIGN-UP · NO INSTALL · FREE WEB TESTS