-
Notifications
You must be signed in to change notification settings - Fork 752
Reporting a bug
While it would be the perfect bug report if you follow all of the following steps you can start with basic information and still add more at a later point or on request. A bug report missing a few details is better than no bug report at all.
Some bugs or issues might already be known, to check that visit the issue tracker. Check current and recently closed issues. If you find a similar issue post a comment under it, otherwise make a new issue.
Gather basic information about your setup, which includes
- What kind of device you have (e.g. Nexus 5)
- What kind of Android version and or custom ROM it's running (e.g. latest stock Android 6.0.1)
- If your device is rooted or unrooted (e.g. Rooted with SuperSU v2.67)
- What version of SD Maid and (if applicable) SD Maid Pro you were running (e.g. SD Maid v4.1.0, Unlocker v4.0.2)
- Long press the settings menu entry, which will open the debug menu. At the top of the page is your install-id tap it to copy it and attach it to your bug report. This way I will be able to check for automatic crash reports from your device.
Good, now we have a baseline for what kind of device setup you have. Now add a little description describing your issue:
- What happened?
- What did you expect to happen?
- What actions did you take?
- Can you reproduce it, i.e. does this happen everytime?
The following instructions are valid for SD Maid v4.2.6+.
If SD Maid crashed I should have gotten an automatic crash report (unless you turned that off, but why would you...). To find this crash report on my server I need to identify your SD Maid installation. This happen through a UUID which is a unique and anonymous identifier SD Maid generates on it's first start. You can find it by going into the Overview section and expanding the box containing SD Maids version information or by long pressing the settings menu entry. Tap it to copy it to your clipboard and add it to your issue ticket.
Record everything that SD Maid sees and does into a text file.
The best thing you can provide to help fix an issue is a debug log of the problem manifesting. A debug log is a very detailed description of everything SD Maid did. Note that the file may private information in form of file names and pathes on your device.
- Open SD Maid, long press Settings to reveal the hidden debug menu and click
RECORD DEBUG LOG
. - A new notification will show and indicate that it's recording.
- Now reproduce the behavior you want to debug. You can reboot the device, as well as kill and restart SD Maid, the recording will automatically resume when SD Maid's process is launched by any means.
- Once you are done, stop the recording via the notification. A window will popup and allow you to share the recorded file.
- Force stop SD Maid.
- Create the file
<sdcard>/Android/data/eu.thedarken.sdm/files/sdm_force_debug_run
- Launch SD Maid by any means, the core process will be loaded in any case which will also consume the created file and start a recording. A visible notification will indicate the on-going recording.
- If parts of SD Maids UI are still responsive then you can finish like in the above. If SD Maid's UI including the log-sharing is inaccessible then you can directly pull the file from
<sdcard>/Android/data/eu.thedarken.sdm/cache/logfiles
We can't pick an easier path for this as this is the only path SD Maid can write to it without any extra permissions or requirements, thus we can use the debugrun to troubleshoot permission issues too 😉.