In certain development environments like the , the D-pad may be treated as axes rather than buttons.
(Note: Some variations may exist depending on whether the controller is in Android or DirectInput mode). Common FAQs
When you connect this controller, your operating system recognizes it by its USB/Bluetooth ID.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Because this is an Amazon-branded device, it often relies on generic Microsoft USB Human Interface Device drivers. gamepad -vendor 1949 product 0402-
Once you have this information, you can search for specific solutions (like adding your user to the input group on Linux) or configure emulators and game launchers to recognize the controller.
The shadow didn't just vanish; it folded into itself like a paper crane being crushed by an invisible hand, leaving behind nothing but the faint scent of ozone and the silence of the basement.
While functional, this gamepad is considered legacy hardware. Modern, official Xbox or PlayStation controllers offer native "plug-and-play" support across all platforms without needing specialized troubleshooting.
Boot the controller into standard Android HID mode (usually by holding or Home + A depending on the exact brand variation). In certain development environments like the , the
You need to force a manual udev rule or explicitly tell RetroArch to ignore the mouse/keyboard nodes.
Open a terminal and run the command lsusb . This will list all connected USB devices. For a Bluetooth device, you will need to use the lsusb command with additional permissions. You can also check the kernel's input device information directly with cat /sys/bus/usb/devices/*/idVendor,Product .
Bluetooth may pair but not auto-connect or show up in RetroArch.
The combination, 1949:0402 , appears in system logs as 0005:1949:0402.000A or similar, where the leading 0005 indicates it is a , not a wired USB peripheral. This public link is valid for 7 days
The specific printed on the back of your controller?
Linked initially to Lab126, the underlying firmware is frequently integrated into generic Bluetooth chipsets designed for low-cost Android, iOS, and PC gamepads.
Before we identify the specific gamepad, it's important to understand what this string of numbers represents. In the world of USB and Bluetooth devices, 1949:0402 is a unique identifier, often displayed as VID_1949&PID_0402 in Windows or 1949:0402 on Linux systems. This is the combination of a and a Product ID (PID) .
The USB identifier 1949:0402 is a fascinating time capsule of the early 2010s mobile gaming scene—a Bluetooth gamepad with a Kindle Fire bootloader signature. While it may not compete with modern low-latency controllers like the PS5 DualSense or Xbox Series X gamepad, the iPEGA PG-9053 remains a viable, low-cost option for retro gaming on tablets and phones. With a bit of troubleshooting (especially on Linux), this old warrior can still provide an excellent handheld gaming experience for emulators up to the PlayStation 1 era.
: 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.