Intiface Central on Linux doesn't reconnect to device until engine is restarted

Intiface® Central Support
1

I’ve noticed that when a device gets disconnected from Intiface Central 3.1.1 running on Arch Linux, the only way to get it reconnected is to fully stop and start the engine. The same behavior does not occur on Intiface Central 3.1.1 running on /e/OS (Android 16), where devices reconnect automatically while within range.

I can see that the behavior is not specific to the connected device or device manufacturer. I tested with four different devices from Lovense and WeVibe, and found that on the Intiface Android app, when carrying the phone out of Bluetooth range, all devices become disconnected, but then reconnect automatically on returning to range. While on the Intiface Linux application, when doing the same with the laptop, all devices become disconnected, and fail to ever reconnect until the engine is restarted.

My laptop hardware is Framework 13.

Does this point to an issue in Intiface Central? If not, what information could I collect to identify the source of the problem?

2

It’s probably a bluez issue, either in buttplug’s event handling from btleplug, or btleplug itself.

3

Oh cool - Should I file a bug? Is there some logging I should enable or test I could run that would help to determine which component needs a bug report?

(I’m also happy to try and look at the code myself if that would be helpful.)

4

Yeah, file something on Intiface, since that’s where it’s showing up.

Debugging help is appreciated, though setting up that specific build chain is not exactly fun. There’s commented out patch sections in some of the cargo files for pointing dependencies at each other as long as they share a root, but I’m not sure they’re everywhere you’ll need them.

1 Like
5

Cool - filed Linux app doesn't reconnect to device until engine is restarted · Issue #286 · intiface/intiface-central · GitHub - and if I’m able to do any investigation, I’ll post notes there.