Skip to content

Integrate Android 16 Waydroid on Jaguar Screen - #53

Open
ajlennon wants to merge 75 commits into
mainfrom
feat/jaguar-screen-waydroid-2gb
Open

ajlennon wants to merge 75 commits into
mainfrom
feat/jaguar-screen-waydroid-2gb

Conversation

@ajlennon

Copy link
Copy Markdown
Member

Summary

  • integrate the pinned LineageOS 23.2 / Android 16 Waydroid payload for the 2 GB i.MX8MM Jaguar Screen
  • select the Etnaviv, DMA-heap, Binder AIDL6, V4L2 decode, AppArmor, and constrained LXC host runtime
  • require artifact hashes, immutable source provenance, Android and host SBOMs, NOTICE evidence, and release-mode gates
  • add the digest-pinned KAS host-image workflow and board evidence tooling
  • retain the reconciled Jaguar Screen BSP, Qt, splash, rotation, and product-feature integration accumulated on this branch

Validation

  • Android 16 run 34823170549 completed successfully for lineage_waydroid_aesl_2gb_arm64_only-bp4a-userdebug
  • downloaded artifact aesl-lineage-23.2-34823170549-1 passes sha256sum --check --strict SHA256SUMS
  • validate-waydroid-build-info.py --release-mode integration accepts the artifact provenance
  • workflow YAML parses successfully and git diff --check passes
  • host-image CI and physical-board runtime evidence remain follow-on gates after merge exposes the dispatch workflow on the default branch

AI disclosure

This change set was developed with assistance from OpenAI Codex. Final technical responsibility remains with the repository maintainers.

Use Node 24-compatible action majors before exposing the Android 16 host build on the default branch.

Assisted-by: OpenAI Codex
Resolve the BSP submodule divergence with the published integration commit while retaining the current layer-adoption gate and shared-board fixes from main.

Assisted-by: OpenAI Codex

This branch has not been deployed

No deployments
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.

1 participant