[Android] "DragonRise Inc. Generic USB Joystick" USB Encoder auto initialized on start

Description

In RetroArch Android my 2 "DragonRise Inc. Generic USB Joystick (121/6)" Zero Delay USB Encoders auto initialize immediately at Retroarch and game startup time rather than waiting for a button to be pressed. This makes it less user-friendly because controller 1 is randomly decided instead of simply being the first controller that has a button pressed.

See Reddit thread with @hizzlekizzle help for more context: https://www.reddit.com/r/RetroArch/comments/xcyz1x/retroarch_android_usb_encoder_controller_input

Expected behavior

I'd expect when RetroArch Android starts up that non of my controllers will initialize until I press a button on one, identifying that controller as the first input.

Actual behavior

Both of my Zero Delay USB Encoders initialize right when RetroArch starts causing a race condition for which controller is identified as input 1.

Steps to reproduce the bug

1. Plus "DragonRise Inc. Generic USB Joystick (121/6)" USB Encoder into android device
2. Start RetroArch
3. Watch the controller get initialized despite no buttons pressed.

Bisect Results

My USB Encoders are new. This has always happened with these encoders in RetroArch. I will note though that RetroX behaves the way I'd expect RetroArch to behave (waiting for a button press to initialize the controller)

Version/Commit

• RetroArch: 1.10.3/102abb0 But multiple builds and versions tried all the way back to 1.9.0. Same behavior in all.

Environment information

• OS: Android (multiple android devices and versions tested)
• Exact USB Encoder Product: https://www.amazon.com/SJ-JX-Controller-Joystick-Raspberry-Pi/dp/B081NYVT72

No source file or test is named. Start by reproducing the Android startup sequence with two DragonRise Inc. Generic USB Joystick encoders and trace where controller initialization occurs; done means neither encoder initializes until a button press identifies it, without controller 1 being chosen by a startup race.