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


Groups > comp.mobile.android > #154242

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

From Hank Rogers <Hank@nospam.invalid>
Newsgroups comp.mobile.android, alt.comp.os.windows-10, alt.os.linux
Subject Re: PSA: How to capture Android crash logs or app errors & warnings on your desktop using adb & logcat
Date 2026-06-19 17:09 -0500
Organization A noiseless patient Spider
Message-ID <1114emk$3kp5m$1@dont-email.me> (permalink)
References <110tdtc$2qt$1@nnrp.usenet.blueworldhosting.com> <11146mj$137c$1@nnrp.usenet.blueworldhosting.com> <111491q$2v1a$1@nnrp.usenet.blueworldhosting.com>

Cross-posted to 3 groups.

Show all headers | View raw


Maria Sophia wrote on 6/19/2026 3:32 PM:
> Maria Sophia wrote:
>> This is why Samsung devices produce massive logcat noise compared to Pixel,
>> OnePlus, Motorola, etc., apparently.
>>
>> How to filter out Samsung's spam on Windows:
>>   adb logcat *:E | findstr /V /C:"MARsPolicyManager" /C:"Watchdog" /C:"SDHMS"
>>
>> This removes 95% of Samsung's bogus "errors" and leaves actual useful logs.
> 
> ADDITION
> 
> Below are specific Windows & Linux commands (findstr vs grep) to help
> others capture Android error logs and warnings and information output.
> 
> This removes the flood of Samsung garbage in the logcat log:
>   adb logcat *:E | findstr /V /C:"MARsPolicyManager" /C:"Watchdog" /C:"SDHMS"
>   adb logcat *:E | grep -vE "MARsPolicyManager|Watchdog|SDHMS"
> 
> This shows only real app crashes:
>   adb logcat -v time | findstr /C:"FATAL EXCEPTION" /C:"AndroidRuntime"
>   adb logcat -v time | grep -E "FATAL EXCEPTION|AndroidRuntime"
> 
> This shows only battery or power errors:
>   adb logcat | findstr /I /C:"battery" /C:"thermal" /C:"power" /C:"charger" /C:"voltage" /C:"current"
>   adb logcat | grep -iE "battery|thermal|power|charger|voltage|current"
> 
> This shows only network errors:
>   adb logcat *:E | findstr /I /C:"Wifi" /C:"DNS" /C:"Network" /C:"Socket"
>   adb logcat *:E | grep -iE "wifi|dns|network|socket"
> 
> This shows network warnings and info also:
>   adb logcat | findstr /I /C:"Wifi" /C:"wpa" /C:"DNS" /C:"Network" /C:"Connectivity" /C:"Socket" /C:"EHOSTUNREACH" /C:"ETIMEDOUT"
>   adb logcat | grep -iE "wifi|wpa|dns|network|connectivity|socket|EHOSTUNREACH|ETIMEDOUT"
> 
> This shows ANR (App Not Responding) events:
>   adb logcat | findstr /I /C:"ANR in"
>   adb logcat | grep -i "ANR in"
> 
> This shows low-memory and OOM events:
>   adb logcat | findstr /I /C:"lowmemorykiller" /C:"OutOfMemory" /C:"oom_adj"
>   adb logcat | grep -iE "lowmemorykiller|OutOfMemory|oom_adj"
> 
> This shows storage or filesystem errors:
>   adb logcat | findstr /I /C:"fsck" /C:"ext4" /C:"f2fs" /C:"I/O error" /C:"write failed"
>   adb logcat | grep -iE "fsck|ext4|f2fs|I/O error|write failed"
> 
> This shows camera errors:
>   adb logcat | findstr /I /C:"CameraService" /C:"CameraProvider" /C:"E/Camera"
>   adb logcat | grep -iE "CameraService|CameraProvider|E/Camera"
> 
> This shows audio errors:
>   adb logcat | findstr /I /C:"AudioFlinger" /C:"AudioTrack" /C:"AudioRecord" /C:"E/Audio"
>   adb logcat | grep -iE "AudioFlinger|AudioTrack|AudioRecord|E/Audio"
> 
> This shows Bluetooth errors:
>   adb logcat | findstr /I /C:"Bluetooth" /C:"bt_stack" /C:"btif" /C:"hci"
>   adb logcat | grep -iE "Bluetooth|bt_stack|btif|hci"
> 
> This shows GPS or location errors:
>   adb logcat | findstr /I /C:"LocationManager" /C:"Gnss" /C:"gps" /C:"E/Gps"
>   adb logcat | grep -iE "LocationManager|Gnss|gps|E/Gps"
> 
> This shows app install or update failures:
>   adb logcat | findstr /I /C:"PackageManager" /C:"INSTALL_FAILED" /C:"DexOpt" /C:"dex2oat"
>   adb logcat | grep -iE "PackageManager|INSTALL_FAILED|DexOpt|dex2oat"
> 
> This shows SELinux denials:
>   adb logcat | findstr /I /C:"avc: denied"
>   adb logcat | grep -i "avc: denied"
> 
> This shows system_server crashes:
>   adb logcat | findstr /I /C:"system_server" /C:"crash"
>   adb logcat | grep -iE "system_server.*crash"
> 
> This shows wakelock issues:
>   adb logcat | findstr /I /C:"WakeLock" /C:"wakelock"
>   adb logcat | grep -iE "WakeLock|wakelock"
> 
> This shows thermal throttling:
>   adb logcat | findstr /I /C:"thermal" /C:"throttle" /C:"overheat"
>   adb logcat | grep -iE "thermal|throttle|overheat"
> 
> I'll write up a linux/windows script to make all this easy peasy.
> 

Thanks Mary.  Will you also post it to a github page so everyone 
benefits from it's value?

I really appreciate your efforts.

Also, do you have a web page where we can submit other problems which 
you might investigate and eventually provide needed solutions?

I realize how busy you are, but many people get no value from your 
research because it's distribution is so limited.

I really think you can do better, and I hope you will.

Back to comp.mobile.android | Previous | NextPrevious in thread | 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