When you deploy a SUNMI K2, Flex 3, or D3 PRO Kiosk as a self-ordering terminal, the last thing you want is customers tapping through the Android home screen instead of your ordering app. Kiosk mode locks the device to a single app – or a curated shortlist – so the experience stays focused, compliant, and frustration-free.
This guide covers the complete SUNMI kiosk mode setup in about 15-30 minutes: enabling it, setting your default startup app, removing navigation, device compatibility, QSR/fast casual compliance considerations, and how Rosper’s pre-configuration service can have your fleet ready to go right out of the box.
Why Kiosk Mode Matters for Self-Ordering Deployments
Running a SUNMI kiosk without lockdown is a liability in a customer-facing environment. Here’s why operators in QSR, fast casual, and retail lock their devices down:
- Customer experience consistency: Customers always land on your ordering app – no accidental taps into settings or other apps.
- PCI-DSS & payment security: Locking the device reduces the attack surface and limits what users can access during a payment session.
- Brand control: Your app is the only interface customers see, keeping brand presentation clean.
- Reduced support burden: No one can “accidentally” uninstall your app or change system settings.
- Regulatory compliance: Many municipalities and payment processors require kiosk lockdown for unattended public-facing terminals.
As one North American restaurant chain discovered during a PCI audit, an unlocked tablet in a self-ordering kiosk is a compliance red flag. Switching to kiosk mode resolved it within a day.
Supported SUNMI Devices
Kiosk mode is available across SUNMI’s current North American kiosk lineup:
All models run Android-based OS with SUNMI’s proprietary SUNMI Desk or direct MDM integration. The setup process is identical across models, with minor UI variations.
Prerequisites
Before you begin, make sure you have:
1. SUNMI device running latest firmware – Check Settings > About > System Update.
2. Your self-ordering app installed and verified – Install your APK or PWA via sideloading or your MDM (e.g., Esper, Intune, Wandera).
3. Admin/developer access to the device – You’ll need to toggle developer options and access kiosk settings.
4. MDM credentials (optional but recommended) – If you’re managing multiple devices, an MDM platform simplifies fleet-wide kiosk configuration.
5. The app’s package name – You’ll need this to set the default launcher. Find it in your app’s build settings or via an APK inspector.
Step-by-Step: Enable SUNMI Kiosk Mode
Step 1: Enable Developer Options
Before you can access kiosk settings, enable Android developer options:
1. Go to Settings on the SUNMI device.
2. Navigate to About Device (or About Tablet).
3. Tap Build Number 7 times consecutively. On some SUNMI firmware versions (especially K2 series), the tap count may be 5 or 10 – if 7 does not work, consult your firmware release notes.
4. You will see a toast message: “You are now a developer!”
5. Go back to Settings and open Developer Options.
6. Enable USB Debugging (required for some MDM tools and direct ADB kiosk setup).
Common pitfall: On some SUNMI firmware versions, the Build Number tap count differs. If 7 taps don’t work, try 5. If the device is already in a locked state, you may need to enter a admin PIN (check your device documentation or contact SUNMI support for the default credentials specific to your firmware version) to access developer settings.
Step 2: Install and Verify Your Ordering App
If your app is not yet on the device:
1. Transfer your APK to the device via USB, microSD, or your MDM.
2. On the SUNMI K2/K2 Mini, you can also use SUNMI App Store management if your app is listed.
3. Install the APK – you may need to enable Install from unknown sources in Settings > Security.
4. Open the app and verify it launches correctly and handles edge cases (no network, payment timeout, etc.) before locking it down.
Common pitfall: If your app crashes on launch and the device is already in kiosk mode, you may be locked out. Always test thoroughly before enabling full lockdown. Consider setting up a “fallback” accessible home button or a remote MDM rescue unlock before going live.
Step 3: Set the Default Startup App (Launcher)
This is the core of kiosk mode – telling the SUNMI which app to auto-launch on boot.
Method A: Through SUNMI System Settings (Native)
1. Go to Settings > Apps on the SUNMI device.
2. Tap the three-dot menu (top right) and select Default Apps.
3. Tap Home App.
4. Select your self-ordering app from the list.
5. Confirm – the device will now open your app instead of the standard Android launcher on startup.
Method B: Through Your MDM (Recommended for Fleets)
For multi-device deployments, use an MDM solution like Esper, Intune, Wandera, or SUNMI’s own device management platform:
1. Enroll the device in your MDM.
2. Create a Device Policy with the following settings:
– Kiosk Mode: Enabled
– Allowed Apps: Add only your ordering app (plus any essential system apps like your payment SDK).
– Package Name: Enter your app’s package name (e.g., com.yourcompany.selforder).
– Auto-launch on Boot: Enabled
– Disable Status Bar: Enabled (prevents swiping down to access settings)
– Disable Navigation: Enabled
3. Apply the policy to your device group.
4. The device will push the kiosk configuration on next sync – no per-device setup needed.
Common pitfall: Some MDM solutions like Esper block SUNMI system apps needed for Bluetooth pairing or printer functionality. If your self-ordering kiosk uses a paired Bluetooth card reader or SPRINT printer, make sure to whitelist the necessary SUNMI system packages in your MDM policy. Known packages to allow:
com.sunmi.bt,com.sunmi.print(varies by model – contact SUNMI support for the exact package names for your device).
Step 4: Remove Navigation and System UI
To fully lock down the device, you need to hide or disable the navigation bar, status bar, and any system gestures.
Disable Status Bar
1. Go to Settings > Display > Status Bar.
2. Disable notification icons and system icons as needed.
3. Alternatively, use your MDM to hide the status bar entirely.
Disable Recent Apps / Navigation Gestures
1. In Settings > Developer Options, look for Quick Settings Developer Tiles and disable them.
2. For deeper lockdown, use Screen Pinning (Settings > Security > Screen Pinning) – but note this is designed for temporary use, not permanent kiosk deployment.
3. For a permanent solution, use an MDM kiosk policy that suppresses the navigation bar and recent apps view entirely.
Common pitfall: Android’s gesture navigation (introduced in Android 10+) can still be triggered even when apps are set as home. The most reliable fix is an MDM-enforced screen overlay block combined with USB device policy restrictions. Also ensure Play Protect is configured to not prompt during kiosk operation.
Step 5: Configure Auto-Launch on Boot
The final step is ensuring your app relaunches automatically after a power outage, crash, or manual restart.
1. Go to Settings > Apps > [Your App Name].
2. Tap Battery and set to Unrestricted (prevents Android from killing the app to save power).
3. In Developer Options, ensure Don’t keep activities is OFF (this would kill your app on launch).
4. In your MDM policy, enable Auto-start on Boot. On SUNMI devices, this is often found in Settings > Battery > App Launch or set via the MDM’s device policy.
Common pitfall: After a firmware update, some SUNMI devices reset the default home app to the standard launcher. Always re-verify kiosk settings after updating firmware on a fleet device. Consider using an MDM to enforce kiosk settings as code – so updates don’t override your configuration.
Step 6: Verify the Lockdown
Once configured, test thoroughly:
- [ ] Device boots directly to your ordering app – no launcher visible
- [ ] Swiping down from the top does not reveal settings or notifications
- [ ] Pressing the home button does not return to Android launcher
- [ ] The recent apps button does not show other applications
- [ ] Your app restarts automatically after a forced close
- [ ] Power cycling the device (unplug and replug) returns to the ordering app
- [ ] Payment flow works end-to-end in kiosk mode
- [ ] Bluetooth peripherals (card reader, printer) connect and function
Common Pitfalls and How to Fix Them
Pitfall 1: App crashes and you’re locked out
Fix: Set up a factory reset shortcut or MDM rescue unlock before going live. Most SUNMI devices allow recovery by the device-specific reset method (varies by model – check SUNMI documentation for your device, as large-format kiosks like the K2 may use a physical reset pinhole rather than button combinations). Alternatively, use an MDM that supports remote device rescue.
Pitfall 2: Kiosk mode resets after firmware update
Fix: After any firmware update, re-apply your kiosk policy. For fleet management, your MDM should push kiosk settings automatically on enrollment – so re-enrollment after a reset will restore the correct configuration. Document your firmware update process.
Pitfall 3: Bluetooth peripheral disconnects in kiosk mode
in kiosk mode
Fix: Add the Bluetooth system app (com.sunmi.bt or equivalent) to your MDM’s allowed apps list. Some MDM solutions block all Bluetooth access by default, breaking SPRINT card readers and paired printers.
Pitfall 4: Touch screen calibration drift
Fix: The SUNMI K2 supports touchscreen calibration via Settings > Display > Touch Calibration. If tap accuracy degrades over time, recalibrate. In kiosk mode, a miscalibrated screen can cause ordering failures – set a monthly calibration reminder.
Pitfall 5: Device won’t enter kiosk mode
– “This app is not set as home”
Fix: Ensure your app has an Android intent filter for android.intent.action.MAIN with category android.intent.category.HOME. Your app must be “launchable” to be set as the home/default app. Check your AndroidManifest.xml – if the intent filter is missing, your app can’t be set as the default launcher.
Pitfall 6: Multi-app kiosk (customer + staff mode)
(customer + staff mode)
Fix: Some deployments need both a customer-facing kiosk app and a staff back-office app. Use MDM profiles or device owner mode to switch between kiosk profiles. Apps like Kiosk Lockdown Pro or Esper support multiple kiosk profiles per device.
QSR and Fast Casual Compliance: What You Need to Know
If you’re deploying SUNMI kiosks in a Quick Service Restaurant (QSR) or fast casual environment in North America, here are the regulatory considerations:
- PCI-DSS compliance: Unattended kiosk terminals handling card payments must be PCI-DSS compliant. Kiosk mode helps by limiting the device’s attack surface. Work with your payment processor (e.g., Chase, Stripe Terminal, Adyen) to ensure your terminal meets PCI DSS v4.0 requirements for kiosk environments.
- ADA accessibility: If your self-ordering kiosk is the primary ordering interface, it may need to meet ADA accessibility standards (WCAG 2.1 AA). Ensure your app supports screen readers and provides alternative ordering methods (e.g., staff-assisted ordering).
- FDA / health code: In food service, the kiosk screen must be cleanable and the device must meet local health codes for food-adjacent equipment. The SUNMI K2’s sealed design is built for this.
- Age-restricted sales: If selling alcohol or tobacco through the kiosk, ensure your app enforces age verification per local laws.
How Rosper’s Pre-Configuration Service Works
Managing a fleet of self-ordering kiosks across multiple locations is complex. Rosper Technology offers pre-configuration services for SUNMI K2, Flex 3, and D3 PRO Kiosk devices so they arrive ready to deploy:
- Kiosk mode pre-configured – Your app is set as the default launcher before the device ships.
- MDM enrollment – Devices can be pre-enrolled in your MDM (Esper, Intune, etc.) so they’re immediately manageable on first boot.
- App pre-loading – Your ordering app is installed and verified before delivery.
- Network pre-configuration – Wi-Fi credentials and VPN settings can be configured per location.
- Peripheral pairing – Card readers, printers, and scanners can be paired and tested before deployment.
- Burn-in testing – Every pre-configured device undergoes a 24-hour run test to verify stability.
Contact Rosper at rospertech.com or email [email protected] to discuss your fleet pre-configuration needs.
Summary: Key Takeaways
1. Kiosk mode is essential for any customer-facing self-ordering deployment – it locks the device to your app and prevents unauthorized access.
2. Use an MDM (Esper, Intune, or SUNMI’s platform) for fleet-wide kiosk management – manual per-device setup doesn’t scale.
3. Always test thoroughly before going live: verify auto-restart, payment flow, Bluetooth peripherals, and firmware update behavior.
4. Whitelist SUNMI system packages in your MDM for Bluetooth and printer access – blocking them is a common mistake.
5. Pre-configuration saves time – Rosper’s fleet pre-configuration service gets SUNMI kiosks ready to deploy out of the box.
6. Stay compliant – Kiosk mode supports PCI-DSS, ADA accessibility, and health code requirements for QSR and fast casual environments.
Ready to Deploy?
Rosper Technology is a SUNMI authorized North American distributor with U.S.-based inventory, fast shipping, and official SUNMI after-sales support. Every device comes with 3-year warranty coverage (3 generations, 3 years).
Explore Rosper’s SUNMI kiosk lineup, or request a quote for fleet pricing:
– SUNMI K2 – Full-size floor-standing self-ordering kiosk
– SUNMI Flex 3 – Flexible-mount compact kiosk
– SUNMI D3 PRO Kiosk – Integrated all-in-one kiosk
Need help with your kiosk mode setup or fleet configuration? Request a free consultation or Contact Rosper’s technical team for a free consultation.
*Last updated: April 2026. SUNMI device specifications and firmware features are subject to change. Always verify current compatibility with your specific firmware version before deployment.*
About the Author
Micah Morgan is a POS hardware specialist at Rosper, helping businesses across the US and Canada find the right SUNMI terminals for their needs. With years of experience in retail and hospitality technology, Micah writes about POS hardware selection, payment processing, and deployment logistics.
