Revision [555]
This is an old revision of MagiskHelpBugs made by didgeridoohan on 2018-12-27 04:44:32.
Asking for help/reporting bugs
Asking for help
If you can't fix the problem yourself, start by looking in the support thread where you might find that someone else have had this problem as well. Search for your device and/or problem. If you can't find anything (it's a big thread), search again. If you still can’t find anything, provide as much information as possible (in the support thread). For example:- Detailed description of the issue and what you've tried so far.
- Details about your device, Android version, ROM, custom kernel, mods, etc.
- Logs! A bug report or a report about some kind of issue that is not accompanied by logs will likely be ignored. Always provide logs! And when providing logs, do NOT paste them into your post. Attach as a file or upload the file somewhere and provide the link.
Reporting a bug
When reporting a bug, make sure you have the latest Canary bleeding edge debug build installed on your device. Otherwise any bug you're reporting may already be fixed upstream. It will also have much more detailed logging enabled (see below).Logs
Relevant logs include:
- Recovery log from installation (in TWRP, go to Advanced - Copy log). If you experience errors when installing Magisk or modules through recovery. Note that this log HAS to be saved right after you've done whatever you're trying to save a log of. If you reboot inbetween, the info will likely get lost.
- Installation log from the Manager (press "Save log" after installing Magisk or a module). If you experience errors when installing Magisk or modules in the Manager.
- Magisk log save from the Manager or in /cache (or /data/cache on A/B devices) through recovery if you don't have root access. If the log is empty, see "The Magisk log is empty" below. Note that when reporting about issues and bugs it is required to use verbose logging (see "Verbose logging" below).
- Logcat. Grab it via ADB or an app (always start by clearing the log so you don't end up with a lot of useless info before whatever you're trying to catch; "logcat -c" with ADB and there's usually an option for it in the app). Useful when other parts of the system are aren't working properly or if it's something that doesn't show up in the Magisk log. Also immensely useful if the Manager is crashing or having other issues. If you can't get root access it's easiest to hook up your device to a computer and use ADB. If your device isn't booting, it might be possible to grab a logcat during boot with ADB.
Verbose logging
When reporting about issues and bugs, it's useful to have more verbose logging. To get the most information possible, make sure to install the Canary bleeding edge debug build. It has debug logging active and will show much more useful information. The log is then saved just as the normal Magisk log, described above. When reporting about Magisk bugs, it is required to use the Canary bleeding edge debug build and the verbose logging.The Magisk log is empty
If your Magisk log is empty, it's likely that you have Android logging disabled. Try enabling it.If you're here because MagiskHide, SafetyNet, Google Pay, etc, isn't working. This is why... Android logging need to be enabled for MagiskHide to work (also see "Requirements").
It might also be that your kernel/ROM wipes the /cache directory during boot, thus removing the log. See here for details.
