androtools
对 Android SDK、第三方模拟器命令行工具、以及通过 adb 连接的 Android 设备的封装。
核心价值是把「判断状态、等它就绪、卡死了怎么办」这段最容易出错、也最难手工验证的流程收进一处。 支持真机、雷电模拟器、MuMu 模拟器。
安装
pip install androtools
快速开始
真机
真机不需要任何子类 —— 它就是一个 adb 可寻址的目标。
from androtools.android_sdk.platform_tools import ADB
from androtools.core import Device, DeviceInfo
adb = ADB()
serial, status, _ = adb.get_devices()[0]
device = Device(DeviceInfo(name="我的手机", serial=serial, adb_path=adb.bin_path))
print(device.get_status()) # DeviceStatus.BOOT_COMPLETED
print(device.android_version) # 问设备本身要，不是查本地表
print(device.read_prop("ro.product.model"))
device.shell.list_packages() # 所有应用
device.shell.list_packages(flag=0) # 只看第三方应用
device.shell.pull("/sdcard/DCIM", r"D:\backup")
同时插着多台设备时，serial 必须指定 —— 否则 AndroidShell 会抛
AmbiguousDeviceError，而不是让 adb 乱挑。
模拟器
模拟器比真机多两样东西：厂商 Console，以及「启动 / 关闭」。
from androtools.core import EmulatorInfo, LDPlayer
player = LDPlayer(
EmulatorInfo(
name="雷电",
serial=None, # 启动后由控制台决定，见下
adb_path=r"D:\ProgramFiles\LDPlayer9.0.79.2\adb.exe",
index="0", # 厂商 Console 里的编号
console_path=r"D:\ProgramFiles\LDPlayer9.0.79.2\ldconsole.exe",
)
)
player.launch() # 启动模拟器并等它就绪
print(player.get_status())
player.shell.tap(100, 200)
player.run_app("com.android.settings")
player.close()
LDPlayer 会自己按 console_path 找 ldconsole.exe，MuMu 同理：
from androtools.core import MumuPlayer
mumu = MumuPlayer(EmulatorInfo(
name="MuMu",
serial=None,
adb_path=r"D:\Program Files\Netease\MuMu\nx_main\adb.exe",
index="1",
console_path=r"D:\Program Files\Netease\MuMu\nx_main\MuMuManager.exe",
))
mumu.launch() # 启动 → 反查 serial → adb connect
MuMu 启动后 adb 端口会变，launch() 会从 Console 查出新的 serial 并 adb connect。
如果你自己管理启动流程，记得调 mumu.refresh_serial()。
抓包
按应用抓 —— 用应用的 user id 做 iptables 标记。
from androtools.utils import Tcpdump
tcpdump = Tcpdump(device.shell, "com.example.app")
tcpdump.start_capture()
...
tcpdump.stop_capture()
tcpdump.pull_pcap_file(r"D:\capture")
设计
Device 真机。serial、状态判定、超时探测、应用操作
└─ EmulatorSession 加上厂商 Console 和 launch / close / ensure_ready / recover
└─ ConsoleSession 雷电、MuMu
AndroidShell adb 命令字典（shallow：省的是打字，不是藏复杂度）
EmulatorConsole 厂商 CLI 的方言止步于此（probe_state / getprop / run_app / …）
两个 seam 都可以替换，所以生命周期逻辑不需要真机就能测：
from androtools.testing import FakeADB
adb = FakeADB(responses={("get-state",): CmdResult("device", "")}, devices=[...])
device = Device(info, adb=adb, sleeper=lambda _s: None)
FakeADB 未声明的命令会直接抛错，所以「代码多调了一次 adb」会变成红灯而不是悄悄通过。
开发
make sync # uv sync
make test # 单元测试（默认排除 integration）
make typecheck # mypy
make test-integration # 需要真实 Android SDK 和设备
CI 在 .github/workflows/ci.yml，跑 Python 3.10（声明的最低版本）和 3.13。
术语
领域词汇见 CONTEXT.md —— 尤其「Device 与 Emulator 差在哪」「Serial 为什么是运行期才确定的」这两条。
破坏性变更
1.x → 2.0 的迁移说明见 CHANGELOG.md。
1 maintainer
Metadata
1 maintainer
Release files for androtools 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| androtools-2.0.0.tar.gz | 25.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| androtools-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 59.4 kB
Release files / androtools-2.0.0.tar.gz
| Download URL | androtools-2.0.0.tar.gz |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3dc5caf684ffb2c5090334102ce254ea1e9fc69ce7c2c27909b649688501439
|
|
BLAKE2b-256 checksum How to use checksums |
e3074334c1185feb9cd32aefe0f8f22aeab4468219c5a397c4a556d7ebd3066b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / androtools-2.0.0-py3-none-any.whl
| Download URL | androtools-2.0.0-py3-none-any.whl |
|---|---|
| Size | 33.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10844994eb39e4600da3202e1e4839d590ff0a68703dbf019b5ec259453e31a8
|
|
BLAKE2b-256 checksum How to use checksums |
7732f21bbf5187bcc332f2c69f4ba02f66153a14a53a7e5179dd6a35bc8e2272
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for androtools 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
