Device help
Start with the device you actually have.
Choose a device family to see what DeviceOK can test directly, what requires an operating-system or manufacturer diagnostic, and which checks give the highest-signal evidence first.
81 matching device types
Computers & mobile
Computers & mobile
PhoneRun browser-safe camera, microphone, speaker, touch, display and motion checks, then use the phone maker's native diagnostics for charging, battery, cellular, NFC, biometrics and other protected hardware.→TabletUse touch, display, camera, microphone, speaker and orientation checks before escalating to the tablet maker's native diagnostics.→LaptopRun a browser-first inspection of screen, keyboard, pointer, camera, microphone and speakers, then use the manufacturer diagnostic for battery, ports, storage and internal hardware.→Desktop PCCheck browser-visible peripherals, display, audio, cameras and game controllers while keeping motherboard, RAM, storage and temperature diagnostics in the correct native-tool layer.→SmartwatchUse phone/browser-side connection and sensor context where possible, then use the watch maker's own diagnostics for battery, health sensors, charging and protected hardware.→E-readerUse screen, touch, charging and browser/network checks where available, then rely on the device maker for storage, battery-health and firmware diagnostics.→Smart GlassesCheck companion-device audio, microphone, Bluetooth and browser-facing components while camera, display and sensor diagnostics remain manufacturer-specific.→
Audio, video & creator
Audio, video & creator
USB MicrophoneDiagnose detection, input level, mute, USB connection, permissions and app routing before treating the microphone as failed.→WebcamTest video capture, resolution, frame-rate settings and permission before changing camera drivers or replacing the webcam.→HeadsetCheck the headphone channels and microphone as two separate paths so one working half does not hide a failure in the other.→USB Audio InterfaceUse microphone and speaker tests to prove the browser-level input/output path, then investigate interface routing, gain, monitoring and official driver/software settings.→Video Capture CardTest whether the capture card appears as a browser-visible camera/video device before changing OBS, streaming or USB configuration.→Wireless EarbudsTest left/right audio and microphones after OS Bluetooth pairing to distinguish channel/output/input problems from app routing.→ProjectorUse display reference patterns and source-device checks to separate image/source/scaling problems from projector optics or hardware that require native controls/service.→Digital CameraUse DeviceOK for webcam/USB/storage-adjacent checks when the camera exposes them, then continue with the camera maker's own diagnostics and media-card guidance.→Action CameraCheck webcam-mode output, storage planning and connection symptoms while battery, overheating and waterproof hardware diagnostics stay with the manufacturer.→Conference SpeakerphoneTest its microphone and speaker paths independently before changing meeting-app selection, echo cancellation or USB/Bluetooth configuration.→Bluetooth SpeakerTest browser audio and Bluetooth-adjacent symptoms while keeping battery, codec negotiation and internal amplifier diagnostics within device and OS tools.→Soundbar / TV Audio SystemUse controlled audio and channel references on the source device and then isolate HDMI, eARC, optical or Bluetooth settings before replacing hardware.→AV ReceiverUse source audio and network tests to narrow input and routing symptoms while speaker calibration, HDMI handshakes and amplifier protection remain receiver-specific.→Portable Audio RecorderUse storage, runtime and microphone reference tools around a recorder workflow while preamp, media and firmware diagnostics stay model-specific.→Document CameraTreat a document camera as a webcam path first: verify browser video, active resolution and frame stability before changing presentation software.→USB Video Capture AdapterVerify whether the adapter exposes a browser camera stream, then test active resolution and FPS before changing source or capture software.→
Input & gaming
Input & gaming
Gaming KeyboardCheck keys, rollover, ghosting, chatter and browser input before changing game binds, keyboard profiles or firmware.→Gaming MouseCheck buttons, double-click behavior, scrolling, movement and browser polling estimates before changing game or vendor software.→Game ControllerInspect buttons, sticks, triggers, center offset, drift and dead-zone behavior using the browser Gamepad API where available.→Racing Wheel & PedalsUse gamepad/HID input to check browser-visible axes and buttons before changing simulator mappings or manufacturer calibration.→Flight Stick & HOTASVerify axes, buttons, hats and browser-visible HID/gamepad input before changing simulator profiles.→Drawing Tablet / Pen TabletTest pointer/pen events where browsers expose them, then use the tablet maker's official driver utility for pressure curves, mappings and calibration.→Stylus / Digital PenSeparate touch/pointer recognition from app-specific pressure, hover, shortcut and palm-rejection behavior.→VR / XR HeadsetBrowser XR support is specialized; DeviceOK focuses on controller/input/display prerequisites and honest capability detection rather than pretending every headset exposes diagnostics to the web.→Game ConsoleUse controller, display, audio and network checks around the console setup while leaving console-internal storage, thermal and firmware diagnostics to the platform vendor.→TrackballTest buttons, pointer movement and scrolling separately to distinguish sensor/ball contamination, switches, connection and software settings.→Laptop TouchpadUse pointer/click/drag evidence to separate touchpad hardware from gesture settings, palm rejection, app behavior and OS configuration.→
Printing & scanning
Printing & scanning
PrinterPrint controlled DeviceOK references to separate document-specific problems from repeatable color, alignment, banding, smearing or scaling defects.→Thermal / Label PrinterCheck 4×6 scaling, clipping, barcode sharpness, small text and margins before wasting real shipping labels.→ScannerUse camera/file/browser checks around the workflow, then rely on OS and manufacturer diagnostics for the scanner transport and imaging hardware.→Barcode ScannerMany scanners behave as keyboards or HID devices; test the actual input mode before changing POS or inventory software.→POS Terminal & PeripheralsTest keyboard-like scanners, compatible HID devices, receipt/label output and browser connectivity before changing POS software or replacing peripherals.→
USB, storage & accessories
USB, storage & accessories
USB DeviceUse standard browser tests first; WebUSB is only for compatible devices that the browser is allowed to access directly.→USB Hub / DockDiagnose a hub or dock by testing the downstream device paths individually and separating power, cable, port and display/network functions.→USB-C / Thunderbolt ConnectionSeparate connector/cable/power/display/data problems by testing the function you expect rather than assuming every USB-C port/cable supports the same features.→External SSD / Hard DriveDeviceOK can diagnose browser/file workflow symptoms, but a browser cannot read generic SMART health or scan disk sectors without explicit file/device access.→USB Flash DriveSeparate connection and OS recognition problems from browser upload/file-selection problems without pretending the browser can scan the flash memory itself.→SD / microSD CardUse OS/card-reader recognition first; DeviceOK focuses on safe troubleshooting boundaries because browsers cannot generically inspect card health.→USB-C CableCheck entered power rating and transfer-rate implications while keeping e-marker, Alt Mode, USB generation and protocol support tied to the actual cable specification.→KVM SwitchCheck keyboard, mouse and display behavior on each computer to separate the KVM path from the attached peripherals themselves.→USB Peripheral SwitchUse keyboard, mouse and HID checks after switching to determine whether a peripheral reached the selected host before debugging vendor software.→
Network & smart home
Network & smart home
Bluetooth DeviceUse normal OS pairing for headsets, keyboards, mice and controllers; use Web Bluetooth only for compatible BLE/GATT hardware.→Wi-Fi AdapterUse browser connectivity evidence plus OS adapter state to separate a web/app problem from a Wi-Fi adapter or network problem.→Ethernet AdapterUse network connectivity and HTTP round-trip evidence after confirming the operating system sees a wired link.→Wi-Fi RouterUse endpoint connectivity evidence to separate a single-device browser problem from a wider Wi-Fi/router outage before resetting or replacing network equipment.→Smart TVUse visual screen/audio references and connection isolation to troubleshoot a TV without treating browser tests as a substitute for panel, HDMI or service diagnostics.→Streaming DeviceSeparate network, TV/input and app-specific symptoms for streaming sticks/boxes before factory resetting or replacing the device.→Smart SpeakerSeparate local network, Bluetooth/audio-source and account/app problems before treating a smart speaker as failed.→Smart Home HubNarrow whether a smart-home failure belongs to the hub, local network, cloud service, radio protocol, device pairing or automation before mass-resetting devices.→Security CameraSeparate camera power/network/app/account problems from actual image-sensor failure; browser webcam tests apply only when the camera exposes a normal browser media path.→Mesh Wi-Fi SystemSeparate internet-service problems from node placement, backhaul, roaming and client-device issues before resetting the whole mesh.→Cable / Fiber Modem & ONTUse browser network evidence to determine whether the problem is local to one device or more consistent with the gateway, modem, ONT or ISP path.→NAS / Network StorageNarrow browser and network-access problems before changing disks, RAID configuration or storage firmware.→Robot VacuumNarrow app, network and charging symptoms while using the manufacturer's diagnostics for wheels, brushes, lidar/camera and internal sensors.→Smart ThermostatSeparate browser, account and network symptoms from HVAC wiring and control-system faults that require model-specific or professional diagnosis.→Video DoorbellUse network and camera-adjacent diagnostics around viewing and calls while model-specific power, chime and event-detection tests stay with the manufacturer.→Smart ApplianceSeparate app, Wi-Fi and account problems from appliance hardware faults and error codes that need the exact manufacturer/model service path.→Ethernet Network SwitchUse endpoint connectivity and timing tests to identify whether failures are device-specific or affect multiple ports before changing switch configuration.→Wi-Fi Access PointCompare browser connectivity from different clients and locations before changing channels, transmit power or enterprise authentication settings.→Baby Monitor / Indoor CameraUse network and viewer-device camera/audio checks around the monitoring workflow while camera hardware and cloud connectivity remain vendor-specific.→
Power & charging
Power & charging
USB-C ChargerUse manual power/profile calculations and device symptoms to check whether a charger is plausibly sized before verifying USB PD/PPS and manufacturer-specific fast-charge requirements.→Laptop ChargerCheck the basic power-rating relationship, connector/cable path and charging symptom before treating a laptop battery or charging port as failed.→Power BankEstimate runtime/energy and check USB power ratings while keeping battery-cell health, charge-controller safety and real protocol negotiation outside browser claims.→Portable Power StationEstimate backup runtime for entered loads and compare charger/output ratings without pretending nominal battery capacity equals delivered AC energy.→UPS / Battery BackupEstimate runtime from entered energy and load, then use the UPS maker's software for battery health, self-tests and protected electrical measurements.→Wireless ChargerCheck power-source assumptions and device symptoms before treating slow or intermittent wireless charging as a failed phone or charger.→Power Tool Battery & ChargerUse manual energy and runtime calculations plus manufacturer charge indicators while avoiding unsafe claims about cell health or charger electronics.→
Maker, vehicle & specialist
Maker, vehicle & specialist
MIDI Keyboard / ControllerProve note, velocity, pedal, knob and fader messages before changing DAW routing or controller mappings.→3D Printer / Serial DeviceUse Web Serial with supported USB/serial controllers only for safe connectivity checks; printer control protocols remain model/firmware specific.→Camera DroneUse storage, charging and controller checks around the drone workflow, while flight-control, battery-cell and sensor calibration remain native/OEM tasks.→Dash CamPlan storage and transfer time, check webcam mode where supported, and use the manufacturer for GPS, parking mode, battery or capacitor and firmware diagnostics.→OBD-II AdapterCheck Bluetooth, USB or serial connection capability where the adapter exposes it, while vehicle diagnostics and code interpretation must use reliable automotive procedures.→HDMI Switch / Capture PathUse display, camera/capture and raw-bandwidth planning tools to narrow source, cable, switch and capture-device failures.→
Other devices