About Controller Overclocking
How to use this validator
- Ensure your DualSense is connected via Bluetooth.
- Press any button to wake the Gamepad API.
- Move the analog sticks in rapid, continuous circles.
- Watch the telemetry graph stabilize to see your browser-observed update timing.
What to expect over Bluetooth
Bluetooth transport is subject to the HID-over-GATT connection interval, so the browser will observe a far lower report ceiling than wired no matter the firmware — this validator still detects overclocking claims that exceed what Bluetooth can physically deliver. Wireless report timing varies with radio interference and connection interval; expect a wider, noisier band on the graph than the same pad over USB.
The DualSense reports on a 1000 Hz-capable interface over USB in ideal conditions, but your browser's gamepad polling and OS scheduling decide what you actually see. A clean wired graph near 1000 Hz with low jitter is the healthy signature.
The DualSense runs the community hidusbf patching path well, and its native report rate is genuinely higher than older pads — so a 1000 Hz reading over USB is realistic, not a fantasy. The nuance is that PlayStation's own firmware updates have changed HID behavior several times: a pad updated to a recent firmware can present slightly different polling characteristics than the same pad on an older one. If your graph caps well below 1000 Hz after patching, re-check the USB descriptor with the pad freshly rebooted and on a direct port — hubs and extension cables are the usual culprits that quietly reset the negotiated interval.
Patching a DualSense is newer territory than the DS4 because the pad ships with a modern report rate already; the value of the community tooling is mostly in stabilizing the negotiated interval rather than unlocking a hidden ceiling. The DualSense also needs the adaptive-trigger and touchpad features left idle during measurement — if the haptics motor is mid-rumble when you sample, the reported frame timing can shift because the pad shares its USB bandwidth between the motors and the input reports. Measure with haptics disabled, keep the pad on a direct USB-C port, and reboot the pad between the patch and the verification run so the descriptor reloads cleanly.
On Bluetooth, the connection interval is negotiated between the pad and the host adapter, and it is the single biggest factor in the Hz you will measure. A controller connected through a built-in laptop radio at a crowded connection interval can report half the rate of the same pad on a dedicated adapter with a shorter interval. So a low Bluetooth number is not proof an overclock failed — it may simply be the radio negotiation. Match the adapter, move the dongle closer, and clear other Bluetooth devices from the connection before judging the result.
Is 1000Hz (1ms) always better?
Not necessarily. While 1000Hz reduces average input latency by a few milliseconds compared to 250Hz, it demands more CPU cycles. The key metric is stability (Jitter). An overclock that results in severe frame pacing spikes can feel worse than a rock-solid lower polling rate.
Does hidusbf work on Bluetooth?
No, the popular LordOfMice hidusbf utility only overrides USB device descriptor limits. Overclocking Bluetooth requires changing the polling interval in your OS Bluetooth stack or using custom dongles.