I am using computer with adb installed to update some apps on my nvidia shield. My nvidia shield has network debugging enabled.

I would like to create an android app that could "send adb commands" to my shield. Can I use your library for this purpose or is it only intended to be used on desktop? Is there any special permission to give to the android application?

Hi, I'm interested in using this library to connect an Android phone to an Android (WearOS) watch, with the Dadb-enabled app running on the phone. ADB over wifi would be enabled on the watch, and I would know the ip address. What I'd hope for is that the phone app makes an adb connection request to the watch's ip address. This would generate a prompt on the watch that the user can accept or reject. If the request is accepted, then the connection is established. This is broadly how I've seen other ADB libraries work.

But I can't figure out how to accomplish that using Dadb. The only example given is connecting to an emulator. The real power of this library would be to connect two actual Android devices over wifi. Please say if this is possible with the current version of Dadb and, if so, give some brief example code.

Thanks.

Hi, there. I've been enjoying playing with this library. Thank you so much for it!

I have a need to set up port forwarding, as in adb -s emulator-5554 forward tcp:6100 tcp:7100. I suspect this requires the adb server itself, but I'm still green, figuring out how the protocols work. I've tried my own hand at adding a reboot command, via a simple dadb.open("reboot:"), and that worked. So I toyed with something like that I thought might work for forwarding (e.g. dadb.open("host-serial:5554:forward:tcp:10001;tcp:10001)) based on looking at the ddmlib source for forwarding, but I barely know what I'm doing. Obviously, that didn't work for me. Any advice?

Thanks again for the great library and any help.

As requested in issue #1

Usage (Kotlin):

dadb.tcpForward(
    hostPort = 7001,
    targetPort = 7001
).use {
    // Do operations that depend on port forwarding
}

I'm getting the following error when calling dadb.install.

dadb.AdbStreamClosed: ADB stream is closed for localId: e2527064

It looks like it returns a close command immediately when it receives the abb_execute command.

When the server receives the message it only returns the close command if it can't read the response for some reason. https://cs.android.com/android/platform/superproject/+/master:packages/modules/adb/adb.cpp;drc=867c71e5114e76b4f64e9f38e1be060fd9ba3a26;l=475

Sending shell commands work fine. Calling the install command through adb on my local machine to the same target host also works fine.

	at java.base/java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.base/java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:110)
	at java.base/java.net.SocketOutputStream.write(SocketOutputStream.java:150)
	at okio.OutputStreamSink.write(JvmOkio.kt:56)
	at okio.AsyncTimeout$sink$1.write(AsyncTimeout.kt:99)
	at okio.RealBufferedSink.flush(RealBufferedSink.kt:267)
	at dadb.AdbWriter.write(AdbWriter.kt:92)
	at dadb.AdbWriter.writeClose(AdbWriter.kt:60)
	at dadb.AdbStream.close(AdbStream.kt:118)
	at dadb.AdbStream.nextMessage(AdbStream.kt:109)
	at dadb.AdbStream.access$nextMessage(AdbStream.kt:24)
	at dadb.AdbStream$source$1.message(AdbStream.kt:61)
	at dadb.AdbStream$source$1.read(AdbStream.kt:40)
	at okio.RealBufferedSource.request(RealBufferedSource.kt:206)
	at okio.RealBufferedSource.require(RealBufferedSource.kt:199)
	at okio.RealBufferedSource.readByte(RealBufferedSource.kt:209)
	at dadb.AdbSyncStream.send(AdbSync.kt:73)
	at dadb.Dadb$DefaultImpls.push(Dadb.kt:54)
	at dadb.TestDadb.push(DadbTest.kt:331)
	at dadb.DadbTest$adbPush_basic$1.invoke(DadbTest.kt:119)
	at dadb.DadbTest$adbPush_basic$1.invoke(DadbTest.kt:113)

Not sure if you are taking PRs, or consider this in scope, so no offense taken if you close this.

Ideally I would use host:devices or host:devices-l to find the available emulator and devices. But I couldn't get that working with Dadb (https://github.com/mobile-dev-inc/dadb/issues/7).

As a shortcut, I read from the avd process files as described here https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:utp/android-test-plugin-host-retention/src/main/java/com/android/tools/utp/plugins/host/icebox/IceboxConfigUtils.kt?q=8554%20f:android

Original code in https://github.com/yschimke/emulator-tools/commit/96374554160a8707315001796d16f3f8c7f1d25b

Making the packets an explicit class type makes it easier to use a when statement and handle the use cases. Using an int type means that a consumer would have to use an else statement, even though the ID types have already been checked.

also updates compileJava tasks with targetCompatibility of 1.8 we do not have any compileJava today, but tomorrow even if we add any annotation-based libraries, a compileJava step will get added, and kotlin and java both should specify the same JVM target

Signed-off-by: Arnav Gupta [email protected]

I am using dadb and it was not able to discover local device,

I am using following code to discover locally connected device val dadb = Dadb.discover("localhost") if (dadb == null) throw RuntimeException("No adb device found")

I ran into following error java.lang.RuntimeException: No adb device found

I'm trying to use a combination of dadb and grpc to the emulator to implement some useful functions when using emulators.

This led me to a couple of questions

1. Have you considered Kotlin multiplatform support? You are already using Okio, which is KMP enabled and there is code for KMP Certificate handling code in github.com/cashapp/certifikit. Generally seems like a incremental change that could unlock a lot of other cases.
2. Have you considered supporting gRPC in Dadb also?

I have a working implementation of gRPC using Square's Wire project (again KMP native)

https://github.com/yschimke/emulator-tools/blob/main/src/jvmMain/kotlin/ee/schimke/emulatortools/Main.kt#L41-L48

again, please close if this it undesired or out of scope and I'll maintain the bits I need separately.

Hi guys,

I'm Victor, and I'm trying to run the library in a poc application to know how to use it. But the first method that I'm trying is "discover", but it returning me a FileNotFoundException

I'm doing:

fun discover(){
        try {
            val result = Dadb.discover("localhost")
            binding.tvcommandline.text = "" + result.toString()
        }catch (ex: java.lang.RuntimeException){
            binding.tvcommandline.text = "Failed to discover emulator. No adb device found"
            ex.printStackTrace()
        }
    }

The error is:

Caused by: java.io.FileNotFoundException: .android/adbkey: open failed: ENOENT (No such file or directory)

Some advice?

I'm testing on a Samsung S20 Ultra with Android 12 and connected via USB.

Thank you

Is the pair command supported by Dadb? If not, it would be great to add this feature.

https://developer.android.com/studio/command-line/adb#connect-to-a-device-over-wi-fi-android-11+

The discover and create functions are hanging as long as the allow button has not been clicked. Internally this is the open function that blocks endlessly. Is this the desired behavior? If so, why?

val dadb = Dadb.discover("192.168.1.62")

It would be great to throw timeout exception after x seconds. Or throwing something like AuthorizationRequiredException or FailedAuthenticationException would be even better.

It's trivial with the official binary, you just have to check the connect output.

adb connect 192.168.1.62
* daemon not running; starting now at tcp:5037
* daemon started successfully
failed to authenticate to 192.168.1.62:5555