device-owner

I've got an app that registers itself as the default launcher and pins itself automatically when started. This all works fine when installing the app. It pins itself and only the back button is visible. The problem is that when the device first boots up, it does not pin properly. I see a series of toasts "Screen pinned" and "Screen unpinned" multiple times. The "Home" and "Recent Tasks" buttons are still visible as well. -- Running "adb shell dumpsys activity activities" - the last lines indicate that it is not pinned: mLockTaskModeState=NONE mLockTaskPackages (userId:packages)= 0:[com.example

I am able to make my app, the device owner app through NFC as mentioned here . Now I want to update my app over the air, but I couldn't find a method without rooting . Google is providing many options for enterprises to develop apps as mentioned here , but nowhere providing a way to update the application through OTA. Looking for a solution. This is just pure speculation as I've never tried to use the package installer API myself: You could try to set an installer package for your device owner app (using PackageManager.setInstallerPackageName() ). This installer package would need to be a

'm trying to set up Device Owner using the sample apps downloadable from developer.android.com https://developer.android.com/samples/NfcProvisioning/index.html https://developer.android.com/samples/DeviceOwner/index.html But when I NFC tap the devices in the logcat for the device I am trying to set the Device Owner for I see this: /? E/ManagedProvisioning﹕ Device already provisioned. However I am doing a factory reset just before attempting the provisioning, so how can I get the device into an unprovisioned state? I've seen different behaviours depending on models. Usually removing all

I am developing an app that will work in 2 different Android environments (consumer & corporate markets). Lets say it is a texting app with a dozen configuration parameters to manage. The first environment is a standard Android device that has no Android Enterprise (AfW) features enabled. So there is no EMM (MDM) to supply an Android Agent/Client app to be a device/profile owner implementing a Managed Configurations Provider. The second environment is within a corporation. An EMM (MDM) is used to manage all their corporate owned devices. The EMM is either a device or profile owner. They are

According API documentation a device owner app can modify a few "secure settings" and specially the LOCATION_MODE with the following call : devicePolicyManager.setSecureSetting (ComponentName admin, String setting, String value) Called by profile or device owners to update Settings.Secure settings [...] A device owner can additionally update the following settings: LOCATION_MODE According my understanding the value of LOCATION_MODE is an int (resp. 0 for location disabled, 1 for GPS only, 2 for battery saving mode and 3 for high accuracy). My problem is the type of the String value parameter.

Working with Lollipop, I have a device-owner app that is installed with NFC at provision time. What I need now is to handle automatic updates for my App, from Google Play to rely on the standard Android App update system... So far I can imagine 2 ways to get this done, but don't know how to handle any of them : in my NFC install constant EXTRA PROVISIONING DEVICE ADMIN PACKAGE DOWNLOAD LOCATION install the App directly from the Play Store instead of the url on my own dev server. However this constant need to handle the url of an apk file, and I did not find any official way to get apk install