Skip to content

v13 - Android 11 launch/boot-wait hardening

Choose a tag to compare

View all tags
@Jordan231111 Jordan231111 released this 03 Jun 15:39
· 16 commits to main since this release
v13
4424b28

What changed

This release hardens the Android 11 / Rvc64 online boot stage after reports where PREP succeeded but DATA failed with:

instance 'Rvc64' did not boot / become adb-reachable within 300 s

The issue discussion showed ADB works after manually opening the instance, so the fix focuses on host-side launch/wait/adb behavior rather than changing Magisk, the APK, or the disk payload.

Fixes

  • Boot-And-Wait now retries HD-Player --instance Rvc64 if the target player process never appears.
  • The boot wait is scoped to the requested instance, so another running BlueStacks instance cannot mask an Rvc64 launch miss.
  • Inherited ANDROID_ADB_SERVER_PORT=5037 is ignored because 5037 is the shared default adb server port that can reintroduce SDK adb vs HD-Adb conflicts.
  • Private adb server overrides such as 15040 are still honored.
  • Shutdown now waits only as long as needed, up to 20s, to reduce stale adb listener races around 5555.
  • Timeout logs now include the adb server port, candidate device ports, target HD-Player count, and the last connect/getprop result.
  • README download link now points to v13.

Validation

  • Live tested on Android 11 / Rvc64 with a foreign listener still occupying 5037; Rvc64 booted through the private HD-Adb server and reached sys.boot_completed=1.
  • PowerShell parser checks passed for tools/bsr_magisk.ps1 and tools/bsr_engine.ps1.
  • tests/Run-Resolve-Tests.ps1: 44 passed, 0 failed.
  • tests/Run-Tests.ps1: 28 passed, 0 failed.
  • tests/Check-Embedded-Sync.ps1: embedded engine, Magisk orchestrator, and APK are in sync.

Asset

  • blueStackRoot.cmd
  • Size: 21,379,513 bytes
  • SHA-256: 4022D3BA78E7243EA49F3CF268D87A3025D363EFD53842CC0F777C2178121626
Assets 3
Loading