Mouse Jiggler
jiggle / jg — Prevent Host Screen Lock
CMD> jg # USB HID (plug in cable)
CMD> jg ble # BLE HID (pair on host)
Press q to stop.
Two transports, identical behaviour:
| Command | Transport | Setup |
|---|---|---|
jg | USB HID | Plug the T-DECK into the target PC with a data cable |
jg ble | BLE HID | Run it, then pair AL-ANQA-KBD on the host (Just Works, no PIN) — reuses the btkbd BLE HID stack |
The BLE mode advertises as AL-ANQA-KBD; once the host pairs and the link is encrypted, jiggling begins. If the host drops the link the jiggler pauses and waits to reconnect.
How It Works
jiggle sends tiny HID mouse movement packets to the host on a timed interval (over USB or BLE). The cursor moves 2 pixels right, then 2 pixels left — staying in effectively the same position but continuously resetting the host OS’s idle timer.
Most operating systems treat any mouse movement as “user activity” and reset their screen lock/sleep timer. This keeps the host awake and unlocked indefinitely without touching the actual keyboard or mouse.
The movement is imperceptible in normal use — the cursor returns to its original position after each tick.
Use Cases
- Keep a session alive while working on the T-DECK without touching the host
- Prevent a locked workstation during a pentest assessment
- Keep a remote desktop session from timing out
Requirements
- T-DECK must be connected via USB data cable (not charge-only)
- The host must recognise T-DECK as a HID device (same as
usbkbd) — no additional drivers needed on Windows, macOS, or Linux - If the host prompts for driver installation, try a different USB port
Notes
- The jiggler runs independently — you can use the T-DECK keyboard and trackball normally while
jgis active - Movement interval is fixed — there is no configurable timing
- Some enterprise endpoint-security tools detect jiggling patterns; if the host has strict HID monitoring this may be logged