Bug in Gamesir T3S support: X button not recognized when paired in iOS mode
What happened?
Using 3.10.2, and the controller example in Arduino IDE, X button press is not registered when pairing in iOS mode with Gamesir T3s.
Also tell us, what did you expect to happen?
The button display in the serial monitor should register a button press
Bluepad32 Version
What version of our software are you running?
E.g: v3.10.2
Bluepad32 Platform and its version
What Bluepad32 platform are you using? and which version ?
E.g: - Arduino IDE v2.1.0 - Arduino ESP-IDF with ESP-IDF v4.4.4 - Arduino + NINA - CircuitPython 8.0.0 + AirLift - Unijoysticle - MightyMiggy - Other (explain)
Arduino IDE v2.2.1
Which controller
Which controller and its firmware version. Add link to the controller when you are using clones, or not mainstream controllers.
Gamesir T3s -- latest default firmware (1.3?)
E.g: Xbox Wireless model 1708 with Xbox firmware 5.15.1923
Which ESP32
E.g: ESP32, ESP32-S3, or ESP32-C3
ESP32 Dev board
Specify the board model as well
OS
Valid for Arduino platforms: What operating system are you using?
E.g: Linux Ubuntu 23.04, macOS 10.14, Windows 10, etc.
Logs
Please copy and paste any relevant log output. They can be seen from the serial terminal.
13:00:11.379 -> BTstack up and running at B0:A7:32:28:B8:96
13:00:11.379 -> Firmware: Bluepad32 for Arduino v3.10.2
13:00:11.379 -> BD Addr: B0:A7:32:28:B8:96
13:00:46.629 -> CALLBACK: Controller is connected, index=0
13:00:46.629 -> Controller model: XBox One, VID=0x045e, PID=0x02e0
...
13:01:02.960 -> idx=0, dpad: 0x00, buttons: 0x0000, axis L: 0, 0, axis R: 0, 0, brake: 0, throttle: 0, misc: 0x00, gyro x: 0 y: 0 z: 0, accel x: 0 y: 0 z: 0
13:01:03.121 -> idx=0, dpad: 0x00, buttons: 0x0000, axis L: 0, 0, axis R: 0, 0, brake: 0, throttle: 0, misc: 0x00, gyro x: 0 y: 0 z: 0, accel x: 0 y: 0 z: 0
13:01:03.284 -> idx=0, dpad: 0x00, buttons: 0x0002, axis L: 0, 0, axis R: 0, 0, brake: 0, throttle: 0, misc: 0x00, gyro x: 0 y: 0 z: 0, accel x: 0 y: 0 z: 0
13:01:03.446 -> idx=0, dpad: 0x00, buttons: 0x0002, axis L: 0, 0, axis R: 0, 0, brake: 0, throttle: 0, misc: 0x00, gyro x: 0 y: 0 z: 0, accel x: 0 y: 0 z: 0
13:01:03.611 -> idx=0, dpad: 0x00, buttons: 0x0000, axis L: 0, 0, axis R: 0, 0, brake: 0, throttle: 0, misc: 0x02, gyro x: 0 y: 0 z: 0, accel x: 0 y: 0 z: 0
13:01:03.773 -> idx=0, dpad: 0x00, buttons: 0x0000, axis L: 0, 0, axis R: 0, 0, brake: 0, throttle: 0, misc: 0x02, gyro x: 0 y: 0 z: 0, accel x: 0 y: 0 z: 0
13:01:03.936 -> idx=0, dpad: 0x00, buttons: 0x0000, axis L: 0, 0, axis R: 0, 0, brake: 0, throttle: 0, misc: 0x00, gyro x: 0 y: 0 z: 0, accel x: 0 y: 0 z: 0
13:01:04.101 -> idx=0, dpad: 0x00, buttons: 0x0000, axis L: 0, 0, axis R: 0, 0, brake: 0, throttle: 0, misc: 0x02, gyro x: 0 y: 0 z: 0, accel x: 0 y: 0 z: 0
Sketch
If using Arduino/CircuitPython, attach the sketch that reproduces the bug
Your controller sketch