Root My Galaxy 0.3.53

SHA-256: 18cda173799bac8792e3fd63a7dacf697ec1ad39f745b8c441813cfe7be5bf1b

Changes since v0.3.52.

What's changed

• #43 Fix history ZIP export and large-log save stalls
• #44 Restore minimal Auto Root without CZG3 instrumentation

Full changelog

Detailed pull-request notes for all changes included in this release.

#43 — Fix history ZIP export and large-log save stalls

Problem

Batch history export still used OpenDocumentTree() and wrote individual .log files into a folder. Large reports could stall the export sequence. Single-log export also generated and wrote the diagnostic report synchronously from the ActivityResult callback, which could block the UI for large logs.

Fix

• Batch export now uses ACTION_CREATE_DOCUMENT with application/zip, producing one RootMyGalaxy-logs-*.zip at any user-selected location.
• Selected reports remain separate .log entries inside the ZIP, with duplicate-name disambiguation.
• ZIP export runs entirely on Dispatchers.IO, uses a buffered stream and BEST_SPEED compression, and removes the partial ZIP on failure.
• Single-log export now generates/writes the report on Dispatchers.IO with a 64 KiB buffer, so a ~1 MB+ diagnostic cannot block the main UI thread.

Scope

No payload/exploit logic, timings, Auto Root, Shizuku execution, diagnostics, safety policy, or workflows changed.

#44 — Restore minimal Auto Root without CZG3 instrumentation

Goal

Return app runtime to the last pre-instrumentation Auto Root architecture while keeping the repository's current release/tooling infrastructure and only a small set of intentional runtime features:

• original Auto Root + once-per-kernel-boot guard;
• exact KernelSU v3.3.0 / 32601 metadata;
• adjustable CZG3 minimum boot uptime (Diagnostic Launch Time), default 120 s;
• automatic KernelSU soft reboot after successful root, controlled by a persistent Settings toggle;
• KernelSU Manager v3.3.0 / 32601 download link.

The runtime restoration base is 5b458af76ad876931fb29f6d4c4e25dcdea01a90, exactly before app-side logging/structured diagnostics began.

Payload PR #28 should be merged first so the embedded/online CZG3 manifest resolves the restored native payload.

Removed from runtime

• External Observer native process/service;
• process-tree/system telemetry;
• Czg3ExternalTelemetry;
• ExploitObserver*;
• structured ExploitDiagnostics;
• race/preparation telemetry parsers;
• pstore diagnostic collection;
• CZG3 diagnostic gate service and associated diagnostic history/report machinery.

No observer process is spawned around the exploit.

The modern .github release/scripts/Dependabot infrastructure and Gradle/JDK configuration are retained; this is a runtime rollback rather than a tooling rollback.

Diagnostic Launch Time retained without diagnostics

The setting remains in Settings, outside Advanced mode. Values:

0 / 30 / 60 / 90 / 120 / 180 / 300 / 600 s

120 s remains the default.

Implementation is only an Android-side wait on SystemClock.elapsedRealtime(). It performs no native instrumentation, /proc sampling, marker collection, observer startup, or payload telemetry. It applies to exact CZG3 manual and Auto Root launch.

Soft reboot simplified

Soft reboot after root is now a persistent Settings toggle configured before rooting, not a post-success control.

After verified root, the route is deliberately minimal:

bootstrap root helper -> /data/adb/ksud soft-reboot

with fallback to /data/local/tmp/ksud-s25u-kdp if the installed ksud is absent.

Removed from this path:

• KernelSU Manager libksud.so selection;
• ksud debug su -g nesting;
• Shizuku fallback;
• keeper scan/gate;
• soft-reboot trace/RMG diagnostics;
• boot-property acknowledgement polling.

Only command timeout/exit output remains so a launch failure can be shown concisely.

KernelSU

The embedded Auto Root manifest keeps the validated v3.3.0 / 32601 ksud:

• size 5096104
• SHA-256 5a009f1fc58b25a6e197d8ec951a86ec11a9b5ec9d56bdb5f7a3410a22b9b48a

The Manager link points to the official KernelSU_v3.3.0_32601-release.apk asset.

Validation status

Static review confirms the restored app tree contains no External Observer runtime or RMG_* instrumentation. Key API compatibility was checked against the restored DeviceSnapshot and AutoRootRunner definitions.

A full Android build has not been run from this environment: the container cannot resolve GitHub and the available GitHub connector does not expose workflow dispatch. The retained release workflow itself runs unit tests, lint, and assembleRelease before publishing.

Other changes

Commits merged directly without an associated pull request:

• 75b7ee4 chore: add gradle-daemon-jvm.properties with JDK 21 toolchain URLs
• fd66ca5 Fix release lint translations and restore README presentation