Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.mobile.android > #154198

PSA: How to capture Android crash logs or app errors & warnings on your desktop using adb & logcat

Cross-posted to 3 groups.

Show all headers | View raw

PSA: How to capture Android crash logs or app errors & warnings 
     on your desktop using adb & logcat

Note: In my setup, none of the work is done on the phone. Everything,
including reproducing the issue on the phone, is done on the desktop.

When an Android package throws an error, warning, or outright crashes, 
what steps do you use to record what happened for debugging purposes? 

Here's my first-pass attempt at coming up with a test sequence.
I'll use Aurora Store as the package for my example testcase.

We will use logcat, which records system-wide logs including app output, 
stack traces and crash reports.
  <developer.android.com/tools/logcat>

The following sequence is an initial attempt to document the process. 
Corrections and additions are welcome.

When an Android package throws an error, warning, or outright crashes, 
what steps do you use to record what happened for debugging purposes? 

Here's my first-pass attempt at coming up with a test sequence.
I'll use Aurora Store as the package for my example testcase.

We will use logcat, which records system-wide logs including app output, 
stack traces and crash reports.
  <developer.android.com/tools/logcat>

The following sequence is an initial attempt to document the process. 
Corrections and additions are welcome.

1. Clear existing logs to ensure only events from the test are captured.
    adb logcat -c

2. Start a filtered live log view.
   Select any preferred filtering method.
    a. Filter by package.
        adb logcat | grep -i com.aurora.store  (for Linux)
        adb logcat | findstr -i com.aurora.store (for Windows)
    b. Filter only errors.
        adb logcat *:E
    c. Filter warnings and errors.
        adb logcat *:W
    d. Filter with timestamps.
        adb logcat -v time

3. Manually reproduce the issue on the device.
    Note that I use screen copy to manipulate the phone on the desktop.

4. If the package crashes, check the crash buffer.
    adb logcat -b crash

5. Save logs for later analysis or sharing.
   Save the full session to a file.
    adb logcat -d > aurora_log.txt
   Save only errors.
    adb logcat *:E -d > aurora_errors.txt

6. Optionally capture only the target application's PID.
    adb shell pidof com.aurora.store
    adb logcat --pid <PID>

Additional options:

1. Use logcat buffers separately.
   adb logcat -b main
   adb logcat -b system
   adb logcat -b events
   adb logcat -b crash

2. Capture a full bug report for deeper debugging.
   adb bugreport bugreport.zip

Some applications include internal debug toggles that produce richer logs.
Aurora does not (AFAIK).

As always, please strive to add value so that everyone benefits every time
you post anything to Usenet, where the goal is perfect interoperability.
-- 
All of us are volunteers who pitch in together to kindly help each other.

Back to comp.mobile.android | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

PSA: How to capture Android crash logs or app errors & warnings on your desktop using adb & logcat Maria Sophia <mariasophia@comprehension.com> - 2026-06-17 01:13 -0500
  Re: PSA: How to capture Android crash logs or app errors & warnings on your desktop using adb & logcat Maria Sophia <mariasophia@comprehension.com> - 2026-06-19 14:52 -0500
    Re: PSA: How to capture Android crash logs or app errors & warnings on your desktop using adb & logcat Maria Sophia <mariasophia@comprehension.com> - 2026-06-19 15:32 -0500
      Re: PSA: How to capture Android crash logs or app errors & warnings on your desktop using adb & logcat Hank Rogers <Hank@nospam.invalid> - 2026-06-19 17:09 -0500
        Re: PSA: How to capture Android crash logs or app errors & warnings on your desktop using adb & logcat Maria Sophia <mariasophia@comprehension.com> - 2026-06-27 03:57 -0400

csiph-web