Repository navigation
WaEnhancer Community 0.0.9
WaEnhancer Community 0.0.9
SHA-256: 5ce62372ba4117428bb5f95bac11cdb1e68be1665bfd5715319f2c3ccbbacbdc
Changes since v0.0.8.
What's changed
- #65 Fix blue-on-reply receipt release and sync compatible upstream fixes
- #64 Expand opt-in Liquid Glass to WhatsApp surfaces; document One UI heads-up feasibility
- #66 Fix unified receipt routing, glass capture, listener races and history preservation
- #67 Fix public Android SDK compilation of shared glass frame timing
- #68 fix: register hook-read preference keys so Liquid Glass, Ghost/DND and others reach WhatsApp
- #69 fix: stop app-surface Liquid Glass from crashing WhatsApp on startup
- #70 feat: rebuild conversation Liquid Glass on WaThemer's pane model
- #71 feat: live glass on every surface and a neutral power-saving fallback
- #72 docs: record Liquid Glass optical report review and next steps
- #73 feat(glass): optical corrections LG-01..LG-13 behind experimental switches
- #74 fix(glass): sticky live budget and one pane per surface
- #75 fix(glass): retain stopped sessions and recover window-local surfaces
- #76 fix(glass): keep the header band from growing the holder to full height
- #77 feat(glass): log home surface bindings and the home view hierarchy
Full changelog
This section compiles the descriptions of the pull requests included in this release.
#65 — Fix blue-on-reply receipt release and sync compatible upstream fixes
Merged by contribution from @igorcv88.
With Hide Delivered and Send Blue Ticks upon Reply enabled, automatic reply receipts can remain blocked by downstream guards and an enqueue/authorization race. Publish per-message authorization before queueing, honor it at direct/dispatch/protocol gates, and restore pending state if enqueueing fails. Use exact SendE2EMessageJob discovery and its destination for chat/status routing.
Audit all 55 original-upstream commits since 4d91b33c through 749c3cae. Port compatible download-path, slider, locked-chat, ML Kit picker, online-status, media-preview and layout corrections; add candidate WA/Business catalogs through 2.26.38.xx. Record every disposition in docs/UPSTREAM_AUDIT_2026-10-06.md. The X source URL returns HTTP 451, so newer X commits remain unaudited.
Add AGENTS.md, a Git symlink CLAUDE.md -> AGENTS.md, and handoff.md with the corrected user report (Community v0.0.8, WhatsApp 2.26.33.76), current state, pending features, and the Kotlin/YukiHookAPI/KSP/RemotePreferences/DataStore/status-history migration sequence. The user chose compatible fixes now and migration/new features separately.
Validation: 14 focused JUnit tests passed; Java 17/API compilation of 11 changed/new classes and the modified DexKit resolver passed using Android 36/DexKit with stubs for unavailable dependencies; edited XML and symlink checked; git diff --check passed. Full Gradle tests/APK build are blocked at distribution download. Two-phone receipt validation and physical validation of the ports remain pending. No workflows dispatched.
#64 — Expand opt-in Liquid Glass to WhatsApp surfaces; document One UI heads-up feasibility
Merged by contribution from @igorcv88.
The Liquid Glass settings page previously covered only the floating navigation bar and scroll-to-bottom button. This PR adds experimental, independently opt-in adapters for toolbars, search/filter controls, FABs, composer, quoted replies/drafts, message bubbles, information/action cards, and native popup/dialog/sheet panels. New toggles default off.
Adapters replace native backgrounds without reparenting Views or changing IDs, layout params, listeners or IME. Bubble discovery uses a semantic DexKit anchor and refuses ambiguous matches. Stateful native masks preserve silhouette, padding, state/level/visibility, hotspot bounds, RTL and mirroring. Native background rebinds are adopted without nesting wrappers. Geometric child-background removal has been removed entirely; restoration preserves native padding/tint updates.
Review corrections: shared GPU RenderNode capture runs once per Choreographer frame token per window, with AGSL applied to background slices via RenderEffect. Software capture remains a bounded 10 Hz fallback. Providers own exclusions, weighted frame budgets and independent recoverable GPU/software backoff. Normal/motion/conserving tiers use output resolution, sampling/mask cost, FrameMetrics feedback, battery saver and thermal status. A fixed capture-only drawChild hook bypasses cached glass display lists; a ripple guard preserves static layers without retargeting HWUI animators. Incremental add/attach/background discovery and cached resource IDs replace periodic whole-tree scanning.
Material shaders are compiled once and all uniforms update when the immutable spec or geometry changes. Sampling failures recover independently of invalid AGSL compilation. The inline review's no-optics fallback issue is fixed: this drawable applies the 72% opacity floor rather than assuming it has a BlurView/RenderScript backend.
Same-process WindowStackBackdrop composes Activity/Dialog/Popup ancestry, intervening glass and dim layers through the target window, excluding higher/unrelated windows. Incomplete topology fails closed. This does not reproduce cross-process surfaces, SurfaceFlinger animations, special-window ordering or protected video. Existing navbar/scroll-button capture remains independent.
Validation: Java 17/API checks against Android 36 and DexKit, with stubs for unavailable internal/AndroidX/Material/Kotlin dependencies; 62 focused JUnit tests passed; git diff --check passed. Tests cover frame-token idempotence, count/output-work caps, tier hysteresis, retry recovery, fallback opacity and window topology/order/cycles. This is not a complete Gradle/APK build; the Gradle distribution download was blocked by the environment. No workflow was dispatched.
Full APK build, actual AGSL/HWUI rendering, stateful WhatsApp scenarios and S25 Ultra performance calibration remain pending. Custom ViewGroups, native animations/shadows and additional WhatsApp versions may need adapters. Initial work ceilings are heuristics, not measurements on the device. Opaque parents or missing wallpaper underlay can still make targets appear flat.
The checked-in report docs/LIQUID_GLASS_PORT_AND_HEADSUP_2026-10-01.md maps all 12 review points and the inline comment to changes and validation, documents limitations, and lists physical acceptance scenarios including grouped/selected/reaction/media/quoted/disappearing/RTL bubbles and popup over dialog. Heads-up work remains investigation only; no SystemUI implementation or scope was added.
#66 — Fix unified receipt routing, glass capture, listener races and history preservation
Merged by contribution from @igorcv88.
Review the unified master after #64 and #65 merged. Correct #65's status-reply route using the outgoing job's quoted status key and matching author PN/LID; queue only the exact incoming quoted item, independent of viewer changes, keep blue-on-reply independent of manual status buttons, and fix the raw-LID getter. Confirm #64's no-optics opacity fix was already present.
Preserve native text/children during shared glass capture, isolate snapshot lifecycle/contact/status callbacks, and serialize receipt authorization/cache updates. Replace destructive version 4–6 history upgrades with a transaction that preserves edits and archives original receipt rows; reject unmapped older row-ID schemas and downgrades without erasing their files. Older unsupported schemas can still enter the existing in-memory recovery path.
Validation: 216 current-source JUnit tests across 27 classes passed; five production-SQL SQLite preservation/rollback tests passed; partial Java 17/API 36 checks and all XML/diff checks passed. These offline tests use the shims/signature stubs documented in docs/UNIFIED_RUNTIME_REVIEW_2026-10-06.md. No APK/device result is claimed. Full Gradle APK/unit tests are blocked before configuration by the inaccessible Gradle 8.14.5 distribution, and JDK 21 is unavailable locally. No workflows dispatched.
Refresh upstream: Dev4Mod master still points to 749c3cae, with zero newer commits. Update ARCHITECTURE.md, the audit and handoff.md with findings, acceptance and the build gate. Kotlin UI, Yuki/KavaRef/KSP, preference transport, DataStore and coordinated status/history-provider migrations remain pending until the required full baseline is available; translation, system emoji, public recordings and compatibility ports stay separate.
#67 — Fix public Android SDK compilation of shared glass frame timing
Merged by contribution from @igorcv88.
The manual runner build fails compiling SharedGlassBackdrop because Choreographer.getFrameTimeNanos() is hidden from the public SDK. Use public postFrameCallback timestamps through a clock shared across windows, preserving once-per-token pre-draw capture and shader budgeting. Coalesce pending requests; callbacks do not invalidate views, self-schedule or retain window providers. Bootstrap/fallback covers the initial missing token; an idle-to-active first traversal can reuse the prior backdrop until the next callback. The 100 ms software limit remains.
Three focused clock tests passed. Partial glass renderer/backdrop/adapters/settings compilation passed against the public API 36 stub jar from Sable/android-platforms at 1e98db1a199e8f7f85541af26bfc27019501b132, verified to exclude the hidden getter. Third-party/module signature stubs remain. Correct the earlier validation record: the cached framework jar exposed hidden APIs and did not validate the public SDK surface. Update handoff and the unified review report.
Based on merged #66 (3963084). Full APK and device validation remain pending; the supplied runner log is a failed build. No workflows dispatched. Rerun the manual build on this head before advancing the foundation migrations.
#68 — fix: register hook-read preference keys so Liquid Glass, Ghost/DND and others reach WhatsApp
Merged by contribution from @igorcv88.
Problem
HookProvider serves only keys that PreferenceSchema marks Store.PUBLIC and rejects writes to unknown keys. Hooks that read an unregistered key always see its default value inside WhatsApp, even when the settings UI shows the option as enabled. This is the same class of bug as #60.
Broken keys found by the audit
| Keys | Effect before this PR |
|---|---|
liquid_glass_{toolbars,search,fab,composer,quotes,bubbles,cards,panels} (#64) |
None of the eight Glass surfaces could turn on inside WhatsApp |
ghostmode_actual, dndmode_actual |
Ghost/DND tiles and home-menu toggles had no effect on the hooks |
call_recording_use_root |
Root call recording was never used |
custom_versions_wpp/business |
User-added supported versions were ignored |
Contact-online tile → show_toast_on_contact_online |
The tile toggled a key that does not exist; the real key is showonline |
BaseTileService always wrote to the public file |
The Smart Typing tile and the settings screen got out of sync (always_typing_global is PRIVATE) |
BasePreferenceFragment used waex_color_* |
Disabling the preset under Monet and recreating the activity never ran (the real keys are wae_*) |
Tests
LiquidGlassSettingsTest.everySurfaceKeyCrossesTheHookBridgePreferenceSchemaTest.everyHookReadKeyCrossesTheBridge: scans literal hook reads underxposed/. Defaults with no writer are on an allowlist, with the reason for each.PreferenceSchemaTest.everyTileKeyIsInTheSchema,hookStateKeysArePublic
Negative check: run against the original schema and tile code, all four new tests fail and name the broken keys.
Validation
./gradlew :app:testWhatsappDebugUnitTest: 338 tests, 0 failures (JDK 21, SDK 36)../gradlew :app:assembleWhatsappDebug: succeeds. This is the first full build of the tree after #67.- Not done: release variant, workflow runs, device testing.
Not fixed, recorded in handoff.md
- The global Always Typing settings have no hook that reads them.
bootloader_spoofer_default_xmlis read but nothing ever writes it.- Some module-only settings are missing from the schema, so backups leave them out.
Device check
Enable only Toolbars and Composer, force-stop WhatsApp, reopen. Check that both show Glass. Then check the Ghost/DND tiles, the contact-online tile and root recording.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VJEpLuiM1hMfRR5SS8KCBK
Generated by Claude Code
#69 — fix: stop app-surface Liquid Glass from crashing WhatsApp on startup
Merged by contribution from @igorcv88.
Problem
After #68 the eight Liquid Glass surfaces reach WhatsApp for the first time, so the #64 app-surface rendering ran on a real device for the first time. On a device, WhatsApp opens on the last conversation. The header, quotes and bubbles show the simplified material (no blur or refraction) for about one second, and then the process dies.
Cause (from the code; no crash log yet)
SharedGlassBackdroprecorded the window into aRenderNode, andGlassMaterialDrawabledrew that node inside each bound view's background.- On a hardware canvas,
View.drawBackgroundrecords the background into the view's cachedmBackgroundRenderNode. The window recording therefore points at a node that draws the glass, which draws the recording. - That cycle makes HWUI recurse on the RenderThread, which crashes natively. Java try/catch cannot contain it, and the
drawChildcapture hook cannot prevent it, because a view's background node is not drawn throughdrawChild. - The timing fits: the simplified material shows before the first capture, and the crash comes as soon as the first real Glass frame closes the cycle.
- The floating bar uses
GlassSurface, a separate pipeline, which is why it never crashed.
Fix
- Remove the
RenderNodecapture and the glass path that drew it. App-surface glass now samples the existing software bitmap snapshot. A bitmap is a pixel copy with no references back to the views, so no cycle can form. - During capture, a child view that throws (for example a hardware bitmap that a software canvas cannot draw) is now skipped and logged. Previously it aborted the whole capture.
- The rule is now recorded in
ARCHITECTURE.md.
Trade-offs
- The backdrop updates at most every 100 ms, at up to 400,000 pixels and 0.35 scale, so glass can lag during fast scrolling.
- Software capture runs on the UI thread; its cost has not been measured on a device.
Validation
:app:testWhatsappDebugUnitTest: 338 tests, 0 failures.:app:assembleWhatsappDebug: succeeds.- Not tested on a device. The cycle explanation stays unconfirmed until a crash log or a device run that passes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VJEpLuiM1hMfRR5SS8KCBK
Generated by Claude Code
#70 — feat: rebuild conversation Liquid Glass on WaThemer's pane model
Merged by contribution from @igorcv88.
Problem
On the device, after #69, app-surface glass did not crash, but it was wrong in three ways:
- Stale content. The composer showed a sticker that had been behind it before a scroll. #69 replaced the crash with a full-window software snapshot (0.35 scale, at most 10 Hz), and that snapshot was out of date.
- Slow and pixelated, for the same reason.
- Nothing behind the header or search. In WhatsApp's native layout no content passes behind them: the list starts below the header, and the bar has an opaque fill.
How upstream does it
The primary source of the port is WaThemer, ayane-04/wathemer@d39b293 (GPL-3.0). It never samples from inside a view's own background:
- Each surface gets a
GlassViewpane added beneath it, with no reparenting. BackdropCapturerecords only the pane's own region on the GPU, from a named source subtree (the list host or the coordinator), drawn over the wallpaper.safeToCapturerefuses any source that contains the pane, directly or through another pane.- It refracts first and then blurs. It recaptures every frame while something is moving, and every 250 ms when idle.
GlassConversation.ktfloats the header and footer and pads the list withclipToPadding=false, so messages scroll behind the chrome.
Changes
theme/GlassPane: a port ofGlassViewandBackdropCapture, usingLiquidLens(the shader the floating bar already uses) as the optics. It records the region behind the pane at 1/4 resolution on the GPU, over the wallpaper, and applies the lens as aRenderEffect. Below Android 13, or if the lens fails, it draws the static material.theme/GlassPaneGraph: the guard that refuses any source that could contain the pane. It has no Android dependencies and is covered by 6 JUnit tests.ConversationGlassPanesbuilds the conversation screen:- Header: a wallpaper-only band, plus a live capsule whose source is the coordinator.
- Composer: a live pane whose source is the list host.
- The header and footer float and the list is padded. When this moves the content edge, the list is pinned back to its last message if it was resting there.
- WhatsApp's opaque fills are cleared.
- Every change is recorded and restored when the surface is switched off.
AppLiquidGlass: the software capture is removed. Ripple and list-selector guards are active while a pane records. Views owned by a pane are skipped by the old background-drawable path.GlassMaterialDrawableis now a static material only.- Removed: the dead live-sampling classes (
SharedGlassBackdrop,WindowStackBackdrop,GlassWindowOrder,GlassFrameClock,GlassRenderPolicy) and their 14 tests. - Docs: the settings page text,
ARCHITECTURE.mdandhandoff.mdare updated.
Not in this PR
- The home header and search (WaThemer's
GlassToolbars.ktandGlassSearch.kt), bubbles, cards, panels, quotes and FAB stay on the static material, with no live sampling, until they are ported the same way.
Validation
:app:testWhatsappDebugUnitTest: 330 tests, 0 failures (338 − 14 removed + 6 new).:app:assembleWhatsappDebug: succeeds.git diff --check: clean.- Not tested on a device. The view IDs and parent types come from WaThemer's source, not from evidence on WhatsApp 2.26.33.76. A mismatch is logged and that pane is skipped.
Device checks
- Open a chat with Headers and Message input enabled, and scroll. Messages should pass behind the header and composer and be refracted live.
- The first and last messages should rest clear of the chrome.
- Check the keyboard, reply preview, voice recording, selection mode and search in chat.
- Turn both switches off. WhatsApp's native layout should return without reopening the chat.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VJEpLuiM1hMfRR5SS8KCBK
Generated by Claude Code
#71 — feat: live glass on every surface and a neutral power-saving fallback
Merged by contribution from @igorcv88.
Why
On the device, after #70, the conversation header and composer looked right, and the user asked for every surface to get the same treatment. Two more reports:
- Green fallback. In power saving, and briefly on the composer during a screenshot, glass turns into a flat green slab.
- Cause:
GlassSpec.resolve(..., blurSupported=false)sets a 72% fill floor and adds an accent glow (refractionColor). The accent is WhatsApp green. - The floating bar uses the same fallback in power saving, since
GlassRenderer.blurSupportedreturns false there. So doeswithoutOptics().
- Cause:
- Screenshot flash. A pane drew the fallback until its next capture after the system dropped its display list.
Changes
-
theme/LiveBackdrop: the GPU recording and lens engine, extracted fromGlassPane. It records at quarter size and appliesLiquidLensas aRenderEffect. -
theme/BehindRecorder: records what the window draws beneath a view, and nothing else:- each ancestor's background;
- the overlapping siblings drawn before the view's branch (ordered by Z, then index).
It never records the view itself or anything after it. That ordering is antisymmetric, so two surfaces can never record each other (the native-crash loop from #68). Siblings that contain a live
GlassPanewhose source holds the target are skipped. -
GlassMaterialDrawable: gains a live mode (captureBehind). This brings live glass to every non-pane surface: other headers, search, FAB, quotes, bubbles, cards and panels. -
AppLiquidGlass.Session: one pre-draw pass per window captures all live surfaces in the same draw order.- Timing: every frame while the user scrolls or the layout changes, every 250 ms at rest.
- Budget: only surfaces visible on screen, taken top to bottom, until their area reaches one window or 32 surfaces. The rest draw the static material. The selection is stable while scrolling.
-
GlassPane: uses the shared engine. It recaptures immediately after its display list is dropped, and may draw its live glass inside another surface's recording. -
Fallback: no accent glow when there is no blur or optics, and the fill floor drops from 72% to 58%. The result is a neutral translucent pane with a rim and a top highlight, for the floating bar and for every surface.
-
The settings page text and
ARCHITECTURE.mdare updated.
Not in this PR
- The home header and search now have live glass, but no messages pass behind them yet. Porting WaThemer's home layout (list extension, lifts, search overlay) is next.
- Making the look closer to iOS is a tuning decision, still pending with the user.
Validation
:app:testWhatsappDebugUnitTest: 336 tests, 0 failures, including 5 new ordering tests and 1 new fallback test.:app:assembleWhatsappDebug: succeeds.git diff --check: clean.- Not tested on a device. The GPU cost with many live bubbles has not been measured.
Device checks
- In a chat with bubbles, quotes and the composer enabled, scroll fast. Check smoothness, and that no bubble flickers between live and static.
- Check contact info cards, menus and dialogs, and the FAB on the home screen.
- Turn on power saving. The floating bar and all surfaces should look neutral and translucent, not green.
- Take a screenshot. There should be no green flash.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VJEpLuiM1hMfRR5SS8KCBK
Generated by Claude Code
#72 — docs: record Liquid Glass optical report review and next steps
Merged by contribution from @igorcv88.
This PR changes only handoff.md.
It records the review of the user's Liquid Glass optical report against current master (224e88c):
- Findings checked against current code: the warp fold at the rim (LG-01), the effectively full-resolution input (LG-02/07), the scale rounding (LG-06), no adaptation outside
GlassSurface(LG-03), the saturation and dispersion settings (LG-05), the tint amount, shader recreation on tint change (LG-11), and the panes missing from the budget (LG-12). LG-11 is confirmed in code only; its symptom has not been reproduced on a device. - The parts the report could not reflect because it predates #71.
- The agreed next steps, in order: geometry, then filtering and legibility, then colour, then timing and budget.
- The device evidence the user can provide on request.
No code changes. I did not run tests or a build for this PR.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VJEpLuiM1hMfRR5SS8KCBK
Generated by Claude Code
#73 — feat(glass): optical corrections LG-01..LG-13 behind experimental switches
Merged by contribution from @igorcv88.
This PR adds the corrections from the Liquid Glass optical report as a second renderer, behind experimental switches, so they can be compared on a device without rebuilding. It has been revised after the user's independent review; that round is listed below.
Default is off. Off is the original shader, capture scale and scheduling logic. That logic now lives in shared classes, so it is equivalent but not literally the same code. No existing preference changes meaning.
To use it, open the Liquid Glass page → Optical corrections (experimental):
- Master switch ("Corrected renderer"). Stable refraction is always part of it: a bounded, fold-free warp, 1:1 capture and exact placement. It is not a switch.
- Four groups, on by default once the master switch is on: Optical blur, Adaptive contrast, Colour and highlights, Capture timing and budget.
- Presets: All improvements and Original.
- Clear profile: an experimental, more transparent material for the app surfaces.
- Developer diagnostics: raw input, displacement field, Jacobian heat map, synthetic grid, protection/β, and the original warp. The original warp is a diagnostic view only, labelled as folding.
Changes apply when WhatsApp resumes. Every provider, the floating bar included, rebuilds its effect when the switches' revision changes.
| Part | Report items | Implementation |
|---|---|---|
| Stable refraction (always on) | LG-01, 06, 08 | The warp follows a geometry shape whose corner radius is at least the bevel. Amplitude is 0.28 of the bevel, capped at 0.33 after every multiplier and per colour channel. Recording is 1:1, and views are placed by inverse(G_target)·G_view. |
| 1. Optical blur | LG-02, 07 | Lens over a platform Gaussian, plus the lens on the sharp input. Each pass carries its own share including coverage, and the two are added (PLUS), so coverage is applied exactly once. The recording gets a 3σ margin; siblings are culled against that margin and drawn in Z order. |
| 2. Adaptive contrast | LG-03 | Protection is applied last, after lighting, in linear light, in both passes. Because luminance is linear in the composite, the composite meets 4.5:1 wherever both passes do, up to a 0.85 cap. The bar's adaptation colour is smoothed with τ = 120 ms. |
| 3. Colour and highlights | LG-05, 09, 13 | Linear sRGB with layout(color) uniforms. Saturation 1.10 instead of 1.55, red–blue separation ≤ 1.5 px, quieter rim. |
| 4. Capture timing and budget | LG-10, 11, 12 | Captures only frames the window draws anyway, plus one trailing frame at rest and no heartbeat. Effects rebuild on full material equality. Selected-tab and press state survive tint changes. One budget per window in pixel-passes, (w+2p)(h+2p)×passes, which admits panes and drawables alike. |
The acyclic capture model is unchanged and shared by both renderers. If the device refuses to compile the corrected program, or it fails three times, surfaces fall back to the legacy lens. A native RenderThread crash cannot be caught this way.
Review round (user's independent review of 65e6a09)
All findings were addressed except #10 and #12, which are left for device checks; each fix has a regression test (OpticsReviewRegressionTest and others):
- Composition: fractional coverage was too opaque (0.7125 instead of 0.5). The passes are now added (
PLUS). - Folding warp: it could be combined with the other corrections. It is now a diagnostic view only.
- and 9. Contrast protection: it ran on the soft pass only and partly in encoded RGB. It now runs on both passes, in linear light, after lighting.
- Blur margin: siblings in the margin were dropped, and siblings were drawn by index instead of Z. Fixed.
- Budget: it counted visible area only, and panes were never refused. It now uses effective cost, and panes go through admission.
- Bar after a toggle: it could keep the old effect. Fixed with the optics revision.
- Cache key: it ignored some mater
Description truncated; open the PR for the remaining detail.
#74 — fix(glass): sticky live budget and one pane per surface
Merged by contribution from @igorcv88.
Follow-up to #73, based on the user's device report (S25 Ultra, corrected renderer with all improvements on).
Flicker between live glass and fallback
Symptom: the glass changed on every page switch, tap and scroll, alternating between live glass and the fallback and never settling.
Cause (from reading the code, not yet confirmed by a log):
- #73's budget charged
(w+2p)(h+2p)×3per surface against 3 window areas. That leaves far less room than the old visible-area budget: one image bubble costs about 1.7M of about 7.6M. - Every capture re-admitted surfaces from top to bottom, so any layout change moved the cut-off. Surfaces near it flipped between the live glass and the 58% fallback.
Fix:
- Admission is now sticky (
LiveBudget.admitDrawable). A live surface keeps its slot while it is visible; only new surfaces can be refused. - If the total goes past 1.25× capacity, for example when a pane grows, only the newest admission is evicted.
- Slots are released when a surface leaves the screen or its binding is restored. Weak keys back this up.
- Capacity is raised to 4 window areas.
Double rim on the home search field
my_search_bar contains search_bar, and both map to the SEARCH surface, so a glass pill was drawn inside another glass pill. Now only one pane is bound per surface, and the innermost view wins.
Validation
./gradlew :app:testWhatsappDebugUnitTest: 390 tests, 0 failures, including the newLiveBudgetStickyTest../gradlew :app:assembleWhatsappDebug: succeeded.tools/agsl_check.py: passes.- Not tested on a device yet.
Not in this PR
- Home list scrolling behind the header and search. WaThemer does not do this either: it keeps the list in a glass card below the header. Building it needs the home view hierarchy and a design decision; see
handoff.md. - Element Inspector recording nothing. It most likely arms only when WhatsApp starts after it is enabled. Workaround: enable it, then use Restart WhatsApp.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VTXTcEnnUYJpUvPZNWjPA2
Generated by Claude Code
#75 — fix(glass): retain stopped sessions and recover window-local surfaces
Merged by contribution from @igorcv88.
Normal Activity navigation closed Liquid Glass sessions at onStop, restored native backgrounds and rebuilt bindings on return. Missing recordings could also drive an idle recapture loop, while three transient errors could leave a surface in fallback indefinitely. This change retains stopped bindings, discards captured pixels across visibility/source epochs, and recovers in the same window without requiring navigation or restart.
Recording absence now has explicit reasons. Only an eligible surface that unexpectedly lost valid pixels requests immediate recovery; uninitialized, hidden, intentionally released and budget-refused surfaces cannot repeatedly invalidate another admitted surface. Transient recovery uses 16/64 ms retries followed by 1/2/4/5-second backoff, capped at 5 seconds. Due retries bypass throttling without forcing damage-driven redraws, and one surface's earlier callback preserves the other surfaces' later deadlines. Permanent capability/linkage failure remains disabled.
Destruction dispatches the old Activity identity without overwriting a newer same-class name mapping. Conversation panes require safe live message content: wallpaper-only capture cannot report complete recovery, the header never falls back to an ancestral coordinator, and a late safe list is re-resolved on permitted retries. Source and underlay acyclicity guards remain active.
Pane materials resolve from their own window. The header has one optical capsule over plain wallpaper continuity; the composer leaves a measured gap before the native action disc in LTR/RTL. Battery Saver no longer disables intra-window optics. Temporary neutral fallback uses provisional 18–32% tint, while permanent renderer loss retains the existing 58% opacity floor. Shape, rim and content colour are preserved. V2/legacy shader programs and optical profile defaults are unchanged.
Resumed window epochs separately record each surface's first presentation, first complete capture, first live presentation and fallback-frame count, excluding nested capture draws. Ordinary successful captures do not produce per-frame logs.
Review corrections
- Addresses the idle recapture-loop finding and same-class Activity destruction finding.
- Adds regressions for absent recording reasons, mixed admitted/refused surfaces, autonomous recovery after three or more failures, staggered retries, recursive/wallpaper-only sources, late safe source availability, fallback materials, resume timing and destruction callback identity.
Validation
- Full
:app:testWhatsappDebugUnitTest :app:assembleWhatsappDebug --no-daemonpassed with JDK 21.0.8, Gradle 8.14.5, Android SDK 36 and real project dependencies. - 424 tests passed in 57 suites, zero failures/errors/skips. The focused policy/adapter harness also passed 127 cases; full Gradle results supersede the previous partial-build limit.
- Debug APK produced:
com.waenhancer.community, version1.8.0-alpha1/ code18001, arm64-v8a and armeabi-v7a. APK v2 signature, ZIP integrity and 16 KB ZIP alignment verified. - APK SHA-256:
e94975b7b6482a9ee644bcc06d562c02967ca1c09e935e4155c34f50d782eb61. This APK uses an Android debug certificate, so it cannot replace a release signed with a different key. - Published tree
d1ca6c7dd11aba84453ac385bc28211a53a37209matches the tested local tree.git diff --checkpassed. - No device installation/rendering, GPU or energy measurement is claimed. No workflow was dispatched and no merge performed.
Device acceptance steps are in GLASS_RECOVERY_ACCEPTANCE.md. Validate navigation, keyboard/voice recording, Battery Saver, dropped recordings, late safe message sources and mixed budgets on the S25 Ultra. Calibrate temporary fallback legibility and measure static/scroll GPU time and actual presentation t
Description truncated; open the PR for the remaining detail.
#76 — fix(glass): keep the header band from growing the holder to full height
Merged by contribution from @igorcv88.
Problem
After #75, turning on Liquid Glass Headers left the conversation empty. Only the header capsule drew, over a dark screen with no messages and no composer. The user reported the same thing on the home screen. With Headers off, the screen renders normally.
Root cause (from reading the code; no device log)
#75 changed the header band from a GlassPane (a FrameLayout with no children) to WallpaperUnderlay extends View. The band is added as MATCH_PARENT to the wrap-content search_fragment_and_toolbar_holder. The holder measures its children under AT_MOST and counts MATCH_PARENT children toward its own size:
View.onMeasuretakes the whole AT_MOST offer. AFrameLayoutwith no children takes 0.- So the holder grew to fill the rest of the window. With
translationZ = 1it covered the coordinator. syncListPaddingthen set the list's top padding to that height, which pushed every message off-screen.
Fix
WallpaperUnderlay.onMeasure uses its size only under EXACTLY and returns 0 otherwise, which is how the old band behaved. On its second pass, the holder measures its MATCH_PARENT children exactly to its final size, so the band still fills the header.
Validation
./gradlew :app:testWhatsappDebugUnitTest :app:assembleWhatsappDebug(JDK 21, Android SDK 36): 425 tests, 0 failures. Debug APK built.- New test:
WallpaperUnderlayMeasureTest. - Not yet tested on a device.
🤖 Generated with Claude Code
https://claude.ai/code/session_01JN7ZPJjeqP3W2AQTAUUuvr
Generated by Claude Code
#77 — feat(glass): log home surface bindings and the home view hierarchy
Merged by contribution from @igorcv88.
Context
After #76, the conversation screen and the floating bar are correct on the device. Two problems remain on the home screen:
- The header capsule has nothing behind it.
- The search glass seems to apply only on the Groups tab.
The user chose to have rows scroll behind the home header, the same approach as the conversation screen.
This PR doesn't change the home layout yet. In #75, a layout change made without the real hierarchy blanked the conversation screen. The home ids I know (header, pager_holder, the list seated inside or beside the search bar) come from WaThemer's WhatsApp build, not from 2.26.33.76. So this PR first collects the hierarchy from the device.
Changes (diagnostics only; no layout or rendering change)
AppLiquidGlass.bindlogsBOUND reason=surface-bind role=… name=<resource> size=WxH path=<named ancestors>.- It also logs
UNBOUND reason=inner-surface-winswhen the innermost-wins rule drops an outer container. - New
HomeTreeProbe(WaEnhancerX/HomeTree, info level, read-only):- On the home window with TOOLBARS on, it dumps class, id, bounds, padding, layout params/margins, background, Z and clipToPadding.
- Each dump is capped at 400 lines, with at most 4 dumps per window. A new dump runs when a tab adds its first list.
- Resource ids are cached.
Validation
:app:testWhatsappDebugUnitTest: 425 tests, 0 failures.:app:assembleWhatsappDebugsucceeds.git diff --checkis clean.- Not run on a device yet.
Next
Capture WaEnhancerX/HomeTree and WaEnhancerX/GlassState while switching Chats → Groups → Communities → Calls. Then implement the home float and the search fix from that evidence (see handoff.md).
🤖 Generated with Claude Code
https://claude.ai/code/session_01JN7ZPJjeqP3W2AQTAUUuvr
Generated by Claude Code