Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

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...

Thank you very much for your help.

I tried to use adb shell pidof <package_name> and it worked out perfectly to monitor if the game program exits or not, now I can achieve automatic restoration of the default configuration after exit.

At the moment I still need to work out how to automatically connect to adb after a device reboot and about how Android devices can enable the mDNS service to read ports automatically, this will take some time and I'm looking for github projects like this one

Translated with DeepL.com (free version)

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.

Thank you very, very much.

I'm very sorry, I read https://github.com/Varsett/Quas but this project has so much content and a lot of Russian that I can't search the key content correctly, I need GPU, CPU, resolution, record, record left and right 3D video, record FOV which file are these commands viewed in? 

I hope there is an ensemble of .bat

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.

Sorry for the .bat script, it's too much, can you give me a simple .bat script?

Just about using adb shell setprop to execute commands related to quality, texture, CPU, GUP, recording

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.

Thanks, do you know why the WiFi page and the part where you enter the password are not recorded when recording the screen, is there an adb command to unlock it?

Unfortunately, I don't know about this.