itch.io

A Total Commander-style file manager for your Meta Quest / Android device.

Tired of poking around your device's files through raw adb commands in a console window? Quas ADB Commander is a dual-panel file manager in the classic Norton/Total Commander style — your PC on the left, your connected Quest (or any Android device) on the right.

What's inside

📁 Full hotkey-driven file management — F5 to copy, F6 to move, F7 to make a folder, F8 to delete, all the classics. Move files between PC and device in either direction.

📝 Built-in text editor — with syntax highlighting and automatic encoding detection. Open a file from the device, edit it, hit save — it gets pushed back automatically.

📦 Full archive support — browse .zip/.7z/.rar archives like regular folders, extract and pack on the fly. You can even edit text files directly inside an archive without manually unpacking it — save, and the change is written straight back in.

📲 One-click APK/XAPK/APKS installation — with automatic OBB detection and transfer, including split-APK packages.

⚙️ Application Manager — a complete app management panel: uninstall, disable, clear cache, view status, see running processes, extract APK/OBB to your PC, restore removed apps, and more — no manual commands required.

Nothing extra to install

Everything's already bundled in — adb, aapt2, 7z, and everything else you need. Download and  run adbcm.v9.63en_setup.exe, connect your device over USB with debugging enabled, and you're good to go.

Feedback and bug reports welcome! Full description of all features on the release page..

Project link: https://varset.itch.io/quas-adb-commander

Unfortunately, I don't know about this.

Try opening the script in a text editor and searching for the line adb shell setprop. I'm sure you'll find exactly what you need.

In my program all text messages are also translated into English. You can view the code in the file quas_v4.3.2.eng.cmd starting with the label _streamingmenu.

Also note the labels _menugpucpu and _resolutionfix in the code.

I think this will help you find out how to connect:

https://source.android.com/docs/automotive/virtualization/tools?hl=en

Unfortunately, I don't know if mdns is enabled by default on smartphones or not, I only know about VR headsets for now.

To view the application status I use this command:

adb shell dumpsys package %pkgname% | findstr /i /c:"User 0: ceDataInode"

But, unfortunately, the stopped parameter does not display the real state of the application. Perhaps there are other similar things in dumpsys, but I have not looked for them yet.

p.s. Found one clever and quick way to determine whether an application is running or not:

adb shell pidof <package_name>

If a PID is returned, the application is running. If an empty string, it is stopped.

I can probably help with the search for IP and port. For this, I use an exe file that scans devices using the mDNS protocol and displays the IP and port of the found device. This application was written at my request specifically for the Kvass program, but I do not have the source code. It is called AndroidMdnsDiscover.

But there is another option, in Python, it does about the same thing, but less convenient - there you need to pre-specify the range of ports for scanning.

These files can be taken from my cloud resource in the ADB-WiFi directory:

https://k00.fr/ucl4vfd7

In general, everything is done almost automatically through mDNS and through the service _adb-tls-connect._tcp.

There are some good ideas here:

https://stackoverflow.com/questions/65991502/adb-over-wi-fi-android-11-on-window...

Unfortunately, the image quality settings using ADB are very poor, and given the expanded displays on the Meta Quest 3 headset, the useful image is cut off very much. But yes, I have not yet seen any API or documentation in the open. The ideal option would be to implement something similar to what is done in the broadcast via the Meta Quest Developer Hub.

Have you used this program? What they do with the image there is wonderful. But this is done through the API, as far as I understand, and there is no information about it...

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.

If I understand correctly, they are implemented by adb commands that set the resolution. For example, for resolution 3072, the command would be:

adb shell setprop debug.oculus.textureHeight 3380

adb shell setprop debug.oculus.textureWidth 3072

To set the frequency, use the command:

adb shell setprop debug.oculus.refreshRate 90

It is not possible to set the resolution for a specific game, it is always set globally. In QGO and QGT different profiles are used for each game. These profiles have their own settings for resolution, frequency, FFR, etc.

Unfortunately, Meta has seriously limited the rights to use ADB and many things that work on smartphones will not work on the headset. The am and pm commands work, but partially, and sysctl will not allow you to do anything serious.

Thank you for appreciation of Quas. Unfortunately, I don't have a Quest Pro headset, but since the firmwares and shells of all Meta Quest headsets are generally similar, ADB should work roughly the same on all of them.

I'm not quite sure what you mean by "put the headset to PCVR mode" Are you referring to connecting the headset to a PC via Meta Link or Air Link?

ADB is not used in this case—it is an Android operating system mechanism and serves only as a tool for management, control, diagnostics, testing, and other supplementary functions that are built into the Quas program itself.