Post by Varset in Local effects of adb commands

Viewing post in Local effects of adb commands

Sorry for the Cyrillic in the previous post, I corrected it.

I don't know how these functions are implemented in QGO and QGT. You can talk to the developers, I talked to the author of KUGO on another topic, he is a wonderful person.

As for the functions, I would personally do it this way: before the game and when launching the QGO or QGT programs, save the current headset settings in the default profile, and restore them when the game returns.

Almost all the settings are described here:

https://developers.meta.com/horizon/documentation/spatial-sdk/ts-systempropertie...

You can also download the Kvass source code from GitHub and see what commands I use:

https://github.com/Varsett/Quas

If you have any questions, I will be happy to explain.

Unfortunately, I don't have any knowledge of Android, so I can't say how exactly to determine that the game is finished, but I think there are many options to determine the end of the process.

cgapk105 days ago

Thank you.

I've previously used adb dumpsys activity lru polling queries to detect if a game exits in order to restore the default configuration on execution, but they all failed. In fact, I tried multiple adb detection application scenarios such as adb shell ps -A | findstr “com.beatgames.beatsaber” and they all failed.

I also tried how to auto-scan for filling in the port number in wireless pairing so that the user only has to enter the pairing code, but that failed as well. The libadb.so I'm using is this: https://github.com/thedroidgeek/oculus-wireless-adb

I've also tried consulting the authors of QGO or QGT about how manual wireless pairing debugging works and localized game configurations related to it, but they both refused to answer any questions citing trade secrets. I just want to develop an open source free Quest image quality adjustment tool, but I can't find any documentation tutorials about it...

itch.io

Viewing post in Local effects of adb commands