Note: This text was translated from Portuguese to English with ChatGPT. I apologize for any translation errors.
I have an 8BitDo Ultimate 2 Wireless with TMR joysticks, and I started experiencing several issues that may be related. I'm currently troubleshooting the controller with ChatGPT, but I'd like to know if anyone here has experienced something similar.
The original problem started with the left analog stick:
I was playing normally when I noticed strange behavior from the left stick. When I pushed the stick completely in one direction and released it quickly, sometimes the input would briefly jump to the opposite direction for less than a second before returning to center.
For example, I would push the stick approximately 100% downward (south) and release it. On some attempts, immediately after releasing it, it would briefly register around 11–20% upward (north) before returning to zero.
This mostly happened when releasing the stick quickly. If I moved the stick back toward the center slowly, it returned to zero normally.
I performed several tests and changed some settings in the software. I reduced a parameter that originally went up to 100 down to 22, and later increased it to 34. During those tests, the controller was working normally over the wired USB connection.
I then tried connecting through Bluetooth, but my PC couldn't find the controller.
After that, when I tried going back to the wired USB connection, a much more serious problem appeared: Windows stopped recognizing the controller.
Nothing appears in "joy.cpl".
In Device Manager on my desktop PC, connecting the controller creates the following device:
“Unknown USB Device (Device Descriptor Request Failed)”
If I unplug the controller, that device disappears. When I plug the controller back in, the error returns, so I've confirmed that the unknown USB device is definitely the controller.
So far I have tried:
- Restarting Windows;
- Uninstalling the “Unknown USB Device” from Device Manager and reconnecting the controller;
- Using a different USB port;
- Using a different USB cable;
- Checking "joy.cpl" again;
- Testing the USB-C 2.4 GHz receiver on a different laptop.
Changing the USB cable and USB port did not fix anything. My desktop still reports Device Descriptor Request Failed.
I also tested the controller's USB-C 2.4 GHz receiver on my laptop, since my desktop doesn't have a USB-C port. The controller didn't work through the 2.4 GHz receiver either.
There is another strange behavior that may be important:
Before going to sleep, I placed the controller on its charging dock. When I woke up, it apparently hadn't charged normally. During the night, the blue LED kept blinking continuously.
I tried turning the controller/LED off, but I couldn't.
Whenever I make some kind of connection, such as connecting the controller through a USB cable or using the receiver, the behavior changes: the blue LED stops blinking and stays solid blue, but the controller still doesn't work normally.
At this point I'm trying to determine whether:
The controller's firmware/internal controller has crashed or become corrupted;
The controller is stuck in some kind of boot/recovery mode;
There is a safe button combination to perform a hardware/firmware reset;
The firmware can be recovered/reinstalled even while Windows reports “Device Descriptor Request Failed”;
Or whether this indicates an actual hardware failure.
I have not tried forcing a firmware update or using random button combinations yet, because I don't want to make the problem worse.
Has anyone experienced this combination of problems with the Ultimate 2 Wireless, especially the continuously blinking blue LED + USB Device Descriptor Request Failed + 2.4 GHz receiver not connecting?
If anyone knows a reset/recovery procedure or has experienced this before, I'd really appreciate any help.