GFlick

Three mice, hardware-validated

What works on which mouse

Support is capability-driven: a control appears only when the connected mouse advertises the feature behind it. That means an unlisted mouse may still work - GFlick reads what the firmware reports rather than matching a product database - but only these three have been validated against real hardware.

Format 0x04

PRO X Superlight

The only mouse that has taken a live onboard flash write, including a verified profile-name round trip and a restore of all 255 original bytes.

Format 0x07

PRO X Superlight 2

The widest capability set: X/Y DPI, lift-off distance, 8 kHz wireless polling, surface mode, and BHOP. No flash write has been sent to it.

Format 0x03

G305

One public RGB zone with all four effects verified live, plus read/write performance mode. No flash write has been sent to it.

Capability matrix

Every row is an end-user capability rather than a raw HID++ entry, so a feature the firmware merely advertises does not count as supported. A dash means the mouse does not advertise it at all.

Supported capabilities by mouse
CapabilitySuperlightSuperlight 2G305
Name, model, unit ID, firmwareYesYesYes
Battery percentage and charge stateYesYesYes
Live DPI and supported rangeYesYes, X/YYes
Lift-off distanceYes
Wired polling rateYesYesShared rate
Wireless polling rateUp to 1 kHzUp to 8 kHzUp to 1 kHz
Performance/endurance modeRead-onlyRead/write
Gaming surface modeYes
Color LED effectsIndicator onlyOne RGB zone
BHOPYes
Host/onboard mode and active profileYesYesYes
Onboard profile list and decodingFormat 0x04Format 0x07Format 0x03
Profile-sector writesLive proof passedEncoder testedEncoder tested
Profile enable/disable directoryFive profilesFive profilesOne writable
DPI stages and shift stageYesYesYes
Onboard button assignmentsFive buttonsFive buttonsSix buttons
Profile names and power timersYesYesYes
Host button mapping and filterYesYesYes

gflick-probe features prints this same classification for any connected device, so it is the runtime source of truth for a mouse that is not listed here.

Deliberately not supported

Some HID++ features are reachable but intentionally blocked. These are not gaps waiting to be filled.

Hidden and internal features

The 0x18xx and 0x1Exx ranges are firmware manufacturing, RF-test, out-of-box, and reset facilities. They stay blocked from the settings API so no interface can accidentally reset a mouse or put it into a factory mode.

Force pairing and signed DFU

Force Pairing (0x1500) and signed DFU control (0x00c2) are maintenance workflows rather than settings, so they are not exposed either.

Macros and per-application profiles

Host keyboard shortcuts, host macros, onboard macro creation, and per-application profile switching are out of scope by intent. Onboard button assignments are supported; recording macro sequences is not.

How writes are made safe

Every setting write is validated before it is sent and verified by reading the value back from the device. Onboard profile writes go further: they preserve sector bytes whose meaning is unknown, regenerate the HID++ CRC, verify the read-back byte for byte, and roll back automatically on any mismatch. Flash writes additionally require an explicit acknowledgement flag.

Validation is still device-specific, and this is the important caveat. A passing encoder unit test is not the same as a hardware proof. Live onboard flash writes have only ever been sent to the original Superlight; the Superlight 2 and G305 profile encoders are unit-tested only, at the owner's request.

An unlisted mouse

Because discovery is capability-driven, another Logitech HID++ mouse may well be readable and partly controllable. Nothing about it is validated, though - treat it as unverified, start with the read-only commands, and leave onboard writes alone.

The complete matrix, including the diagnostics-only features and the recorded write proofs, is in the feature matrix .