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
Bluetooth controller doesn't reconnect after sleep mode #193
Comments
This will b possible with SDL2 but isn’t supported by SDL1. It’s something i’ll be looking at on the next round of improvements (I.e after the next release) |
Thanks, because it is really a big problem when contrôler shut down in game with batterie low :( |
The next official release will be the last one that supports SDL1, so we can clean up the code and focus on utilizing SDL2 only. |
Hi, Sorry if I bump an old topic but is this issue already fixed with the SDL2 build ? I'm currently waiting to have confirmation that Batocera 5.24 beta on the RPI3 features this version but I'm nearly certain that this is the case. Once a game is launched, I can't retake control of the emu after my controler, 8bitdo SNES pro or XBOX360, entered sleep mode. I have to kill the emu through SSH or to plug a controler or use a keyboard (which is logical for a computer some would say but well, you know... gamers. :)) Thank you all for your help (and for the great work, anyway). |
Same for me same controller, if shut down it, and restart, it is lost by Amiberry. I must kill Amiberry in SSH to return to ES :( |
@waal As this will require some changes in the logic, I wouldn't want to risk introducing new bugs in something that has been tested already. ;) |
@midwan I'd be willing to test dev builds if this has been added. Otherwise Amiberry rocks! Tip of the hat! Workaround: While waiting for this feature, I have solved it by using jslisten to kill Amiberry process when I press a specific combination of buttons on my 8bitdo PRO 2 controller. As this returns me to EmulationStation. It works even if my controller has been sleeping. |
Please try after the latest commit above, and let me know how it works for you?
My tests were done by having a cable connected to the controller, physically disconnecting it during emulation and re-connecting it, to see how it behaves. It should do the same with Bluetooth connected controllers, but I didn't test that scenario. :) Additionally, the logfile will now indicate when these events were detected and show a relevant message (if you have the logfile creation enabled, of course). |
Followed the instructions on how to compile, but getting errors:
Compilation was execute on a recently updated RPi4 with Buster executing make -j2 PLATFORM=rpi4 |
I changed the #define AMIBERRYDATE MAKEBD(2020, 05, 08) to #define AMIBERRYDATE MAKEBD(2020, 05, 07) in src/osdep/target.h and that solved the issue. Probably an easy fix. Meanwhile I will test with my "custom" build. |
Confirmed working with my 8bitdo Pro2 Bluetooth Controller. Awesome. Thank you and a very happy Friday! |
Great!
Meanwhile, I also noticed and fixed the compilation problem.
…On Fri, May 8, 2020, 16:01 mindtripper ***@***.***> wrote:
Confirmed working with my 8bitdo Pro2 Bluetooth Controller.
Awesome. Thank you and a very happy Friday!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#193 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5ST5JYFJ7VFHPJ4XUJI73RQQGEZANCNFSM4EKR3HXQ>
.
|
As the title says. I think RetroArch and EmulationStation tries a reconnect every few seconds in the background and enables you to awake the controller during a game. Amiberry can't do this.
The text was updated successfully, but these errors were encountered: