[4.1-unstable] Need testers for a bluetooth major improvement

[paradadf]

@Substring something worth mentioning is that I am not able to change the Input Player #. The controllers don't appear on the list.
Can anyone else verify that, please?

Update: I just entered a game and quit to pair a second controller, and the first controller was selectable from the list!

[Substring]

@paradadf said in [4.1-unstable] Need testers for a bluetooth major improvement:

not able to change the Input Player #

I'll try on my side. I've updated the 1st post so that people also test it for their feedback

[DjLeChuck]

@Substring Keyboard: Added with bluetoothctl works yes, that's what I used in the past. (I followed the Pairing Process part of this site: https://wiki.archlinux.org/index.php/bluetooth_keyboard)
After reboot, the keyboard is paired instantaneously and I can use it.

PS4 pad: Added with bluetoothctl too. Works great and paired after reboot.

[Mercvtio]

@Substring The odd thing is my pad seems to reconnect, but the inputs have absolutely no effect.
I did a pastebin of my /var/log/messages, but it is quite long. Do you want me to paste it here, or do I look for something in particular ?

I should add that when I try to set a pad for a specific player, my sfc30 seems to show up as a PS3 controller. Very strange.

[Mercvtio]

@Substring OK, problem settled. The PS3 controller had me wondering, and so I took a look at my recalbox.conf file. Turns out PS3 controllers were enabled, and disabling them seems to have resolved my issue.

SFC30 now reconnects just fine after a reboot and regular power cycle. Nothing to worry about !

[Substring]

@DjLeChuck supernature2k DS4 worked straight out of the box, no need to use the CLI ... WHAT HAVE YOU DONE ?!?!?

[jimmirehman]

@Substring installed over 4.1, rasp pi3, internal BT.

on first reboot it immediately told me another software update was available. but first i attempted to pair my NES30. Pair a controller instantly found like 10 devices in my area. Paired the NES 30, it was fine. turned off the controller, turned it back on via Start+R (which never ever worked before) and the controller won't reconnect. Rebooted the recalbox, still wouldn't reconnect. So i plugged it in via USB and ran the second update. when that finished it said the update turned off vibration for PSX or something. So i attempted to re-pair my NES30. Now the BT is acting like it did prior to the "Better bluetooth" update. It only finds my TV and my iMac instead a ton of devices. When it finally does find my NES30, i try to pair it, it says its successfully paired but the controller is still blinking and it doesn't actually connect.

I tried turning the controller off and back on with just START. nothing
turned it off and back on with START+R. Nothing.

I don't know why but START+R has never worked for me ever, even on the 4.0 release . I alway had to turn the controller on and off multiple times before it would just decide to connect.

Did the update after the "better bluetooth" update kill the new BT functionality? Cuz now it takes longer to find devices and only finds me TV and iMac half the time.

[supernature2k]

@jimmirehman maybe stupid question but... did you ever update the 8bitdo firmware? Start+R mode is not available in old firmwares...

[Substring]

@jimmirehman you have to switch back to the update type i mentionned on the first post, because you switched back to the unstable branch (well, ES did it for you, sadly). Once your on my branch, do not follow updates

[jimmirehman]

@supernature2k running the absolute latest release version of the nes30 firmware. Updated it this past weekend

[jimmirehman]

@Substring so switch the better Bluetooth update then once it reboots, change back to "stable" updates to kill the update prompt?

[Substring]

@jimmirehman just don't do any update once you switched to the BT specific update unless you want to get back to the "normal" unstable

[jimmirehman]

@Substring ok, giving this another shot. And after i pair the nes30, i should be able to connect it via START+R correct?

[Substring]

@jimmirehman yup. The pad will autoconnect only if the bluetooth on recalbox is already started. If it doesn't connect, Power cycle

[Substring]

@jimmirehman A few tips :

• make sure you cleared the known paired device from your pad
• forget known pads on recalbox
• try again

[jimmirehman]

Ok, went back to the "better Bluetooth" version.

Pi3, NES30 (fw: 2.70), internal BT

scanned for BT devices (tons found, no names though, only MAC addresses)

NES30, paired instantly (i know its MAC address, so i picked it from the list)
NES30, configured without issue
NES30, played games without issue
NES30, reconnected from sleep mode in 3 seconds
NES30, reconnected after recalbox reboot in 3 seconds

THIS. IS. AWESOMESAUCE.

[jimmirehman]

one issues, not related to BT, but whenever i scrape either via the scrape menu or editing the games metadata, the description and images do not save. I scraped all my nes titles using screen scraper (which is way faster than all other methods btw) but after getting the data for all 63 games, the system said it was successful but when i went to the NES section, none of the titles had the metadata. not sure if this is a bug in this particular release, but previously in the release version of 4.0 scraping worked fine.

[Substring]

@jimmirehman this is off topic

And thank you for your feedback, i'm really glad it's working that good for everyone

[jimmirehman]

@Substring i'm sorry, i wasn't sure if the scraping was broken in this release

[Substring]

@jimmirehman make a separate topic for your scraping issue, let's stick to bluetooth here please