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