@LibretroAdmin This issue should be highly prioritized. Can you please label it?

I'll let @sonninnos know about it, since I think he last handled the input remapping code.

I'll let @sonninnos know about it, since I think he last handled the input remapping code.

Thank you very much.

@sonninnos These bugs persist in https://buildbot.libretro.com/stable/1.19.1/android/RetroArch.apk it makes it very inconvenient for people to configure controllers. Have you taken a look at this yet?

Works fine here. Bind timeout is respected, and when setting all it proceeds to the next one in proper order without missing any, and if timeout is triggered, it stops the whole process, because forcefully continuing to the end without a way to quit is way more annoying.

Tested on Windows, and zero idea how platform could make any difference with that code.

Works fine here. Bind timeout is respected, and when setting all it proceeds to the next one in proper order without missing any, and if timeout is triggered, it stops the whole process, because forcefully continuing to the end without a way to quit is way more annoying.

Tested on Windows, and zero idea how platform could make any difference with that code.

Thank you for testing it.

i am experiencing these exact problems with version 1.20.0 on my google pixel 7a. the hotkey feature is unusable in this state.

@zoltanvb Hello. Do you have any idea what may causing this?

Would the same workaround be applicable here as #17157 ? That is, setting "Bind Hold" to e.g. 5.

Would the same workaround be applicable here as #17157 ? That is, setting "Bind Hold" to e.g. 5.

That worked. This will prompt all entries to be displayed for 3 seconds:
Settings -> Input -> Bind Hold: 1

Implementing the 1-second hold requirement as a default setting for Android could significantly enhance user experience, despite making the remapping process longer compared to single taps. This change benefits regular users by ensuring they can map all controller buttons effectively, even if it takes longer than the quicker single-tap method, because regular users are not aware that you have to press button super fast as a workaround if they are not prompted. Also, it makes it easier for them to upload correct autoconfig files.

Do you think that it should it be added as a default setting for the Android release?

The "Bind Hold" workaround could be improved significantly by implementing:

• Workaround for #16217: ifdef Android and clamp it to min 0.1 instead of 0 for "Bind Hold" #17644

This would allow users to hold buttons for 0.1 second instead of 1 second.

[ * [Feature Request] Workaround for #16217: ifdef Android and clamp it to min 0.1 instead of 0 for "Bind Hold" #17644](#17644)

@zoltanvb This workaround should be easy to implement, right?

@zoltanvb Thank you very much!

@LibretroAdmin The workarounds are useful but don't solve the underlying cause. Right now I opened, referenced, and closed #17720 so you can re-open this issue.