What is Android DPC (Device Policy Controller)?

Android DPC is the official Google enterprise API for Android device management. It allows an app to be registered as Device Owner during device setup, giving it OS-level authority over device policies. DevicePolicyManager APIs provide controls over lock, wipe, password requirements, network restrictions, app management, and more — all enforced at the Android framework level, not the application layer.

What is Android accessibility service and how is it used for EMI lock?

Android accessibility service is an API designed to help users with disabilities by reading screen content, injecting input events, and overlaying views. Some EMI lock apps repurpose it to display a lock overlay screen when the customer tries to use the phone while overdue. The problem: accessibility service runs as a background service that the user can disable at any time from Settings → Accessibility.

How do you bypass an EMI lock built on accessibility service?

Go to Settings → Accessibility → find the EMI app in the list → toggle it off. The lock screen disappears immediately. No retailer is notified. This takes about 20–30 seconds and works on every Android version. Some users also bypass by starting the phone in Safe Mode, which disables all third-party services including accessibility services.

Can Android DPC be bypassed like accessibility service?

No. Android DPC registered as Device Owner has no user-accessible off switch. The Device Owner app does not appear in the standard Settings → Apps list with an Uninstall button. Disabling permissions, clearing data, or factory resetting the device do not remove the DPC policy. Factory reset causes re-enrollment on first boot. The only way to remove DPC is through the retailer's panel using Device Owner credentials.

Technical Comparison — Android DPC vs Accessibility Service

DPC vs Accessibility Service for EMI Lock — What Every Retailer Should Understand Before Choosing

Not all EMI lock apps are built the same way. Some use Android's accessibility service API — a framework designed for screen readers, repurposed as a lock overlay. Others, like EMI Locker, use Google's dedicated enterprise Android DPC (Device Policy Controller). The technical choice determines whether your enforcement can be bypassed by a customer in 30 seconds, or whether it is genuinely non-removable.

ABOUT ANDROID DPC FULL APP COMPARISON

DPC — OS Level, Not App Layer Accessibility — Disable in Settings in 30 Seconds DPC Survives Factory Reset Accessibility Cannot — Wiped on Reset

How each approach works technically

Android DPC — Device Owner Mode

During device setup (first boot), the retailer scans a QR code or uses NFC to register the EMI Locker app as Device Owner. This triggers the Android OS to grant the DevicePolicyManager API the highest privilege level available to a third-party app. The Device Owner is registered in the Android OS database — not in a user app list. From this moment, the DPC can call APIs such as lockNow(), addUserRestriction(), setKeyguardDisabledFeatures(), and wipeData() with no further user permission. These APIs are part of the Android platform and cannot be blocked by the user.

Accessibility Service — Background Service

An accessibility service runs as a background service registered under android.accessibilityservice.AccessibilityService. It monitors screen events and can draw an overlay when the lock condition is met. To work, it requires the user to manually enable it under Settings → Accessibility. It runs as a user-space background service — meaning it can be disabled from the same Settings menu, killed by battery optimisation, removed by Play Protect, or wiped in a factory reset. On Android 12+, Google has progressively restricted non-standard accessibility service use, causing breakage on newer devices.

Bypass vectors — where accessibility fails

Bypass 1: Settings → Accessibility

30 seconds. Open Settings, search "Accessibility", find the EMI app, toggle off. Lock screen removed. No alert sent.

Bypass 2: Safe Mode Boot

Long-press power button → Reboot to Safe Mode. All third-party services (including accessibility) are disabled in Safe Mode. Device works normally. EMI app does not run.

Bypass 3: Factory Reset

Factory reset from Settings or recovery mode removes the app completely. Device starts fresh. Nothing persists. DPC is immune to this — accessibility is not.

Bypass 4: OEM Background Kill

Xiaomi MIUI, Samsung One UI, OPPO ColorOS all auto-kill background services aggressively to save battery. Accessibility services are background services and get killed regularly — creating gaps in enforcement that customers can exploit.

Bypass 5: Google Play Protect Flag

Play Protect may flag accessibility service being used for non-accessibility purposes as a potential threat. Some OEM security scanners quarantine or block the app automatically. DPC uses official Google APIs — Play Protect certified.

Bypass 6: Android 12+ Restrictions

From Android 12, Google has tightened restrictions on non-standard accessibility service usage. Apps using accessibility for non-assistive purposes face increased risk of Play Store removal and OEM blocking with each new Android release.

DPC vs Accessibility Service — FAQ

Android DPC is Google's official enterprise API for device management. It registers the managing app as Device Owner at the OS level — giving it authority over device policies via DevicePolicyManager APIs that cannot be overridden by users from Settings.

Settings → Accessibility → find the EMI app → toggle off. Done in 20–30 seconds. No alert sent to the retailer. Alternative bypasses: Safe Mode boot, factory reset, or waiting for the OEM battery optimiser to kill the service.

No. DPC Device Owner has no user-accessible off switch. It does not appear in Settings → Apps with an Uninstall button. Factory reset causes re-enrollment. The only removal path requires the retailer's panel credentials. This is the technical foundation that makes EMI Locker non-bypassable.

DPC enrollment must happen during device setup (first boot). It cannot be retrofitted to a device the customer already has. Accessibility service can be added to any already-running device. The retrofit convenience of accessibility is why it exists in EMI apps, but it comes at the cost of bypassability. EMI Locker requires DPC enrollment — this is a deliberate design choice for security.

EMI enforcement that cannot be disabled from Settings

See how DPC-based enforcement differs from accessibility-service workarounds. Start from ₹60/key with no monthly fees.

Start Free Learn About DPC