It seems you are encountering some confusion regarding kernel patching and configuration with KernelSU, especially concerning automatic patching and the use of Tracepoint Hook versus Kprobe. Let's break down the issues and provide some guidance.

Automatic Patching and KernelSU

Automatic patching in KernelSU is designed to apply patches to the kernel without manual intervention. If the manager indicates that the kernel has not been patched, it could be due to several reasons:

  1. Patching Failure: The patch might have failed due to compatibility issues or conflicts with the existing kernel configuration.
  2. Configuration Issues: There might be a misconfiguration in the KernelSU settings that prevents patches from being applied.
  3. KernelSU Version: Ensure that you are using a compatible version of KernelSU for your kernel version (4.14.186).

If automatic patching is not functioning as expected, you may need to manually check the patch status and logs to identify the issue. This can often be done through the KernelSU dashboard or command-line tools provided by KernelSU.

Tracepoint Hook vs Kprobe

The confusion between Tracepoint Hook and Kprobe arises from their different use cases in kernel tracing and patching:

  • Tracepoint Hook: This is used for tracing specific events in the kernel. If the manager shows the use of a Tracepoint Hook, it suggests that some part of the kernel or a module is utilizing this feature, even if you haven't explicitly configured it.
  • Kprobe: This is used for more general-purpose tracing and allows you to hook into specific kernel functions or instructions. If you have selected Kprobe in the configuration, it means you are setting up tracing using Kprobe, which is different from the Tracepoint Hook.

If the manager shows the use of a Tracepoint Hook and you intended to use Kprobe, there might be a configuration error or a misunderstanding in how KernelSU interprets your settings. Review your KernelSU configuration to ensure that the correct tracing method (Kprobe or Tracepoint Hook) is selected based on your requirements.

Recommendations

  1. Check KernelSU Logs: Review the logs provided by KernelSU for any errors or warnings related to patching and tracing.
  2. Verify Configuration: Double-check your KernelSU configuration to ensure that the correct options for patching and tracing are set.
  3. Consult Documentation: Refer to the KernelSU documentation for specific instructions on configuring automatic patching and selecting between Tracepoint Hook and Kprobe.
  4. Contact Support: If the issue persists, consider reaching out to KernelSU support for further assistance.

By addressing these points, you should be able to resolve the issues with automatic patching and the incorrect use of Tracepoint Hook in your KernelSU setup.