{ "schemaVersion": "0.11.0", "canonical": "https://www.pystone.net/notes/adb-internals/", "atlas": "https://www.pystone.net/?node=adb-internals#knowledge-atlas", "markdown": "https://www.pystone.net/notes/adb-internals.md", "context": "https://www.pystone.net/notes/adb-internals.context.json", "knowledgeVersion": "224c990773de.5fa8af6e39fa", "build": { "siteCommit": "224c990773de166d23a886306577dd90379529ce", "notesCommit": "5fa8af6e39fa3891d1b9b4832bfa6c4e0ecaaf0a", "builtAt": "1970-01-01T00:00:00.000Z", "version": "224c990773de.5fa8af6e39fa" }, "id": "note:adb-internals", "slug": "adb-internals", "title": "【自动化测试】ADB原理【TOPOST】", "type": "note", "visibility": "public", "idStability": "rename-stable", "author": { "name": "Perrin Yong", "profile": "https://www.pystone.net/profile/" }, "publisher": { "name": "Perrin Yong", "profile": "https://www.pystone.net/profile/" }, "aliases": [], "summary": "【自动化测试】ADB原理【TOPOST】", "contentRole": "unspecified", "isMoc": false, "mocRecognition": "none", "generated": false, "attribution": "unspecified", "domain": "10-计算机、信息技术与工程", "tags": [], "mocs": [], "contentHash": "2d77f0b44f24c9ddd7b818547a31f63cdf9ec9ca953b91da56b13d4097764678", "assets": [ { "reference": "assets/1621006571443.png", "url": "/media/b8cd112701af284343e4.png", "mediaType": "image/png", "contentHash": "b8cd112701af284343e4181ccd0b3782cc21e5a9211c97ba95cbd78f954c9af7", "byteLength": 42313, "width": 1073, "height": 604 }, { "reference": "assets/1620997882024.png", "url": "/media/0524f567931ca6432d9f.png", "mediaType": "image/png", "contentHash": "0524f567931ca6432d9f4d1e7d59c9d7968122d85f6b9ca6af43af46f1982ab0", "byteLength": 177105, "width": 739, "height": 652 }, { "reference": "assets/1621006667165.png", "url": "/media/4fe8d91d51316c90d25c.png", "mediaType": "image/png", "contentHash": "4fe8d91d51316c90d25c60f82ceee9d3366af2e7b695efcd330f2445aa2da2bc", "byteLength": 658633, "width": 1734, "height": 1276 }, { "reference": "assets/1621006991650.png", "url": "/media/433c64e8c67d40eb5219.png", "mediaType": "image/png", "contentHash": "433c64e8c67d40eb52190c0703e2a75ebb44045043582788eb10a230e7a80fed", "byteLength": 25717, "width": 568, "height": 375 }, { "reference": "assets/1621007056515.png", "url": "/media/2b9fdd0eb942de0e40bb.png", "mediaType": "image/png", "contentHash": "2b9fdd0eb942de0e40bb0e7dda00d91be5ed6224d9fbd3926e7a15c8131d6b84", "byteLength": 71649, "width": 1045, "height": 403 } ], "headings": [ { "depth": 1, "text": "【自动化测试】ADB原理【TOPOST】", "anchor": "自动化测试adb原理topost", "citation": "https://www.pystone.net/notes/adb-internals/#%E8%87%AA%E5%8A%A8%E5%8C%96%E6%B5%8B%E8%AF%95adb%E5%8E%9F%E7%90%86topost" }, { "depth": 2, "text": "adb原理", "anchor": "adb原理", "citation": "https://www.pystone.net/notes/adb-internals/#adb%E5%8E%9F%E7%90%86" }, { "depth": 3, "text": "架构", "anchor": "架构", "citation": "https://www.pystone.net/notes/adb-internals/#%E6%9E%B6%E6%9E%84" }, { "depth": 3, "text": "通信机制与workflow", "anchor": "通信机制与workflow", "citation": "https://www.pystone.net/notes/adb-internals/#%E9%80%9A%E4%BF%A1%E6%9C%BA%E5%88%B6%E4%B8%8Eworkflow" }, { "depth": 3, "text": "ADB Protocol 通信协议", "anchor": "adb-protocol-通信协议", "citation": "https://www.pystone.net/notes/adb-internals/#adb-protocol-%E9%80%9A%E4%BF%A1%E5%8D%8F%E8%AE%AE" }, { "depth": 4, "text": "Client 和 Server 间的通信", "anchor": "client-和-server-间的通信", "citation": "https://www.pystone.net/notes/adb-internals/#client-%E5%92%8C-server-%E9%97%B4%E7%9A%84%E9%80%9A%E4%BF%A1" }, { "depth": 4, "text": "ADB Daemon 和 ADB Server 间的通信 — transport协议", "anchor": "adb-daemon-和-adb-server-间的通信-transport协议", "citation": "https://www.pystone.net/notes/adb-internals/#adb-daemon-%E5%92%8C-adb-server-%E9%97%B4%E7%9A%84%E9%80%9A%E4%BF%A1-transport%E5%8D%8F%E8%AE%AE" }, { "depth": 3, "text": "USB Vendor ID", "anchor": "usb-vendor-id", "citation": "https://www.pystone.net/notes/adb-internals/#usb-vendor-id" }, { "depth": 3, "text": "adb forward", "anchor": "adb-forward", "citation": "https://www.pystone.net/notes/adb-internals/#adb-forward" }, { "depth": 2, "text": "实践用法", "anchor": "实践用法", "citation": "https://www.pystone.net/notes/adb-internals/#%E5%AE%9E%E8%B7%B5%E7%94%A8%E6%B3%95" }, { "depth": 3, "text": "Profiler: Editor-to-Android connection", "anchor": "profiler-editor-to-android-connection", "citation": "https://www.pystone.net/notes/adb-internals/#profiler-editor-to-android-connection" }, { "depth": 3, "text": "log抓取", "anchor": "log抓取", "citation": "https://www.pystone.net/notes/adb-internals/#log%E6%8A%93%E5%8F%96" }, { "depth": 3, "text": "其他常用命令", "anchor": "其他常用命令", "citation": "https://www.pystone.net/notes/adb-internals/#%E5%85%B6%E4%BB%96%E5%B8%B8%E7%94%A8%E5%91%BD%E4%BB%A4" }, { "depth": 2, "text": "Ref", "anchor": "ref", "citation": "https://www.pystone.net/notes/adb-internals/#ref" } ], "claims": [], "outgoing": [], "incoming": [ { "id": "note:software-engineering-and-quality", "title": "软件工程与质量保障", "url": "https://www.pystone.net/notes/software-engineering-and-quality/", "atlas": "https://www.pystone.net/?node=software-engineering-and-quality#knowledge-atlas", "label": "软件工程与质量保障", "origin": "explicit", "humanReviewed": true, "context": "CI-CD与质量保障/CI-CD工具链中的“【自动化测试】ADB原理【TOPOST】”导航项", "citation": "https://www.pystone.net/notes/software-engineering-and-quality/#ci-cd%E4%B8%8E%E8%B4%A8%E9%87%8F%E4%BF%9D%E9%9A%9Cci-cd%E5%B7%A5%E5%85%B7%E9%93%BE" } ], "contentMarkdown": "# 【自动化测试】ADB原理【TOPOST】\n\n# 【自动化测试】ADB原理【TOPOST】\n\n\n\n| **创建时间：** | _2021/5/14 21:06_ |\n| --------- | ----------------- |\n\n * 【自动化测试】ADB原理\n * adb原理\n * 架构\n * 通信机制与workflow\n * ADB Protocol 通信协议\n * Client 和 Server 间的通信\n * ADB Daemon 和 ADB Server 间的通信 — transport协议\n * USB Vendor ID\n * adb forward\n * 实践用法\n * Profiler: Editor-to-Android connection\n * log抓取\n * 其他常用命令\n * Ref\n\n## adb原理\n\nADB - Android Debug Bridge\nADB源码：\n\n\n\n\n### 架构\n\n![Alt text](assets/1621006571443.png)\n\n**ADB Client** : 运行在PC HOST端，用来发送adb命令。 **本质上就是Shell** ，用来发送命令给Server。发送命令时，首先检测PC上有没有启动Server，如果没有Server，则自动启动一个Server，然后将命令发送到Server，并不关心命令发送过去以后会怎样。\n\n**ADB Server** :\n运行在PC HOST端，用来管理Client端和手机的Deamon之间的通信。\n检测USB接口何时连接或者移除设备。ADB Server维护着一个“已连接的设备的链表”，并且为每一个设备标记了一个状态：offline，bootloader，recovery或者online。Server一直在做一些循环和等待，以协调client和Server还有daemon之间的通信。\n\n> offline说明Server发现了一个设备，但是不能成功连接到Daemon。\n\n**Daemon（adbd守护进程）** :\n运行在调试设备中（手机或者模拟器），连接到adb server（通过usb或tcp-ip）,接受并执行adb命令, 为client提供一些服务。\n\n![Alt text](assets/1620997882024.png)\n\n### 通信机制与workflow\n\n 1. 在PC HOST端，adb会fork出一个守护进程（不是adbd），即ADB Server，而父进程（ADB Client）继续处理Client请求，所有的Client通过TCP端口号5037进行与Server通信，而Server创建 local socket 与 remote socket，前者用于和Client通信，后者用与远端进行通信，emulator通过TCP，real device则通过usb。\n\n 2. 在emulator/device端，adbd也创建 local socket 和 remote socket，前者与通过 jdwp 与Java虚拟机进程通信，后者通过 TCP/USB 与 PC HOST通信。\n\n * Client和Server虽然是同一个执行程序，但在命令行输入一条adb命令后，实际上完成了一次通信。adb server启动后，会在 **5037** 端口侦听从client发起的TCP连接\n\n * Server与模拟器或者手机设备的端口5555~5585建立TCP连接，PC上与之相连的端口号随机。\n\n![Alt text](assets/1621006667165.png)\n\n通过以下命令，可以看到server的启动日志：\n\n```cpp\nstring s = String.Empty;\n```\n\n\n通过以下命令，可以看到TCP的5037端口，在侦听连接：\n\n```cpp\nstring s = String.Empty;\n```\n\n 1. Client 调用某个 adb 命令\n 2. adb 进程 fork 出一个子进程作为 Server\n 3. Server 查找当前连接的 emulator/device\n 4. Server 接收到来自 Client 请求\n 5. Server 处理请求，将本地处理不了的请求发给\n 6. emulator/device\n 7. 位于 emulator/device 的 adbd拿到请求后交给对应的java虚拟机进程。\n 8. adbd 将结果发回给 Server\n 9. Server 将结果发回给 Client\n\n### ADB Protocol 通信协议\n\n#### Client 和 Server 间的通信\n\nClient发送的指令分为三种\n\n * 不需要经过Server处理就能成功的，如adb version,adb help。\n * 需要和Server通讯，但不需要和Demon通讯的指令，如adb devices.\n * 需要Daemon进行处理的命令。\n\nClient 和 Server 间传输的命令定义: \n\nClient每个命令都包含两个部分:\n\n 1. 命令的长度(Length)，由四位的十六进制表示\n 2. 实际的命令(Payload)，通过ASCII编码\n\n```cpp\nstring s = String.Empty;\n```\n\n\n000C：表示”host:version”这条命令的长度为12个字节；\nhost前缀：是为了区分其他类型的命令(后面还会看到shell前缀的命令)；\n\nServer收到Client的请求后，返回的数据遵循如下格式：\n\n * 如果成功，则返回四个字节的字符串”OKAY“\n * 如果失败，则返回四个字节的字符串”FAIL“和出错原因\n * 如果异常，则返回错误码\n\n#### ADB Daemon 和 ADB Server 间的通信 — transport协议\n\n这个数据通道对client而言，完全是透明的，client不关注这个通道怎么建立以及怎么进行数据传输。\n\n关于 transport 协议的定义在 system/core/adb/protocol.txt 文件中\n\n```cpp\nstring s = String.Empty;\n```\n\n\nclient与adbd的数据传输是需要用到两个通道的，当与server建立第一个通道的连接后，需要向server发送transport命令，表示接下来，要与adbd进行数据传输。当server返回“OKAY”后，client后续发送的数据，就直接传输到adbd了。\n\n![Alt text](assets/1621006991650.png)\n\n### USB Vendor ID\n\n![Alt text](assets/1621007056515.png)\n\n### adb forward\n\n设置任意端口转发，将特定主机端口上的请求转发到设备上的其他端口。PC 作为Client客户端 可以任意访问 Phone 上的 Server 服务器\n\n```cpp\nstring s = String.Empty;\n```\n\n\n该转发可以用于自己写的程序。\n\n## 实践用法\n\n用法大全: \n\n### Profiler: Editor-to-Android connection\n\nadb forward tcp:34999 localabstract:Unity-{insert bundle identifier here}\n\n### log抓取\n\nadb logcat -s Unity\nadb -s %DeviceName% logcat -s Unity\nadb logcat -s Unity ActivityManager PackageManager dalvikvm DEBUG #获取log，-s指定过滤器\nadb -s deviceName logcat -s Unity -f c:\\unity_log.txt #-f 输出log到指定文件\n\n### 其他常用命令\n\n\n\n## Ref\n\n\n\n\n\n" }