[General Topics] IronTechmonkey:
- vii. BUG REPORTING, TROUBLESHOOTING, AND FAQ WIP

----------------------------------------------

Bug Reporting:

Please report bugs in the primary MiXplorer thread here: http://xdaforums.com/showthread.php?t=1523691.

Bug reports should come from the newest beta version of the app. If you notice a bug in the newest release version then check the newest beta. If it also occurs in the beta then log it from there.

Bug reports should include. details about your device (Android version, ROM version, Root status, SU method, MiXplorer version) as well as a step by step description of how to reproduce the issue and a log taken while the issue was reproduced.

----------------------------------------------

MiXplorer's Built-in Logging:

Enable MiXplorer logging: Settings . More settings . Logging (enable)

MiXplorer has a native logging feature. If logging is enabled (as it is by default) then the most efficient and the recommended way to do it is the following:

- After crash or after experiencing issue,

- Open MiXplorer

- 3-dots menu

- Send log.

If you have disabled logging in the past, or you if are diagnosing more complicated issues or if you will be reviewing the logs yourself before sending. Here is a manual method that some people use:

- Enable MiXplorer logging.

- Close MiXplorer.

- Open MiXplorer.

- Reproduce the issue.

- Close MiXplorer.

- The logs should be in /storage/emulated/0/Android/data/com.mixplorer/cache/log/ (The path may vary slightly depending on ROM).

- Use alternative file manager (just for this ;)) to get most recent log in folder.

- If using MiXplorer to get the log manually, then make sure to get the log for the previous MiXplorer session rather than the one for the current session.

Testing and Logging Notes:

- Reproduce and log issues in a new session of MiXplorer that was started after logging has been enabled. In other words: Enable logging, then close MiXplorer, then start MiXplorer to reproduce the issue and send the log. A new log is created each time you open MiXplorer. Note: - In some cases it is recommended to test the issue in a clean installation of MiXplorer (after uninstalling MiX then reinstalling it).

- The MiXplorer log directory will not appear until MiXplorer logging has been enabled at least once since last new installation of MiXplorer. Also, if MiXplorer is uninstalled the log folder will be deleted, so if you are getting logs manually during repeated tests remember to do so before next uninstall.

- Before sharing logs it is a good practice to review them for information that you don’t want to share, and to delete that information or replace it with an obvious label, eg <thing x deleted>. To each their own about what to delete, but reviewing logs with privacy in mind before sending is prudent.

- For logging more complex issues, or certain types of FCs where native app logging does not catch the error, a full system log (logcat) may be needed. The app "MatLog" (formerly "CatLog") from Play Store https://play.google.com/store/apps/details?id=com.pluscubed.matlog&hl=en can be used to capture logcats on the device. If an issue is causing reboots then the log might have to be taken from a USB connection on a computer via ADB.

- When you share the log, also share the following:

1) Full details of the device including: Android version, ROM version and variant, Root status, SU status, busybox status.

2) A detailed description about how to reproduce the error when logging so others may try to reproduce it.

----------------------------------------------

LINKS TO FAQ SECTIONS

i. INTRODUCTION, GETTING MIXPLORER, & INSTALLATION

ii. UI, NAVIGATION, VIEW CONFIGURATION, BOOKMARKS, TABS

iii. WORKING WITH FILES & FOLDERS (Copy Move methods, Trash option)

iv. FTP, HTTP, TCP SERVERS

v. MiX NUGGETS (Freestanding Topical Posts)

vi. THEMES and SKINS

vii. BUG REPORTING, TROUBLESHOOTING, AND FAQ WIP