Persistent Bluetooth Control Between OS's

[crogers2287]

Would it be possible to retain bluetooth pairing when switching OS's? Pairing in Recalbox then just using the controller in Rasplex once you boot into it?

[LaurentMarchelli]

Hi crogers2287,

Unfortunately I do not have the trick to copy bluetooth parameters from Rasplex to Recalbox.
But, if you find it, I will be pleased to implement the solution into the next distribution.

Best regards,
Laurent

[LaurentMarchelli]

No solution for the moment.

[substring]

hey @LaurentMarchelli ;)

Sorry to necro the issue, I thought I could be of some help.

Regarding this issue, this mostly depends on bluez version. No idea of which version rasplex uses, but it will be tricky with recalbox :

• Recalbox 4.0 uses bluez4. Paired BT MACs are stored in ~/bluetooth afair
• Recalbox 4.1 uses bluez5. Paired BT MACs are stored in ~/bluetooth/bluetooth.tar and restored at boot

Both bluez versions store data differently and are not compatible nor can be [up|down]graded
Both are resotred using the S12share init script.

Sidenote : Recalbox is officially available in NOOBS through net install ;) It will always be the latest stable update available

[LaurentMarchelli]

Hi @substring,
Thank you to have dig up this issues with this valuable information, I need to check Rasplex now, to identify where and how it stores bluetooth information.
Yes I saw Recalbox in the NOOBS install, you've made an amazing work, however recalbox-rasplex also allows the installation of unstable and and upcoming version for both Recalbox and Rasplex, as the automatic configuration of the switch between both.
I hope to have time in September to work on it.
Best regards.