Tutorial to capture bug log(Update of PRO 5)

36331

62

2015-12-14 20:17

Descending
Author
How to Capture bug log?

Update： Tutorial for PRO

After the logreport apk is installed, you can select the issue type to capture logs. Enter the \Android\log\ directory on the storage disk of the mobile phone. Then, upload the corresponding logs.

1.For the basic issue(battery draning issue)，please select the first mode 【Automatic Mode】
 

2.For other functional issue,please select the second mode【Professional Mode】
 


- Wi-Fi Issues:

Settings > Accessibility > Developer options > Enable WiFi Verbose Logging

Enable the logreport app and select all of the five issue types and click the Start button on the bottom part. After the Wi-Fi  issue is reproduced, click the Stop button on the bottom.


- Bluetooth Issues:


Settings > Accessibility > Developer options > Enable Bluetooth HCI snoop log

Enable the logreport app and select all of the five issue types and click the Start  button on the bottom part.  After the Bluetooth issue is reproduced, click the Stop button on the bottom.


- Signal Issues:

Enable the logreport app and select the Mobile and network issue types and click the  Start button on the bottom part. After the signal issue is reproduced, click the Stop button on the bottom.


If you dont know the bug type, you just need to select all of the five issue types!


----------------------------------------------------------------------------------------------------------------------------------------------------------------
For all MTK log

1.      Close “Logcat Guard” switch：
Tester have to check in developer option that the “Logcat guard is disabled”
 
2.      Manual grab Log setup:
A.Modem bug log (whenever there is an issue related to signal, audio message reception problem):

Click “Dial”Icon>input“*#*#3646633#*#*” which Navigate to >Engineer Mode
Swipe to “Hardware Testing”
Tap “Audio”
Tap “Audio logger”
Tap “Speech Logger”
{Tester has to enable speech and AP speech log}
 
Then back to“Log and debugging”>Tap”MTKLogger”>Tap red start button (usual MTK logfile would now contain an extra log for connectivity issue)

B. Normal bug log:
Click “Dial”Icon>input“*#*#3646633#*#*” which navigate to >EnginnerMode
Swipe to “Log and debugging”
Click MTKLogger

 


3.     Click on “play” option navigateyourself back to home. Now do what you usually do and navigate to the step where bug is present! Once done stop the mtk file logger. The log file would now contain all the steps which you produced. and it would be used by official tester to reproduce them.

4.     Export the log info
Log info is stored in the “FileManager> “mtklog”, compress the “mtk log”file to .rar/zip format file.
~Rename the log file with the issueinfo, such as “Can’t switch to other carriers normally”.


Tips:
1. If the Bug is display issues( such as strings display incomplete /overlapping/display not clear/translation incorrect etc), need provide the screencapture or the reproduce path.

2. If the bug is function problem,please provide the log and reproduce path, such as wifi cannot be connected /cannot dial/send message failed/ App error/Auto exit/phone lagging etc.

3. If it is the third app compatibility issue, such as the Google play cannot download applications. User should provide the app version number/download address, describe the issue details.

meizu.logreport_2400526.apk

3.36 MB