device-owner

ScreenCapture via MediaProjection without user intervention in Kiosk apps - Android

爱⌒轻易说出口 提交于 2019-12-07 17:04:13
问题 I work for a digital signage company which has Android devices running in kiosk mode. Lately, we wanted to add screen capture for debugging. The easiest way to do that was to use getWindow().getDecorView().getRootView().getDrawingCache() to create bitmap and to send it over the network, but this will not capture videos as it's been rendered in surface view. MediaProjection's createVirtualDisplay seems promising, but the explicit permission needed to use this feature is not acceptable. Even

Device-Owner now disables the Backup service

扶醉桌前 提交于 2019-12-07 10:29:58
问题 I've had an issue with my device-owner App : before Android 5.1 it was working nicely, but now after the update to Android 5.1, installing a device-owner App disables the Backup Service. Now in the device settings, when going into the Backup & reset option, the Backup service is greyed out, saying this: Backup service is inactive. This is set by your device policy I could find this source on the google git repository... The code is not very long and easy to understand, they use android.app

ScreenCapture via MediaProjection without user intervention in Kiosk apps - Android

北城余情 提交于 2019-12-06 03:26:53
I work for a digital signage company which has Android devices running in kiosk mode. Lately, we wanted to add screen capture for debugging. The easiest way to do that was to use getWindow().getDecorView().getRootView().getDrawingCache() to create bitmap and to send it over the network, but this will not capture videos as it's been rendered in surface view. MediaProjection's createVirtualDisplay seems promising, but the explicit permission needed to use this feature is not acceptable. Even requesting user permission for the first time and persisting the result for further use is not acceptable

Stuck on “Connecting to WiFi” screen while provisioning Android Lollipop device

☆樱花仙子☆ 提交于 2019-12-06 01:36:49
问题 I am trying to auto connect with WiFi when provisioning Android Lollipop device using below NFC tags: p.setProperty(DevicePolicyManager.EXTRA_PROVISIONING_WIFI_SSID, "-----"); p.setProperty(DevicePolicyManager.EXTRA_PROVISIONING_WIFI_PASSWORD, "----"); It seems it is getting connected with WiFi but stuck on Connecting to Wi-fi... Screen and it is not finishing with provisioning process. Can anybody guide me to resolve this issue? 回答1: You need to surround SSID with double quotes : p

Device-Owner now disables the Backup service

喜夏-厌秋 提交于 2019-12-05 17:35:23
I've had an issue with my device-owner App : before Android 5.1 it was working nicely, but now after the update to Android 5.1, installing a device-owner App disables the Backup Service. Now in the device settings, when going into the Backup & reset option, the Backup service is greyed out, saying this: Backup service is inactive. This is set by your device policy I could find this source on the google git repository... The code is not very long and easy to understand, they use android.app.backup.IBackupManager to disable the service... But easier is the commit comment: Shutdown backup manager

Is it possible to have a “Profile Owner” app in Android Lollipop that is not co-present

安稳与你 提交于 2019-12-05 05:38:31
The Lollipop API provides 2 new features "Profile Owner" and "Device Owner" ( http://developer.android.com/about/versions/android-5.0.html#Enterprise ). Between them, they offer just the features I need for an app that parents can use to control their children's device activity. The setup flow for each is: Device Owner During device setup, using NFC, you can tell Android that you want your app to be a Device Owner. Android then downloads the app from a URL, and the device is encrypted and is provisioned with the app as a Device Owner. So for someone installing my app from Google Play, I would

How do I get the signature checksum of my APK that is signed with only the v2 scheme?

送分小仙女□ 提交于 2019-12-05 00:26:28
问题 I previously posted a question on how to get the signature checksum of my APK here: How do I get the signature checksum of my APK? The answer is perfect if an app is signed with the v1 signature scheme or the combination v1/v2 signature schemes. (Jar and Full APK Signatures) However, since my app will only be running on Android O or greater (it is a device specific app), I will only be signing it with the APK signature scheme v2 (v2 scheme). I will be using EXTRA_PROVISIONING_DEVICE_ADMIN

Android pin activity on boot

一个人想着一个人 提交于 2019-12-04 19:03:25
问题 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

Stuck on “Connecting to WiFi” screen while provisioning Android Lollipop device

杀马特。学长 韩版系。学妹 提交于 2019-12-04 06:45:42
I am trying to auto connect with WiFi when provisioning Android Lollipop device using below NFC tags: p.setProperty(DevicePolicyManager.EXTRA_PROVISIONING_WIFI_SSID, "-----"); p.setProperty(DevicePolicyManager.EXTRA_PROVISIONING_WIFI_PASSWORD, "----"); It seems it is getting connected with WiFi but stuck on Connecting to Wi-fi... Screen and it is not finishing with provisioning process. Can anybody guide me to resolve this issue? You need to surround SSID with double quotes : p.setProperty(DevicePolicyManager.EXTRA_PROVISIONING_WIFI_SSID, "\"my SSI\""); Yes, it's broken in L MR0 (Android 5.0).

How do I get the signature checksum of my APK that is signed with only the v2 scheme?

久未见 提交于 2019-12-03 16:03:14
I previously posted a question on how to get the signature checksum of my APK here: How do I get the signature checksum of my APK? The answer is perfect if an app is signed with the v1 signature scheme or the combination v1/v2 signature schemes. (Jar and Full APK Signatures) However, since my app will only be running on Android O or greater (it is a device specific app), I will only be signing it with the APK signature scheme v2 (v2 scheme). I will be using EXTRA_PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM. See: https://developer.android.com/reference/android/app/admin/DevicePolicyManager