Repository navigation
Open
2 / 62 of 6 issues completedLabels
os:windowsRuns on, or affects, Windows hostsRuns on, or affects, Windows hosts
Milestone
Description
Umbrella for running simlock natively on Windows (Android only; iOS needs macOS). Today the published package cannot start its daemon on Windows (#1051).
All work below is in the Windows support milestone.
Bug report
- Windows: daemon start/doctor time out with ENOENT because IPC uses a filesystem socket (0.2.0) #1051 — daemon start/doctor time out with ENOENT; Android SDK not found on Windows
Open PRs (by @leonardoxr)
- fix(ports): the daemon listens on a named pipe on Windows #1052 — the daemon listens on a named pipe on Windows (daemon half of Windows: daemon start/doctor time out with ENOENT because IPC uses a filesystem socket (0.2.0) #1051)
- fix(drivers,ports,core): Android on Windows #1053 — Android on Windows: SDK
.exe/.batdiscovery, running.battools throughcmd.exe, device-root mode check (Android half of Windows: daemon start/doctor time out with ENOENT because IPC uses a filesystem socket (0.2.0) #1051; needs fix(ports): the daemon listens on a named pipe on Windows #1052 to run) - feat(ports): read CPU, memory and swap on Windows #1054 — read CPU, memory and swap on Windows (
WindowsHostLoadProbe) - fix(agent-device): find an npm-installed agent-device on Windows #1055 — find an npm-installed agent-device on Windows (
;PATH,.cmdshim, no execute bit)
Not covered yet
- Windows: simlock daemon install and uninstall run the daemon as a service #1069 —
simlock daemon install/uninstall(run as a service) — a usage error on Windows today - CI: run the tests on Windows #1070 — CI: no Windows job, so Windows paths are only tested by passing the platform explicitly on Linux
- Docs: worker platforms and Windows setup #1071 — website docs: say which platforms a worker supports, and Windows setup (Android SDK default
%LOCALAPPDATA%\Android\Sdk)
Written by an agent.
Metadata
Metadata
Assignees
Labels
os:windowsRuns on, or affects, Windows hostsRuns on, or affects, Windows hosts
Activity
test(agent-device): assert the ':' PATH split and the Windows backsla…
leonardoxr commentedon Oct 30, 2026
Four more Windows PRs, as drafts, each one commit on
main:adb getpropandavdmanagerflash one every 30 s.node.exeprocesses part of Windows: daemon start/doctor time out with ENOENT because IPC uses a filesystem socket (0.2.0) #1051.ps, which Windows lacks.avdmanager list device(two JVMs) is no longer run on every 30 s catalog read, on any OS. Its answer is kept until its inputs change.#1052–#1055 have their review fixes pushed. #1052 is merged up to
main.Written by an agent.
fix(ports): the daemon listens on a named pipe on Windows (#1052)
fix(drivers,ports,core): Android on Windows (#1053)
fix(ports): read a pid's command line on Windows, so a crashed daemon…
fix(daemon): a start that fails at the socket claim exits (#1077)
fix(ports): the daemon's children open no console window on Windows (#…
perf(android): keep the avdmanager list device answer while its input…
feat(ports): read CPU, memory and swap on Windows (#1054)
fix(agent-device): find an npm-installed agent-device on Windows (#1055)