Gamepad -vendor 1949 Product 0402- Work -

It looks like you’re referring to a USB gamepad with Vendor ID 1949 and Product ID 0402.

After checking the USB ID database, 1949:0402 corresponds to:
"Sony Interactive Entertainment" – "DualShock 4 Wireless Adaptor" (actually, the identifier is tied to the official Sony Wireless Adaptor for DualShock 4, though some generic controllers may clone/report this ID).

But if your device is a gamepad showing that ID, it’s likely a third-party PS4-style controller using Sony’s wireless adaptor ID for compatibility. gamepad -vendor 1949 product 0402-

2. Driver & OS Support

3. Android

Android 11+ supports the Stadia Controller natively via USB OTG. Apps that use the Android gamepad API see it correctly. However, button labels may not match because Android expects Xbox layout.

Problem 3: Controller powers off after idle (wired mode)

Cause: The Stadia Controller has an auto-shutdown feature even over USB.
Fix: Press the Stadia button to wake it. To disable auto-shutdown, you need original Stadia firmware update (no longer possible post-shutdown) or a custom firmware (community projects exist). It looks like you’re referring to a USB

Are There Other Products from Vendor 1949?

Yes. Vendor 1949 produces several PIDs. Knowing them helps contextualize the 0402:

PID 0401: A SNES-style retro pad (d-pad + 4 face buttons, no analog sticks).
PID 0402: The standard DualShock 2-style pad (this article's focus).
PID 0403: A racing wheel/pedal combo (very poor quality, uses the same vibration motor logic as the gamepad).
PID 0404: A single analog stick "flight stick."

3. Common Issues & Fixes

| Problem | Likely fix | |---------|-------------| | Not recognized in games | Use DS4Windows (Windows) or map buttons manually | | Shows as “Wireless Controller” but no input | Update USB drivers; try different USB port | | Input lag | Use wired mode (if available) or disable Bluetooth if using adaptor | | Random disconnects | Re-pair DS4 to adaptor (pin hole reset on controller) | PID 0401: A SNES-style retro pad (d-pad +

How to Use This Gamepad After Stadia’s Shutdown (January 18, 2023)

Since Google refunded all Stadia hardware purchases and disabled the cloud service, the controller is now just a standard USB/BT gamepad. But the 0x1949:0x0402 VID/PID remains. Here’s how to maximize its life:

Update to Bluetooth mode – Use Google’s official self-service tool (still available as of 2026) to switch the controller from Wi-Fi to Bluetooth LE. After switching, the USB VID/PID changes only when wired. Bluetooth shows a different PID (e.g., 0x9400).
Keep it wired – Best latency, no battery concerns, and full audio support.
Use xpadneo driver – For Linux users, xpadneo (a third-party advanced Xbox One driver) also handles the Stadia Controller with extra features like battery reporting.

Troubleshooting: The "Vendor 1949 Product 0402" Driver Error

If you see a yellow exclamation mark in Device Manager, or the controller simply doesn't work, here is the common fix.

Why This Matters for Linux, RetroPie, and Batocera Users

If you search gamepad -vendor 1949 product 0402-, chances are you are:

A RetroPie / Batocera / Lakka user who plugged in a Stadia controller and saw this in dmesg or evtest.
An Ubuntu or Arch Linux gamer trying to get the controller working in Steam or Lutris.
A developer writing udev rules for controller mapping.

The Stadia Controller is not plug-and-play on all Linux distributions because the kernel’s default xpad driver may not recognize 0x1949:0x0402. Instead, the hid-google-stadia module (introduced in kernel 5.15+) or the community xpadneo driver is required for full button mapping and rumble.