android-management-api

问题 I'm trying to find out how to locate an Android 9.0 device which has been enrolled using a Service Account and the Android Management API. The documentation does not seem to have any hints for my case. Since there is apparently no way of logging in with a Service Account, I believe I cannot use https://www.google.com/android/find either. 回答1: You can use the Android Management API to turn on "high accuracy" location mode but you will need to use another app to get the location of the device.

问题 I'm trying to find out how to locate an Android 9.0 device which has been enrolled using a Service Account and the Android Management API. The documentation does not seem to have any hints for my case. Since there is apparently no way of logging in with a Service Account, I believe I cannot use https://www.google.com/android/find either. 回答1: You can use the Android Management API to turn on "high accuracy" location mode but you will need to use another app to get the location of the device.

问题 I'm trying to find out how to locate an Android 9.0 device which has been enrolled using a Service Account and the Android Management API. The documentation does not seem to have any hints for my case. Since there is apparently no way of logging in with a Service Account, I believe I cannot use https://www.google.com/android/find either. 回答1: You can use the Android Management API to turn on "high accuracy" location mode but you will need to use another app to get the location of the device.

问题 We are working on an Android app which is intended to replace the default Android dialer and handle by itself all the calls going on in the device. So far, the app works as expected and we are able to both handle incoming calls and make calls by launching ACTION_CALL intents. However, this app is intended to be run in kiosk mode via Android Management API. Whenever we fire the ACTION_CALL intent, kiosk mode blocks it, although the app is set as default dialer. After some debugging we

问题 I am using Chrome Managed Configurations to set a whitelist with this code in my policy: { "packageName": "com.android.chrome", "managedConfiguration": { 'URLBlacklist': ['*'], 'URLWhitelist': ['chrome://*', 'google.com', 'stackoverflow.com'], 'ForceGoogleSafeSearch': True, 'NTPContentSuggestionsEnabled': False, } } Now, in the Chrome enterprise docs it says there is a way to apply the same settings to Android Web view with the com.android.browser:URLBlacklist restriction, but it does not

问题 I am using Chrome Managed Configurations to set a whitelist with this code in my policy: { "packageName": "com.android.chrome", "managedConfiguration": { 'URLBlacklist': ['*'], 'URLWhitelist': ['chrome://*', 'google.com', 'stackoverflow.com'], 'ForceGoogleSafeSearch': True, 'NTPContentSuggestionsEnabled': False, } } Now, in the Chrome enterprise docs it says there is a way to apply the same settings to Android Web view with the com.android.browser:URLBlacklist restriction, but it does not

问题 I am using Chrome Managed Configurations to set a whitelist with this code in my policy: { "packageName": "com.android.chrome", "managedConfiguration": { 'URLBlacklist': ['*'], 'URLWhitelist': ['chrome://*', 'google.com', 'stackoverflow.com'], 'ForceGoogleSafeSearch': True, 'NTPContentSuggestionsEnabled': False, } } Now, in the Chrome enterprise docs it says there is a way to apply the same settings to Android Web view with the com.android.browser:URLBlacklist restriction, but it does not

问题 We have a Kiosk mode setup completed using Android Management API with our launcher app acting as kiosk app. However customizations applied through policy are not working as per expected. "kioskCustomization": { "systemNavigation":"HOME_BUTTON_ONLY", "statusBar":"SYSTEM_INFO_ONLY", "deviceSettings":"SETTINGS_ACCESS_BLOCKED" } We have this in the policy and it is getting synced to device but still all buttons in navigation bar working and still we can able to access settings. What we need to

问题 We have a Kiosk mode setup completed using Android Management API with our launcher app acting as kiosk app. However customizations applied through policy are not working as per expected. "kioskCustomization": { "systemNavigation":"HOME_BUTTON_ONLY", "statusBar":"SYSTEM_INFO_ONLY", "deviceSettings":"SETTINGS_ACCESS_BLOCKED" } We have this in the policy and it is getting synced to device but still all buttons in navigation bar working and still we can able to access settings. What we need to

问题 Background I currently maintain a Kiosk app on devices managed by the Android Management API. These devices run Android 7. I had been managing the app updates on these devices via the application minimumVersionCode , and moving the devices onto a new policy every time with a higher minimumVersionCode , forcing the affected devices to update the app. However some of the devices would factory reset if they had been off for a reasonable period of time (a week or two) even after extending the