Short answer: on LineageOS 23.2 (Android 16), there's no cmd notification subcommand to dismiss a specific notification — the AOSP shell interface for the notification service only offers things like allow_listener, set_dnd, post, list, get, snooze, unsnooze, set_bubbles, etc., with no remove/dismiss/cancel verb (NotificationShellCmd.java). LineageOS ships this code essentially unchanged. So you can't do it with a plain one-liner as the shell user; here are the realistic no-swipe options:

1. Root: service call notification (most direct)

1. Find the notification's identity:
   bash

   Copy

   adb shell dumpsys notification --noredact | grep -B2 -A10 'NotificationRecord'

   Each notification key looks like 0|com.example.app|123|null|<channel>, i.e. userId|pkg|id|tag. Note the package, the numeric id (and tag, often null).
2. Then invoke the cancelNotificationWithTag binder method against the notification service as root (the caller must be the posting app or the system, hence root):
   bash

   Copy

   adb shell su -c "service call notification <N> s16 com.example.app s16 'null' i32 123 i32 0"

   The transaction number <N> differs per Android version/build, so read it from your device's INotificationManager.Stub (e.g. via the build's framework, or trial from the transaction list — it changes, so don't trust numbers posted online for other builds).

2. Root-free: use a notification-listener app and grant it via ADB

• Install an app that exposes dismiss through NotificationListenerService (Tasker + AutoNotification, or a small custom NotificationListenerService app calling cancelNotification(key)).
• Grant it listener access without the settings UI:
  bash

  Copy

  adb shell cmd notification allow_listener com.joaomgcd.tasker/com.joaomgcd.tasker.notification.TaskerListenerService

  The component name must be a full ComponentName; a bare package name fails with "Invalid listener" (Stack Overflow). Then trigger the dismiss from that app (e.g. Tasker's "Notification Cancel" action).

3. Crude root-free fallbacks (kill the notification at the source)

• adb shell am force-stop <package> — removes all notifications posted by that app (also kills the app/process).
• adb shell cmd notification set_dnd priority etc. — hides but doesn't dismiss.
• adb shell pm revoke <pkg> android.permission.POST_NOTIFICATIONS — blocks future ones.

Caveats: ongoing/foreground-service notifications can't be user-dismissed anyway; force-stop or root binder calls still remove them, but some system apps respawn the notification immediately.