Quest Games Optimizer
v12.2.3 is available and fixes, among other things, the problems caused by v74
Hello, I've just pushed v12.2.3, which fixes, among other things, the problems caused by v74.
- QGO was no longer updating
- the Home environment profile no longer applied
- QGO froze at times and some menus were not always displayed
The rest of the updates can be found here: https://anagan79.itch.io/quest-games-optimizer/devlog/360224/changelog
I remind you that even though this version of QGO now works with v74, it's wiser to stay with v72 until v74 is official and bug-free. Today it's still a buggy beta version, as always.
v74 has broken the installation and updating of apk files, which means that for the time being, it is no longer possible to install applications (apk files) directly from the headset, or even to update them. Everyone is affected.
If you are on Meta Horizon OS v74 and your QGO version is less than the v12.2.3, you must install the update via other methods. See the Tutorials to do that with SideQuest Advanced Installer (PC app) or Meta Quest Developer Hub (PC app), or Bugjaeger (smartphone app), or ADB Link (PC app)
Anagan79
Files
Get Quest Games Optimizer
Quest Games Optimizer
Unlock the full pontential of your Quest. Make all your Quest games better
| Status | Released |
| Category | Tool |
| Author | Anagan79 |
| Tags | anagan, game-optimizer, game-tuner, graphics, meta, oculus, performance, qgo, sidequest, Virtual Reality (VR) |
| Languages | German, English, Spanish; Castilian, Spanish; Latin America, French, Italian, Portuguese (Brazil), Chinese, Chinese (Simplified) |
More posts
- Quest Games Optimizer has reached 100,000 users39 days ago
- New QGO official Website & affiliate links & more48 days ago
- Install QGO on secondary account74 days ago
- +900 games have been officialy optimized by QGO98 days ago
Comments
Log in with itch.io to leave a comment.
Hi, please add Russian in the future
thanks, any chance you could release a profile for IB Cricket? I think it's the only cricket game that doesn't have one and the game is massive! Cheers
Will add it in the todo list
thank you!
Idk if it just me or if anyone else this problem with the ADB. FYI I had installed QGO v11.1.0 on both the Quest 1/2 before which did work until I tried to update v12.2.3/v12.2.4 while I haven't use both Quest 1 & 2 in a while. For Quest 2 (v72), I tried to enable the adb through the pairing code solution. It paired successfully but I couldn't tell if the adb is enable or not, it not showing green nor does it show red, the adb just showing grey without the small hourglass next to it. I made sure to restart but nothing changed, still showing as grey. For Quest 1 (v50), I tried to enable the adb with usb connection (the only solution), I click retry and the popup came up to allow wireless debugging. I click the "always" and it shows the adb with a small hourglass next to it for a while. I restart the headset and tried to open the QGO. It shows the adb still red and what happen is that the screen will go black, loading circle, and shows the QGO menu over, over, and over again. In between the black screen and the loading circle the "Enable wireless debugging" popup will show for a split seconds before disappearing so idk what is happening. Keep in mind I did do the uninstall, restart, and reinstall QGO solution but nothing changed. Strangely, when I install the old versions of QGO (v11.1.0) and did the whole enable adb with usb again. The issue happen there too but the "Enable wireless debugging" popup stay there instead of disappearing quickly until I hit "always" which the popup keep coming back. So something is going on with "Enable wireless debugging" popup but not sure what is happening.
Hello, using old QGO version or old Meta Quest firmware version isn't a good idea. I develop QGO to run with the latest firmware available. SO if you are using a v65 or 69 for example, I can't assure you QGO is still working on these old firmware version.
Many of the previous QGO version doesn't work anymore.
Not using your headset for very long can also cause ADB to deactivate.
I removed the hourglass next to the ADB icon since a long time now. So the ADB icon must be either green or red, but can't be gray. If the color is grey it could be because you changed some things in color settings in the headset. If this is the case, can you screenshot me that ?
When ADB is enabled, you can start a game with a profile and if you receive the applied profile notification this means ADB is working, or you can run a command in the ADB Shell terminal or change the proximity sensor or guardian option to see if it works. Also if you don't have the banner that tells you ADB isn't enabled this means ADB is enabled. For me, you just changed something about colors.
In recent QGO versions, QGO ca bypass the ADB wireless debug prompt, so that people don't have to see it anymore (if auto detect mode is enabled).
Anyway, you should uninstall QGO, then restart your device and install QGO v12.2.4 on a v72 on your Quest 2.
Then come back to me.
You can share screenshots and videos if needed to help me to understand better
Hello,
I'm able to reproduce your color thing. It seems you enabled the High Contrast Color ;-)
=> https://drive.google.com/file/d/1kx1MjOodOYVaZsjz6sGCP9ALDMwBN6rc/view?usp=shari...
About your Quest 1, I saw your video, I don't have Quest 1, so I can't confirm latest QGO versions are still working on it. But as you can see QGO doesn't seems to have the same behaviors and the QGO view is way bigger (I had to make it big because of v69) to fit the correct size after this v69.
Firmware v50 is really too old now...
QGO is designed to run on latest firmwares because Meta broke too many things in all the firmware, so the QGO behavior fits teh more recent ones.
Ah, thx for letting me know that it was due to the High Contrast Color. To be fair I knew that the High Contrast Color was enable, but in my defense when I had v11.1.0 installed it still show that ADB has green color even when High Contrast Color is enable. As for the quest 1, I kinda expected that to be the answer. However, I do want you to know that QGO did work on the Quest 1 with v11.1.0 at the time I installed it which was last October 2024. Plus, not to mention, you do have the quest 1 listed as compatible.
Okay thanks for letting me know.
Could you join me on discord, I would love you do (if you are okay) some tests for me as I don't have the Quest 1.
Need to know what is the latest version that works great with Q1 (perhaps some after the v11.1.0)
I think the 12.1.0 should also work.
Buenas tardes mis gafas quest 2 se quedaron en la v63 y no consigo actualizar ; algún sitio donde pueda descargar ?
You should try to d a factory reset so that your headset is clean and ready to receive the new Meta Quest updates
ADB stopped working (did't update the quest)
None of the solutions works since clicking in the Tutorial button does nothing
Something if broken for some reason
Tried a restart, tried to re-enable debugging (usb and wifi), re-installed QGO, and nothing
Hello, I guess you can't open the tutorial because you have uninstalled Oculus/Meta Quest Browser ?
Tutorial can be found on my Itch page and here : https://www.quest-games-optimizer.com/tutorials-videos
Did you try the pairing code method ?
Did you try to uninstall QGO, then restart the Quest (important) then install QGO again ?
Hello! I have the browser ( I use it ) but those buttons does nothing.
Anyway I searched for the youtube videos and managed to enable it. My problem is that I was searching for a tutorial with the name "ADB" and it was inside the main tutorial. Sorry, I did that a while ago and forgot it was an all in one video. Thanks!
Oh you're right, I did shit in the latest update... Will have to fix the browser...
v12.2.4 is coming
https://www.youtube.com/watch?v=73HFzJEQGuA&list=PLIdRYcemAgleZ4Xp_3k_STNn3Xw1D0gwc
Edit : I pushed the update, thanks a lot for the report of this bug
Android has changed the way for pairing for wireless debugging, now the IP with port and the code must be entered, not just the code. So solution 1 is now basically not working any more for adb, only solution 2 works but it is kind a hassel. Hope you will fix the way debugging work for solution 1 so it can run on its own.
Hello, don't worry it's working with the pairing code, I did install QGO almost 10 times yesterday before to push the new update to be sure it worked.
You don't have to enter the port as QGO is able to get it automatically.
Can confirm what @ntm2301 says.
Every time I open up the wireless debug settings, and then open the android pair code popup, port changes. And as i can see in the QGO settings, it doesnt handle the new port in the popup.
So basically without possibility of entering wireless debug port manually, solution 1. is not going to work.
I'm currently on V72.
Did you try to toggle OFF then ON the wireless debug toggle button then generate a new pairing code ? This should do the trick
I have tried toggling the button multiple times, after updating to latest version of QGO. The QGO kept declining the pairing code, as being wrong. So I've uninstalled QGO, installed it again, but still didnt worked.
Fortunately for some unknown reason it started working as always after I restarted the headset.
Maybe I've got some corrupted update from Meta (even through I'm not in PTC), or something...
Yes in the little lines in the left part of the ADB Slider panel in QGO I suggested to restart the Quest. When restarting the Quest, the device cleans some things on network.
Hi, I uninstalled and reinstalled the QGO and everything works perfectly now. So there must be some bug lurking around when updating the app. Clean install will not have the problem.