py-scrcpy-sdk
一个基于 scrcpy-server 通信协议提纯出来的最小化 Python SDK,聚焦三件事:
- 实时获取指定 Android 设备画面
- 保存当前画面为
jpg,录制片段为gif - 向设备发送点击、长按、拖动、文本、按键、滚动等操作
这个项目直接复用 adb + scrcpy-server + Python socket 的链路,不依赖桌面版 scrcpy 窗口截图。
安装
要求:
- Python 3.10+
- 本机可执行
adb - Android 设备已开启 USB 调试
安装:
pip install py-scrcpy-sdk
本地开发:
pip install -e .
快速开始
from py_scrcpy_sdk import ScrcpyClient, ScrcpyConfig
config = ScrcpyConfig(serial="YOUR_DEVICE_SERIAL")
with ScrcpyClient(config) as client:
frame = client.wait_until_ready()
print(frame.shape)
client.save_screenshot("artifacts/screen.jpg")
client.save_gif("artifacts/demo.gif", seconds=3, fps=8)
client.tap(300, 600)
client.long_press(300, 900, duration=1.2)
client.drag(200, 1000, 800, 1000, duration_ms=400)
常用 API
from py_scrcpy_sdk import ScrcpyClient, ScrcpyConfig, list_devices
print(list_devices())
client = ScrcpyClient(ScrcpyConfig(serial="YOUR_DEVICE_SERIAL"))
client.start()
frame = client.get_frame()
for next_frame in client.frames():
# 实时处理视频帧
pass
def on_frame(frame):
print(frame.shape)
return True
client.listen(on_frame)
listener = client.start_frame_listener(on_frame)
listener.join(timeout=3)
client.show() # OpenCV 窗口预览,q / Esc 退出
client.save_screenshot("screen.jpg")
client.save_gif("clip.gif", seconds=5, fps=10)
client.tap(100, 200)
client.long_press(100, 400, duration=1.0)
client.drag(100, 500, 900, 500)
client.swipe(100, 900, 900, 900)
client.scroll(500, 1200, vertical=12)
client.input_text("hello")
client.press_key(4) # Android BACK
client.stop()
设计说明
- 仅保留 SDK 必需能力,不包含 CLI、模板识别、服务编排等 POC 功能
- 当前固定使用
h264解码,便于稳定接入 PyAV - 默认优先走
adb reverse,失败后自动回退到adb forward - 触控坐标以当前解码后的视频帧分辨率为基准
回调式监听
listen(callback):阻塞式逐帧回调,适合当前线程直接消费画面start_frame_listener(callback):后台线程持续回调,适合嵌入其他系统- 回调返回
False时可自动停止监听
可运行示例见 examples/basic.py
交互式预览示例
examples/interactive_control.py- 基于 Tkinter 实时显示设备画面,不依赖 OpenCV HighGUI
- 鼠标左键单击发送点击,左键拖动发送滑动
- 键盘
s保存 jpg 截图,g保存 gif,q/Esc退出
包含内容
- 内置
scrcpy-server v3.3.4 - 安装后可直接被其他 Python 项目
pip install引用
典型使用场景
- 自动化项目中实时拉取设备画面做识别
- 识别后回写点击、拖动、长按等控制动作
- 保存调试截图和回放 GIF 作为证据
Metadata
Release files for py-scrcpy-sdk 0.1.2
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 | Actions |
|---|---|---|---|---|
| py_scrcpy_sdk-0.1.2.tar.gz | 108.2 kB | Without provenance | Details for py_scrcpy_sdk-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| py_scrcpy_sdk-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for py_scrcpy_sdk-0.1.2-py3-none-any.whl |
Total release size: 213.5 kB
Release files / py_scrcpy_sdk-0.1.2.tar.gz
| Download URL | py_scrcpy_sdk-0.1.2.tar.gz |
|---|---|
| Size | 108.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
621f7f64554ee7bb9fbec72979c4f0539ab5c8daefbb8b447c86f2b415603a73
|
|
BLAKE2b-256 checksum How to use checksums |
f6299aee41cf6a25bb4831965a26bc6139535e9ffc7ce60eb4a52c80dbf88d65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Release files / py_scrcpy_sdk-0.1.2-py3-none-any.whl
| Download URL | py_scrcpy_sdk-0.1.2-py3-none-any.whl |
|---|---|
| Size | 105.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d40702257d417ff62014fc81ce106ed987e64695587a84d38990ea25e2e7ab3b
|
|
BLAKE2b-256 checksum How to use checksums |
8d4e5f4787a0956377e2b96dfd89664f0669b95fea7ccf22603f6363f045f5f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Security for py-scrcpy-sdk 0.1.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.