A way to retry Autocapture (Oakley Meta Vanguard)
Was wondering if anyone knows a way to retry an attempted auto edit of a bunch of clips that were taken via Autocapture. I ran a 10k recently, and all of the clips were imported, but the auto-edit failed and some clips didn't fully get processed (still have the raw fisheye look to them). Before the error was dismissed, I think it read something like "error with cloud import". (I have cloud backups on) Is there any known way to "redo" the import or attempt to re-edit the clips? Now I'm just stuck with a handful of full-processed, non figheye'd clips in a sea of raw captures that aren't usable. Thanks!
[HELP] Can't reconnect Spotify on Meta Ray-Ban
[HELP] Can't reconnect Spotify on Meta Ray-Ban after factory reset – Connect button doesn't open Spotify auth screen Hi, I'm having an issue reconnecting Spotify to my Meta Ray-Ban after a factory reset. Here's the full timeline: **Timeline:** 1. **First setup** – Connected Spotify successfully, everything worked fine 2. **Factory reset** – Lent the glasses to my sister after resetting 3. **Factory reset again** – Got the glasses back and did another factory reset for my own use. Now Spotify no longer works **Current symptoms:** - When I say "Play music on Spotify," the glasses respond: "I can't do that on your glasses" - In the Meta AI app, when I tap "Connect Spotify", it does NOT redirect to the Spotify authentication screen at all (it did redirect during the very first setup) - Despite no auth screen appearing, the app shows Spotify as "Connected" immediately after tapping the button — as if the connection succeeded, but it clearly hasn't - The connection simply does nothing — no OAuth screen, no error message **What I've tried:** - Disconnected Spotify from Meta AI app (Device settings → Connected apps) - Disconnected Spotify from Instagram (Settings → Apps and media) - Revoked all Meta/Instagram access at https://www.spotify.com/account/apps/ - Cleared Spotify cache on iPhone - Logged out and back into Spotify **My setup:** - Meta Ray-Ban (Gen 2) - iPhone - Spotify Premium The fact that the app shows "Connected" without even opening the auth screen suggests a broken/cached connection state is stuck somewhere on Meta's backend. Has anyone experienced this after a factory reset? Any fix appreciated.
New Quest 3 locked on software update, impossible to fix.
Hi guys, I bought my first Quest 3 today. When I turned it on, it started a software update but it gets stuck there — the device keeps turning on and off without completing the update, and I can’t get past that screen. I haven’t even set up my Meta Horizon account yet, and since I didn’t purchase my Quest 3 through the official Meta store, when I try to enter my device’s serial number on the website it gives me an error. I tried doing the sideload update (the only fix I found on the internet) by holding the volume down and power buttons on the Quest 3. But when I select my device in the browser, I get a message saying: “your device is not supported, please try reconnecting your devices.” Weird cause both my PC and Chrome are detecting it as Quest 3. I also tried disabling adblock, deleting caché and cookies, incognito mode, other browsers, other PCs, other cables, connecting it on different times, etc. There is not a single thing I haven't tried. (Every single one of these attempts were done while having 50% battery. There’s nothing else I can do, literally — I’ve already tried factory reset several times as well. Do I need to return my device? I'm submitting this post so support can help me. I'm quite desperate, I don't see my issue anywhere on google and I spoke to support via Whatsapp and everything they told me to try, I already had.
Mic issues on Meta Ray-ban Display
Hi! I have been using it daily since October and I love the day to day with it on my updated Android. This morning I ran into a problem: the microphone on my glasses stopped working on my phone. My main case of wearing glasses is still using them as a headset for calls and sending voice messages. It is updated to the last version available. I've tried factory restoration (also unpair and re-pair) and nothing. I already had a first generation with a very similar problem, but there it was possible to remedy the problem by activating an option in the app settings. However, we do not have that option here. Anyone else with this problem and/or solution?
Oakley Vanguard's Microphone not working since last software update
Happening to me now, 6 months old and used maybe 10 times. I have done everything the terrible Meta support pages suggest. Un-paired and re-paired. Restored to factory Cleared the speaker. Uninstalled and re-installed the software on my phone. Release version 124 and since then the glasses dont respond to Hey Meta or OK Meta and nobody can here me if i answer a call or try and respond to a WhatsApp message. Strangely though if i want to use the translate function that works just fine, go figure. I have removed all app connections that i had previously setup, tried in English UK and English USA langauges, nothing works to get the glasses to hear the Hey Meta or OK Meta voice prompts.
Issue: Quest 3 controllers always fall back to “Oculus Touch Legacy” in SteamVR games
Hi everyone, I recently switched to a new Meta Quest 3 from meta warranty services, i continue to use my same Touch Pro controllers and I’ve been stuck with a very frustrating issue: In the SteamVR menu / dashboard, the controllers show up correctly as Quest 3 Touch Plus (blue laser, correct 3D model). But the moment I launch any SteamVR game, SteamVR switches them to “Oculus Touch Legacy Bindings”. In-game, the controllers look wrong (smaller, with tracking rings, purple lasers) and are miscalibrated (like held backwards in Paradiddle, drumsticks pointing the wrong way). With my previous Quest 3 on the same PC, everything worked perfectly out of the box (no tweaking, games launched fine with the right bindings). --- What I’ve already tried (nothing worked so far): Full factory reset of Quest 3, complete clean reinstall of SteamVR and Oculus PC app, deleted every config folder and registry keys (AppData\Local\openvr, Steam\config, Roaming\SteamVR, Oculus folders, etc.). Tested both SteamVR Stable and SteamVR Beta. Stable → no oculus_touch_plus profiles exist → always falls back to legacy. Beta → includes Touch Plus profiles, but some games won’t even launch properly. Manually added custom bindings_oculus_touch_plus.json and oculus_touch_plus_profile.json into SteamVR\drivers\oculus\resources\input\ and Steam\config\input\. → SteamVR still insists on using Legacy inside games. Disabled SteamVR Home, disabled Steam Input (globally and per-game). Tried forcing Oculus runtime (-vrmode oculus / -oculus) in launch options. → Works only for some Unity/Unreal titles, not for all. Confirmed in SteamVR Developer > Input Debugger → games always load oculus_touch (legacy), never oculus_touch_plus. --- Summary SteamVR Stable right now does not ship oculus_touch_plus bindings. My old Quest 3 worked perfectly (must have been on a version where they were included). My new Quest 3 is stuck in Legacy mode for all games → broken calibration and wrong models. Only way it works correctly is launching games via Meta Link library or Virtual Desktop (bypassing SteamVR). --- What I need help with Is there a way to force SteamVR Stable to always use oculus_touch_plus globally for Quest 3? Or is this simply a bug/missing feature in the current Stable build of SteamVR? Has anyone else solved this without being stuck on Beta (where some games won’t launch)? Thanks a lot — this issue has been driving me crazy because my previous Quest 3 worked flawlessly, but the new one refuses to use the right controller profile. ---Quest controllers Idle off is way to sensitive
As the title says, in the past few updates or so setting the controllers down will instantly set the controller off.. This can also happen when laying down or even standing still in a pose with the controllers still in-hand or sitting with your hands on your lap. We need a way to either disable this 'feature', or allow us to set the idle timer with a max of never.
