Fixed
- Restart ADB now reconnects network devices.
adb kill-serverdrops every
TCP connection, and network devices (ip:port) don't re-attach on their own
the way USB devices do — so after a restart the device list came back empty
even though the daemon restarted fine. Restart ADB now remembers the
connected network devices and reconnects them automatically, and reports
which ones came back (or which to reconnect manually via Scan Network /
Connect IP). (Reddit report.) - Windows: installers now upgrade in place. Previously the
.msimade you
uninstall the old version first. The MSI version encoded the release counter
in the 4th version field — which Windows Installer ignores for upgrade
detection — so every build looked like the same version. The build/3rd field
now carries a strictly-increasing, semver-ordered value, so new releases
install on top of the old one. (First applies upgrading from this build
forward.) - Network scan now connects the devices it finds. The scan could report
"found N devices, connected 0" — the port sweep detected them, but the
follow-upadb connectraced a cold adb daemon and failed (which is why a
manual Restart ADB then made them connect). The scan now starts the adb
server first and retries each connect once, so found devices connect on the
first pass. (Reddit report.)
First-run warnings
These builds are unsigned. Your OS may complain on first launch:
- macOS (Gatekeeper): the first-launch dialog on macOS 15+ only offers "Move to Trash" or "Done" — click Done, then either:
- Terminal:
xattr -dr com.apple.quarantine "/Applications/Shield Optimizer.app"(one-time, then double-click as normal) - GUI: System Settings → Privacy & Security → scroll to the "Shield Optimizer was blocked" message → Open Anyway → enter password
- Terminal:
- Windows (SmartScreen): "More info" → "Run anyway".
- Linux:
chmod +x ShieldOptimizer*.AppImagebefore running.
See the v2 README for setup and feature docs.