Skip to content

Releases: Bahtya/adb-proxy-browser

v0.8.0

06 Mar 11:14

Choose a tag to compare

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-tools into the application resources.
  • CI downloads the correct platform-tools before packaging, so release artifacts no longer depend on a separately installed ADB binary.
  • Packaged builds now consistently use electron-builder.yml, which keeps extraResources and 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 Devices after 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 pure adbkit usage and remove incorrect binary dependency pathing
  • 0.7.45 - stabilize ADB server/device manager behavior and health checks
  • 0.7.46 - start bundling platform-tools into packaged apps
  • 0.7.47 - fix packaging so embedded ADB actually ships in release artifacts
  • 0.7.48 / 0.7.49 - fix device refresh timing and listener registration issues
  • 0.7.50 - add visible app version and harden fallback device detection
  • 0.7.51 - improve reuse of existing ADB server and forward state
  • 0.7.52 - add terminal/tunnel UI panels
  • 0.7.53 - enable remote debugging and improve terminal focus
  • 0.7.54 - fix ADB terminal newline / Enter behavior
  • 0.8.0 - polish terminal interaction feedback and shell usability

Upgrade notes

  • Existing users can move directly from any 0.7.x build to 0.8.0.
  • If you already run another local ADB-based tool, 0.8.0 is 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

06 Mar 10:49

Choose a tag to compare

Full Changelog: v0.7.53...v0.7.54

v0.7.53

06 Mar 10:14

Choose a tag to compare

Full Changelog: v0.7.52...v0.7.53

v0.7.52

06 Mar 09:17

Choose a tag to compare

Full Changelog: v0.7.51...v0.7.52

v0.7.51

06 Mar 07:43

Choose a tag to compare

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 adbkit finishes loading, removing the No Devices startup 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:7890 forward 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 server errors when another ADB instance already owns port 5037

v0.7.50

06 Mar 04:29

Choose a tag to compare

Full Changelog: v0.7.49...v0.7.50

v0.7.49

06 Mar 03:39

Choose a tag to compare

Changelog

Device listener timing fix

  • Create DeviceManager before async ADB initialization starts.
  • Register device and server listeners before init() so devices:updated events are not lost during startup.

Release impact

  • Fix portable builds where ADB starts successfully but the UI still stays on No Devices because the main process never forwards the device update.
  • Bump version to 0.7.49.

v0.7.48

06 Mar 03:30

Choose a tag to compare

Changelog

Device detection fix

  • Retry initial ADB device enumeration after startup instead of relying on a single immediate listDevices() call.
  • Forward devices:updated events 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

06 Mar 03:05

Choose a tag to compare

Changelog

Build packaging fix

  • Make npm build scripts explicitly use electron-builder.yml.
  • Keep electron-builder packaging settings in one place so extraResources is actually applied during release builds.
  • Preserve embedded platform-tools packaging into resources/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

06 Mar 02:42

Choose a tag to compare

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:5037 when 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-tools script for CI packaging.
  • Add a tracked placeholder platform-tools directory so packaging config has a stable source path.