Skip to content

v1.2.0-rc.4 - Reliable wake routing and Wi-Fi retries

Pre-release
Pre-release

Choose a tag to compare

@lucabnt lucabnt released this 16 Nov 09:46
f3d573e

A reliability and security update based on the 2026-11-15 technical review.

Changes since RC3

  • One wake sender. The Wake button, widget, Quick Settings tile and
    automations now share the same Android sender. When Wi-Fi is connected, the
    packet is sent on Wi-Fi even if mobile data or a VPN is the default network.
  • Wi-Fi rules retry when their window opens. A rule triggered outside its
    allowed time window, or during its cooldown, is checked again when the window
    opens, as long as the phone is still on the same connection. Without
    exact-alarm access Android can delay this check.
  • Faster ping scans. Ping uses ICMP sockets instead of starting a process per
    address, so a full /22 fits within the 30-second limit. Kernels that deny
    ICMP sockets fall back to the previous method.
  • External integrations. An intent with a wrong token now always receives
    rejected, even when the rule is paused. Apps using the correct token still
    see disabled.
  • Devices saved in the same millisecond receive distinct identifiers.
  • The app no longer rewrites the encrypted archive at every start.
  • New privacy notice.
  • Build and CI: patched fast-xml-parser (GHSA-474x-hrwr-fgx4), CI compiles the
    instrumented tests, and GitHub Actions are pinned to commit SHAs.

The archive format, backup format and MacroDroid contract are unchanged.
This remains an Android prerelease. Real-device and background-delivery
validation limits described in RC2 still apply.

Wake routing verification

Multi-network behaviour has been tested on the emulator only and still needs
verification on physical hardware.

  • Connect a phone to Wi-Fi without internet, keep mobile data enabled, and
    capture the packet on the target LAN.
  • Repeat with a VPN active. Check both the configured destination and the
    default broadcast.
  • Send from the device list, widget, tile and an automation. Verify the
    destination, UDP port and packet contents on the LAN for each.

The expected maintainer certificate SHA-256 is
b28b8a226b2e27771f5ba5a276ed16b5235c1b3d764a802bc68610e69e284fe9.

The RC3 APK preparation guide describes the
same commands and output folders; replace rc.3 with rc.4 and the version codes
above.