About Controller Overclocking
How to use this validator
- Ensure your DualShock 4 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 DualShock 4 is the classic overclock target because its stock wired report rate sits well below the pad's own capability. A flat, consistent interval in this validator is a stronger signal than the headline Hz number alone.
The DualShock 4 is the most documented overclock target in the space because its stock 1000 Hz-capable hardware ships configured well below that ceiling, and the hidusbf descriptor patch has been stable on it for years. Over USB you should see a flat interval very close to 1000 Hz after patching; Bluetooth is a different story — the DS4's wireless report rate is far lower and no descriptor hack changes that, because the connection interval is negotiated by the host stack. Expect the classic result: near-flawless wired pacing, and a clearly separate, noisier wireless band.
The DualShock 4 is the reference target for the hidusbf ecosystem because the descriptor patch has been battle-tested across Windows versions for years, and the pad accepts it without firmware conflicts. One catch specific to the DS4: the touchpad keeps sending its own reports, and some drivers interleave those into the same pipe, which can inject periodic jitter spikes into an otherwise clean wired graph. If you see a repeating spike pattern that tracks roughly once per second, that is the touchpad's report stream, not a failed patch — either ignore those frames when judging the interval or disconnect the pad and reconnect it with the touchpad left untouched during the sample.
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.