[Android] Razer Kishi's trigger axes are inconfigurable in the UI (and are possibly mislabeled in the cfg file).

Description

Razer Kishi's analog trigger axes are mislabeled and unconfigurable through the UI.

Expected behavior

I expect to be able to use the triggers as analog axes.

Actual behavior

It's impossible to use the trigger axes without manually editing "retroarch.cfg".

Steps to reproduce the bug

1. Launch RetroArch on Android.
2. Connect and autoconfigure a Razer Kishi.
3. Try to map L2 and R2 as analog axes.

Bisect Results

Through some trial and error I found out that the proper axes are +9 for the L2 trigger and +8 for the R2 trigger. In the autoconfig file they are stated as +23 and +22 respectively which are the decimal representations of their addresses, but i don't think that's how RetroArch actually labels axes.

It's also impossible to configure them through the UI because the Razer Kishi is designed to report the trigger axes and their corresponding button output at the same time (i guess it's intended for some compatibility): if you try to map it it just defaults to the button output. The only way to make it work for the end user is to manually assign the axes through "retroarch.cfg".

Version/Commit

• RetroArch: 1.9.6

Environment information

• OS: Android 11
• Device: ASUS ZenFone 8 Flip

Reproduce the issue on Android with a Razer Kishi, then inspect the device's autoconfig mapping and the generated retroarch.cfg entries for the trigger axes. Done means the L2 and R2 analog axes are correctly labeled and can be selected through the controller-mapping UI without manual configuration.