Reproduction steps:
1. Download and open the attached project: "DualSenseButtonsAndroid.zip"
2. Go to Edit > Build Settings and change the build target to Android
3. Connect a PS5 DualSense controller to an Android device
4. Enable Developer Build and Auto Connect Profiler in the Build Settings
5. Deploy to the Android device via the Build and Run option
6. In the Editor navigate to Windows > Analysis > Input Debugger
7. In the Input Debugger navigate to Remote Devices... > AndroidPlayer(ADB@IP) > Remote > DualShock4GamepadAndroid
8. Press various buttons on the controller (e.g. buttonSouth, buttonNorth, leftTrigger, etc)

Expected result: The corresponding button's value changes in the Input Debugger to reflect that it is being pressed
Actual result: A minority of the buttons are identified correctly, most of the buttons are detected as another button

Reproducible with: Input System 1.3.0 (2019.4.38f1, 2020.3.34f1, 2021.3.2f1, 2022.1.0f1, 2022.2.0a12)

Reproduced on these devices:
----------, Oneplus OnePlus 8 Pro (IN2023), Android 12, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
VLNQA00134, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71

----------, Samsung Galaxy A52 (SM-A525F), Android 12, CPU: Snapdragon 720G (SM7125), GPU: Adreno (TM) 618

Could not test with these devices due to errors:
VLNQA00025, Xiaomi Mi 5s (MI 5s), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00112, Htc M9 (HTC One M9), Android 7.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430

Notes:
- Proper DualSense controller support supposedly comes with the Android 12 update, however, after updating the OnePlus 8 Pro device, the issue was still reproducible
- The DualSense controller is being recognized as DualShock4GamepadAndroid in the Input Debugger and upon opening it, the Product line identifies it as just a Wireless Controller
- If you connect the DualSense controller to the computer, it is recognized as a Gamepad and the Product line identifies it as a PS5 Controller