QPAD Support

Question 1

WAVE Model 3: how to tell the current mode and change it

Accepted Answer

A double click on the power button moves the headset between the 2.4 GHz dongle and Bluetooth. Connect the USB-C cable and it goes to wired sound-card mode on its own.

Reading the light: green flashes every two seconds mean 2.4 GHz is connected (red and green take turns while it searches). Blue flashes every two seconds mean Bluetooth is connected (red and blue take turns while it searches). Six red flashes and then a steady light mean wired mode.

To turn the headset on or off, keep the power button pressed for 3 seconds (the light shows blue for 1 second on power-up and red for 1 second on shutdown). It reconnects to whichever device it was last paired with.

The dongle plugs into either a USB-A or a USB-C port. No connection? Move it to a different port on the device itself, not a hub.

Question 2

WAVE Model 3: a new device refuses to pair over Bluetooth

Accepted Answer

Make sure the headset is off, then keep the power button pressed for 8 seconds. When the indicator gives three white flashes, the Bluetooth pairing list has been cleared.

Change to Bluetooth mode by pressing the power button twice, wait until the light alternates red and blue, and then select "Qpad Wave Model 3" from the Bluetooth list on your device.

Some devices only support certain modes. The manual has a compatibility table that lists which modes your device can use.

Question 3

WAVE Model 3: no audio or mic with a console, a phone or a tablet

Accepted Answer

Whether you get sound, mic and mute is decided by the connection mode together with the device. Test the other two modes before anything else: USB-C cable, 2.4 GHz dongle, Bluetooth.

The manual's compatibility table says: PC, Mac, Nintendo Switch and Android phones work in all three modes. PS4 and PS5 consoles work wired and over Bluetooth. iOS devices and tablets work over the 2.4 GHz dongle. Xbox consoles and controllers are not supported. System software version, device settings and the connection method can all change this.

For wired mode, check that the USB-C cable sits all the way into the charging and audio port of the left earcup, with the other end plugged into one of the device's USB-A ports.

Question 4

WAVE Model 3: charging, battery life and the low-battery light

Accepted Answer

Under roughly 3.3 V a voice prompt warns about low battery once every 10 minutes, while the light blinks red every 2 seconds. Under 3.1 V the headset switches off. Put in the spare or connect the cable.

To charge, plug the USB-C cable into the charging port. A steady red light shows it is charging, and the light goes green once the battery is full. From a low-battery shutdown, a complete charge takes around 3 hours, and you can keep using the headset while it is charging.

You get two 800 mAh batteries, one already fitted and one spare. When the first is charged, put the spare in the headset and charge that one too.

Question 5

WAVE Model 3 shuts off by itself

Accepted Answer

Smart shutdown: if nothing has been connected for around 5 minutes, the headset switches off. It also switches off after around 45 minutes of being connected without any audio playing. To start it again, keep the power button pressed for 3 seconds.

A red flashing light followed by a shutdown in the middle of a game means an empty battery. Fit the spare or charge it.

Question 6

WAVE Model 3: muting the mic, taking calls, and music mode versus gaming mode

Accepted Answer

A single press on the microphone button mutes or unmutes the mic. Roll the volume wheel either way to adjust volume.

Calls over Bluetooth: press the microphone button twice to pick up or hang up, or keep it pressed for 1.5 seconds to decline a call.

A single click on the power button plays or pauses the audio. Three clicks move you from music mode to gaming mode and back.

Question 7

Keyboard not detected / no input

Accepted Answer

Try a direct motherboard USB port (avoid unpowered hubs). Re-seat the detachable USB-C cable if your model supports it.

LOOP TKL: set the tri-mode switch to OFF for wired use (USB cable required in OFF), or to 2.4G / BT for wireless.

Reset the keyboard: hold FN + ESC until the backlight flashes 3 times. (Timing varies by model: LOOP 65 / LOOP TKL typically ~3s; FLUX 65 uses a longer hold.)

Test on another PC if possible to rule out OS / driver conflicts.

Question 8

LOOP TKL: 2.4G / Bluetooth won't pair or reconnect

Accepted Answer

2.4G mode: set the switch to 2.4G, plug in the 2.4G dongle, then hold the FN + 2.4G pairing key shown in the manual for ~3s (the key's backlight flashes during pairing).

Bluetooth mode: set the switch to BT. Hold FN + 1 (BT1), FN + 2 (BT2), or FN + 3 (BT3) for ~3s to pair to that slot.

Clear paired Bluetooth devices (BT mode only): hold FN + Ins or FN + Esc for ~3s to reset Bluetooth pairing, then pair again.

Move the dongle closer (front USB port) and reduce nearby wireless interference (Wi-Fi routers, other dongles, etc.).

Question 9

Wrong layout (Windows / Mac mode mismatch)

Accepted Answer

FLUX 65: switch system mode with FN + O = Windows, FN + P = Mac.

LOOP 65: switch system mode with FN + U = Windows, FN + I = Mac.

LOOP TKL: use the physical WIN / MAC switch (shown in the manual) if your unit has it.

If keys still feel “swapped”, confirm your OS keyboard layout (e.g., ISO-UK vs ISO-Nordic) matches your model.

Question 10

RGB, lightbar, or dials not responding

Accepted Answer

Quick reset: hold FN + ESC until LEDs flash 3 times, then test again.

FLUX 65: FN + Enter cycles backlight modes; FN + Right Shift switches color (per manual shortcut table).

LOOP 65: FN + Enter changes backlight mode; use the manual's RGB shortcuts for brightness / speed / color control.

LOOP TKL lightbar: slide the touch lightbar to adjust overall keyboard brightness. If it flashes red, charge the keyboard.

LOOP TKL dials: Dial 1 controls backlight speed and pressing it changes backlight mode; Dial 2 controls volume and pressing mutes.

Question 11

Win key locked / FN shortcuts don't work

Accepted Answer

Win Lock: toggle with FN + WIN (supported on FLUX 65 / LOOP 65 / LOOP TKL per manuals).

LOOP TKL: some functions (like clearing paired BT devices) only work when the switch is set to BT.

If media keys / shortcuts behave oddly, confirm you're in the correct Windows / Mac mode (see “Wrong layout” above).

Still stuck? Do a FN + ESC reset and retest shortcuts.

Question 12

Software / customization not applying (lighting, keys, profiles)

Accepted Answer

Download the correct software for your model from qpad.com/software.

Close other keyboard / macro / RGB software while testing (they can conflict).

After making changes, look for an Apply / Save action in the app (some lighting modes are stored with “memory” per manual behavior).

If settings won't stick: do a FN + ESC reset, then reapply your settings.

Question 13

Hot-swap switch / key feels stuck or unresponsive

Accepted Answer

Unplug the keyboard. Remove the keycap, then use the included 2-in-1 switch / keycap puller (listed in package contents) to remove the switch.

Inspect the switch pins (straighten carefully if bent) and reinsert the switch evenly until fully seated.

Swap in another compatible switch (if available) to confirm whether it's the switch or the socket.

If the key still fails: perform a FN + ESC reset and test again before contacting support.

Question 14

Mouse not detected / no cursor movement (wired)

Accepted Answer

Reconnect the USB-C cable firmly into the front port of the mouse, then plug into a direct motherboard USB port (avoid unpowered hubs).

If you're using a tri-mode model (Mark Model 1 / 3 / 5), set the bottom switch to OFF for wired use.

Try a different USB port and test on another computer to rule out OS / driver conflicts.

Question 15

2.4G wireless won't connect / receiver not working (M1 / M3 / M5)

Accepted Answer

Plug the 2.4G dongle / 4K receiver into your PC and set the mouse switch to 2.4G. A green indicator should light for ~10 seconds (factory default is paired).

Move the receiver closer (front USB port) and keep it away from Wi-Fi routers / other dongles to reduce interference.

If it still drops out, try another USB port and remove other high-bandwidth USB devices temporarily.

Question 16

Bluetooth won't pair (M1 / M3 / M5)

Accepted Answer

Set the bottom switch to BT. The blue indicator turns on.

Start pairing by pressing Left + Middle (wheel click) + Right at the same time for 3 seconds until the blue indicator flashes quickly.

On your computer, open Bluetooth settings and select the QPAD mouse to complete pairing.

For gaming / lowest latency: use 2.4G. Bluetooth runs at a lower default polling rate than 2.4G.

Question 17

DPI feels “wrong” / sensitivity changes unexpectedly

Accepted Answer

On Mark Model 1 / 3 / 5, the DPI button is on the underside. Make sure it isn't being pressed during handling.

Default DPI steps and LED colors: 400 (Green), 800 (Blue), 1600 (Red – Default), 3200 (Cyan), 16000 (White).

If you use the software, you can increase max sensitivity (up to 26,000 DPI) and customize DPI steps.

Download software: qpad.com/software (Mark Model 1 / 3 / 5 manuals).

Question 18

Lag, stutter, or “slow” response

Accepted Answer

Use 2.4G for the best performance. (Default polling is 1KHz on 2.4G; Bluetooth is 125Hz.)

Plug the dongle / receiver into a closer USB port and avoid unpowered hubs.

Close background utilities that hook input devices (macro tools, RGB suites) and retest.

If tracking feels inconsistent, clean the sensor and use a quality mousepad surface.

Question 19

Battery drains fast / won't charge / keeps sleeping (wireless models)

Accepted Answer

Low battery: indicator flashes red = time to charge.

Charging: orange LED flashes while charging, and turns off when fully charged.

Sleep behavior (manual): ~5 seconds to Sleep (move to wake), ~20 seconds to Deep Sleep (move to wake).

If wake feels delayed, use 2.4G mode and keep the receiver close.

Question 20

4K Vision receiver screen is off / not updating (Mark Model 3 / 5)

Accepted Answer

Press the receiver's Screen ON / OFF button (listed in the manual package overview).

Unplug / replug the receiver and try a different USB port (preferably front / closer to the mouse).

Confirm the mouse is set to 2.4G mode (the receiver displays Polling Rate / DPI / Battery when connected).

Question 21

Buttons not registering / double-click / side buttons not working

Accepted Answer

Blow out dust around buttons and the scroll wheel using compressed air (avoid liquids).

Test wired vs wireless to rule out connection issues.

If you've remapped buttons in software, revert to default and test again.

Still failing? Contact support with your model name (Mark Model 1 / 3 / 5) and a short description of the issue.

Question 22

Inconsistent tracking (dust, oils, or surface contamination)

Accepted Answer

Wipe the surface with a soft, lint-free cloth to remove dust and hair.

For deeper cleaning: use lukewarm water + a tiny amount of mild soap. Gently rub, then rinse thoroughly.

Air dry completely (flat) before use: moisture can cause tracking issues and curling.

Also clean the mouse sensor feet area and ensure your skates are not dirty / worn.

Question 23

Mousepad slipping during gameplay

Accepted Answer

Clean the rubber base and the desk surface (dust and oils reduce grip).

Make sure the desk is flat and dry; humidity can reduce friction.

If your desk has texture / varnish issues, add a thin non-slip mat underneath.

Question 24

Curling edges / bumps / won't lay flat

Accepted Answer

Lay it flat and place a book / heavy object on top for a few hours.

If it arrived rolled, gently roll it the opposite direction and let it rest flat.

Avoid heat sources (radiators, direct sun) that can warp the rubber backing.

Question 25

RGB lighting issues (RGB mousepads only)

Accepted Answer

Reconnect the USB cable and try a direct USB port (avoid hubs).

Check that the controller button (if included) isn't stuck; cycle modes to confirm it responds.

If your RGB pad supports software control, close other RGB software that may conflict.

Question 26

Edge wear or stitching damage

Accepted Answer

Avoid dragging the pad across sharp desk edges or rough surfaces.

Don't pull on loose threads: trim carefully with small scissors to prevent further fraying.

If stitching separates or the surface bubbles, contact support with photos.

Question 27

Mic not detected / no power

Accepted Answer

Reconnect the USB cable at both ends. Try a direct motherboard USB port (avoid unpowered hubs).

Try a different USB cable (if detachable) and a different USB port.

Windows: open Device Manager → Sound, video and game controllers and confirm the mic appears (unplug / replug to refresh).

Mac: Apple menu → System Settings → Sound → Input and confirm the mic is listed.

Question 28

No audio capture (silent in Discord / OBS / Zoom)

Accepted Answer

Set the mic as the input device in the app (Discord / OBS / Zoom all have separate input selectors).

Windows: Settings → System → Sound → Input and raise input volume. Then check Privacy & security → Microphone (allow apps).

If the mic works in one app but not another: disable Exclusive Mode (Windows: Sound Control Panel → Recording → Properties → Advanced).

Test quickly in Windows “Voice Recorder” or macOS “Voice Memos” to isolate app vs system issues.

Question 29

Tap-to-mute not working (or always muted)

Accepted Answer

Tap the top once and look for a visible status change (LED / RGB or app input meter).

Gently wipe the top surface (dry cloth) to remove oils / dust that can affect touch sensors.

Unplug the mic for 10 seconds and reconnect to reset the touch / mute state.

Also check the app mute (Discord / Zoom) and OS mute toggles: these can override the mic's own mute.

Question 30

Distorted, “crackly”, or low-quality audio

Accepted Answer

Clipping (harsh distortion): lower mic gain and / or lower input level in Windows / macOS / app.

Keep a consistent distance (typically 10–20 cm) and use a pop filter / windscreen if possible.

Match the mic's sample rate across OS + app (common stable setting: 48 kHz). Mismatched rates can cause artifacts.

Avoid plugging into noisy front-panel USB ports; try a rear motherboard port.

Question 31

Background noise, echo, or room reverb

Accepted Answer

Move the mic away from fans / PC exhaust and keep it off the same surface as a loud keyboard (use a stand / arm if possible).

Lower gain and move closer to the mic (this improves voice-to-noise ratio).

Enable noise suppression / echo cancellation in your app (Discord / Zoom / Teams) if needed.

Headphones recommended to avoid speaker echo / feedback.

Question 32

Headphone monitoring has no sound (if your mic has a headphone jack)

Accepted Answer

Confirm headphones are fully seated (try another headset / cable).

Check the mic's monitoring / volume control (if present) and raise it gradually.

Windows: ensure the playback device is set correctly (your mic headphone output may appear as an audio device).

Question 33

USB dropouts, random disconnects, or crackle under load

Accepted Answer

Move the mic to a different USB controller (try rear ports vs front ports).

Avoid USB hubs and shared dongles; plug the mic directly into the PC.

Close heavy background USB / audio software temporarily (RGB suites, virtual audio cables) and retest.

If it only happens in one app, try lowering the app's audio processing settings (noise suppression can increase CPU load).

Find your fix.

Need more help? Talk to a human.