Capture a bug report and video recording for Android device

To help the Support team resolve issues with the Messages app on Android devices, generate a bug report and a video recording.

To get a bug report directly from your Android device, follow these steps.

Enable developer options and USB debugging

For information about developer options used to configure system behaviors that help you profile and debug your app performance, see Configure on-device developer options.

Enable verbose logging for Messages

Rooted device

On a rooted device, use the following commands to enable verbose logging:

adb shell setprop log.tag.Bugle VERBOSE
adb shell setprop log.tag.BugleDataModel VERBOSE
adb shell setprop log.tag.RcsProvisioning VERBOSE
adb shell setprop log.tag.CarrierServices VERBOSE
adb shell setprop log.tag.BugleAction VERBOSE:
adb shell setprop log.tag.BugleRcsEngine VERBOSE;
adb shell setprop log.tag.BugleTransport VERBOSE;
adb shell setprop log.tag.BugleRcsProvisioning VERBOSE;
adb shell setprop log.tag.RcsClientLib VERBOSE;
adb shell setprop log.tag.BugleRcs VERBOSE;

Enable verbose logging only for the testing devices. The following log includes personally identifiable information (PII).

adb shell su root am broadcast -a com.google.gservices.intent.action.GSERVICES_OVERRIDE -e carrier_services_log_level VERBOSE
adb shell su root am broadcast -a com.google.gservices.intent.action.GSERVICES_OVERRIDE -e carrier_services_enable_debug_mode true
adb shell su root am broadcast -a com.google.gservices.intent.action.GSERVICES_OVERRIDE -e bugle_rcs_allow_overrides true
adb shell su root am broadcast -a com.google.gservices.intent.action.GSERVICES_OVERRIDE -e bugle_debugging true
adb shell su root am broadcast -a com.google.gservices.intent.action.GSERVICES_OVERRIDE -e carrier_services_enable_sensitive_logging true

Unrooted device

On an unrooted device, use the following command to enable verbose logging:

adb shell am broadcast -a 'com.google.android.gms.phenotype.FLAG_OVERRIDE' --es package "com.google.android.apps.messaging#com.google.android.apps.messaging" --es user "\*" --esa flags "bugle_phenotype__enable_verbose_bug_reports" --esa values "true" --esa types "boolean" com.google.android.gms

Reproduce your issue

  1. In Settings > System > Developer options > Logger buffer sizes, maximize the logger buffer size. Use the largest size for the device (for example, 16 MB on a high-end device).
  2. Force stop the Messages app.
  3. If the bug relates to Rich Communication Services (RCS) provisioning, complete the following steps:
    1. Enable Airplane mode.
    2. Clear the Messages and Carrier Services storage from Settings.
    3. Disable Airplane mode.
    4. Enable RCS chat in Settings.
    5. Wait at least five minutes before starting the bug report.
  4. For each new bug, clear the logcat messages:

    adb logcat -c
    
  5. Start the video recording:

    • Record only the reported bug.
    • Keep video recordings as short as possible. For example, if the bug occurs after making a single call, record only that section of the call.
    • Don't record repetitive steps.
  6. Start the Messages app and reproduce the bug.

  7. Stop the video recording.

Collect the bug report

  1. In the report, capture the following:
    1. The timestamp when the bug occurs.
    2. The steps that trigger the bug.
    3. The bug itself (for example, error message).
    4. A recording of the screen while reproducing the bug.
  2. In Developer options, tap Take bug report.

  3. Select a bug report type and tap Report. A notification indicates when the bug report is ready.

  4. Attach the bug report in a submitted bug.

If the bug relates to one or more messages (for example, messages couldn't be sent), provide the Message IDs of the affected messages.

  1. Enable the Messages debug menu:
    1. Open Messages.
    2. Tap the search bar.
    3. Search for *xyzzy*. The Debug Utils menu opens or a toast appears with the message Debug menu option enabled.
  2. Touch & hold the message.
  3. Tap Menu, then tap View Details.