Skip to main content
Level 1.5: Cupcake
August 4, 2025
Question

Device Owner Provisioning

  • August 4, 2025
  • 5 replies
  • 2 views

My company is building a startup that utilizes Android boxes, and we want to have a way to provision applications to all of the devices and control their configurations remotely. I had a brief look at "device owner provisioning," and it seems like the right thing.
 
Do we have to use an EMM, or can we use the management API by ourselves? 
Is there a way to get a technical support on call to discuss the best path for us?
 
Main requirements:
- The user does not have to log into the Play Store on the device to receive application updates.
- The only application that can be used on the device is the one we provision (Kiosk mode).
- Preferably, restrict device settings so only specific settings are visible to the user.

- Management of thousands of devices.
 
Constraints:
- Devices do not have NFC or a camera. 

5 replies

Level 2.2: Froyo
August 5, 2025

Hi, the best resource for your need I think is in the parther portal here:

Android Enterprise Partner Portal

Emilie_B
Community Manager
August 6, 2025

Thank you ​for your assistance, @Rakib  😊

Emilie_B
Community Manager
August 6, 2025

Hi @AleksaBajat and welcome to the Android Enterprise Customer Community! 

 

Would you be able to share some make models of the Android boxes you’re mentioning and would be deploying? 

 

I’ve checked with our team and they said that the OS of Android TV boxes does not have the OS with GMS services and built-in features that allow wider management capabilities. So, a TV OS has some limitations. 

If these devices should be compatible, you may be able to enrol them using web enrolment or DPC Identifier Enrolment (afw#setup) but, management policies are ultimately up to the devices and EMM (and whether they would be supported or not). 

 

Here are examples of devices that are recommended and supported (Android Enterprise Recommended devices). 

 

I hope this is helpful - do let us know how you get on and if we can help further! 

 

Thanks and chat soon, 

Emilie

Level 1.5: Cupcake
August 7, 2025

Thank you very much on the answer Emilie!

Is creating our own DPC and setting the device ownership through ADB something we can do without having access to Android Enterprise?

Best regards,

Aleksa

Emilie_B
Community Manager
August 8, 2025

No worries @AleksaBajat 

 

If by DPC you mean “Device Policy Controller” app, this is the intermediary between an EMM and an Android device so that involves Android Enterprise. 

 

The following are the AE provisioning methods - you can’t use the ADB alone to complete a device provisioning/enrolment: https://developers.google.com/android/work/requirements#1.-device-provisioning_1

 

While this link refers to the management types, you will need an EMM solution in order to manage devices: https://developers.google.com/android/work/overview#android_devices_management_use_cases

 

Here is some more information on developing your own solution: https://developers.google.com/android/work/dev-options 

 

As outlined in that document, the methodology will require Android Enterprise technology and methodologies https://developers.google.com/android/work/dev-options#set_up_devices_for_management 

 

I hope this is helpful!

Thanks,

Emilie 

Level 1.6: Donut
August 6, 2025

Welcome to the community AleksaBajat :). I've proposed a similar use-case previously to a customer (who was looking to make TV screens 'remotely manageable' via android and an EMM).

 

If you want to have a quick call to run through the brief - I can help. Can you message me your contact details / linkedin details please?

Level 1.5: Cupcake
August 7, 2025

Hey Ben,

For sure! Let's get in touch https://www.linkedin.com/in/aleksa-bajat-059011216/.

Level 2.0: Eclair
August 6, 2025

You don’t have to use an EMM — you can use Google's free Android Management API (AMAPI) to build your own EMM solution. "https://developers.google.com/android/management"

 

Since your Android boxes do not have NFC or built-in cameras, consider the following provisioning options:

 

1) Zero-Touch Enrollment (ZTE)

  • Best option for large-scale, hands-off deployment
  • Requires Android 9+ and support from the device manufacturer
  • Devices must be registered (by serial number or IMEI) via an authorized reseller
  • Configuration is applied automatically on first boot or after factory reset
    Recommended if your hardware vendor supports it

2) Manual ADB Provisioning

  • Suitable for development, testing, or small-batch provisioning
  • Requires connecting the device to a computer via USB
  • Set the Device Owner manually using ADB: "adb shell dpm set-device-owner com.example.yourmdm/.YourReceiver"
  • Does not require camera or NFC, but does require physical access

3) QR Code Enrollment Using External Camera or Scanner

 

  • Use a wired USB camera or Bluetooth barcode/QR scanner attached to the Android box
  • This allows scanning a QR code to trigger provisioning, even without a built-in camera
    Requires Android 9+ and the device must be in a factory-reset state
  • Initiate QR enrollment by tapping 6 times on the welcome screen or through ADB: " shell am start -a android.app.action.PROVISION_MANAGED_DEVICE"
  • Useful when Zero-Touch is unavailable but QR enrollment is preferred

Well-known enterprise hardware vendors often provide their own provisioning or staging tools to simplify device enrollment:

  • Zebra devices use StageNow, which supports barcode or NFC-based staging.
  • Honeywell offers the Honeywell Enterprise Provisioner for device setup and configuration.
  • Samsung devices support Knox Mobile Enrollment (KME) for bulk provisioning.
  • Datalogic provides Datalogic StageNow, which is based on Zebra’s tool.
  • Panasonic devices often integrate with Zero-Touch Enrollment or use custom scripts via USB or QR code.


Level: 4.1: Jelly bean
August 6, 2025

Howdy,

 

Do your boxes have GMS - Google services? If so you can use any open market MDM solution to enrol and manage devices.

 

If you don't have GMS, the Android Management API won't be supported, but you can either use an MDM on the market supporting AOSP (no Google services), or build yourself a DPC, device policy controller.

 

Capabilities you're after are supported by many platforms, there's nothing complex there.

 

Note the suggestion to just use the Android management API directly (if you have GMS) goes against permissible usage unless you also plan to sell your platform to the ecosystem. 

Level 2.0: Eclair
August 6, 2025

Jason, you are correct on the AMAPI and it goes against the googles policy if you are not planning to sell to the ecosystem .

 

If you're working without GMS, I looked into some open-source options that support AOSP:

  • Headwind MDM – It’s open-source, supports AOSP, and has features like kiosk mode and remote app management. Pretty straightforward to set up.
    GitHub: https://github.com/headwind-mdm/headwind-mdm
  • Flyve MDM – Another open-source option built on GLPI. It’s a bit more complex but has good features for device management. GitHub: https://github.com/flyve-mdm