DeoVR app v15.5.3662 update = broken bluetooth functionality on Quest 3

slrdigital

DeoVR app auto-updated yesterday on my Quest 3 to version v15.5.3662 and appears to have broken Bluetooth multi-device functionality. After this update I can no longer connect more than one Bluetooth device simultaneously on the Haptics setting page in DeoVR.

Steps to Reproduce:

Open Haptics setting page in v15.5.3662.
Connect a Bluetooth device (e.g., handy).
Attempt to connect a 2nd device, 2nd device connects.
Result: The 1st device is immediately disconnects, allowing only one active device at a time.

This multi-device sync connection worked flawlessly on v15.4 and all previous version, and broke immediately after the v15.5 update got applied. Does anyone know a way to fix this or roll back to DeoVR version 15.4 on Quest 3?

JordanSLR

slrdigital, thanks for the details, we'll check

JordanSLR

slrdigital, what toys are you trying to connect?

slrdigital

JordanSLR Handy x 3 via bluetooth. Worked perfectly on v15.4 and all previous versions. Broke immediately after the 15.5 update was auto-applied.

*** Please explain how to roll back on Quest 3. How can we roll back to v15.4??? This 15.5 version is broken and the update automatically applied with no warning, breaking a critical feature in the process. When I check the release channel sub-menu in Quest 3 Apps page, there is no prior version listed. PLEASE ADD v15.4 BACK AS A SELECTABLE RELEASE CHANNEL OPTION so we can at least roll back to a working configuration.

slrdigital

@Kieshi , @JordanSLR , any help here please?

Summary: The v15.5 update has broken the ability to connect multiple Bluetooth peripherals simultaneously on the Haptics settings page (SexLikeReal domain). In v15.4, connecting 3x Handy devices worked perfectly. Now, connecting a second device immediately kills the first. This is an app-level regression, not a hardware limitation.

Please add v15.4 as a selectable Release Channel in the Meta Quest store immediately. Currently, only v15.5 is available, leaving users with multi-device setups completely bricked with no way to opt-out of this broken build. Adding the previous stable build to the "Version" dropdown in the Quest Store is a standard fix for major regressions.

I suspect the culprit is the new "Automatic Reconnect" logic introduced in v15.5.3662.

The Symptom: The app appears to be monopolizing the Bluetooth radio.

The Theory: The reconnection script is likely performing a "soft reset" of the Bluetooth stack or GATT server whenever a new handshake is initiated. In v15.4, the app likely deferred to the Quest OS to manage concurrent HID/LE profiles. v15.5 seems to have implemented a more aggressive, single-profile polling loop that doesn't account for multiple concurrent haptic streams, effectively "kicking" existing connections to ensure the newest one has exclusive access.

guywithtaste

slrdigital Don't worry, I complained about them breaking XBVR compatibility 3 months ago and I am yet to see a fix or hear back about it, even though they are "looking at it". At this point they fix a thing and break 2 others so I wouldn't get my hopes up. Deo has been broken for a long time and the only thing they have any desire to fix is the ones that make them money. At this point I wouldn't be surprised if they made bluetooth usage a subscription so they'd have a reason to fix it. And yeah they don't offer previous versions of their software ever so it just is what it is until they maybe fix it probably not.

guywithtaste

Their focus seems to be on DeoVR Hyper, which itself is a hot mess too, and can't even be used on many devices...

doublevr

guywithtaste hyper works great on quests and avp's with new features coming with every update.

I can't think of a single deficiency for people who want to enjoy vr with no hassle

Pcvr is dead

SchnuppiLilac

I can't think of a single deficiency

JordanSLR

slrdigital, we're investigating the case

Aeria

slrdigital Hi, we identified an issue and will be rolling a fix for it. Running multiple same type devices through bluetooth is improved and also adding some naming changes to differentiate between different Handy versions in player.

When connected, the Bluetooth identifier eg. OHD_hw3_device-UID is displayer when clicking on more info so you can better know which device is which (eg. connecting 3x Handy)

slrdigital

Aeria , Thanks for the quick confirmation and the UID identification fix, that will be a significant UX improvement for multi-device users.

Could you provide a quick update on the rollout strategy for this fix?

Is this being pushed as a hotfix (e.g., v15.5.3664+) to the Main Channel?
Will a pre-release build be available on the Beta/PTC channel sooner?

Knowing the target build number or channel would help me keep an eye out so I can verify the fix for you as soon as it drops.

Aeria

Likely available by end of week on PTC, Prod next week.