System app database

Package

com.android.partnerbrowsercustomizations.example

11device profiles
14observations
0user-facing hits
31 May 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.

3
signing certs
OEM-forked / varies
2
permissions
largest set observed
0.0 MB – 0.1 MB
APK size
28 – 33
target SDK
14 → 15
versions observed
3
device profiles
Declared permissions (2)

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
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 ↗

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.android.partnerbrowsercustomizations.example
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.android.partnerbrowsercustomizations.example
Re-enable
adb shell pm enable com.android.partnerbrowsercustomizations.example
Restore (re-install for the current user)
adb shell pm install-existing com.android.partnerbrowsercustomizations.example

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
Blackview VARG Android 11 - 1 1 Sep 2025
Crosscall Stellar-X5 Android 13 - 1 16 Jul 2025
Crosscall Stellar-X5 Android 14 - 3 1 Sep 2025
Crosscall Stellar-X5 Android 15 OEM Crosscall 1 9 Apr 2026
HMD Global Nokia 8.3 5G Android 10 OEM HMD Global 1 25 Dec 2025
HMD Global Nokia G22 Android 14 - 1 4 Dec 2025
OUKITEL WP100 TITAN Android 14 - 2 25 Jul 2025
OUKITEL WP100 TITAN Android 15 - 1 6 Dec 2025
OUKITEL WP28 E Android 14 OEM OUKITEL 1 31 May 2026
realme RMX3627 Android 12 - 1 20 Sep 2025
Smt_hk YUMPINGO_1 Android 9.0 - 1 9 Aug 2025

Known labels

Locale-aware display names seen in the wild.

LabelLocaleSeen
com.android.partnerbrowsercustomizations.example en-us 9
com.android.partnerbrowsercustomizations.example en-gb 3
com.android.partnerbrowsercustomizations.example en-US 1
com.android.partnerbrowsercustomizations.example en 1
com.android.partnerbrowsercustomizations.example en-GB 1
com.android.partnerbrowsercustomizations.example en-us-u-fw-sat 1
com.android.partnerbrowsercustomizations.example ru-ru 1