android/SukiSU-Ultra
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

website: update translation (#2471)

Browse Source
This commit is contained in:
igor
2025-02-24 00:41:00 -03:00
committed by GitHub
parent 0254936bb2
commit cef7f30c2e
4 changed files with 23 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
website/docs/guide/faq.md
View File

@@ -2,13 +2,13 @@
## Does KernelSU support my device?
KernelSU supports devices running Android with an unlockable bootloader, moreover official support is only for GKI Linux Kernels 5.10+ (in practice this means that your device needs to have Android 12 out of the factory in order to be supported).
KernelSU supports devices running Android with an unlocked bootloader. However, official support is only for GKI Linux Kernels 5.10+ (in practice, this means your device needs to have Android 12 out-of-the-box to be supported).
You can easily check support for your device via the KernelSU Manager, which you can get [here](https://github.com/tiann/KernelSU/releases).
You can easily check the support for your device through the KernelSU manager, which is available [here](https://github.com/tiann/KernelSU/releases).
If it shows `Not Installed`, then your device most likely supports KernelSU officially.
If the app shows `Not installed`, it means your device is officially supported by KernelSU.
If it shows `Unsupported`, then your device is not officially supported at present. However, you can build kernel source and integrate KernelSU to make it work, or use [Unofficially supported devices](unofficially-support-devices).
If the app shows `Unsupported`, it means your device isn't officially supported at present. However, you can build kernel source code and integrate KernelSU to make it work, or use [Unofficially supported devices](unofficially-support-devices).
## Does KernelSU need to unlock bootloader?
@@ -16,15 +16,15 @@ Certainly, yes.
## Does KernelSU support modules?
Yes, most Magisk modules work out-of-the-box with KernelSU, check [Module guide](module.md) for more info.
Yes, most Magisk modules work on KernelSU. Check [Module guide](module.md) for more info.
## Does KernelSU support Xposed?
Yes, you can use LSPosed (or other modern XPosed derivative) with [ZygiskNext](https://github.com/Dr-TSNG/ZygiskNext).
Yes, you can use LSPosed (or other modern Xposed derivative) with [ZygiskNext](https://github.com/Dr-TSNG/ZygiskNext).
## Does KernelSU support Zygisk?
KernelSU has no built-in Zygisk support, but you can a module like [ZygiskNext](https://github.com/Dr-TSNG/ZygiskNext) to support it.
KernelSU has no built-in Zygisk support, but you can use a module like [ZygiskNext](https://github.com/Dr-TSNG/ZygiskNext) to support it.
## Is KernelSU compatible with Magisk?

8
website/docs/guide/module.md
View File

@@ -99,7 +99,7 @@ author=<string>
description=<string>
```
- `id` has to match this regular expression: `^[a-zA-Z][a-zA-Z0-9._-]+$` .<br>
- `id` has to match this regular expression: `^[a-zA-Z][a-zA-Z0-9._-]+$`<br>
Example: ✓ `a_module`, ✓ `a.module`, ✓ `module-101`, ✗ `a module`, ✗ `1_module`, ✗ `-a-module`<br>
This is the **unique identifier** of your module. You should not change it once published.
- `versionCode` has to be an **integer**. This is used to compare versions.
@@ -150,7 +150,7 @@ REPLACE="
This list will automatically create the directories `$MODPATH/system/app/YouTube` and `$MODPATH/system/app/Bloatware`, and then execute `setfattr -n trusted.overlay.opaque -v y $MODPATH/system/app/YouTube` and `setfattr -n trusted.overlay.opaque -v y $MODPATH/system/app/Bloatware`. After the module takes effect, `/system/app/YouTube` and `/system/app/Bloatware` will be replaced with empty directories.
::: tip DIFFERENCE WITH MAGISK
KernelSU's systemless mechanism is implemented through the kernel's OverlayFS, while Magisk currently uses magic mount (bind mount). These two implementation methods have significant differences, but the ultimate goal is the same: modifying /system files without physically modifying the /system partition.
KernelSU's systemless mechanism is implemented through the kernel's OverlayFS, while Magisk currently uses magic mount (bind mount). These two implementation methods have significant differences, but the ultimate goal is the same: modifying `/system` files without physically modifying the `/system` partition.
:::
If you're interested in OverlayFS, it's recommended to read the Linux Kernel's [documentation on OverlayFS](https://docs.kernel.org/filesystems/overlayfs.html).
@@ -250,8 +250,8 @@ In KernelSU, scripts are divided into two types based on their running mode: pos
In KernelSU, startup scripts are divided into two types based on their storage location: general scripts and module scripts.
- General scripts
- Placed in `/data/adb/post-fs-data.d`, `/data/adb/service.d`, `/data/adb/post-mount.d` or `/data/adb/boot-completed.d.`
- Only executed if the script is set as executable (`chmod +x script.sh`)
- Placed in `/data/adb/post-fs-data.d`, `/data/adb/service.d`, `/data/adb/post-mount.d` or `/data/adb/boot-completed.d`.
- Only executed if the script is set as executable (`chmod +x script.sh`).
- Scripts in `post-fs-data.d` runs in post-fs-data mode, and scripts in `service.d` runs in late_start service mode.
- Modules should **NOT** add general scripts during installation.
- Module scripts