Skip to content

Softened the cgroup devices controller and devtmpfs checks to maintain GKI compatibility#39

Merged
ravindu644 merged 3 commits intomainfrom
dev
Apr 8, 2026
Merged

Softened the cgroup devices controller and devtmpfs checks to maintain GKI compatibility#39
ravindu644 merged 3 commits intomainfrom
dev

Conversation

@ravindu644
Copy link
Copy Markdown
Owner

  • Even in normal mode, we were forcefully checking and refusing to run Droidspaces, even though the non-hw-access mode doesn't require devtmpfs at all.
  • From now on, we will only enforce devtmpfs mode if the user uses hardware access mode.
  • Also, there's no point in hardcoding a check for legacy cgroup devices controller support if cgroupv2 support is present. We only need the cgroup devices controller in forced cgroupv1 mode anyway.
  • By not enabling the cgroup devices controller in the GKI kernel, we have completely eliminated ABI breakage, allowing Droidspaces to run on the GKI kernel without breaking the ABI, which is a big deal.

… for the hardware access mode

Signed-off-by: ravindu644 <droidcasts@protonmail.com>
…roupv2

Signed-off-by: ravindu644 <droidcasts@protonmail.com>
@ravindu644 ravindu644 merged commit 7a375fa into main Apr 8, 2026
3 checks passed
@ravindu644 ravindu644 deleted the dev branch April 8, 2026 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant