Skip to content

Nova PR #117 Thor dual-screen debug APK

Pre-release
Pre-release

Choose a tag to compare

View all tags
@papi-ux papi-ux released this 05 Jul 18:38
pr117-thor-dual-screen-debug
c160817

Field-test APK for Nova PR #117: Thor dual-screen companion routing + NovaHUD reconnect FPS fix.

This is a debug-signed, arm64-v8a APK intended for AYN Thor field testing only.
It should remain a prerelease asset until real Thor hardware confirms the routing behavior.

Install note: uninstall any release-signed Nova build first if Android reports a signature mismatch.

Updated build: PR #117 follow-up at commit a2c24c6.

This refresh includes:

  • PR #117 display routing fix for launching streams from the Thor bottom/companion screen.
  • Dedicated stream-display launch trampoline so the singleton companion controls activity no longer bootstraps Game.
  • Reconnect/relaunch now uses the same display-aware launcher instead of plain application-context startActivity.
  • Issue #118 NovaHUD FPS fix: decoder rolling FPS windows are reset on stream setup/reconnect and when frame numbering restarts, so fresh post-reconnect HUD samples are not divided by stale pre-disconnect timing.

Expected display-routing log shape:

  • Nova: Android display role stream id=... target=...
  • Nova: Android display role companion id=... stream_id=...
  • Nova: Android display launch stream id=...

Expected Thor field-test behavior:

  • Launching Nova from the top screen should keep the game on top and controls on bottom.
  • Launching Nova from the bottom screen should still move the stream/Game activity to the selected top/primary stream display, then show controls on the bottom/companion display.
  • Disconnect/relaunch should not get stuck at “preparing video, audio and controller input...” because of a plain relaunch on the wrong display.
  • After disconnect/reconnect, NovaHUD FPS should no longer collapse to obviously wrong single/double-digit values while the stream is smooth and the legacy/AYN FPS source reports normal FPS.

APK SHA256:
6e2e023adcaad64bea3d3f398b836819ee2e51c2a3e4891b53c500d701782036

Known follow-up to validate separately:

  • If audio still routes to the bottom/control display after this build, treat that as a separate Android audio-device/display routing bug and attach a fresh log plus exact output device behavior.
Assets 4
Loading