Issue - z and c keys, both getting registered as 0(N/A) for Retro Bit Sega Saturn Bluetooth Controllers

[imranzunzani]

Description

I am running RetroArch 1.9.14 on Firestick 4k with two Retro Bit Sega Saturn Bluetooth Controllers. The problem I am facing is with keys z and c there. All works fine except for z and c both of which are getting detected as 0 (N/A) keys which makes them both getting mapped to the same last input i.e. both z and c ends up getting mapped to the same action in a game. I tried a lot of things like unpairing and re-pairing the controllers, updating controller profiles with online updater and even updating the firmware of the gamepads but z and c still keep registering as 0 (N/A).

Expected behavior

The two keys should get detected as two separate actions i.e. different or non-zero numbers.

More Information

The controller(s) are detected as 'Retro Bit Bluetooth Controller'. They also showed up as 'ipega PG-9055 BT' when connected for the first time and then showed up as 'Retro Bit Bluetooth Controller' on restarting the Firestick.

Bisect Results

I played with the same controllers on RetroArch 2-3 months back but on an Android Phone for which I lost the setup since, and at that time these keys worked fine. As the version of RetroArch has updated since then, has anything changed or is this because of the Firestick's OS?

Version

• RetroArch: 1.9.14

Environment information

• OS: Amazon Firestick 4k - Fire OS 6.2.8.1 (NS6281/4061)

[imranzunzani]

So, I had a confusing time trying to figure out what is going on here, and as far as I checked this happens only on Fire OS and not on Android. I tried all the modes of the Gamepad and keys keep getting registered as a 0 or -2 here and there. The only combination that worked was pairing the controller with home+X mode which the Mac mode instead of the home+A which is mentioned in the manual for Android and Amazon Fire OS. Then switching on the analog mode with L+R+Start.

I also kept removing the auto configs that keep getting detected but didn't work. Then creating the config (cfg) from a combination of the dinput mappings of Retrobit Bluetooth's cfg and XBox controllers' cfgs in the android folder, which finally worked and is so far going ok.

But it would be great if someone could try this out of Fire OS and dig a bit into what is causing this behavior there while things work fine on Android.

This is the link to the controller's manual for more details about the pad:
https://www.dropbox.com/s/taonlui70y882bc/RB_SEGA%20SATURN_BT_NA_MANUAL_091219.pdf?dl=0

[dennie0]

Had a similar issue with a generic controller branded as "X3 wireless controller" which had a x box key layout.

The options for pairing were

1. X+ Home for Android
2. Y+ Home for iOS
3. A+ Home for Switch
4. B+ Home for PlayStation
5. L2 + Home for PC X input
6. L1 + Home for PC D input / X input

On choosing Option 1, a lot of keys were not working... Option 5 works