There are two ways you can create an Android bug report: using adb or generating it directly from your device.
Generating the bug report directly from the device is quicker, but requires you to sign in to a Google account on your device, to be able to share it after it is generated.
Generating the bug report through adb requires you to install adb on a connected computer.
Option 1 : Capture a bug report from a device.
You will need to set up a Google or Gmail account on the device to be able to share the bug report (by email or by Drive)
To take a bug report from Developer options, you must have Developer options enabled on your device so you can access the Take bug report option. The Developer options screen is hidden by default. To make it visible:
- Go to Settings > About phone.
- Tap Build number seven times. Note: if your device is in kiosk, you need to force install the package com.android.systemui in the applications in your profile.
- Return to the previous screen to find Developer options at the bottom. This may vary by device and OS version, but can often be found in the About phone section.
- In Developer options, tap Take bug report.
- Select the type of bug report you want and tap Report.
- After a moment you get a notification that the bug report is ready.
- Tap the notification box to share the bug report.
For this method to work, the device must be signed in to a Google account.
Option 2: Capture a bug report using adb
You will need a USB cable, to connect your device to your computer.
- Open the Android SDK platform tools.
- In the Downloads section, choose the SDK Platform Tools that are appropriate for your workstation.
- On your workstation, open the Downloads folder and uncompress platform-tools file that was downloaded in the previous step.
- Make a note of the directory that adb is downloaded in i.e. /Downloads/adb.
Enable adb report
To use adb with a device connected over USB, you must enable USB debugging in the device system settings, under Developer options.
On Android 4.2 and higher, the Developer options screen is hidden by default.
- To make it visible, locate the device Build number in the device Settings app. This may vary by device and OS version, but can often be found in the About phone section.
- Once located, tap Build number seven times.
- Return to the previous screen to find Developer options at the bottom. (On some devices, the Developer options screen might be located or named differently i.e. under System > Advanced > Developer options on the Pixel).
- From your WizyEMM console, enable the policy Allow debugging features on the profile of the device.
- From your device, open the Developer menu and turn USB debugging on.
- Once complete, connect a USB cable from your workstation to your device. If the device has never been connected to your workstation previously a pop-up will appear asking if it's OK to allow debugging. If the pop-up doesn’t appear, open Terminal and write adb devices to force the pop-up message on the device.
- On the device, check the box to always allow USB debugging.
Generate a bug report
- Open a command line terminal. On a Mac or Linux workstation, it's the Terminal app, on a Windows workstation, it is the Command prompt.
- Use the cd (change directory) command to reach the platform-tools folder where adb is located e.g. cd /Users/Username/Downloads/Tools.
- The command for generating the bug report depends on your OS.
- On Mac: adb bugreport
- On Windows: adb.exe bugreport
It may take a few minutes to generate the report. Once complete, it will be copied to the same directory that adb is located in.
- Open the .txt file in a text editor.
Note: When troubleshooting managed Google Play app update issues, you will need to add the additional adb command to increase the logcat capture:
adb logcat -G 32M; adb shell setprop persist.log.tag.dpcsupport VERBOSE; adb shell setprop persist.log.tag.Finsky VERBOSE; adb shell setprop persist.log.tag.Auth VERBOSE; adb shell setprop persist.log.tag.PackageManager VERBOSE; adb shell setprop persist.log.tag.JobScheduler VERBOSE
This is applicable when escalating a managed Google Play app update or install issue to another partner or Google. Make sure you have a read through the managed Google Play help pages for more details.
Read more here (Android documentation)