AudioShare USB v3.0.0-rc.2

AudioShare USB v3.0.0-rc.2

Second public release candidate of the portable Windows-to-Android USB audio
application.

Improvements since rc.1

• Keeps usable phones visible when an optional ADB metadata request or a later
  device refresh fails temporarily.
• Requires an explicit successful Android activity-launch status and gives
  actionable errors for wrong-signature or newer companion installations.
• Extends the native capture-start budget so the global-capture compatibility
  fallback is not interrupted prematurely.
• Adds capture-discontinuity diagnostics and fails early if the packaged native
  DLL is missing a required export.
• Renews Android's speaker-route grace window after every transient route-data
  loss and reports a bounded playback-stalled error if pending PC audio stops
  advancing through the phone's AudioTrack.
• Stops an identical automatic failure after three attempts in one minute so a
  broken environment is shown clearly instead of retrying forever.
• Makes Disconnect stop the current session without forgetting the preferred
  phone.
• Migrates preferences into the CodeinScrubs application-data namespace, keeps
  a crash-recovery backup, and makes persistence failures visible.
• Embeds the matching signed Android 1.0.0-rc.2 companion and removes an
  unused Linux ADB binary from the Windows-only package source.

Release-candidate limitations

The portable executable remains unsigned because no trusted Windows
Authenticode certificate is available, so Microsoft SmartScreen may display an
unknown-publisher warning. A ten-minute screen-off run, repeated cable recovery,
measured median/p95 latency, restricted-PC validation, and a two-hour endurance
run remain manual gates before stable promotion.

Download the Windows ZIP, verify its adjacent SHA-256 file, extract the entire
archive into a user-writable directory, enable USB debugging, and run
audioshare.exe without administrator access.

New users should follow the
beginner guide,
which explains the complete setup in plain language and clarifies that Android
Studio and its desktop-deployment tool are not required.