Memory Butler v4

Memory Butler v4 — new identity (memory_butler), evolution of the ZRAM Manager line.

WebUI (4 tabs):

• Home — memory-health hero, live gauges, swap hogs, kill ticker, recommendation slot
• Tune — profile dropdown, allocation slider + byte calculator, compression & paging, disk-swap fallback section, Advanced vault (collapsed), Apply & Reboot
• Apps — gaming-mode card (auto trigger + manual override), per-app Stay-Alive/Suspend policies, game detection, cached app list (weekly refresh + Rescan), restore-suspended
• Insights — bench Snapshot/Report scoreboard, kill history, diagnostics terminal, Learn cards, About/Uninstall

Engine: persistent bench logger (/data/adb/memory-butler/bench.log, survives updates); session snapshot before every Apply & Reboot; boot marker in service.sh. Disk-swap fallback backend: creates /data/memory-butler-swapfile (1/2/4G, fallocate-first) at boot when enabled in Tune, attached behind zram; removed on uninstall.

v51 fixes: App Policy scan rewritten — the old version walked /data/app dirs directly, which fails under file-based encryption (exit 1). New scan_apps.sh resolves each APK via pm path (works), scans the APK tail for engine libs (libUE4/libil2cpp/libunity/libGLES/libvulkan/libcocos), caches to apps_cache.txt for a week so the list loads instantly; Rescan button forces refresh.

Migration: fresh install auto-imports config.prop + bench.log from a legacy ZRAM Manager install — uninstall the old module afterwards so only one boot script runs.

Update channel: ships updateJson → memory-butler/update.json in this repo.

SHA256: bb3786b9b0515921f79afbad8140d7df79f397c4fc0aa9382f14c7998dd02959

---

Techniques studied from third-party modules for reference only — all code original.

v54 fixes: Clean display names (curated map for common apps + smart prettify fallback — no more raw package strings); variant packages bundled into one family card (base.pkg · N pkgs, policy applies to all members).

v55 fixes: App list = installed apps + flashed GApps only (ROM/AOSP/system packages never scanned); fresh-install zram default 50% → 70%.

ZRAM Swap Configurator v4.0 — Zygisk-Next Style UI

ZRAM Manager v2 — Zygisk-Next style (versionCode 40)

Dark obsidian theme, hero status banner with live swap-utilization gauge, 2x2 stat cards, profile presets, floating action dock, live memory calculator.

Known bug (fixed in v3): live status numbers do not update — ksu.exec was called with a JS function object as callback instead of a callback name string.

Update channel: ships updateJson → zram-manager/update.json — KernelSU Manager auto-discovers newer releases (currently v3).

SHA256: 563001c5d510fb39cdf4f6cb978e4e499c3cd38aec2f90c64ff5ed6aba34b545

---

ZRAM Swap Configurator v4.0 — Draft WebUI

ZRAM Manager v1 — Draft (versionCode 40)

Minimal single-card layout (live status + refresh button). Baseline build.

Update channel: ships updateJson → zram-manager/update.json — KernelSU Manager auto-discovers newer releases (currently v3).

SHA256: 134af3abb84688910b3b7a162f60b8b9371c3e2057387f6afcbe3220fde5e810

---

ZRAM Swap Configurator v4.0 — AZenith-Inspired UI

ZRAM Manager v3 — Latest (versionCode 42, latest)

3-page cyber-obsidian UI (floating glass pill nav: Status / Tuning / Advanced).

• Status — hero memory-core card, 2x2 stat grid, device architecture readout
• Tuning — 1-tap profiles, live allocation slider with byte calculator, algorithm chips, swappiness, swap priority, Apply & Reboot
• Advanced — VM watermarks, LMKD props, diagnostics terminal, Snapshot + Report bench buttons

Apply & Reboot: saves config.prop and immediately reboots — always-clean, faster than the previous live swap rebuild.

Bench logger (bench.sh): every Apply snapshots the outgoing config's session — compression ratio, swap fill %, stall pressure, swap churn — into /data/adb/zram-manager/bench.log, which survives reboots and module updates. Boot marker logged per session. Report prints a per-resize scoreboard (sessions, hours, ratio, swap fill, stalls, churn rate) so you can compare ratios and pick the best for your workload.

Bug fix: correct ksu.exec callback protocol — live status now updates correctly.

Update channel: ships updateJson → zram-manager/update.json.

SHA256: 4df04b51ba2b3620b55fe7a63aaaac899ee018e6150e0a5841a96cbcf7005026

---