Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a configurable workaround for Android reconnecting devices #13649

Merged
merged 1 commit into from
May 12, 2022

Conversation

phcoder
Copy link
Contributor

@phcoder phcoder commented Feb 21, 2022

Closes #3414

@ofry
Copy link

ofry commented Mar 9, 2022

@phcoder This PR has merge conflicts. Please resolve them.

Closes libretro#3414

I have investigated the issue. The crux of the problem is that on Android there
is no way distinguishing 2 scenarios:
1) 2 identical bluetooth controllers A and B and first there are button presses
only on controller A and then on controller B
2) the same controller disconnects and reconnects.
Android doesn't give bluetooth mac address of where the touch came from, only
opaque ID and this opaque ID changes after reconnect. Hence without changes to
android this is infeasible without giving up the ability for 2 users to play on
identical controllers.

I guess that this sacrifice makes sense for affected users
@phcoder
Copy link
Contributor Author

phcoder commented Apr 5, 2022

Rebased
@twinaphex can we merge this?

@MastaG
Copy link

MastaG commented May 22, 2022

So is this PR already merged into the RetroArch Plus version in the Google Play Store?
If yes, where can I find this option?

@victorviana3
Copy link

Same doubt... please give us some answer. Thanks

@javito1081
Copy link

So is this PR already merged into the RetroArch Plus version in the Google Play Store? If yes, where can I find this option?

Any response to this?

@kold666number
Copy link

Solved here: #3414 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
7 participants