Releases: Bahtya/adb-proxy-browser
Releases · Bahtya/adb-proxy-browser
v0.8.0
0.8.0 Release Notes
0.8.0 is the first release that consolidates the ADB startup, packaged binary, device discovery, tunnel reuse, and terminal interaction work that landed across the 0.7.x line.
Highlights
1. Embedded ADB in packaged apps
- Windows/macOS/Linux build artifacts now bundle
platform-toolsinto the application resources. - CI downloads the correct
platform-toolsbefore packaging, so release artifacts no longer depend on a separately installed ADB binary. - Packaged builds now consistently use
electron-builder.yml, which keepsextraResourcesand embedded ADB behavior aligned with CI.
2. More reliable ADB startup and device detection
- Improved ADB server startup handling, including clearer failures when the binary is missing or server startup is abnormal.
- Restored and hardened the device manager flow around
adbkit, device refresh, and listener registration. - Startup now better tolerates the case where ADB initializes slightly after the window becomes visible.
- Device updates are pushed to the renderer more reliably, reducing the chance of being stuck on
No Devicesafter launch.
3. Reuse existing ADB services instead of fighting them
- If another application already started the local ADB server, the app now reuses it instead of forcing its own copy.
- Existing port forwards are reused where possible, especially for the proxy/SSH tunnel path.
- This makes coexistence with other Android desktop tools and existing ADB-based workflows more practical.
4. Better tunnel and runtime visibility in the UI
- Added in-app version display so it is clear which build is actually running.
- Added tunnel status / connection status panels to the welcome/status view.
- Added an ADB terminal mode alongside the SSH terminal mode.
- Enabled Electron remote debugging for release builds to support direct MCP / DevTools inspection of packaged apps.
5. Terminal quality improvements
- Fixed ADB terminal Enter handling so typed commands execute correctly in packaged builds.
- Improved terminal focus behavior when opening the panel.
- The terminal now gives clearer interaction feedback:
- explicit ready/input state
- visible command prompt cue (
>) - clearer distinction between typing, running, and streaming output
- cleaner live guidance in the terminal header area
Included 0.7.x work summarized
0.7.44- restore pureadbkitusage and remove incorrect binary dependency pathing0.7.45- stabilize ADB server/device manager behavior and health checks0.7.46- start bundlingplatform-toolsinto packaged apps0.7.47- fix packaging so embedded ADB actually ships in release artifacts0.7.48/0.7.49- fix device refresh timing and listener registration issues0.7.50- add visible app version and harden fallback device detection0.7.51- improve reuse of existing ADB server and forward state0.7.52- add terminal/tunnel UI panels0.7.53- enable remote debugging and improve terminal focus0.7.54- fix ADB terminal newline / Enter behavior0.8.0- polish terminal interaction feedback and shell usability
Upgrade notes
- Existing users can move directly from any
0.7.xbuild to0.8.0. - If you already run another local ADB-based tool,
0.8.0is designed to reuse the existing local ADB server when possible. - If you debug packaged releases, the remote debugging endpoint remains available on
127.0.0.1:9222.
v0.7.54
Full Changelog: v0.7.53...v0.7.54
v0.7.53
Full Changelog: v0.7.52...v0.7.53
v0.7.52
Full Changelog: v0.7.51...v0.7.52
v0.7.51
What's Changed
- reuse an already-running ADB server instead of falling back to a slow or failing reconnect path
- surface connected devices in packaged Windows builds before
adbkitfinishes loading, removing theNo Devicesstartup regression - switch tunnel forward management to the bundled ADB binary so packaged builds no longer fail with
spawn adb ENOENT - reuse an existing
tcp:7890 -> tcp:7890forward without deleting it on app exit, so external ADB tunnel workflows keep working - harden server detection with retry and timeout rechecks to avoid false
Failed to start ADB servererrors when another ADB instance already owns port 5037
v0.7.50
Full Changelog: v0.7.49...v0.7.50
v0.7.49
Changelog
Device listener timing fix
- Create
DeviceManagerbefore async ADB initialization starts. - Register device and server listeners before
init()sodevices:updatedevents are not lost during startup.
Release impact
- Fix portable builds where ADB starts successfully but the UI still stays on
No Devicesbecause the main process never forwards the device update. - Bump version to
0.7.49.
v0.7.48
Changelog
Device detection fix
- Retry initial ADB device enumeration after startup instead of relying on a single immediate
listDevices()call. - Forward
devices:updatedevents from the main process to the renderer so the UI can refresh when devices appear after launch.
Release impact
- Fix the case where ADB initialization succeeds but the app still shows
No Devices. - Bump version to
0.7.48.
v0.7.47
Changelog
Build packaging fix
- Make npm build scripts explicitly use
electron-builder.yml. - Keep electron-builder packaging settings in one place so
extraResourcesis actually applied during release builds. - Preserve embedded
platform-toolspackaging intoresources/platform-tools.
Release impact
- Fix the release pipeline so packaged builds can include the bundled ADB resources as intended.
- Bump version to
0.7.47.
v0.7.46
Changelog
ADB packaging
- Bundle Android platform-tools into packaged builds instead of requiring users to install adb separately.
- Add a CI preparation step that downloads platform-tools before electron-builder runs.
- Copy platform-tools into the app resources directory during packaging so the app can start adb from an embedded binary.
Runtime ADB behavior
- Keep ADB initialization asynchronous so the app window can appear before adb/device tracking finishes.
- Reuse an existing ADB server on
127.0.0.1:5037when another program has already started it. - Start the bundled adb server only when no existing ADB server is running.
- Improve adb startup error reporting and adbkit module loading compatibility.
Dev/build workflow
- Add a
prepare:platform-toolsscript for CI packaging. - Add a tracked placeholder platform-tools directory so packaging config has a stable source path.