8bitdo SF30 Pro and SN30 Pro
-
@theelite1x87 That's great news. Perhaps leaving your connect mode as 'default' allowed the left/right triggers on the "Android" profile to finally work.. as my (undesirable) results were tested on the v1.22 firmware with connect mode left on 'background'. Didn't even think to change it.. I'll retest everything tonight.
-
I've re-connected my controllers (SN30 Pro) in Android mode. So far so good -- it appears all is working quite well. I loaded a N64 game and did notice my triggers responded so that is also good news.
I'll keep testing out more. Thanks everyone for the good feedback!
-
I retested the v1.22 "Android" profile with udev settings in place.. but this time I changed the connect mode to 'default'. Not sure that had much effect since I couldn't get the left/ right triggers to recognize at first. The difference happened after I immediately tried configuring the buttons again without exiting the EmulationStation start menu. Somehow the left/right triggers became recognized on that 2nd attempt! I was able to repeat this bizarre behavior after exiting the start menu, going back in, & configuring my controllers again; triggers were only recognized on a 2nd config attempt following the incompleted first.
The fact that others don't face this hurdle could be attributed to my tests since older firmwares. Maybe some conflicting configuration files were left behind as I upgraded... who knows how RetroPie was reacting behind the scenes.
Bottom line, the "Android" profile is definitely solid now, not to mention its full analog range.
One thing to note, however, is that the controllers' Hotkey(Select)+Start combination that exits an emulator doesn't work in N64. As luck would have it, pressing the left/right triggers together exits N64 for me. Some N64 games even exit when pressing left-trigger+Y. Very wierd.. although I'm aware that N64 is not exactly RetroArch-friendly. For that reason, I can live with these varying exit button combinations. Good news is that the other consoles (Genesis/32x/NES/SNES) still exit as expected to Hotkey(Select)+Start.
-
connect mode should always be left at "default" unless you have a controller that will not reconnect once powered on (it's a hack that forces a reconnect attempt every 10 seconds or so). for my 8bitdo controllers, "default" is fine.
-
@louiehummv said in 8bitdo SF30 Pro and SN30 Pro:
Somehow the left/right triggers became recognized on that 2nd attempt! I
This can even happen on a fresh install. Had this problem with my 8bitdo Sfc/Snes30 and Nes30 Gamepads.
-
Did more testing.. figured I'd update the record. "Android" profile remains best.
As of firmware v1.22, 2017-12-20:
Confirmed Issues
- "Switch": analog range is only 85% (-27391 to 26966 instead of -32767 to 32767); turbo feature not recognized
- "Mac" : reconnection established only after reboot when connect mode has been set to 'boot' or 'background'
- "Windows" : left & right triggers aren't recognized
- "Android" : acceptable; may need to configure controller input twice (a 2nd attempt immediately following the 1st) to get EmulationStation to recognize the left & right triggers; note this profile's Hotkey+some-button combinations vary in N64 emulator per game
Confirmed LEDs
- "Switch" : all 4 LEDs cycle back-n-forth
- "Mac" : the first 3 LEDs blink repeatedly
- "Windows" : the first 2 LEDs blink repeatedly
- "Android" : the first LED blinks repeatedly
Confirmed Profile Selection Buttons
- "Switch" : START + Y
- "Mac" : START + A
- "Windows" : START + X
- "Android" : START + B
Confirmed Bluetooth IDs & Name (SN30 | SF30)
- "Switch" : 98:B6:E9:42:--:-- Pro Controller | 98:B6:E9:42:--:-- Pro Controller
- "Mac" : E4:17:D8:20:--:-- Wireless Controller | E4:17:D8:CF:--:-- Wireless Controller
- "Windows" : E4:17:D8:20:--:-- 8Bitdo SN30 Pro | E4:17:D8:CF:--:-- 8Bitdo SF30 Pro
- "Android" : E4:17:D8:20:--:-- 8Bitdo SN30 Pro | E4:17:D8:CF:--:-- 8Bitdo SF30 Pro
Notes
- Hitting only START button activates previously selected profile
- Firmware receive mode activated by LEFT SHOULDER + RIGHT SHOULDER + START
- click for manual
- click for support/firmware
-
Hi. I just bought the SN30 pro and it seems i cant get Y working and X button is L1 somehow in retroarch on android. Anyone knows if its possible to fix?
-
@dracule There are many unknowns to your setup. Please update RetroPie to the latest version, upgrade your controller firmware to v1.22, & follow the suggestions/links on this thread to configure the "Android" profile on your SN30 Pro.
-
Just a note that firmware v1.23 has been released. Below are the details.
Firmware v1.23
Enhanced vibration optimization on Xinput mode.
Added USB connection to Mac mode.
Fixed the bug that the controller would not turn on occasionally.- Press and hold L+R and then plug in USB cable to update the controller if it does not power on.
Edit: Not sure if it was just me or not, but after I did the firmware update to v1.23 I had to remove the bluetooth devices and reconnect them. The controllers also seemed to turn on default to "Switch Mode". So I returned them to "Android Mode".
-
Hello - I just bought the SN30 pro - I've had similar problems like others here, but this has been very helpful.
I'm having one problem that folks here haven't mentioned. I can't seem to enter the settings for the individual emulators / cores. For instance, when I load up a game, before it starts, I get a splash screen telling me to hit A to configure. Normally this works, however my SN30 pro doesn't allow me to do this (firmware 1.23).Has anyone had any luck doing this? Is it not the traditional A button anymore?
-
@action937 I know I was able to get into those setup screens. I don't recall what button I hit, but I want to say I used "Start". I can test later and confirm. I am running in Android mode.
-
I'm in Android mode as well - sorry ... didn't mention that.
-
@action937 I didn't realize that splash screen actually meant the A button.. thought it meant 'a button' as in any button. In light of that, I'm using the same controller, 'Android' profile, firmware 1.23, under RetroPie 4.3.. and only the A button works for me.
-
Sorry for the delay but I have the same results. The "A" button is what gets into that screen. I am in Android mode.
-
Just got an SF30 Pro. Upgraded to v1.23, ran udev, in Android mode. Not able to use the left or right trigger buttons. :/
-
I can confirm that SF30 Pro on newest firmware (1.23) works in Android mode. I just updated my retropie today, and I'm using a Pi3 with Berryboot. I added udev, kept connection type to "default" and had to setup the controls twice to get the triggers to work. There are no disconnection issues, and if the controller is turned off it reconnects without any issue. Thanks for everybody's help in treading this path before me. This is a fantastic controller for retropie!
-
This post is deleted! -
Guys i am absolutely ripping my hair out over this!
I have two SF30 controllers, and i have tried everything I have read online and i can still not get the following things working consistently;
1: Controller does not pair after reboot (I have tried udev, doesnt work for me)
2: Cannot connect both controllers using the same method. I was always connected on SWITCH method which i did manage to get working. Now i have tried to do the same with android method in light of above comments, and it simply refuses to work. I pair one without an issue (apart from the controller going into pair mode constantly while in the bluetooth menu afterwards) but no matter how many times i try it will not pick up the second controller using android mode. I am at a loss here, and feel like ive tried everything.I had some success pairing one controller with android and the other with switch mode, however one controller (switch mode) had the worst input lag while the other one was working perfect.
I really just want these controllers to work as they are awesome.
If anyone has any suggestions on what i could be doing wrong please let me know
-
Also just to add some other things i have tried.
I have turned off wifi
updated to latest RP version
updated to 8bitdo firmware latest version
switching off the paired controller while putting the unpaired controller into pair mode
pressing the udev option (this always just says its already done, it doesnt seem to ever forget this somehow even when i remove the connected devices from the list)I can probably think of other things i have tried, but yeah its just driving me mad, might have to send one back at this rate because i dont see them ever working without lots of faffing.
#plshalp
-
@wutangdan88 There are a few recommendations across this topic:
- Update to the latest firmware
- Start the BT Pairing with the controller in Android mode.
Are your controllers identical ? How did you install your system ?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.