Arcade2TV-XR mode switching and red startup flashes

Useful Answer

Three red flashes at startup are normal. They indicate the controller is starting in Keyboard Mode.

Mode switching requires a real data connection. The controller will not switch modes if it is only powered through USB-C. Connect the unit to a PC or console with the USB-B cable, then hold P1 Mode on the touch panel for about 5 seconds. The light should blink to confirm the mode change.

On manuals or units that describe a modified shortcut, be careful to distinguish P1 from P1 Mode. One customer could not enter XInput because they were reading the normal P1 player button instead of the P1 Mode control. For that unit, support instructed: hold Button 3, then hold P1 Mode for 5 seconds until the controller reboots into XInput.

Mode colors:

If the controller appears stuck in XInput after changing firmware versions, first try the USB-B connection plus 5-second P1 Mode hold. If it still will not leave XInput, perform the force firmware upgrade from the Arcade2TV software guide, then test mode switching again while connected over USB-B.

If the expected Keyboard / D-Input / XInput switching behavior does not work on an older unit, check the firmware version. One customer found that firmware 2.2.1 did not respond to the current mode-switching method, while updating to 2.2.7 restored normal behavior.

If P1 Mode still does not respond with USB-B connected, check the internal touch-panel wiring:

Holding P1 Mode + X-Logo does not lock the controller. That shortcut decreases brightness.

Quick Reference

Source Context

The customer thought the controller was locked because P1 Mode did nothing and the unit flashed red three times. They later confirmed that mode switching worked after plugging into a PC. A second customer who was stuck in XInput after firmware changes confirmed that USB-B connection plus holding P1 Mode for about 5 seconds restored mode switching. A third customer reported that updating from firmware 2.2.1 to 2.2.7 fixed mode-switching behavior that had not worked with the older firmware. Another customer confirmed the issue was reading the wrong button in the manual: they used P1 instead of P1 Mode.