(2023-11-17, 13:12)janweinreich Wrote: Thank you. I currently can't try a Kodi build other than main release since this device is shared with the waifu.
Fair, avoid v21 beta then until it goes final (or even a point 1 release).
However, the latest v20.2 release is paradoxically rather far behind the latest stable version. Due to Android store issues, we probably won't release a v20.3 on the Play store, even though we continue to maintain v20 with (only safe) bugfixes for users to sideload.
One such fix is directly related to fixing joysticks on Android:
https://github.com/xbmc/xbmc/pull/23482
The latest v20 version is available on our mirrors:
https://mirrors.kodi.tv/nightlies/androi...v8a/Nexus/
If you're on Android it's worth using the latest v20 due to this fix.
(2023-11-17, 13:12)janweinreich Wrote: And debug log (had to split in two parts due to size, sorry)
https://pastebin.com/hTBKEDkN
https://pastebin.com/NbsyJBLn
You can see the input devices that Android sees starting at line 674 in the first log:
Code:
2023-11-17 07:41:03.992 T:8141 info <general>: CPeripheralBusAndroid: scanning for input devices...
2023-11-17 07:41:03.993 T:8141 debug <general>: CPeripheralBusAndroid: Device discovered:
2023-11-17 07:41:03.993 T:8141 debug <general>: Name: "NVIDIA Virtual Mouse"
...
You can see RetroPlayer initializing at line 1326 of the second log:
Code:
2023-11-17 07:49:27.145 T:8141 info <general>: RetroPlayer[PROCESS]: Created process info for Android
The first button (A) is pressed on line 1683:
Code:
2023-11-17 07:49:29.831 T:8140 debug <general>: Android Key AKEYCODE_BUTTON_A (96) pressed
2023-11-17 07:49:29.835 T:8230 debug <general>: BUTTON [ 0 ] on "NVIDIA Corporation NVIDIA Controller v01.04" pressed
2023-11-17 07:49:29.835 T:8230 debug <general>: FEATURE [ a ] on game.controller.default pressed (ignored)
2023-11-17 07:49:29.835 T:8230 debug <general>: FEATURE [ a ] on game.controller.genesis.6button pressed (handled)
2023-11-17 07:49:29.973 T:8140 debug <general>: Android Key AKEYCODE_BUTTON_A (96) released
2023-11-17 07:49:29.992 T:8230 debug <general>: BUTTON [ 0 ] on "NVIDIA Corporation NVIDIA Controller v01.04" released
2023-11-17 07:49:29.993 T:8230 debug <general>: FEATURE [ a ] on game.controller.default released
2023-11-17 07:49:29.993 T:8230 debug <general>: FEATURE [ a ] on game.controller.genesis.6button released
Then you get your game OSD issue:
Code:
2023-11-17 07:51:38.133 T:8141 debug <general>: ------ Window Init (GameOSD.xml) ------
2023-11-17 07:51:38.133 T:8141 info <general>: Loading skin file: GameOSD.xml, load type: KEEP_IN_MEMORY
2023-11-17 07:51:38.134 T:8141 error <general>: Unable to load window XML: /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/skin.arctic.horizon.2/1080i/GameOSD.xml. Line 0
Failed to open file
(2023-11-17, 13:12)janweinreich Wrote: Here's the debug log of these latest efforts:
https://pastebin.com/AZEYYYGt
It's weird that "start" sends multiple presses without releases, but the code should handle this:
Code:
2023-11-17 08:27:15.906 T:8141 debug <general>: ------ Window Init (GameOSD.xml) ------
2023-11-17 08:27:15.906 T:8140 debug <general>: Android Key AKEYCODE_BUTTON_START (108) pressed
2023-11-17 08:27:15.913 T:8230 debug <general>: BUTTON [ 11 ] on "NVIDIA Corporation NVIDIA Controller v01.04" pressed
2023-11-17 08:27:15.959 T:8140 debug <general>: Android Key AKEYCODE_BUTTON_START (108) pressed
2023-11-17 08:27:15.965 T:8230 debug <general>: BUTTON [ 11 ] on "NVIDIA Corporation NVIDIA Controller v01.04" pressed
2023-11-17 08:27:16.008 T:8140 debug <general>: Android Key AKEYCODE_BUTTON_START (108) pressed
2023-11-17 08:27:16.031 T:8230 debug <general>: BUTTON [ 11 ] on "NVIDIA Corporation NVIDIA Controller v01.04" pressed
Maybe the problem is there.
Once you click on the settings option in the game OSD, it looks like the down button works:
Code:
2023-11-17 08:27:29.505 T:8141 debug <general>: ProcessMouse: trying mouse action leftclick
2023-11-17 08:27:29.505 T:8141 debug <general>: Activating window ID: 11101
2023-11-17 08:27:29.505 T:8141 debug <general>: ------ Window Init (Custom_1101_SettingsList.xml) ------
2023-11-17 08:27:29.508 T:15568 debug <general>: Thread JobWorker start, auto delete: true
2023-11-17 08:27:29.508 T:8141 debug <general>: PERIPHERALS: Event poll handle deactivated
2023-11-17 08:27:29.508 T:8161 debug <general>: void CXBMCApp::OnPlayBackPaused()
2023-11-17 08:27:30.339 T:8230 debug <general>: FEATURE [ down ] on game.controller.default pressed (ignored)
2023-11-17 08:27:30.340 T:8230 debug <general>: FEATURE [ down ] on game.controller.genesis.6button pressed (ignored)
2023-11-17 08:27:30.340 T:8230 debug <general>: FEATURE [ down ] on game.controller.default pressed (handled)
2023-11-17 08:27:30.340 T:8230 debug <general>: FEATURE [ down ] on game.controller.default pressed (ignored)
2023-11-17 08:27:30.340 T:8230 debug <general>: FEATURE [ down ] on game.controller.default pressed (handled)
2023-11-17 08:27:30.498 T:8230 debug <general>: FEATURE [ down ] on game.controller.default released
2023-11-17 08:27:30.499 T:8230 debug <general>: FEATURE [ down ] on game.controller.genesis.6button released
2023-11-17 08:27:30.499 T:8230 debug <general>: FEATURE [ down ] on game.controller.default released
2023-11-17 08:27:31.203 T:8230 info <general>: Skipped 2 duplicate messages..
You can see that there are 5 input handlers (4 use default, one uses genesis) that handle presses, then you can see the 5 input handlers handling the release.
(2023-11-17, 13:12)janweinreich Wrote: I'm gonna try setting up two controllers now.
Let me know how it goes, and if one or both work in the menu but not in the game, then definitely sideload the latest v20 with the android controller fix.