Gamepad -vendor 1949 Product 0402- Jun 2026

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.

If you see that cryptic ID in your system logs, don’t panic. Update your kernel to 6.x or install xpadneo , and you’ll have a perfectly functional controller. The numbers 1949:0402 are not an error – they are the signature of a device that outlived its original cloud.

SUBSYSTEM=="usb", ATTRSidVendor=="1949", ATTRSidProduct=="0402", RUN+="/sbin/modprobe hid-google-stadia"

(Vendor ID 1949). This specific ID is commonly used by third-party controllers mimicking original hardware to ensure compatibility with Android and various gaming systems. Device Identification 1949 (Lab126, Inc. / Amazon) Product ID: 0402 Common Names: GEN GAME S3 Go to product viewer dialog for this item. Go to product viewer dialog for this item. , or simply "Gamepad"

However, the legacy of the Luna Controller is defined by a tension between its innovative engineering and its market reception. Technically, the device is competent. It borrows the ergonomic symmetry popularized by the Xbox Wireless Controller, offering a comfortable, familiar grip for the average consumer. Yet, it suffered from the classic "chicken and egg" dilemma. The controller was designed specifically for the Luna cloud service, but without a massive, install-base-owning console to anchor it, it struggled to justify its existence against the ubiquitous Xbox controller, which could be used for Luna just as easily as it could for an Xbox or a PC. While the Luna Controller works via Bluetooth on PCs and mobile devices, its premium price point made it a hard sell for those not fully committed to Amazon’s ecosystem. gamepad -vendor 1949 product 0402-

By applying a custom mapping string, you can resolve these vendor configuration errors.

2 analog triggers (L2/R2) and 2 digital shoulder buttons (L1/R1). Action Buttons: A, B, X, Y.

Bluetooth, Wi-Fi Direct (on older Fire controllers), or Micro-USB/USB-C wired connections. Linux and Udev Configuration

Many users on open-source game engines (like Godot or Unity) report that the digital directional pad (D-Pad) fails to register entirely, or registers as a static axis value instead of independent button presses. Android 11+ supports the Stadia Controller natively via

| Issue | Likely Cause | Solution(s) | | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | | D-pad is mapped to an axis (axis 9) rather than buttons, and the default axis value is outside the standard [-1, 1] range | Use a wrapper like x360ce to remap the D-pad or report the issue to the browser/engine developers. | | Gamepad not recognized in Linux games | Permission issues preventing the gamepad from being seen as a joystick; often missing udev rules | Create a udev rule (e.g., /etc/udev/rules.d/99-gamepad.rules ) to set permissions. Add your user to the input group. | | Bluetooth connection issues on Windows | Inconsistent Bluetooth driver support; Windows may not handle the HID profile correctly | Use the included USB cable for a wired connection, or use a dedicated Bluetooth dongle. Try different pairing modes (Home + X/A/B). | | Generic "Unknown Gamepad" label | The system has detected the device (VID/PID) but does not have a specific driver mapping for it | Use a compatibility wrapper like x360ce (Windows) or ensure your Linux kernel is up to date (5.13+). |

(specifically the first-generation model). While originally designed for Fire TV, it is often detected as an Ipega PG-9069

Are you attempting to configure this controller for a or a particular game engine ? AI responses may include mistakes. Learn more Bluetooth controllers are not working - CoreELEC Forums

: If games do not natively see the device, install mapping layers such as the ShootingPlus V3 App via the Google Play Store. This software binds touch screen coordinates directly to the controller’s hardware registers. If you see that cryptic ID in your

Which (Windows, Linux, macOS) or game engine you are developing/playing on?

After cross-referencing Linux kernel’s hid-ids.h , USB ID repositories, and Android documentation, — specifically the Founder’s Edition or early production run when used in USB wired mode.

If your game or game engine asks for a SDL2 input string, you can use this configuration rule to fix the "Vendor 1949 Product 0402" gamepad:

Map the buttons manually, particularly the D-pad and triggers, to resolve the 1949:0402 mapping issue. Method B: Linux/RetroPie Fix