Repository navigation
LayaWave Android preview 12
Pre-releaseLayaWave Android integration preview: LastWave's complete music app plus NewTube v1.15.0 video playback and shared Laya filtering controls.
Install the APK on Android 10 or later (arm64 or x86_64). This preview uses Android's debug signing key. A production signing identity must be configured before a stable release.
Configure your deployed Laya service's HTTPS address and allow metadata processing under Settings → Laya Feed Control. Without that service, explicit local metadata rules remain available; semantic filtering and free-form prompt interpretation require the backend. Explicit control prompts (for example, “disable filters” and “enable filters”) also work offline and retain saved topic preferences. Saving an address checks that both Laya models are ready without sending content metadata.
The backend implementation, deployment files and exact Android integration source are in this release's commit. Filtering considers text metadata, offers reasons and reveal actions, and does not guarantee visual content detection or factual verification. The video settings tree, choice dialogs and global settings search now use LastWave's headers, cards, typography and theme alongside its original music frontend. NewTube's native video player and remaining account/comment/casting panels retain upstream layouts in this preview. CI checks startup, navigation, saved toggles, offline prompt commands and video settings/search before publishing an APK. Online YouTube playback still needs device testing; the CI network received a YouTube sign-in/bot challenge in prior runs.
Video settings are also available from LastWave's main Settings screen. This update preserves NewTube's local TV HTTP discovery configuration, keeps Laya metadata HTTPS-only, and fixes feed results being discarded when preferences change during loading. Playback choice and gesture persistence are included in the runtime gate.
Delayed request handling
Preference changes and metadata-consent revocation cancel obsolete HTTP work. Queued checks retain their captured policy and destination, and only decisions for the current settings can update a row. Delayed prompt results cannot overwrite newer edits. Responses also validate the content ID before applying a decision.
Shared-client tests use a local HTTPS fixture and real Android preferences to verify consent, readiness, redirects, caching and preference changes. They check integration behavior, not Laya classification accuracy. The backend invalidates cached evidence decisions when their curated record changes or expires, and Android checks evidence expiry before reusing a cached result.