I've tried two devices now, on two networks. Both have got stuck downloading the device update during setup. The blue progress bar almost reaches the end but then it just stops. Anyone else experienced this? Any solution? I've tried rebooting, it just goes back to the downloading update screen...
Running Android Pie. Pixel 2. I really don't think it's anything to do with the phone. The problem is on device. As soon as it learned my WiFi it started the download and then just hangs. The blue bar never fills.
Same here. But I think it is while the setup procress. That means the headset is updating infos while the setup. Just go through it to the end on your phone.
Meta Facebook Community Accelerator 2022 winner Facebook Community Partner Founder of the Meta Quest VR Familie - The largest German Facebook Group for VR and Metaverse https://www.facebook.com/groups/oculusvrgermany/
Same here, it's been stuck with the updating screen for ever. My phone app wont let me finish setup , in the middle of it , it says that he can't find the headset, even though in the main menu it clearly says the headset is connected to the phone. I'm wondering if I need to do factory reset.
I am running into this as well. Tried with both stock iPhone X and iPad. Have done multiple factory resets and tried on multiple wifi routers. Not sure what to do. Just stuck on downloading screen with bar at 50% and phone first says "something went wrong try again" and then I get a headset did not connect message. Frustrated here....
I figured out my issue. Must be something with my home network (maybe firewall?). I had it connect to the hotspot on my phone and it seems to be working now....
I had the same issue and fixed it. I had my phone on my cellular network and if you are like me, you might have more than one home network. Make sure the network connection you choose for the Quest is the same wifi network your phone is on at the time of the setup. It actually worked on the cellular network up until the update, so it can fool you.
I hope this helps some of you out.
On a side note, took me FOREVER to give you guys this answer. Their servers were throwing "too many requests" (429) when trying to login. Guess launch day for 2 products overran their services a bit.