Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Gadgetskopf

7
Posts
3
Following
A member registered Dec 20, 2018

Recent community posts

tl;dr fixed!  (and I found what appeared to be the problem totally accidentally) 

The paring code issue was my fault.  I'll blame old eyes for not seeing the extra 'click' I needed to get to the code screen.  Still didn't help.  I uninstalled/rebooted/reinstalled SO many times.  I even found a 'backup' folder and deleted it.  I had just gone through removing EVERYTHING and revoking all USB debugging approvals (which I had done before, to no avail). What FINALLY seems to have made a difference was going to verify developer settings were set in the app for the device (even tho they were showing up in the headset, I was getting a bit desperate here and grasping and anything that even resembled a straw).  The app did not think I had ever "completed" the setup for my Q3.  I 'completed' it by basically tapping a couple of 'next' buttons, and THIS time when I connected the USB cable to my windows machine for side loading, all the pop-ups showed up like expected.  A LOT.  I clicked through 4 or 5 "always" options for either machine fingerprints or wifi signals.  (oh!  and I got the V71 update sometime between today and the last time I wrote).

I tried with sidequest on the pc, and sidequest directly on the headset (though I did not try to install it from there, so that will be next).  I wanted to use the code, but the setting screen I have in v69 did not match your video showing how to obtain it (debug options different).  I will try sidequest directly from the headset after and uninstall/restart.

I just rebooted my headset and now QGO no longer can access ADB on the headset.  I've gone through various options, including complete removal/full reinstall to no avail.  The native SideQuest app has no problems connecting to the wifi adb.

Can the icon be changed based on the state of the setting.  Like the ADB indicator.  If the option is on it can be green, off can be red (or maybe just a different image with a slash or X through it for the 'off' state).

Any way we could get a color change for those as an indicator of which way they're set?

Oh!  Dangit, I was looking all over for that in the settings, instead of right in front of my face.  D'uh!  I remember clicking it now when I was 'poking' around.  In case you didn't see the edit I made to my original post (because you were replying to it...<grin>), QGO did notify me of the new firmware version on it's first post-upgrade launch, but none of my 'time in game' stats got reset.  Not complaining, just pointing out a difference from what was expected based on something I thought I read in the doc.

(1 edit)

Just discovered QGO.  LOVE it.  Atlantis in WMG is even MORE spectacular and there are so many games I want to revisit now.

On to the issue:  I just received the V63 update yesterday, and since that time, once QGO has been launched (and after approving wireless ADB), my quest will no longer recognize that I have removed the headset.  Front/power lights stay white.  I am running v9.5.1.  I got the notification for the 9.5.1 drop seconds after I managed to successfully install 9.5.0 (great timing, huh?)

I have verified that after a reboot, the headset behaves as it always has (screen turns off/on with doffing/donning), and once I launch/approve QGO the headset remains fully powered/active/screen on.  If I press the power button to force screen off, external LEDs remain white.

I should also note that the first time I launched QGO (apologies, but I once ran a bookstore that sold a bunch of card battle games and my brain will apparently forever after read that abbreviation at "Que-Ghee-Oh"... so sorry.....) after the firmware upgrade It did toast me with a notification that I was now on v63, but non of my "time in game" stats got reset.