Repository navigation
Releases: 4uva4ek/KernelSU-GXR
Release list
KernelSU GXR gxr-v1.0.9
KernelSU GXR: tested configuration
GXR 1.0.9: WebUI module installation
Manager samsung-gxr-v1.0.9, code 32674. The reviewed installer accepts
checksummed webroot/ assets, fixing Unexpected payload directory for
Steam Link Pose Time 0.1.7. Checksums, safe paths, disabled replacement and
old-patch restoration remain enforced. See release notes and validation
limits. No module activation or restart is part of this
release. The signed APK and increasing update manifest are built by release CI.
Validation: Android arm64 check, clippy with warnings denied and formatting
passed; 13 host regressions and the actual eight-module CI ZIP set passed.
Live module replacement and WebUI interaction were not exercised on the headset.
GXR 1.0.8: installer log and Manager self-update
Manager version samsung-gxr-v1.0.8, code 32673 (1.0.7 shipped the 1.0.6
code 32672 because KSU_VERSION_CODE is pinned in manager/gradle.properties;
bump it for every release). See release changes and validation
limits. The reviewed GXR package route now prints an
installer log in the standard KernelSU style (banner, package identity, verified
files, stop/restore of the previous version, DISABLED install path, backup, an
"About this module" block from the optional bounded install-info.txt or the
module description, enable/Action instructions). The home screen checks the
latest 4uva4ek/KernelSU-GXR release and, on the user's tap, installs the APK
only after the release SHA-256, the package name, the installed Manager's signing
certificates and an increasing version code all match. Releases ship a versioned
APK, manager-update.json and a SHA256SUMS.txt covering both.
Validation: Manager assembleRelease and ksud clippy -D warnings/arm64 build
pass locally; a unit test covers the install-notes bounds. The CI artifact of
2c868d2 (retained certificate, SHA-256 verified) was installed on the headset
and read back; the kernel boot ID and every module preference were unchanged,
and the daemon reported gxr-v1.0.6-1-g2c868d2a after the first launch. The
new installer log was exercised with an already-installed package: banner,
package identity, verified-file count and route line printed, then the
version-must-increase refusal before any change. A live self-update to a newer
release and the full log of a successful installation are pending.
GXR 1.0.6: sources, disabled updates and themes
Manager version samsung-gxr-v1.0.6, code 32672. See
release changes and validation limits. Module discovery
and legacy feed lookup are driven by configured GitHub catalogues, without a
compiled list of supported module IDs. Host regressions cover discovery,
installation and replacement of twelve previously unknown IDs. Material controls
in Miuix now inherit the selected light/dark/accent palette.
Android checks/lints, native host suites and Manager tests passed. Live module
replacement through this updater has not been validated on the headset. The
preceding preview was installed with unchanged module preferences/kernel boot;
that is installation evidence, not a runtime activation test. Version-specific
APK hashes and installation evidence are included with the release assets.
Local candidate: GXR 1.0.5
Manager samsung-gxr-v1.0.5, code 32670, was installed and tested in one
user-authorized soft restart. APK SHA-256:
ba5757f8e6abe10d2163d47e93cca1ca040f45b5591bf862340f99896a1483c2.
Embedded/deployed daemon:
55222b770cbeb7dcaaed8d359e9f6efda02628dc111cba96306400466372716c.
This candidate has not been published.
The logger Steam Link process, which had OpenXR loaded, was force-stopped at
02:06:28.950 on 2026-10-12. The verified empty runtime-client list was logged
at 02:06:29.101, before Android stop at 02:06:29.269. Android completed its
restart in 27.508 seconds. Root remained available and kernel boot ID stayed
eef1a7a9-d6ce-46a6-bc27-ed28214d3efa. Haptics, Whitening and Timestamp were
verified active afterward. The ordinary Steam Link was also launched before
the restart, but remained in its non-OpenXR menu and was not an app-close target.
Velocity was already inactive before this test: its checkbox was ON, but its
worker had failed after a prior application task removal within 30 seconds.
Its existing same-boot supervisor quarantine and auto.pending were preserved.
The new test therefore does not establish active Velocity's health through
the planned app exit. It does establish app shutdown order and Android recovery.
Android check/clippy with warnings denied/fmt, nine new OpenXR shutdown tests,
the existing service/restart/wake-lock suites, and ten module lifecycle tests
passed. ARM64 Manager build, v2 signature, certificate continuity, 16 KiB ZIP
alignment and exact embedded/deployed daemon verification passed. Kernel payload
is unchanged. No cold boot, tracking-motion validation or public release was done.
Current release: GXR 1.0.4
Manager samsung-gxr-v1.0.4, code 32669. The exact signed release APK
was installed and tested; its SHA-256 is
5c0d71f7034eeb94c8d54990cdd1325e80906f96b7cb7aea228d9575ba74317a.
Embedded and deployed daemon SHA-256:
dfe94b55316418a312c1e676033cdabbc76cce433e660f747cbfd7bf7051db19.
During an intentional same-version reinstall in a soft restart, the running
executable became /data/adb/ksud (deleted). All four module supervisors
successfully launched through /proc/self/exe. Haptics MAIN, module-owned
Whitening and Timestamp were verified live. Velocity's worker was alive and
waiting for an OpenXR app. Framebuffer10 was disabled and removed; it was
not activated in this test. The kernel boot ID was unchanged, with no restart
error. The kernel/root payload remains unchanged.
Android check, clippy with warnings denied, formatting, deleted-executable
regression, lifecycle guards and six stage-error propagation tests passed.
Full power-cycle and active-app Velocity validation were not performed.
See 1.0.4 details.
Historical release: GXR 1.0.3
See 1.0.3 changes and test scope and the
restart API. The Manager version is
samsung-gxr-v1.0.3, code 32668; the original GXR kernel payload is unchanged.
The local test APK SHA-256 was
719c9bebff288f4ce09db3a7de8936ee9edfc3ef9befa95e81188526e15f5475.
Its embedded/deployed ksud SHA-256 was
3b54400ff1b5928e8871c89ffaaa5545691fb52810ccae26e0760704fe98dc1f.
Two consecutive coordinated soft restarts passed with active Framebuffer10
0.3.1 and Whitening 0.1.3; Haptics was also verified active, and Velocity was
waiting for an OpenXR target. An earlier cycle passed on 1.0.2. This is runtime
lifecycle evidence, not a visual/physical quality or cold-boot validation.
The public APK uses the same daemon but removes the test-only installation flag.
Its exact signed bytes have not been device-tested. Release hashes and build
provenance are supplied separately. The sections below retain historical tests
and must not be interpreted as tests of every later binary.
Reference device test
| Item | Tested value |
|---|---|
| Device | Samsung Galaxy XR SM-I610 |
| Codename | xrvst2 |
| Device firmware / build | I610UEU2AZF3 |
| Running kernel | 5.10.240-android12-9-perf-33775878-abI610UEU2AZF3 |
| Module loader | DFRoot 4.1 |
| KernelSU source base | diabl0w/KernelSU, samsung-v1.0, commit 10aa21cbb6a2b05d7792f60cde76565b99d89a63 |
| Tested local APK | KernelSU-GXR_32664_no-DEFEX.apk |
| APK SHA256 | 106c1646a3a03652ba2946b6e927299c49a8abb705ddb4ea58cad6166e5a3576 |
| Profile | KDP=y, DEFEX=n, RKP_NO_PATCH_TEXT=y; SCS=y, CFI=y |
| Manager signing | APK v2 only; matching certificate compiled into the module |
Confirmed: the GXR module loaded, and the Manager launched two shell
processes with UID 0. This resolved the original module's missing-DEFEX error
and the initial incorrectly signed Manager's authentication failure.
Not yet verified: root grants to other applications, persistence after
a full reboot, long-term stability, other firmware builds or other devices.
The Apply on boot observation was described by the tester as resembling a
soft reboot; it is not evidence of reliable boot persistence.
The older AZD8 dump was used for analysis only. It is not the firmware on
which the successful reference test was performed.
Scope of automated releases
CI builds this GXR profile and checks the module, APK signature scheme,
alignment, embedded ksud and the source-built Manager. A successful CI build
does not mean that its exact APK has been tested on a headset. The table
above describes the specific local APK tested on the reference device.
Each generated package includes BUILD-INFO.txt with its source commit and
workflow run, and SHA256SUMS.txt for the compiled files.
Use DFRoot to load the module.
Do not flash the APK as a boot image.
GXR 1.0.1
The Manager version is samsung-gxr-v1.0.1 (Android version code 32666).
Soft-restart requests run off the UI thread and report submission failures.
The daemon serializes restart requests and acquires a kernel-expiring,
180-second suspend blocker before stopping Android. Standard module startup
and the Action button are retained; no live-checkbox extension is included.
The preceding gxr-1.0.1-test1 build passed native checks, five guard tests
and a clean Manager release build. The owner tested it on the reference
headset and reported the Manager working well. Version 1.0.1 retains that
daemon and kernel payload; it updates Manager branding and release metadata.
This report does not establish module health or authorize a soft reboot.
KernelSU GXR gxr-v1.0.8
KernelSU GXR: tested configuration
GXR 1.0.8: installer log and Manager self-update
Manager version samsung-gxr-v1.0.8, code 32673 (1.0.7 shipped the 1.0.6
code 32672 because KSU_VERSION_CODE is pinned in manager/gradle.properties;
bump it for every release). See release changes and validation
limits. The reviewed GXR package route now prints an
installer log in the standard KernelSU style (banner, package identity, verified
files, stop/restore of the previous version, DISABLED install path, backup, an
"About this module" block from the optional bounded install-info.txt or the
module description, enable/Action instructions). The home screen checks the
latest 4uva4ek/KernelSU-GXR release and, on the user's tap, installs the APK
only after the release SHA-256, the package name, the installed Manager's signing
certificates and an increasing version code all match. Releases ship a versioned
APK, manager-update.json and a SHA256SUMS.txt covering both.
Validation: Manager assembleRelease and ksud clippy -D warnings/arm64 build
pass locally; a unit test covers the install-notes bounds. The CI artifact of
2c868d2 (retained certificate, SHA-256 verified) was installed on the headset
and read back; the kernel boot ID and every module preference were unchanged,
and the daemon reported gxr-v1.0.6-1-g2c868d2a after the first launch. The
new installer log was exercised with an already-installed package: banner,
package identity, verified-file count and route line printed, then the
version-must-increase refusal before any change. A live self-update to a newer
release and the full log of a successful installation are pending.
GXR 1.0.6: sources, disabled updates and themes
Manager version samsung-gxr-v1.0.6, code 32672. See
release changes and validation limits. Module discovery
and legacy feed lookup are driven by configured GitHub catalogues, without a
compiled list of supported module IDs. Host regressions cover discovery,
installation and replacement of twelve previously unknown IDs. Material controls
in Miuix now inherit the selected light/dark/accent palette.
Android checks/lints, native host suites and Manager tests passed. Live module
replacement through this updater has not been validated on the headset. The
preceding preview was installed with unchanged module preferences/kernel boot;
that is installation evidence, not a runtime activation test. Version-specific
APK hashes and installation evidence are included with the release assets.
Local candidate: GXR 1.0.5
Manager samsung-gxr-v1.0.5, code 32670, was installed and tested in one
user-authorized soft restart. APK SHA-256:
ba5757f8e6abe10d2163d47e93cca1ca040f45b5591bf862340f99896a1483c2.
Embedded/deployed daemon:
55222b770cbeb7dcaaed8d359e9f6efda02628dc111cba96306400466372716c.
This candidate has not been published.
The logger Steam Link process, which had OpenXR loaded, was force-stopped at
02:06:28.950 on 2026-10-12. The verified empty runtime-client list was logged
at 02:06:29.101, before Android stop at 02:06:29.269. Android completed its
restart in 27.508 seconds. Root remained available and kernel boot ID stayed
eef1a7a9-d6ce-46a6-bc27-ed28214d3efa. Haptics, Whitening and Timestamp were
verified active afterward. The ordinary Steam Link was also launched before
the restart, but remained in its non-OpenXR menu and was not an app-close target.
Velocity was already inactive before this test: its checkbox was ON, but its
worker had failed after a prior application task removal within 30 seconds.
Its existing same-boot supervisor quarantine and auto.pending were preserved.
The new test therefore does not establish active Velocity's health through
the planned app exit. It does establish app shutdown order and Android recovery.
Android check/clippy with warnings denied/fmt, nine new OpenXR shutdown tests,
the existing service/restart/wake-lock suites, and ten module lifecycle tests
passed. ARM64 Manager build, v2 signature, certificate continuity, 16 KiB ZIP
alignment and exact embedded/deployed daemon verification passed. Kernel payload
is unchanged. No cold boot, tracking-motion validation or public release was done.
Current release: GXR 1.0.4
Manager samsung-gxr-v1.0.4, code 32669. The exact signed release APK
was installed and tested; its SHA-256 is
5c0d71f7034eeb94c8d54990cdd1325e80906f96b7cb7aea228d9575ba74317a.
Embedded and deployed daemon SHA-256:
dfe94b55316418a312c1e676033cdabbc76cce433e660f747cbfd7bf7051db19.
During an intentional same-version reinstall in a soft restart, the running
executable became /data/adb/ksud (deleted). All four module supervisors
successfully launched through /proc/self/exe. Haptics MAIN, module-owned
Whitening and Timestamp were verified live. Velocity's worker was alive and
waiting for an OpenXR app. Framebuffer10 was disabled and removed; it was
not activated in this test. The kernel boot ID was unchanged, with no restart
error. The kernel/root payload remains unchanged.
Android check, clippy with warnings denied, formatting, deleted-executable
regression, lifecycle guards and six stage-error propagation tests passed.
Full power-cycle and active-app Velocity validation were not performed.
See 1.0.4 details.
Historical release: GXR 1.0.3
See 1.0.3 changes and test scope and the
restart API. The Manager version is
samsung-gxr-v1.0.3, code 32668; the original GXR kernel payload is unchanged.
The local test APK SHA-256 was
719c9bebff288f4ce09db3a7de8936ee9edfc3ef9befa95e81188526e15f5475.
Its embedded/deployed ksud SHA-256 was
3b54400ff1b5928e8871c89ffaaa5545691fb52810ccae26e0760704fe98dc1f.
Two consecutive coordinated soft restarts passed with active Framebuffer10
0.3.1 and Whitening 0.1.3; Haptics was also verified active, and Velocity was
waiting for an OpenXR target. An earlier cycle passed on 1.0.2. This is runtime
lifecycle evidence, not a visual/physical quality or cold-boot validation.
The public APK uses the same daemon but removes the test-only installation flag.
Its exact signed bytes have not been device-tested. Release hashes and build
provenance are supplied separately. The sections below retain historical tests
and must not be interpreted as tests of every later binary.
Reference device test
| Item | Tested value |
|---|---|
| Device | Samsung Galaxy XR SM-I610 |
| Codename | xrvst2 |
| Device firmware / build | I610UEU2AZF3 |
| Running kernel | 5.10.240-android12-9-perf-33775878-abI610UEU2AZF3 |
| Module loader | DFRoot 4.1 |
| KernelSU source base | diabl0w/KernelSU, samsung-v1.0, commit 10aa21cbb6a2b05d7792f60cde76565b99d89a63 |
| Tested local APK | KernelSU-GXR_32664_no-DEFEX.apk |
| APK SHA256 | 106c1646a3a03652ba2946b6e927299c49a8abb705ddb4ea58cad6166e5a3576 |
| Profile | KDP=y, DEFEX=n, RKP_NO_PATCH_TEXT=y; SCS=y, CFI=y |
| Manager signing | APK v2 only; matching certificate compiled into the module |
Confirmed: the GXR module loaded, and the Manager launched two shell
processes with UID 0. This resolved the original module's missing-DEFEX error
and the initial incorrectly signed Manager's authentication failure.
Not yet verified: root grants to other applications, persistence after
a full reboot, long-term stability, other firmware builds or other devices.
The Apply on boot observation was described by the tester as resembling a
soft reboot; it is not evidence of reliable boot persistence.
The older AZD8 dump was used for analysis only. It is not the firmware on
which the successful reference test was performed.
Scope of automated releases
CI builds this GXR profile and checks the module, APK signature scheme,
alignment, embedded ksud and the source-built Manager. A successful CI build
does not mean that its exact APK has been tested on a headset. The table
above describes the specific local APK tested on the reference device.
Each generated package includes BUILD-INFO.txt with its source commit and
workflow run, and SHA256SUMS.txt for the compiled files.
Use DFRoot to load the module.
Do not flash the APK as a boot image.
GXR 1.0.1
The Manager version is samsung-gxr-v1.0.1 (Android version code 32666).
Soft-restart requests run off the UI thread and report submission failures.
The daemon serializes restart requests and acquires a kernel-expiring,
180-second suspend blocker before stopping Android. Standard module startup
and the Action button are retained; no live-checkbox extension is included.
The preceding gxr-1.0.1-test1 build passed native checks, five guard tests
and a clean Manager release build. The owner tested it on the reference
headset and reported the Manager working well. Version 1.0.1 retains that
daemon and kernel payload; it updates Manager branding and release metadata.
This report does not establish module health or authorize a soft reboot.
KernelSU GXR gxr-v1.0.7
KernelSU GXR: tested configuration
GXR 1.0.7: installer log and Manager self-update
Manager version samsung-gxr-v1.0.7. See release changes and validation
limits. The reviewed GXR package route now prints an
installer log in the standard KernelSU style (banner, package identity, verified
files, stop/restore of the previous version, DISABLED install path, backup, an
"About this module" block from the optional bounded install-info.txt or the
module description, enable/Action instructions). The home screen checks the
latest 4uva4ek/KernelSU-GXR release and, on the user's tap, installs the APK
only after the release SHA-256, the package name, the installed Manager's signing
certificates and an increasing version code all match. Releases ship a versioned
APK, manager-update.json and a SHA256SUMS.txt covering both.
Validation: Manager assembleRelease and ksud clippy -D warnings/arm64 build
pass locally; a unit test covers the install-notes bounds. The CI artifact of
2c868d2 (retained certificate, SHA-256 verified) was installed on the headset
and read back; the kernel boot ID and every module preference were unchanged,
and the daemon reported gxr-v1.0.6-1-g2c868d2a after the first launch. The
new installer log was exercised with an already-installed package: banner,
package identity, verified-file count and route line printed, then the
version-must-increase refusal before any change. A live self-update to a newer
release and the full log of a successful installation are pending.
GXR 1.0.6: sources, disabled updates and themes
Manager version samsung-gxr-v1.0.6, code 32672. See
release changes and validation limits. Module discovery
and legacy feed lookup are driven by configured GitHub catalogues, without a
compiled list of supported module IDs. Host regressions cover discovery,
installation and replacement of twelve previously unknown IDs. Material controls
in Miuix now inherit the selected light/dark/accent palette.
Android checks/lints, native host suites and Manager tests passed. Live module
replacement through this updater has not been validated on the headset. The
preceding preview was installed with unchanged module preferences/kernel boot;
that is installation evidence, not a runtime activation test. Version-specific
APK hashes and installation evidence are included with the release assets.
Local candidate: GXR 1.0.5
Manager samsung-gxr-v1.0.5, code 32670, was installed and tested in one
user-authorized soft restart. APK SHA-256:
ba5757f8e6abe10d2163d47e93cca1ca040f45b5591bf862340f99896a1483c2.
Embedded/deployed daemon:
55222b770cbeb7dcaaed8d359e9f6efda02628dc111cba96306400466372716c.
This candidate has not been published.
The logger Steam Link process, which had OpenXR loaded, was force-stopped at
02:06:28.950 on 2026-10-12. The verified empty runtime-client list was logged
at 02:06:29.101, before Android stop at 02:06:29.269. Android completed its
restart in 27.508 seconds. Root remained available and kernel boot ID stayed
eef1a7a9-d6ce-46a6-bc27-ed28214d3efa. Haptics, Whitening and Timestamp were
verified active afterward. The ordinary Steam Link was also launched before
the restart, but remained in its non-OpenXR menu and was not an app-close target.
Velocity was already inactive before this test: its checkbox was ON, but its
worker had failed after a prior application task removal within 30 seconds.
Its existing same-boot supervisor quarantine and auto.pending were preserved.
The new test therefore does not establish active Velocity's health through
the planned app exit. It does establish app shutdown order and Android recovery.
Android check/clippy with warnings denied/fmt, nine new OpenXR shutdown tests,
the existing service/restart/wake-lock suites, and ten module lifecycle tests
passed. ARM64 Manager build, v2 signature, certificate continuity, 16 KiB ZIP
alignment and exact embedded/deployed daemon verification passed. Kernel payload
is unchanged. No cold boot, tracking-motion validation or public release was done.
Current release: GXR 1.0.4
Manager samsung-gxr-v1.0.4, code 32669. The exact signed release APK
was installed and tested; its SHA-256 is
5c0d71f7034eeb94c8d54990cdd1325e80906f96b7cb7aea228d9575ba74317a.
Embedded and deployed daemon SHA-256:
dfe94b55316418a312c1e676033cdabbc76cce433e660f747cbfd7bf7051db19.
During an intentional same-version reinstall in a soft restart, the running
executable became /data/adb/ksud (deleted). All four module supervisors
successfully launched through /proc/self/exe. Haptics MAIN, module-owned
Whitening and Timestamp were verified live. Velocity's worker was alive and
waiting for an OpenXR app. Framebuffer10 was disabled and removed; it was
not activated in this test. The kernel boot ID was unchanged, with no restart
error. The kernel/root payload remains unchanged.
Android check, clippy with warnings denied, formatting, deleted-executable
regression, lifecycle guards and six stage-error propagation tests passed.
Full power-cycle and active-app Velocity validation were not performed.
See 1.0.4 details.
Historical release: GXR 1.0.3
See 1.0.3 changes and test scope and the
restart API. The Manager version is
samsung-gxr-v1.0.3, code 32668; the original GXR kernel payload is unchanged.
The local test APK SHA-256 was
719c9bebff288f4ce09db3a7de8936ee9edfc3ef9befa95e81188526e15f5475.
Its embedded/deployed ksud SHA-256 was
3b54400ff1b5928e8871c89ffaaa5545691fb52810ccae26e0760704fe98dc1f.
Two consecutive coordinated soft restarts passed with active Framebuffer10
0.3.1 and Whitening 0.1.3; Haptics was also verified active, and Velocity was
waiting for an OpenXR target. An earlier cycle passed on 1.0.2. This is runtime
lifecycle evidence, not a visual/physical quality or cold-boot validation.
The public APK uses the same daemon but removes the test-only installation flag.
Its exact signed bytes have not been device-tested. Release hashes and build
provenance are supplied separately. The sections below retain historical tests
and must not be interpreted as tests of every later binary.
Reference device test
| Item | Tested value |
|---|---|
| Device | Samsung Galaxy XR SM-I610 |
| Codename | xrvst2 |
| Device firmware / build | I610UEU2AZF3 |
| Running kernel | 5.10.240-android12-9-perf-33775878-abI610UEU2AZF3 |
| Module loader | DFRoot 4.1 |
| KernelSU source base | diabl0w/KernelSU, samsung-v1.0, commit 10aa21cbb6a2b05d7792f60cde76565b99d89a63 |
| Tested local APK | KernelSU-GXR_32664_no-DEFEX.apk |
| APK SHA256 | 106c1646a3a03652ba2946b6e927299c49a8abb705ddb4ea58cad6166e5a3576 |
| Profile | KDP=y, DEFEX=n, RKP_NO_PATCH_TEXT=y; SCS=y, CFI=y |
| Manager signing | APK v2 only; matching certificate compiled into the module |
Confirmed: the GXR module loaded, and the Manager launched two shell
processes with UID 0. This resolved the original module's missing-DEFEX error
and the initial incorrectly signed Manager's authentication failure.
Not yet verified: root grants to other applications, persistence after
a full reboot, long-term stability, other firmware builds or other devices.
The Apply on boot observation was described by the tester as resembling a
soft reboot; it is not evidence of reliable boot persistence.
The older AZD8 dump was used for analysis only. It is not the firmware on
which the successful reference test was performed.
Scope of automated releases
CI builds this GXR profile and checks the module, APK signature scheme,
alignment, embedded ksud and the source-built Manager. A successful CI build
does not mean that its exact APK has been tested on a headset. The table
above describes the specific local APK tested on the reference device.
Each generated package includes BUILD-INFO.txt with its source commit and
workflow run, and SHA256SUMS.txt for the compiled files.
Use DFRoot to load the module.
Do not flash the APK as a boot image.
GXR 1.0.1
The Manager version is samsung-gxr-v1.0.1 (Android version code 32666).
Soft-restart requests run off the UI thread and report submission failures.
The daemon serializes restart requests and acquires a kernel-expiring,
180-second suspend blocker before stopping Android. Standard module startup
and the Action button are retained; no live-checkbox extension is included.
The preceding gxr-1.0.1-test1 build passed native checks, five guard tests
and a clean Manager release build. The owner tested it on the reference
headset and reported the Manager working well. Version 1.0.1 retains that
daemon and kernel payload; it updates Manager branding and release metadata.
This report does not establish module health or authorize a soft reboot.
KernelSU GXR 1.0.6 — GitHub sources and themes
KernelSU GXR 1.0.6
Manager version samsung-gxr-v1.0.6, Android version code 32672.
Repository sources and updates
Add a public GitHub repository under Modules -> repository icon -> Sources.
The Manager reads its modules.json catalogue or stable Release ZIP assets, offers
multiple selection, downloads/verifies the selected archives, then installs them
sequentially. There is no five-module ID allowlist and no ten-module selection
limit. New catalogue entries do not require rebuilding the Manager.
Installed packages use their own updateJson. Older packages obtain feed URLs
from the configured Git catalogues; conflicting ID mappings are not guessed.
OFF modules are checked too, and refresh requests recheck the remote version.
Any valid GXR module ID can use the disabled-package installer if its archive
meets the documented lifecycle contract. The installer checks identity, payload
hashes, safe paths and startup layout; stops/restores an existing module; retains
an inert backup and persistent guard/config files; and commits the replacement
DISABLED. Failed or ambiguous restoration blocks replacement. It does not execute
downloaded install scripts, regenerate root/startup metadata, enable modules or
restart Android. Non-GXR modules retain their standard installation path.
See package contract and recovery.
Themes
Shared Material controls inside Miuix now receive a palette derived from the
active Miuix colors and app appearance preference. Sources cards, checkboxes,
dropdowns, text fields and dialogs follow light/dark/system mode and custom
accents instead of using Material's default light palette on a dark screen.
The repository screen paints its themed surface explicitly. AMOLED mode keeps
Material background surfaces black. The existing Material appearance remains.
Userspace
Includes the previously locally tested 1.0.5 change: before an intentional soft
restart, notify module workers, close verified third-party OpenXR app clients,
then stop Android. System services and ambiguous package ownership are excluded;
failed shutdown cancels before Android stop. No app is relaunched automatically.
Module installation/control and soft restart share a volatile operation lock.
Kernel payload, original-file protection and standard checkbox semantics remain.
Validation and limits
Android Rust check, clippy with warnings denied and formatting passed. Host
tests cover OpenXR shutdown, restart/service guards, stage dispatch and GXR
replacement. The new regression installs and upgrades twelve previously unknown
IDs while retaining disabled state. Manager tests cover twelve Git catalogue
entries, remote feed discovery, conflict rejection and ZIP identity/version checks.
Theme/source code builds in the release Manager.
The initial preview APK was installed and its exact bytes read back. Launch was
authorized, but a sleeping headset and later disconnected USB prevented source
UI verification. This is not a claim that live module replacement has been tested.
The 1.0.5 soft-restart device evidence is recorded separately in TESTED.md and does
not establish every later binary's behavior. No module activation, restart,
native throwing or full power-cycle validation is implied by this release.
Final APK 1.0.6 (32672) installed and read back on SM-I610; exact release bytes verified. Boot ID and module versions/preferences unchanged. The headset remains asleep, so theme/source UI visual verification is still pending.
KernelSU GXR 1.0.4
Fix module startup when a running daemon file is replaced during a soft restart.
Service dispatch errors now fail the restart instead of being logged as warnings
followed by success. Logs distinguish script dispatch from live patch activation.
The exact signed APK was tested on Galaxy XR: Haptics, Whitening and Timestamp
were verified active; Velocity was waiting for an OpenXR app. Local Android and
regression checks passed. Full power-cycle validation remains pending.
KernelSU GXR 1.0.3
- Coordinate module preparation and verification around one successful-path Android restart.
- Prevent duplicate service workers and retain bounded per-hook diagnostic logs.
- Keep standard module controls and the existing kernel/root payload.
Android checks and 21 host tests passed. The daemon passed two consecutive soft
restarts with active Framebuffer10 and Whitening. Cold-boot validation remains
pending; the earlier Framebuffer started-hook failure was not reproduced.
APK installs normally without -t; it retains the tested daemon but its exact
repackaged bytes have not been device-tested. Checksums and build details are attached.
KernelSU GXR 1.0.1
KernelSU GXR 1.0.1 for Samsung Galaxy XR (SM-I610).
- App name: KernelSU GXR. Displayed version: samsung-gxr-v1.0.1 (32666), without the test suffix.
- Soft-restart requests run off the UI thread, with submission feedback and duplicate-request protection.
- The daemon acquires a kernel-expiring 180-second suspend blocker before stopping Android, bounds the completion wait, and attempts Android startup if module setup fails.
- Standard KernelSU module controls and the Action button are retained. The removed live-checkbox extension is not included.
- Release automation builds the current GXR Manager from source instead of repackaging the old Samsung Manager.
The APK uses the existing GXR signing certificate and updates the previous GXR Manager without uninstalling it. The previously tested kernel, ksuinit and soft-restart daemon are retained. The APK was installed successfully on the reference headset; Android confirms the release version. The owner reported the preceding soft-restart test build working well; final interactive checks are in progress.
Validation: clean Manager release build plus final release rebuild; five restart-guard tests; APK v2-only signature, alignment, release metadata, absence of testOnly and embedded daemon identity verified. Earlier Android native check/clippy/fmt results apply to the unchanged daemon. The revised full Linux CI pipeline has not yet been run end to end.
Use DFRoot with the existing GXR workflow. This APK is not a boot image. Updating the Manager does not enable modules or perform a soft reboot. See TESTED.md for the tested hardware/firmware scope.
KernelSU GXR gxr-v1.0.0
KernelSU GXR: tested configuration
Reference device test
| Item | Tested value |
|---|---|
| Device | Samsung Galaxy XR SM-I610 |
| Codename | xrvst2 |
| Device firmware / build | I610UEU2AZF3 |
| Running kernel | 5.10.240-android12-9-perf-33775878-abI610UEU2AZF3 |
| Module loader | DFRoot 4.1 |
| KernelSU source base | diabl0w/KernelSU, samsung-v1.0, commit 10aa21cbb6a2b05d7792f60cde76565b99d89a63 |
| Tested local APK | KernelSU-GXR_32664_no-DEFEX.apk |
| APK SHA256 | 106c1646a3a03652ba2946b6e927299c49a8abb705ddb4ea58cad6166e5a3576 |
| Profile | KDP=y, DEFEX=n, RKP_NO_PATCH_TEXT=y; SCS=y, CFI=y |
| Manager signing | APK v2 only; matching certificate compiled into the module |
Confirmed: the GXR module loaded, and the Manager launched two shell
processes with UID 0. This resolved the original module's missing-DEFEX error
and the initial incorrectly signed Manager's authentication failure.
Not yet verified: root grants to other applications, persistence after
a full reboot, long-term stability, other firmware builds or other devices.
The Apply on boot observation was described by the tester as resembling a
soft reboot; it is not evidence of reliable boot persistence.
The older AZD8 dump was used for analysis only. It is not the firmware on
which the successful reference test was performed.
Scope of automated releases
CI builds this GXR profile and checks the module, APK signature scheme,
alignment, embedded ksud and preserved Manager DEX. A successful CI build
does not mean that its exact APK has been tested on a headset. The table
above describes the specific local APK tested on the reference device.
Each generated package includes BUILD-INFO.txt with its source commit and
workflow run, and SHA256SUMS.txt for the compiled files.
Use DFRoot to load the module.
Do not flash the APK as a boot image.