This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
manual:faq:how_to_create_debug_log [2017/01/17 08:51] – [MIUI ROMs] mstupka | manual:faq:how_to_create_debug_log [2024/04/08 10:57] (current) – mstupka | ||
---|---|---|---|
Line 2: | Line 2: | ||
---- | ---- | ||
+ | <WRAP center round important> | ||
+ | **If you use Locus Map in a version newer than 4.3, __send us your user ID first__** (Menu > About app/ | ||
+ | </ | ||
- | Logs are the best way for us to find out what causes your problems with the application. Creating an error message/log varies according to the version of Android. | + | If the internal issue identification fails, logs are the best way for us to find out what causes your problems with the application. Creating an error message/log varies according to the version of Android: |
===== Devices with Android 4.2 and higher ===== | ===== Devices with Android 4.2 and higher ===== | ||
- | Devices with Android version 4.1.2 and higher provide error messages that can be sent directly to us via email. | + | |
- | + | ||
- | **Please follow these instructions: | + | |
- | | + | |
- Repeat the action in Locus that causes the crash | - Repeat the action in Locus that causes the crash | ||
- Move to the above-mentioned “Developer Options” in the settings of your device | - Move to the above-mentioned “Developer Options” in the settings of your device | ||
Line 17: | Line 17: | ||
- Wait a few minutes for the report to be created (it may take up to 15 minutes) | - Wait a few minutes for the report to be created (it may take up to 15 minutes) | ||
- the log report should appear in your notification bar. From there (or from " | - the log report should appear in your notification bar. From there (or from " | ||
- | + | ==== Android | |
- | ===== All devices with Android | + | After tapping "Take bug report" |
- | + | ===== Xiaomi - MIUI ROMs ===== | |
- | | + | ==== MIUI 7 and older ==== |
- | - Start Locus | + | |
- | - Repeat the action in Locus you want to report. If the Force close or dialogue appears, select “Close” | + | |
- | - Start CatLog application and wait a few seconds. {{ : | + | |
- | - Move to the CatLog application Menu > Send [1] | + | |
- | - Add the attachment [2] and include the device information {{ : | + | |
- | - Please describe in detail the problem in Locus | + | |
- | - Please send us the log to < | + | |
- | + | ||
- | <wrap info> | + | |
- | + | ||
- | ===== MIUI ROMs ===== | + | |
- | - Please | + | - install the **CatLog** application (available on the Google Play for free) |
- | - go to //Security > Permissions > Root access// > Allow root access to CatLog | + | - go to //Security > Permissions > Root access// > Allow root access to CatLog |
- go on the same way as in case of devices with Android OS older than 4.1 | - go on the same way as in case of devices with Android OS older than 4.1 | ||
+ | ==== MIUI 8 and newer ==== | ||
+ | - tap *#*#284#*#* on your phone dial | ||
+ | - copy the bugreport from your memory directory // | ||
===== General solution for all Android versions===== | ===== General solution for all Android versions===== | ||
Line 41: | Line 33: | ||
Instructions below are used for creating a detailed log but the procedure is more complicated. | Instructions below are used for creating a detailed log but the procedure is more complicated. | ||
- | - Download[[http://server.asamm.com/locus/data/ | + | - Download |
- | - Unzip file | + | - Run it |
- | - Connect the device | + | - Press Y/Yes to install ADB and Fastboot or N/No to skip |
- | - Move to the unzipped Android monitor directory | + | - Press Y/Yes to install ADB system-wide or N/No for current user only |
- | - Start monitor.bat | + | - Press Y/Yes to install Drivers or N/No to skip |
- | - Select | + | - Continue Driver installation |
- | - Repeat | + | - launch |
- | - Save the log as a new *.txt file – button [4] {{ : | + | - connect your phone with the PC via USB |
- | - Please describe in detail | + | - repeat |
- | - Send us the log to < | + | - input **adb bugreport > c:/ |
- | + | - press Enter | |
- | **What if Android monitor cannot be started** | + | - wait until the bugreport is done |
- | + | - **zip the bugreport** (it's huge - over 30 MBs) **and send it to < | |
- | It may happen that Android monitor is not able to find Java installation in your PC. | + | |
- | {{ : | + | |
- | In this case: | + | |
- | - Move to \sdk\tools\lib please | + | |
- | - Edit find_java_specific.bat file and set the path to your java location | + | |
- | - Save this file as find_java.bat (overwrite the previous file) | + | |
- | - Restart monitor.bat again | + |