System app database

Package

com.google.omadm.trigger

OemDmTrigger

13device profiles
48observations
0user-facing hits
2 Jun 2026last seen

Package intelligence

Observed signing, permission, version and size signals from contributing devices - descriptive of that sample, not a verdict. These come from the v2 Package Search sync, which not every device has contributed to yet, so for some packages this detail is partial or not present at all.

4
signing certs
OEM-forked / varies
9
permissions
largest set observed
0.2 MB – 0.3 MB
APK size
33 – 36
target SDK
1.0
versions observed
6
device profiles
Declared permissions (9)

Largest permission set observed for this package. Text is Android's own published description where one exists; platform permissions Android does not document show their granted protection level (in grey) instead; vendor or unknown constants show the name only.

PermissionDescription
MODIFY_PHONE_STATE Signature or privileged system permission.
READ_PHONE_STATE Allows the app to access the phone features of the device. This permission allows the app to determine the phone number and device IDs, whether a call is active, and the remote number connected by a call.
READ_PRIVILEGED_PHONE_STATE Signature or privileged system permission. docs ↗
RECEIVE_BOOT_COMPLETED Allows the app to have itself started as soon as the system has finished booting. This can make it take longer to start the phone and allow the app to slow down the overall phone by always running.
SCHEDULE_EXACT_ALARM This app can schedule work to happen at a desired time in the future. This also means that the app can run when you\u2019re not actively using the device.
com.android.permission.OMADM_CONFIGURE_DONE -
com.android.permission.WRITE_OMADM_SETTINGS -
com.google.omadm.trigger.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION -
com.qualcomm.permission.USE_QCRIL_MSG_TUNNEL -

Manage on devices

ADB commands for this package (the inverse of each is included so you can undo). Run from an authorised shell or wire the equivalent into your DPC. Verify on a test device first - this database doesn’t yet classify which packages are safe to change. --user 0 targets the current user; drop it (and use a privileged shell) to act device-wide.

Disable for the current user
adb shell pm disable-user --user 0 com.google.omadm.trigger
Remove for the current user - a per-user uninstall; the APK stays on /system, so Restore re-adds it (-k keeps app data)
adb shell pm uninstall -k --user 0 com.google.omadm.trigger
Re-enable
adb shell pm enable com.google.omadm.trigger
Restore (re-install for the current user)
adb shell pm install-existing com.google.omadm.trigger

Seen on

Each record is a device profile (make + model + Android version). Each unique handset that syncs against a matching profile will increase the observations of a package, thereby increasing confidence that a package is expected to be on a device.

OEMModelAndroidProvenanceObservationsLast seen
Google Pixel 10 Pro Android 16 Google 1 26 Mar 2026
Google Pixel 10 Pro Android 17 Google 1 1 Jun 2026
Google Pixel 6 Android 12 - 1 22 Jun 2025
Google Pixel 6 Android 16 - 1 13 Oct 2025
Google Pixel 6 Pro Android 15 - 9 23 Jun 2025
Google Pixel 7 Android 13 Google 1 19 Feb 2026
Google Pixel 7 Pro Android 16 Google 1 9 Mar 2026
Google Pixel 8 Android 16 - 4 1 Jun 2026
Google Pixel 8a Android 15 - 1 5 Oct 2025
Google Pixel 9 Pro XL Android 16 Google 21 29 Mar 2026
Google Pixel 9 Pro XL Android 17 Google 2 2 Jun 2026
Google Pixel 9a Android 15 - 1 15 Jun 2025
Google Pixel 9a Android 16 - 4 28 Nov 2025

Known labels

Locale-aware display names seen in the wild.

LabelLocaleSeen
OemDmTrigger en-us 30
OemDmTrigger nl-NL 12
OemDmTrigger en 11
OemDmTrigger en-gb 7
OemDmTrigger en-GB 4
OemDmTrigger 3
OemDmTrigger nl-nl 3
OemDmTrigger en-ca-u-fw-mon-mu-celsius 1
OemDmTrigger en-us-u-fw-mon-ms-ussystem-mu-fahrenhe 1
OemDmTrigger en-au 1
OemDmTrigger en-de 1