PSA: How to ID from the desktop what just made Android beep (using adb logcat)
From
Maria Sophia@mariasophia@comprehension.com to
comp.mobile.android on Wed Jun 17 14:53:46 2026
From Newsgroup: comp.mobile.android
PSA:
How to ID from the desktop what just made Android beep (using adb logcat)
For whatever reason on my highly-de-googled USA-spec non-rootable Samsung,
I can't seem to figure out what made the phone beep in every case.
My phone is usually in the room somewhere, or maybe in my pocket, or maybe
in another room, as I manipulate Android on my desktop monitor at home.
I have notification-history and notification-log shortcuts in my Android homescreen dock shortcuts folder, but they never seem to show what I need.
Luckily, every notification event is logged by Android.
So we can use adb logcat to see exactly which app posted the notification, which channel it used and whether it played a sound.
Requirements
a. phone must have Developer Options enabled.
b. USB debugging or Wi Fi debugging must be enabled.
c. The desktop computer must have adb installed.
Connect to the phone
a. If using Wi Fi debugging:
adb connect PHONE_IP:5555
b. If using USB:
adb devices
c. Confirm the device is listed.
Here is my first pass at defining the steps to find out what just beeped. Please correct where I err and add value where I omit.
1. Clear the log (optional but recommended)
adb logcat -c
2. Start a filtered log session that shows only notification events
adb logcat -s NotificationService
3. When the phone makes a sound, look at the most recent lines.
You may see entries like:
NotificationService: enqueueNotification pkg=com.example.app ...
NotificationService: sound=...
NotificationService: channel=...
4. Identify the app
The pkg field tells us exactly which app caused the beep.
Alternative filters if we need more detail
a. Show all notification related logs
adb logcat | grep -i notif
b. Show when the system played a sound
adb logcat -s AudioService
c. Show SystemUI handling of notifications
adb logcat -s SystemUI
d. Save the log to a file
adb logcat -d > notif_log.txt
Note this method works even if the notification was dismissed instantly
or even if the notification has never appeared in the notification shade.
--
Each Usenet post should strive to add useful value that wasn't there prior.
--- Synchronet 3.22a-Linux NewsLink 1.2