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

Groups > comp.mobile.android > #154240

Re: 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

Maria Sophia wrote:
> As always, please strive to add value so that everyone benefits every time
> you post anything to Usenet, where the goal is perfect interoperability.

UPDATE:
95% of "errors" in Samsung logcat are Samsung's own broken system services

When I dump out error messages on my Samsung phone from my desktop using:
    adb logcat *:E

95% of the "errors" come from just three Samsung system components. 
These are not app errors. They are not real system failures. 
They are Samsung's own services spamming the error log nonstop.

Here are the three main offenders:

1. MARsPolicyManager

Repeated error message:
Error occurred in setEnabledSetting()java.lang.SecurityException:
Cannot disable a protected package: com.oasisfeng.island.fdroid

MARs = "Mobile Active Resource Service."
It is Samsung's aggressive battery/app management system.
In my case, MARs is repeatedly trying to force-disable Island's F-Droid 
plugin, and Android keeps refusing because it is a protected package. 
Samsung keeps retrying every few seconds, so the error repeats endlessly.

2. Watchdog

Repeated error message:
E Watchdog: !@Sync: 3647 heap: 128 / 138 FD: 966

This is not an error.
It is a diagnostic heartbeat that Samsung incorrectly logs at E (error) 
instead of D (debug) or I (info). Samsung logs internal watchdog sync 
events as errors, which floods the log.

3. SDHMS (Samsung Device Health Monitoring Service)

Repeated error message:
SDHMS_UTIL_IO: e = /sys/class/power_supply/battery/chg_type:
open failed: ENOENT (No such file or directory)

This means SDHMS is trying to read a battery sysfs file that does not exist 
on my kernel. Instead of checking for existence first, Samsung just logs an 
error every time.

Why Samsung logcat is so noisy:
a. mislabels warnings as E (error)
b. logs internal housekeeping as E
c. retries failed operations endlessly
d. does not rate-limit their system logs

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.
-- 
Some people are so helpful, good, so detailed, so technically competent, 
that almost everything they write, becomes a great reference for others.

Back to comp.mobile.android | Previous | Next — Previous 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