kazeia/kazeia-android/app
Kazeia Team 751e3e0868 memory: periodic sweep + expand kill list (photos, calendar, contacts, vending, tachyon…)
First sweep reclaimed 1.6 GB as advertised but ColorOS respawned most
of the killed apps within 1–3 minutes — observed quicksearchbox coming
back at 210 MB, photos/calendar spawning fresh at 150+ MB each. Two
changes:

1. Expanded KILL_TARGETS with the packages that showed up in the
   respawn wave (Google Photos, Calendar, Contacts, Play Store,
   rkpdapp, Tachyon/Meet, permissioncontroller, notificationmanager,
   safecenter, securitypermission, sau, acore). These are user-facing
   but not needed while Kazeia is the active task; they re-spawn on
   demand if the user switches away.

2. New startPeriodicOptimizer() runs freeRamForModels every 60 s
   for the lifetime of KazeiaService so re-spawned apps get trimmed
   again without a service restart. Tied to serviceScope so it stops
   cleanly on destroy.

Net effect observed: avail RAM stays ~1.2–1.5 GB higher than without
the sweep. Models still land in ZRAM once the LLM/TTS/STT finish
loading (Kazeia itself is ~5 GB across them), but page-fault thrashing
during inference is noticeably reduced.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-14 22:44:09 +02:00
..
src/main memory: periodic sweep + expand kill list (photos, calendar, contacts, vending, tachyon…) 2026-04-14 22:44:09 +02:00
build.gradle.kts TTS tremor investigation: identify cross-arch numerical floor, gate diag flags 2026-04-13 00:15:14 +02:00
proguard-rules.pro Initial commit: Kazeia TTS pipeline on NPU via ExecuTorch 2026-04-09 08:42:11 +02:00