Often produced by brands like Ipega , PXN , or GameSir Observed Connectivity & Behavior
But if your device is a gamepad showing that ID , it’s likely a using Sony’s wireless adaptor ID for compatibility.
(Sends media keys like volume up/down)
A four-digit hexadecimal number assigned by the manufacturer to specify the exact model. The ID 0402 tells the operating system which exact layout and firmware generation the controller is running. gamepad -vendor 1949 product 0402-
He realized with a jolt of adrenaline that the gamepad wasn't a peripheral for a computer. It was a remote for reality.
While the might cause driver issues on modern operating systems, it is a sturdy, functional controller. In most cases, using Steam’s input mapper or setting up a custom SDL configuration on Linux will allow you to remap the buttons fully. If the controller is unresponsive, check that it is not in a dedicated Switch mode, which often conflicts with the 1949:0402 Bluetooth mapping. If you are still having trouble, Share public link
Because this is a budget controller, physical wear is fast, but digital drift is often a calibration issue. Often produced by brands like Ipega , PXN
Because the 1949:0402 controller is designed for the Android ecosystem, connecting it to a PC or other platforms can be a mixed experience. Here's a breakdown of what users have reported.
| 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+). |
The gamepad with vendor ID 1949 and product ID 0402 appears to be compatible with various platforms, including: He realized with a jolt of adrenaline that
If your Amazon gamepad buttons are swapped (e.g., A and B are inverted), you can add a custom mapping string to your environment variables or game configuration files. Sample SDL2 Mapping String
Bluetooth, Wi-Fi Direct (on older Fire controllers), or Micro-USB/USB-C wired connections. Linux and Udev Configuration
: This code is officially assigned to Lab126, Inc. —a subsidiary of Amazon responsible for developing Kindle and Fire devices. It is most commonly seen when connecting Amazon hardware in fastboot or ADB modes for debugging. However, it also appears on third-party accessories that licensed or cloned the bootloader handshake protocols during the early Android boom.
The first part of the string is 1949 . According to the USB Implementers Forum database, this Vendor ID is officially registered to Lab126, Inc. , a wholly-owned subsidiary of Amazon.com, Inc. responsible for the development of Kindle e-readers and Fire tablets. This is a key piece of the puzzle.