Making web adb work with computer's adb.

[pojungc]

Hi,
As i understand Tango adb and Google adb don't work well together and if I wanted to use the web adb, I would need to kill the adb server on my computer.

I wanted to discuss if adding Google adb would ever be possible to Tango? Have you tried integrating it and if you ran into some technical limitations? I would like it be seamless between the web and my computer environment.

If not possible, would you have have any ideas for workarounds?

[yume-chan]

We already support connecting through Google ADB Server: https://docs.tangoapp.dev/tango/server/

The only problem is it's not supported in Web browsers. (A WebSockify-like native app is required to workaround this)

[pojungc]

Thanks for the quick response!
If I understand correctly this native app would sit between adb server and web browser to translate websockets/tcp, is that correct?

Do you know if there are any code reference I could look at to get a better understanding?

[yume-chan]

native app would sit between adb server and web browser to translate websockets/tcp

Correct.

Do you know if there are any code reference I could look at to get a better understanding?

Our Tango Desktop Bridge is open-source: https://github.com/tango-adb/bridge-rs/blob/main/src/main.rs, it also embeds and starts Google ADB on incoming WebSocket connections. It's not well-documented, you can also refer to projects like https://github.com/novnc/websockify-js as the basic principle is same.

On the Web side, you need to write a custom AdbServerConnector to utilize the WebSocket connection. We don't have a code example for that, but it's very similar to the Node.js TCP socket connector, just converting events to Web Streams:

ya-webadb/libraries/adb-server-node-tcp/src/index.ts

Lines 12 to 57 in 6a18fa2

	function nodeSocketToConnection(
	socket: Socket,
	): AdbServerClient.ServerConnection {
	socket.setNoDelay(true);
	const closed = new Promise<void>((resolve) => {
	socket.on("close", resolve);
	});
	return {
	readable: new PushReadableStream<Uint8Array>((controller) => {
	// eslint-disable-next-line @typescript-eslint/no-misused-promises
	socket.on("data", async (data) => {
	if (controller.abortSignal.aborted) {
	return;
	}
	socket.pause();
	await controller.enqueue(data);
	socket.resume();
	});
	socket.on("end", () => {
	tryClose(controller);
	});
	}),
	writable: new MaybeConsumable.WritableStream<Uint8Array>({
	write: (chunk) => {
	return new Promise<void>((resolve, reject) => {
	socket.write(chunk, (err) => {
	if (err) {
	reject(err);
	} else {
	resolve();
	}
	});
	});
	},
	}),
	get closed() {
	return closed;
	},
	close() {
	socket.end();
	},
	};
	}

If you don't care about compatibility, you can also use the new WebSocketStream API: https://developer.mozilla.org/en-US/docs/Web/API/WebSocketStream. It provides WebSocket connections using Web Streams API natively.

[pojungc]

Appreciate the detailed explanation! Will look into this workaround more!
Btw, love the project and the work that you have done, ty.