Failed to detect audio driver. Please reboot your device to resolve.

bigmatt

Yes, it's on version v59 (59.0.0.163.706.533208642). I checked other videos that were running fine before and the same issue persists. Restarting headset does not help. Will report the bug as suggested later today or tomorrow. Thanks!

Lucy

bigmatt

natalie_seattle
Hi there, thank you for your feedback!

This issue is most likely due to Meta v59 update. We are in touch with Meta and we will let you know when we find solutions.

natalie_seattle

I'm having the same issue on a Meta Quest Pro. Restarting the headset and uninstalling/reinstalling the app didn't help. I'm using Bose QuietComfort bluetooth earbuds.

bigmatt

natalie_seattle Do you also noticed an increased BT latency with this latest Quest software update? I do. Previously I the latency on my BT headphones was negligible, I think I had Skybox set to -0.3 sec correction. Now I have an audio delay of way more than a second. I think these 2 issues could be connected.

Lucy

bigmatt LeeBox natalie_seattle kawaimahiro garlickcook Tippex ahdoor paulhouston MyEggCracked123 gyorgx
Hey friends,

SKYBOX v1.1.7(beta) is now available. This version fixed the audio issues when using some specific bluetooth earphones.

You can follow the steps to switch to beta channel and try it out.

Visit SKYBOX VR Player product detail page with browser or Meta Quest mobile app. (Make sure you login to your Facebook/Meta account)
Click "Version" and select "v1.1.7 Release: 1.1.7"
Uninstall and reinstall SKYBOX on your Quest.

Feel free to contact us if you have any other concerns.

Cheers,
Lucy

kawaimahiro

This bug still seems not to be fixed today. What's wrong with it?

Lucy

kawaimahiro
Hi there, sorry for the inconvenience. The bluetooth audio issue is most likely due to Meta v59 update. We are in contact with Meta.

garlickcook

Is there any progress? I have same problem too.

Tippex

I have the same problem with Quest 3. No other applications are affected. Ignoring this error message the play back audio is very badly stuttery. Before Bluetooth pairing my Galaxy earbuds and Quest 3 updating, audio was perfect. Please fix.

ahdoor

I have exactly the same problem when using Bluetooth headphones. Only happened in Skybox and happened to all video files.

Jenny

ahdoor Hi ahdoor, can you tell what bluetooth headphones are you using please?

MyEggCracked123

Jenny
Work around I just discovered! Start the video with the headphones off and then turn them on. It will only last for the remainder of the video though (loop or not.) The start of the next video will have a screeching sound and pause the video (just like the original reported error.)

Hopefully this helps debug!

paulhouston

This app hasn't worked for over a month now, how do we get a refund? It's clearly not being looked at. It's unusable.

gyorgx

I have exactly the same problem when using Bluetooth headphones (Samsung Galaxy Buds Live). Only happened in Skybox and happened to all video files.

Lucy

gyorgx
Hi there, we apologize for the inconvenience! After testing, we did notice that some specific bluetooth headphones will have audio issues when using SKYBOX. We'll try to fix this issue in v1.1.7. Thank you for your understanding and patience.

paulhouston

Lucy and if you don't fix it, how do we get a refund.

Jenny

paulhouston Hi there, you can follow this link(https://www.makeuseof.com/how-to-refund-oculus-store-purchase/) to refund. As software developers, we cannot issue refund for users purchasing on Oculus platform. Thank you for your understanding!

bigmatt

I updated the Quest 3 software to the latest (60.0.0193.366.548441753) and the Skybox app to v 1.1.6 but the issue still persists. I'm using the Samsung Galaxy Buds Live (2022 version) and although I don't see the error message anymore ("Failed to detect audio driver. Please reboot your device to resolve.") the audio is very choppy and unusable the same as it was in previous versions if you would ignore the error message.

Lucy

bigmatt
Hi there, sorry for the inconvenience! We'll try to fix this issue in the next update v1.1.7.