Husk
Turn a spare Android phone into a remote camera and control rig
新版本 1.4
Set the access token in the app.
New Access token field with Generate, Copy and Save. A PC app can also ask for the token: the phone shows a notification, and you tap Approve (GET /token/request, /token/status; /token/set changes it).
The token is no longer read from a global system setting set with adb. After updating, set the token again in the app. Without a token, anyone on your Tailscale network can control the phone.
New Access token field with Generate, Copy and Save. A PC app can also ask for the token: the phone shows a notification, and you tap Approve (GET /token/request, /token/status; /token/set changes it).
The token is no longer read from a global system setting set with adb. After updating, set the token again in the app. Without a token, anyone on your Tailscale network can control the phone.
Husk turns a spare Android phone into a remote camera and control rig on your own LAN or
Tailscale network, without root.
Features: camera streaming (MJPEG) in a browser, or as a webcam via a PC tool; front or back
camera, switchable over HTTP while the stream runs; an accessibility engine for scripted
on-screen actions; in-app recovery of Wireless Debugging after a reboot; an adb bridge for
scrcpy from a PC; camera or screen motion alerts with a push and a live snapshot; a Samsung
DeX toggle on DeX phones. It starts automatically after a reboot.
Husk has no built-in updater and never checks for, downloads or installs anything on its own.
Update from F-Droid, or install an APK with adb.
Every host Husk can talk to, and what triggers it:
* 0.0.0.0 - it LISTENS, it never connects out: the HTTP control server on 8090 and the adb
bridge on 15557, while the service runs, both behind a source-IP allowlist.
* 127.0.0.1 - loopback only, inside the phone: the accessibility engine on 8127, and the adb
bridge forwarding to the local Wireless Debugging port.
* ntfy.sh - only when motion alerts are enabled and you have set a topic; one push per alert.
The server is configurable - use your own instance.
* xplat.co - project website and PC companion download. The app itself never contacts it;
1.1 removed the updater that read it.
The allowlist admits loopback, private LAN ranges, fc00::/7 and Tailscale's 100.64.0.0/10;
some carriers use that range too, so on mobile data it is wider than your tailnet alone. An
optional token adds a second layer, off by default. Restrict access with a Tailscale ACL.
Husk uses the AccessibilityService API and exposes an adb bridge by design. 100% open source
(GPLv3), AOSP framework APIs only: no trackers, no ads, no proprietary code.
Tailscale network, without root.
Features: camera streaming (MJPEG) in a browser, or as a webcam via a PC tool; front or back
camera, switchable over HTTP while the stream runs; an accessibility engine for scripted
on-screen actions; in-app recovery of Wireless Debugging after a reboot; an adb bridge for
scrcpy from a PC; camera or screen motion alerts with a push and a live snapshot; a Samsung
DeX toggle on DeX phones. It starts automatically after a reboot.
Husk has no built-in updater and never checks for, downloads or installs anything on its own.
Update from F-Droid, or install an APK with adb.
Every host Husk can talk to, and what triggers it:
* 0.0.0.0 - it LISTENS, it never connects out: the HTTP control server on 8090 and the adb
bridge on 15557, while the service runs, both behind a source-IP allowlist.
* 127.0.0.1 - loopback only, inside the phone: the accessibility engine on 8127, and the adb
bridge forwarding to the local Wireless Debugging port.
* ntfy.sh - only when motion alerts are enabled and you have set a topic; one push per alert.
The server is configurable - use your own instance.
* xplat.co - project website and PC companion download. The app itself never contacts it;
1.1 removed the updater that read it.
The allowlist admits loopback, private LAN ranges, fc00::/7 and Tailscale's 100.64.0.0/10;
some carriers use that range too, so on mobile data it is wider than your tailnet alone. An
optional token adds a second layer, off by default. Restrict access with a Tailscale ACL.
Husk uses the AccessibilityService API and exposes an adb bridge by design. 100% open source
(GPLv3), AOSP framework APIs only: no trackers, no ads, no proprietary code.
版本
雖然在下方可選擇下載 APK 檔案，但要留意這樣的安裝方式將不會收到更新通知，是一種較不安全的下載方法。建議您先安裝 F-Droid 用戶端使用。
下載 F-Droid-
此版本需要 Android 8.0 或更高的版本。
此套件包由原開發者建置和簽署，並保證與此原始碼 Tarball 保持一致。
-
此版本需要 Android 8.0 或更高的版本。
此套件包由原開發者建置和簽署，並保證與此原始碼 Tarball 保持一致。
-
此版本需要 Android 8.0 或更高的版本。
此套件包由原開發者建置和簽署，並保證與此原始碼 Tarball 保持一致。
新版本 1.3
Two camera fixes.
The chosen camera side (front or back) is now remembered, so an app update no longer switches
the camera back to the rear side.
Switching side no longer opens the new side's camera while another app is using it. Husk waits
until it is free, as it already did for the old side.
No new permissions or endpoints; the HTTP interface is the same as in 1.2.
The chosen camera side (front or back) is now remembered, so an app update no longer switches
the camera back to the rear side.
Switching side no longer opens the new side's camera while another app is using it. Husk waits
until it is free, as it already did for the old side.
No new permissions or endpoints; the HTTP interface is the same as in 1.2.
新版本 1.2
Bugfix. Switching the camera side over HTTP (/set?front=0|1) started an extra background check
loop each time instead of reusing the one already running, so repeated switches left several
one-second loops going at once. They are now collapsed into one.
Nothing else changed: no new permissions, no new endpoints, and the HTTP interface is the same
as in 1.1.
loop each time instead of reusing the one already running, so repeated switches left several
one-second loops going at once. They are now collapsed into one.
Nothing else changed: no new permissions, no new endpoints, and the HTTP interface is the same
as in 1.1.