With Android 4.1 (aka Jelly Bean) and upwards the full system log is only visible if you have root.
To get logs, you have to use
adb logcat via a computer.
These are the instructions for getting logs using ADB:
Copy zip to folder and extract it
Navigate to the folder you have extracted it to. You should see files like adb, AdbWinApi, etc1tool etc. Open the Command prompt/terminal in the current folder(In Windows, press Alt + D and write ‘cmd’)
Enable USB debugging on your phone by going to Settings > Developer Options > USB Debugging (this varies from phone to phone, check on the internet if the phone doesn’t fit this)
Connect your phone by USB to the computer
You will see a popup : “Allow USB debugging. The computer’s RSA fingerprint…..". Click OK
Open the command which was opened previously and write the following command:
To check if your phone is properly connected, write the command
adb devices. This will list the devices connected. Something like
Followup with command:
adb logcat > gateway.txt. This stores the android logs in the file
Now it is taking android logs. This is the time to to try to reproduce the error. Check some of the messages that are ‘WAITING’ and click retry Do this for as many times as you deem necessary to capture logs for that event. Wait about 15 minutes to enable capture of sufficient android device environment logs
Disconnect the phone from the computer
Open the folder which has the adb executable, you will see a file called gateway.txt Send that file to the concerned person (PM or techlead)
NB. If you get this error
command not found in steps 7, 8 or 9 this means adb is not in your PATH. This is where the shell looks for executables. You’ll have to append
./ before any
adb command so that you can use the
adb in the current folder you’re on.
./adb logcat > gateway.txt.
The dot is your current directory, and this tells Bash to use
adb from there.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.