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

[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

[jimmirehman]

@Substring This is amazing! This is how I expected the controller to pair and function with recalbox. It was such a crap shoot turning on the RB and hoping my controller would pair with it everyday, often taking 5-10 minutes of power cycling the controller.

Now it is FLAWLESS! Thank you thank you thank you

[Substring]

Thank you everyone for yoyr feedback this will be added in the next ynstabke release

[jimmirehman]

Just bought a nes30pro, got it to pair initially but it won't reconnect. I hold the power button to turn it on, I think that's all I have to do on this model for it to reconnect but the blue LEDs just keep blinking. Any suggestions?

[paradadf]

@jimmirehman haven't you tried simply pairing it again?

[jimmirehman]

@paradadf yeah I did and it would just immediately say paired. I just deleted all controllers and repaired them both. All is wellmow

[badges3000]

I paired a Wii U Pro Controller and a Wii Remote Plus. The Wii U Pro Controller has a delay (around 1s) when pressing any button. On the Wii Remote it was impossible to map the joypad, only up and down worked, no left or right. I juse the internal bluethooth on the ri3.

[Substring]

@badges3000 We know the wiimote is buggy, we need to patch its kernel driver. But regarding the lag ... This can happen in a "noisy" environment (in the bluetooth band i mean). But taht's something i may not be able to fix

[Substring]

I'm closing this thread since the changes have been merged in the main unstable. Please comment further bugs in the main 4.1 unstable thread.

Thank you everyone for your contribution !