Skip to content

Deliver Android 12+ APKs, reliable storage and mobile WebUI - #333

Merged
itlezy merged 74 commits into
mainfrom
fix/android-delivery-diagnostics
Nov 15, 2026
Merged

itlezy merged 74 commits into
mainfrom
fix/android-delivery-diagnostics

Conversation

@itlezy

@itlezy itlezy commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Android now has a minimal Kotlin launcher for Android 12+ that configures the Rust daemon, acquires storage/background permissions, starts its foreground service and opens the existing WebUI. The service starts manually after a reboot. A signed universal APK joins both Android native archives in the nightly release contract.

The batch fixes completed-file publication on shared storage: use atomic no-replace rename where supported, choose numbered names on collision, and use an exclusive verified copy when the filesystem rejects that rename operation. Existing files remain protected, including recovery after interrupted delivery.

Automatic P2P address selection retains normal operating-system routing. Explicit IP/interface and VPN Guard selections remain strict and never fall back silently. This fixes startup on the tested Android 12 phone with a Linux 4.14 kernel without weakening explicit routing controls.

The WebUI gains phone layouts, saved light/dark/system appearance, process CPU/RAM diagnostics and direct diagnostic-download/shutdown buttons. Android follows the system theme. The approved proposal-5 icons are applied to Android, WebUI favicons and existing desktop package resources, alongside per-platform run instructions.

Release inputs select accepted Build/Harness/Tooling main revisions and an independently verified attested multiarch builder image. Original-APK diagnostic replay finishes host tool/cache setup before checking out the selected original source; only the pinned replay executor and sanitized evidence upload follow it.

Validation on final head f24e97c:

  • Required CI passed 14/14, Optional platform CI passed 8/8, and CodeQL/branch checks passed. The high cache finding was repaired and independently reviewed. The medium original-source checkout warning remains; its reviewed trust boundary is documented in the resolved discussion.
  • Full local validation passed on frozen R f24e97c / Build 43515795 / Harness 281ccbc / Tooling f88a8ce6: Windows WebUI/browser, workspace, observed VPN-egress and live REST/OpenAPI; complete GNU/musl x64/ARM64 validation and Ubuntu/Alpine images; both Android ABI Clippy, diagnostics, workspace test linking, release linking and ELF audits. Retained local-check report: 20261114T225913Z-3c6733c3 (all six stages returned zero).
  • Publish-disabled candidate 43645535102 passed every native package, both Android archives, both musl packages, packaged lifecycle checks and all Ubuntu/Alpine image checks. All seven API 31–37 APK jobs reached the obsolete fixture-cleanup filename after delivery/collision/restart/history/hash verification; accepted Harness PR build: update rustls for 2026 advisories #111 corrected only that test-owner contract.
  • All seven source-bound diagnostic replays of that exact bff APK passed with accepted Harness 281c. Those receipts remain publication-ineligible and do not replace fresh merged-source APK/eligible runtime gates.
  • The first Android 17 replay navigation failure and one macOS Intel profile-reopen failure were retained and independently inspected; one unchanged rerun of each passed. Their initial causes remain unconfirmed; no blind key actions, sleeps or lock bypasses were introduced.
  • Independent artifact inspection confirmed package/proof hashes and source identities, the BSD-2-Clause declaration for libpcpnatpmp, Android archive layout versus run instructions, and proposal-5 artwork in the actual APK.
  • Historical source 20a0742 passed 13 fresh Android 12 phone cases. Its public campaign retained about 74 minutes of network observations with 218 eligible contents, HighID/Kad/publication evidence and no observed peer upload; it then ended after an unclassified RuntimeError and verified harness stop. This is neither final-APK evidence nor 24-hour endurance proof.

After merging, fresh actual-main checks and a publish-enabled Nightly must qualify newly built artifacts and all seven eligible APK runtime gates before publication. Further Android runtime tests use emulators unless the operator requests a phone.
Refs #226 (RUST-FEAT-056). FireOS, Termux runtime and boot-resume qualification remain separate acceptance work; no Beta 3 promotion is included.

Threepwood-7 added 30 commits November 13, 2026 10:03
Threepwood-7 added 24 commits November 14, 2026 09:04
Comment thread .github/workflows/nightly.yml Fixed
Comment thread .github/workflows/nightly.yml Resolved
@itlezy
itlezy merged commit 23e685b into main Nov 15, 2026
67 of 70 checks passed
@itlezy
itlezy deleted the fix/android-delivery-diagnostics branch November 15, 2026 01:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants