Debug Build v0.6.6

Debug Build v0.6.6

This prerelease ships the current bugfix line while stable signing is still blocked by missing GitHub Actions secrets.

Included fixes:

• adaptive launcher icon resources for OEM/themed launchers
• stricter local GPU runtime verification and CPU-safe re-arm logic
• richer debug report state for monitor / notification listener triage
• stale LocalBackendHealthTest repaired so backend-health unit tests pass again

Validation done locally:

• ./gradlew testDebugUnitTest passed
• debug APK installed over an existing PokeClaw build on a physical Pixel 8 Pro
• app launch smoke test passed on device

Known limitation:

• GitHub's stable release workflow currently fails because ANDROID_KEYSTORE_B64, ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS, and ANDROID_KEY_PASSWORD are not configured in repo secrets.

Debug Build v0.6.5

Full Changelog: v0.6.4...v0.6.5-20260414

v0.6.4

Local/OEM hardening release.

Highlights:

• re-arm verified GPU devices after stale CPU-safe quarantine
• start Fold 4 local runtime more conservatively
• richer debug reports for backend/monitor/listener state
• extra JNI native keep rule for release builds

If your device was previously stuck on CPU after an older local GPU init failure, update to v0.6.4 and try local mode again.

Debug Build v0.6.4

Full Changelog: v0.6.3...v0.6.4-20260413

v0.6.3

Fixes in v0.6.3

• Hardens task/session cleanup after local tasks so chat context is preserved instead of getting reset.
• Hides the floating overlay when idle instead of letting it linger after work is done.
• Rejects overlapping tasks cleanly with a clear "stop the current task first" message.
• Tightens accessibility health reporting so monitor mode surfaces disconnects quickly and recovers truthfully.

What to verify after updating

• Local chat still remembers earlier messages after running a task.
• If Accessibility drops, monitoring shows as paused instead of pretending everything is still fine.
• If you start a second task while one is already running, PokeClaw refuses it instead of getting stuck.

Debug Build v0.6.3

Full Changelog: v0.6.2...v0.6.3-20260413

Full Changelog: v0.6.2...v0.6.3-20260413

v0.6.2

What's fixed in v0.6.2

• Local model startup is more defensive on devices with unstable GPU/OpenCL bring-up. PokeClaw can now recover into CPU-safe mode instead of retrying the same bad backend path.
• Release builds now keep the LiteRT-LM JNI wrapper classes stable, which should address the nativeCreateConversation / mid == null crash family reported on some devices.
• Auto-reply can now wake and unlock the phone before replying when the device is locked.
• Auto-reply now fails fast when Accessibility drops instead of continuing into a broken reply path.

Notes

• This is a hardening patch on top of 0.6.1.
• If you were seeing local-model startup crashes or monitor/reply instability, please update and try again.

Debug Build v0.6.2

Full Changelog: v0.6.1...v0.6.2-20260413

v0.6.1

PokeClaw v0.6.1

This is a hardening release on top of v0.6.0.

Fixed and improved:

• Local model startup is more defensive on devices where GPU/OpenCL bring-up is unstable. The app can now promote the device into CPU-safe mode after a failed GPU init path instead of repeatedly retrying the risky backend.
• Auto-reply no longer sends the canned fallback message "Got it, thanks!" when context-aware reply generation fails. It now fails closed instead of sending misleading junk.
• WhatsApp contact lookup is more robust and no longer gives up after a single scroll.
• Text input is more resilient across editable fields and input focus edge cases.
• Accessibility disconnects are surfaced faster and more truthfully while monitoring is active.
• Added in-app debug report generation to make future device-specific bug reports easier to capture.

Issue mapping:

• #27 / #29: local model crash hardening
• #28: accessibility disconnect truthfulness hardening
• #31: auto-reply fallback regression fixed
• #32: WhatsApp contact lookup improved
• #33: text input path hardened

Notes:

• The local crash hardening has strong code-level and on-device validation, but OEM crash-family fixes still benefit from real-world validation on affected Xiaomi/Samsung/MediaTek devices.

Debug Build v0.6.1

Full Changelog: v0.6.0...v0.6.1-20260413