Android平板商用展示APP锁定技术问询：禁止退出与系统交互

Hey there! Let's tackle your two questions about locking down an Android tablet for commercial store displays—this is a super common use case, so I’ve got practical, actionable solutions for you.

Absolutely, and the most reliable way to do this is using Android’s built-in Kiosk Mode (also called Single App Mode). Here’s how it works:

• Native Enterprise Management: Use Android’s Device Policy Manager (DPM) framework to set up a managed device. You can configure it to restrict access to only your display app, disable the status bar, navigation keys (Home/Recent/Back), and block all access to system settings. For branded tablets (like Samsung, Lenovo), they often have their own commercial kiosk tools (e.g., Samsung Knox Kiosk) that simplify this setup without heavy coding.
• Custom App Integration: If you’re building the app yourself, you can request the DEVICE_ADMIN permission and use the DevicePolicyManager API to enforce restrictions. For hiding navigation keys, you can use immersive sticky mode on Android 4.0+ with this code snippet:

  getWindow().getDecorView().setSystemUiVisibility(
      View.SYSTEM_UI_FLAG_HIDE_NAVIGATION
      | View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY
      | View.SYSTEM_UI_FLAG_FULLSCREEN
  );
  

  Note: On newer Android versions (10+), directly intercepting Home/Recent keys is restricted, so relying on native Kiosk Mode is far more stable than custom workarounds.

This ties directly into Kiosk Mode, but we’ll add extra layers to ensure persistence and secure admin access:

• Enable Single App Kiosk Mode: This is the foundation. Once enabled, the device will boot directly into your app, and users won’t be able to switch to YouTube or any other app, nor close it via standard methods (like Recent apps).
• Ensure Auto-Startup: While Kiosk Mode usually handles boot-time launch, add a BOOT_COMPLETED broadcast receiver (with the RECEIVE_BOOT_COMPLETED permission) to trigger your app if the system restarts. For Android 8.0+, you’ll need to use WorkManager instead of a static receiver to comply with background restrictions.
• Prevent System Killing: Run your app as a Foreground Service—this tells Android the app is critical, so it won’t be terminated to free up resources. You’ll need to show a persistent notification (you can make it non-interactive or hide it on some devices) to comply with foreground service rules.
• Secure Admin Exit: Add a hidden trigger (like tapping a specific area of the screen 5 times, or swiping a secret pattern) to open an admin login screen. After verifying a secure password (store it encrypted using Android Keystore, don’t hardcode!), use the DevicePolicyManager to exit Kiosk Mode, allowing you to close the app or switch to other tools.

Bonus Tips for Commercial Use #

• Test across Android versions: Kiosk Mode behavior varies slightly between Android 5.0, 10, 13, etc.—make sure your solution works on the tablets you’re deploying.
• Disable auto-updates: Turn off system and app auto-updates to avoid unexpected changes breaking your kiosk setup.
• Physical security: Consider using a tablet enclosure that blocks physical buttons (like the power button) if needed, to prevent users from restarting the device.

内容的提问来源于stack exchange，提问作者Alexandru Sandu