v1.3.5 — Android 17 crash fix, 5G SA toggle

What's new in v1.3.5

🐛 Fix crash on Android 17 (QPR)

Applying carrier config could crash the app on Android 17 (Pixel 10 series, CP3A.*, SDK 37). Android 17 changed the hidden IActivityManager.stopDelegateShellPermissionIdentity signature from () to (int uid). The app was compiled against the old signature, so the call raised NoSuchMethodError — an Error, not an Exception, so it bypassed the existing catch blocks and killed the process. Because it fired after the config write had already succeeded, the crash looked random while the settings still applied.

The call is now dispatched reflectively so both signatures work, releasing the shell delegation is best-effort, and the broker catches Throwable (it runs in the app's own process, so an escaping Error would otherwise take the whole app down).

📶 Enable 5G SA (standalone)

New per-SIM toggle for KEY_CARRIER_NR_AVAILABILITIES_INT_ARRAY. Pixel carrier configs frequently ship NSA-only ([1]), which keeps the modem off standalone 5G no matter what the network menu offers. Networks that run their mid-band 5G as SA (e.g. n79 at 4.6–5.0 GHz) need SA in the list to attach. The toggle writes [NSA, SA] when on and [NSA] when off, is persisted per SIM slot, re-applied on reboot by the auto-apply service, and included in export/import.

🧹 Cleanup

Broker control keys (moder_subId, moder_clear) are no longer written into the carrier config override.

---

Requirements: Shizuku ≥ 13 with Wireless Debugging enabled. No root required.
Signed with the same key as v1.3.4, so it installs as an update.
Verified on Pixel 10 Pro XL (mustang, SKU G45RY), Android 17 CP3A.260905.009.