How to capture a bug report and device logs

Enabling developer options allow users to perform various debugging tasks, including viewing Logs, taking bug reports, etc. It can be very useful in various scenarios and aids tremendously in troubleshooting issues.

1. Open Settings
   1. Either swipe up from the home screen to display the app drawer, and select settings, or
   2. Swipe down from the notification area and tap the settings icon present in the notification panel.
2. Tap About device
3. Swipe down to Build number
4. Tap 7 times on Build number
5. Developer mode will be enabled
6. Enabling USB debugging
7. Prerequisites – PC with ADB configured

1. Tap back into Settings
2. Tap System
3. Tap Advanced
4. Tap developer options
5. Swipe to USB debugging, and toggle it on

It'll now be possible to plug your device into a computer and undertake various debugging activities. When first plugging in, the device will prompt for authorisation. Allow this.

With developer options enabled:

1. Open Settings
   1. Either swipe up from the home screen to display the app drawer, and select settings, or
   2. Swipe down from the notification area and tap the settings icon present in the notification panel.
2. Tap System
3. Tap Advanced
4. Tap Developer options
5. Swipe until bug report appears in view, and tap Take a bug report

The bug report will become available via a notification within a few moments. From there, share it to a preferred application or download it to a connected computer.

Alternatively, and as a preferred option, from the command line of a plugged in device run adb bugreport E:\Reports\MyBugReports (choose an appropriate location on disk) to save a bug report directly to your computer without interacting with the device directly.

More details, via Google.

With developer options enabled:

1. Connect the device to PC via USB
2. Run the command adb logcat > path/filename.txt
   1. NB: Change path/filename.txt to a legitimate path on your computer
3. Replicate the issue(s), one per logcat command issuance and note down the timestamp to the second
   1. If the timestamp isn't provided to the second (ie 12:13:34) with the logcat, it may take a considerable amount of time to locate the relevant log lines.
4. Hit Ctrl + C to stop logging to file
   1. That'll be CMD + C on Mac
5. Fetch the log file from the saved location, and send it to whomever wants too see it.