Tags give the ability to mark specific points in history as being important
-
v0.3.4
718904cb · ·MinsOS v0.3.4 Updates install from Settings, and the battery page shows a measured figure. - In-device updater: reads this device's own manifest, verifies against the MinsOS OTA certificate, stages and reboots. On the T970 the bundled crypto-less recovery installs it unattended. - Battery health is recomputed from the fuel gauge at every boot; the cycle row is hidden rather than shown as a false zero. - T870: the side-key fingerprint enrolment UI renders (display layer only). - Third device: SM-T976B (gts7xl) ships alongside the T970 and T870. Verified on hardware for gts7xlwifi (SM-T970). The other two rest on the build gates and on tester reports. USB-C DisplayPort is NOT fixed in this release - the redriver change had only ever been in one of the three kernel build paths, and the shipped kernels have CONFIG_REDRIVER unset. Both local paths carry it now; it lands with the next kernel.
-
v0.3.2
Release: v0.3.2 - landscape view applies, incremental updates work, the installer checks your model7a5f8fb1 · ·MinsOS v0.3.2 - 2026-08-02 Tags the tree the released gts7xlwifi package was built from (16:43-16:55); the commits after this one are gts7lwifi bring-up, not part of this release. - "Landscape view for portrait apps" applies. Two framework-res booleans ship false and the runtime flag that looks like a way around them is ANDed with the same build-time value, so it cannot reach. Both gates now return true. - Incremental updates work, for the first time on any release. A delta only remaps partitions whose size changed, but still wrote a one-block placeholder to unchanged ones - into a read-only mapping, so the installer aborted with E2001. Unchanged partitions are now skipped entirely. Verified v0.3.1 -> v0.3.2 on hardware: 24 MiB, about two seconds. - The installer asserts ro.boot.em.model, which the bootloader supplies, instead of ro.product.device - which inside a recovery is the recovery's own value, not the tablet's. MinsOS_v0.3.2_20260802_gts7xlwifi.zip 5,756,531,007 B sha256 0e99592be344c2aff7abbba6579c97844e643e01a63a6fa219598c5ff7c969e5 MinsOS_v0.3.1-to-v0.3.2_gts7xlwifi_incremental.zip 25,255,108 B sha256 bf2f07210fde8c2b0b151caec7d623c82df9e8708027cad0aa317e5d512a9dfe
-
v0.3.1
Release: v0.3.1 - KernelSU modules mount, safe mode exists, the touchpad tapsad3eed55 · ·MinsOS v0.3.1 - KernelSU modules mount, safe mode exists, the touchpad taps Three fixes, all of them in the kernel, all of them invisible from userspace: - ksu_handle_sys_read was never called from SYSCALL_DEFINE3(read), so ksud never ran at boot and no module was ever promoted or mounted. Root was unaffected because it rides the execve and open hooks, which is why this read as a module bug for three releases. - ksu_handle_input_handle_event was never called from input_handle_event(), so safe mode - the escape hatch from a module boot loop - did not exist. - stm32_pogo_touchpad.c never called input_mt_report_pointer_emulation(), so the Book Cover touchpad reported contacts belonging to no finger and tap-to-click could never fire. Also: super partition sizes are now measured from this tablet's own firmware rather than copied from another ROM's tree, where they were 116 MiB too large. Verified on device, not in a build log: the rc hook firing at boot, modules promoted, module content readable at its /system path from inside a running app, safe mode recovering a deliberately broken boot, BTN_TOOL_FINGER present where it had never appeared, and the shipped boot.img byte-identical to the image those results came from. sha256 e6e2168b6e0ff29d686f118a2bcc1c80cf0ca7dccb296337d9c20842290f5ab5
-
-
-
-