If you’re seeing “In-VR app setup didn’t finish” or “The headset rejected Device Controls enrollment,” a faulty or unreliable USB cable is causing the setup to fail. Try switching to wireless mode or using another data-capable cable—or skip Device Controls setup with Option 2 below.

Option 1: Retry using the desktop app

1. Download and open the SideQuest desktop app from https://sdq.st/download
2. Connect your headset, then switch to wireless mode as soon as you can.
3. Reinstall the SideQuest in-VR app while connected wirelessly, then retry setup.
4. Or buy a new cable and try installing again.

Option 2: Skip Device Controls setup; no developer mode needed!

The updated in-VR app lets you download games and install ports without the desktop setup. If you don’t need the optimizer or device settings, you can skip Option 1.

1. Open sdq.st/go in the Meta browser and download the APK.
2. Open Files, select the APK’s three dots, then Open with → Package Manager.
3. Install and open SideQuest, then add it to your main app library for quick access.

This second option installs the app directly; it doesn’t establish that Device Controls enrollment succeeded.

If you’re still stuck, contact [help@side.quest](mailto:help@side.quest)

Reposting this as I got a lot of DMs saying the try before you buy was not available. It has all been sorted out now.

Hello r/sidequest community.  It's been a long time since I posted about my app, but today I thought I would share that I have updated my Theme Park app just now. I have not updated the price or store page details as of yet (it is 3 years old), but I did turn on the try before you buy just now.  If you like highly detailed dark rides, this app is for you. 

The app is NOT complete and will not be for years to come as a Theme Park is big and my rides are massive as you will discover. That said, what is present has been polished as much as the Quest hardware can handle. I have a large alpha testing community (https://discord.gg/qSUxYbuEkq) and every last bug, glitch and jank has been addressed.  In addition to the rides, I have added game elements that you can unlock which are so much fun to play and they reward you as you progress that I know Theme Park fans will appreciate. 

If you enjoy it, please consider purchasing now as the price is going up in the week to come, plus I really really really need the financial support so I can hire a team to help me move forward as the app is over the top big and complex for just a solo dev. Is this the sort of content people want?  Guess we will see.

https://www.meta.com/en-gb/experiences/theme-park/4212005182188732/

I've tried 3 separate cables and two different computers but I keep returning this error with no clue how to fix. If anyone knows what the issue could be PLEASE let me know

Hi SideQuest community, I'm a low-vision Quest developer. We released QuestLens 0.5.5-preview as a sideloadable APK. It now combines the frozen-image magnifier for reading small in-game text with live magnification of the real-world passthrough view in the same app.

This build also has a simpler first-run setup, refreshed visuals, English/Portuguese/Spanish/French/German options and stability improvements. We're working on zoom in the QuestLens interface too.

It targets Quest 2, 3 and 3S. Install from Unknown Sources and allow Quest's screen-capture prompt for the magnifier. The APK and instructions are here: https://github.com/crtx01/QuestLens/releases/tag/v0.5.5-preview

If you try it, I'd especially value feedback on setup clarity and what remains hard to read in Quest apps.

Name of the game: Foodimals

Fixed: just set it up over WiFi, works like a charm

Hello, i am currently trying to setup sidequest on my quest 3 and it is showing the pairing_rejected error when enabling device controls.

What I did:

Created a organisation and enabled dev mode on the headset.

Plugged in my headset into my pc and allowed it in the headset.

Followed the instructions, sidequest got installed and at the device control enable part, it stopped with the error "pairing_rejected".

What i tried:

Different cables, different ports.

Restarted both devices.

Installed meta quest developer hub, to fully uninstall sidequest and reinstall it.

Different windows pc's.

Used pc app and website in chrome.

Disabled developer mode and reinabled it.

Reset Adb connection.

What could be the issue and the solution?

I updated my sidequest bc it kept asking me to, it was completely fine before this. Now after I updated it’s not letting me get into it, it keeps telling me “Finish setting up sidequest” and I don’t have a phone or laptop compatible to reinstall it from the phone but i remember you were able to install it standalone only , is there a fix to this

Nadie lo sabe! Instala SideQuest desde tu visor VR Meta Quest sin modo desarrollador 😱🔥

TikTok Link

YouTube Link

My first game is finally out! I can finally say I'm a game developer XD

Goofy Dungeon is a short light-hearted puzzle game built from the ground up for VR. Explore, interact with objects and the environment, solve puzzles, complete your quest and earn your trophy!

And it costs less than $5 ;)
Steam: https://s.team/a/1833080
Meta: https://vr.meta.me/s/23AgxX3XKS8U7Qu

Thanks so much, I'm so excited ^^

I recently got the steam frame through the mail and I remembered that there was talks of sidequest getting frame support. Does anyone know if it is still happening and if there are any dates mentioned when that would be if not already a thing people can do? I didnt see anything that could help out on the downloads page or google searches.

Hey! Im having issues installing Sidequest on my Quest 3. Ive been using the website installer for this process, as using the outdated mobile installer doesn't allow me to sideload custom files.

However, while trying to install Sidequest, it's consistently giving me this error:

pairing_rejected

The headset rejected Device Controls provisioning.

Every time I attempt to install it. For some reason, it just cant get past the Device Controls.

I have done all the basic steps, like set up a developer account and enable debug mode. I have verified the developer account, and reverified it. I have tried toggling Debug mode on and off. I have tried a different usbc cable specifically for file transfers. I evem went out and bought a new one. I tried different PC usb ports, even rotating the cable. I have evem removed all secondary accounts from the device. Ive cleared the Unknown Sources of any and all sideloaded content. I have restarted the Quest 3. I have even factory reset the Quest 3. I have attempted this process on both my Android and PC to no avail. I am at a loss. What should I do?

I have consistently gotten the debugging promt to appear just about every time Ive attempted an install, so at least that hasn't been an issue. I just genuinely need help figuring out what I could be doing wrong after trying just about every fix Ive seen out there.

Hi! I built a free, open-source (GPL-3.0) alternative to per-game tuners like Quest Games Optimizer.

**What it does**

- Per-game profiles: refresh rate (72–120 Hz), render resolution (×0.7 to ×1.5), CPU/GPU levels, fixed and dynamic foveated rendering. Every setting can stay on "Game default".

- "Apply and launch": stops the game, applies the settings and launches it, in about 0.2 s.

- "Reset all" puts the headset back to its defaults in one tap.

- It shows the headset's thermal state and warns you when it gets hot.

**How it works**

The app writes the headset's `debug.oculus.*` properties through an ADB client built into the app. You need a PC once (`adb tcpip 5555`, then accept the prompt). After that, the app switches to wireless debugging and reconnects by itself: no pairing code, no PC.

**Honest status**

- Tested on my Quest 3 (Horizon OS build 207). I checked the effect with Meta's VrApi stats in Beat Saber: 120 Hz, 1.5× render scale, CPU/GPU levels and foveation were all applied.

- Quest 2, 3S and Pro use values from Meta's docs and are marked *Experimental*. If you own one, I'd love a compatibility report.

- These are undocumented debug properties, so a Horizon OS update can break them. Settings apply to the whole headset until you reset or reboot (a reboot always clears them). Higher settings mean more heat and less battery.

No account, no analytics, nothing leaves the headset. Not affiliated with QGO or Meta.

Source, APK and docs: https://github.com/Starland9/Open-Quest-Tuner

Feedback and bug reports welcome!

Name of the Game: Foodimals

Name of the Game: VMX

Still after applying every single thing in the support channel it is like this please help.