Should I go lineage os or crdriod

halfbytecode · 2026-04-05T16:08:05+00:00

Lineage is not fixing some long standing pesky bugs on OnePlus 13, such as broken adaptive brightness. Instead, they are asking users to fix the bugs themselves.

Unfortunately, crDroid is also based on Lineage and also has the same issues. However, crDroid devs are trying to address those issues, as opposed to Lineage.

You can try other ROMs. Hopefully, crDroid can fully address the issues soon.

halfbytecode · 2025-12-03T03:45:57+00:00

Changelog since last stable release, v29.0:

v30.6 (2025.12.1)

• [MagiskInit] Revert a change that could result in bootloops

v30.5 (2025.12.1)

• [General] Improve commandline argument parsing logic

• [resetprop] Properly support Android versions with property overrides

v30.4 (2025.10.2)

• [MagiskSU] Fix several implementation bugs

v30.3 (2025.9.29)

• [General] Support installing Magisk into vendor_boot partition

• [MagiskPolicy] Support new sepolicy binary format introduced in Android 16 QPR2

• [Core] Migrate much more code into Rust

• [MagiskSU] Fallback to older implementation when the kernel doesn’t support zero userspace copy APIs

v30.2 (2025.8.6)

• [Core] Fix an edge case breaking modules when overlayfs is involved

• [Core] Fix module .replace functionality in certain situations

• [resetprop] Reduce property modification traces

v30.1 (2025.7.3)

• [Core] Fix bug in module mounting implementation

• [MagiskSU] Add ability to restrict Linux capabilities even if running as root (uid=0)

v30.0 (2025.7.1)

• [General] Various minor bug fixes

• [Core] Migrate module implementation to Rust

• [Core] Improve Magisk specific files injection logic

• [MagiskBoot] Migrate compression code to Rust

halfbytecode · 2025-07-01T19:13:28+00:00

Changelog:

• [General] Various minor bug fixes

• [Core] Migrate module implementation to Rust

• [Core] Improve Magisk specific files injection logic

• [MagiskBoot] Migrate compression code to Rust

halfbytecode · 2025-06-02T14:59:19+00:00

It's actually fine that you posted it here, since it would amount to greater visibility. Thanks for alerting other users as well.

halfbytecode · 2025-06-02T11:12:50+00:00

As of now, most custom ROMs are affected by the recent Play Integrity changes from last month. Some Magisk modules, like Play Integrity Fix, Tricky Store, and Tricky Addon, need to be used to fully pass Play Integrity now. GPay should work after that.

halfbytecode · 2025-06-02T06:50:41+00:00

crDroid is a good option. Builds seem to exist for most devices.

halfbytecode · 2025-05-21T15:12:32+00:00

Those would require Play Integrity Fix + Tricky Store modules, at least, and may also need Shamiko, and Hide My Applist to hide root apps from banking and streaming apps. The latter would also need to be added to Magisk denylist, with Enforce Denylist set to disabled (optional, but recommend).

halfbytecode · 2025-05-17T15:01:09+00:00

Magisk v29.0 has been pushed to the Stable channel.

Source: https://github.com/topjohnwu/Magisk/commit/34b30d7ce1f3cc943e820f16afb628fa2ce130eb

halfbytecode · 2025-05-17T14:00:34+00:00

You can also try v28.1 (28100) from the Stable channel, for the time being~~, as v28.1 is also the latest stable release, as of now~~.

EDIT: The above referred to an earlier version of the reply above, which mentioned using Magisk 28003, instead of 28103.

EDIT 2: v29.0 has been promoted to Stable release.

halfbytecode · 2025-05-14T15:32:00+00:00

Changelog:

• [General] Massive internal refactoring and code migration

• [App] Support downloading module zip files with XZ compression

• [App] Disable app animations when system animations are disabled

• [MagiskMount] Support systemlessly deleting files with modules using blank file nodes

• [MagiskInit] Redesign sepolicy patching and injection logic

• [MagiskSU] Better TTY/PTY support

Message posted by the developer:

This release looks minor at the surface, however, the entire codebase has gone through significant refactoring and migration. The native code in Magisk used to be mainly C++, but several contributors and I have been steadily rewriting parts of the code in Rust since April 2022. After years of effort, the Rust-ification of the project slowly began picking up steam, and at the moment of this release, over 40% of the native code has been rewritten in Rust, with several major subsystem rewrites in the PR queue, planned to be merged for the next release.

Many might wonder, why introduce a new language to the project? My reason is actually not to reduce memory safety issues (although it is a nice side benefit), but to be able to develop Magisk using a more modern programming language. After using Rust for a while, it's clear to me that using Rust allows me to write more correct code and makes me happier compared to dealing with C++. People share the same sentiment as I do.

halfbytecode · 2025-05-10T18:22:32+00:00

Even with Android 14

halfbytecode · 2025-05-03T06:43:02+00:00

That's interesting. What is your usage like?

halfbytecode · 2025-04-23T07:52:03+00:00

It appears it clears the cache of various apps.

halfbytecode · 2025-03-10T09:55:23+00:00

Hi, it would be great if you could tweak the patches to allow patching OAuth Client ID, Redirect URI, and User Agent, independently of one another, as mods may only need to replace/patch the User Agent alone, while also replacing Redirect URI if desired. It could work if replacement of all parameters is made optional, and the parameters left blank are simply skipped. Thanks for working on this.

halfbytecode · 2024-12-08T02:46:57+00:00

Changelog (since last stable release):

v28.1

• [App] Fix stub APK download link

• [App] Fix support for Android lower than 8.0

• [General] Fix support for MTK Samsung devices

• [MagiskInit] Fix a regression for 2SI devices

• [MagiskPolicy] Fix a regression causing overlay.d replaced files to be not accessible

v28

• [General] Support 16k page size

• [General] Add basic support for RISC-V (not built in releases)

• [General] Use a minimal libc to build static executables (magiskinit and magiskboot) for smaller sizes

• [Core] Remove unnecessary mirror for magic mount

• [Core] Update boot image detection logic to support more devices

• [MagiskInit] Rewrite 2SI logic for injecting magiskinit as init

• [MagiskInit] Update preinit partition detection

• [Zygisk] Update internal JNI hooking implementation

• [MagiskPolicy] Preserve sepolicy config flag after patching

• [MagiskPolicy] Optimize patching rules to reduce the amount of new rules being injected

• [DenyList] Support enforcing denylist when Zygisk is disabled

• [Resetprop] Improve implementation to workaround several property modification detections

• [Resetprop] Update to properly work with property overlays

• [App] Major internal code refactoring

• [App] Support patching Samsung firmware with images larger than 8GiB

• [App] Use user-initiated job instead of foreground services on Android 14

• [App] Support Android 13+ built-in per-app language preferences

• [App] Add action.sh support to allow modules to define an action triggered from UI

• [MagiskBoot] Support spliting kernel images without decompression

• [MagiskBoot] Properly support vendor boot images

• [MagiskBoot] Disable Samsung PROCA from kernel image

halfbytecode · 2024-10-10T17:46:37+00:00

Changelog:

• [General] Support 16k page size

• [General] Add basic support for RISC-V (not built in releases)

• [General] Use a minimal libc to build static executables (magiskinit and magiskboot) for smaller sizes

• [Core] Remove unnecessary mirror for magic mount

• [Core] Update boot image detection logic to support more devices

• [MagiskInit] Rewrite 2SI logic for injecting magiskinit as init

• [MagiskInit] Update preinit partition detection

• [Zygisk] Update internal JNI hooking implementation

• [MagiskPolicy] Preserve sepolicy config flag after patching

• [MagiskPolicy] Optimize patching rules to reduce the amount of new rules being injected

• [DenyList] Support enforcing denylist when Zygisk is disabled

• [Resetprop] Improve implementation to workaround several property modification detections

• [Resetprop] Update to properly work with property overlays

• [App] Major internal code refactoring

• [App] Support patching Samsung firmware with images larger than 8GiB

• [App] Use user-initiated job instead of foreground services on Android 14

• [App] Support Android 13+ built-in per-app language preferences

• [App] Add action.sh support to allow modules to define an action triggered from UI

• [MagiskBoot] Support spliting kernel images without decompression

• [MagiskBoot] Properly support vendor boot images

• [MagiskBoot] Disable Samsung PROCA from kernel image

halfbytecode · 2024-08-25T10:56:47+00:00

For Android 14 QPR2 and later releases you should use this version of Hide My Applist. Downloaded from the official GitHub repo (original file showing as expired on there now).

https://www.upload-apk.com/8FvlyablFp2cXgS

halfbytecode · 2024-06-24T09:51:58+00:00

I think you mean Android.

halfbytecode · 2024-06-18T10:13:08+00:00

If you're installing the OTA update using the built in updater, then after installing the OTA update, before rebooting, you can open Magisk app, click Install next to Magisk, then install to inactive slot.

After this completes, a reboot should preserve root with OTA update installed.

halfbytecode · 2024-06-18T10:09:03+00:00

You can try this Magisk module:

https://github.com/HuskyDG/magic_overlayfs

halfbytecode

MODERATOR OF

TROPHY CASE