QUESTION about API working with the Android client

[xvoland]

Thanks for your interesting project.

I was trying to figure out how your Windows client works (I’m not a C# developer), specifically how it controls the Android app over Wi-Fi — changing the resolution, switching the camera, and so on.

As far as I understand, it switches the app into some kind of simplified mode and then sends commands.

I noticed the following structures:

// PacketType.kt
enum class PacketType(val code: Byte) {
    HELLO(0x01),
    ACK(0x02),
    VIDEO(0x03),
    CONTROL(0x04),
    HEARTBEAT(0x05),
    DISCONNECT(0x06)
}

// ControlPacket.kt
enum class ControlPacket(val code: Byte) {
    SWITCH_CAMERA(0x01),
    TOGGLE_FLASH(0x02),
    SET_ZOOM(0x03)
}

How exactly are the TCP packets sent — what’s the algorithm and the sequence?

Could you help me by describing it step by step, for example:

Windows client → command: (1 byte)(1 byte) → Android

Command: c0

Thanks in advance for your reply.

[darusc]

The windows app doesn't use any C# or dotnet libraries. Networking is done using ASIO for C++.

The app is controlled the same way on both WiFi and over USB (ADB). If connection is over USB adb reverse tcp:6969 tcp:6969 is used to route the request to 127.0.0.1 made by the android phone to the windows server.

The windows app opens a TCP server and waits for a connection from the android app. Upon connecting the android app sends an initial packet with config identifiers (DeviceDescriptor.kt) and starts listening for messages/commands received from the server. (these are all the commands the server can send PacketType.kt)

The android app can talk back to the windows app, sending errors if a command could not be executed.

You can take a look at https://github.com/darusc/VCamdroid/blob/main/windows/src/rtsp/manager.cpp to see how each command is sent by the server.

[xvoland]

Thank you, I'll try to figure it out further.