Recent discussions
Unable to install certificates for WiFi
Our MDM is using an internal app to install certificates that can be managed by our platform. The problem is when trying to set up corporate EAP-TLS networks, the device is unable to use the installed certificate for WiFi authentication. We see that identity certificates that can be installed programatically via DevicePolicyManager.installKeyPair(ComponentName admin, PrivateKey privKey, Certificate[] certs, String alias, boolean requestAccess) are installed under User Credentials settings section but for VPN and apps usage, not for WiFi, which is what the network configuration is expecting. Is there any other Android SDK API we can use in order to install the certificates for WiFi usage? Many thanks.
URGENT: Unable to complete action required for account verification
2 of our accounts got emails this morning that we have to verify our org address because it no longer matches. However, going through verification we get an error at the end to contact support.... going through the support system and answering their questions led to the below need help ASAP as it states we will lose all our apps on July 10th!!!
getting ready for work setup get the issue of something went wrong your app cannot become device owner by the qr code provisison by json in android
i am facing the issue in android 14 or 15 when ever i build the unsigned build it work fine for the android 13 after that it give the error like something went wrong please contact to the it admin and i am build the singed build it give error for the checksum error cannot setup but same thing if i make my app as a device owner by adb command it work fine for me let me know how to fix this issue? i try to replace the checksum and i match both checksum both are same it getting error for me why? below is my mention qr code json, {"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.abc.abc/com.abc.abc.utils.receiver.MyDeviceAdminReceiver", "android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM": "F-EJlegNKdVupdJupPmWz34s2INjWVUDS5ErL-DuETc=", "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://downloadapk", "android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": true}
QR code provisioning - Run OEM Wizard
Hi, I've got a device owner app I've written, it's working well when I install it via a QR code, but I want the stock Pixel / Moto setup wizard to run during / after the device owner setup wizard. I've done quite a lot of research, this doesn't appear to be easy! Any pointers / leads in the right direction to how I might achieve this would be greatly appreciated. Methods, source code to read, etc. Thanks, Richard
Getting DEVICE_POLICY_MANAGEMENT role
I'm stuck with getting DEVICE_POLICY_MANAGEMENT role for my application. DevicePolicyManager reports that my application is active admin (isAdminActive() returns 'true') and device owner (isDeviceOwnerApp() returns 'true'). But role is not assigned ('dumpsys role' reports no holders for android.app.role.DEVICE_POLICY_MANAGEMENT). Pre-requisites for getting this role seem to be fulfilled (like required-components from roles.xml) Found this article from @jasonbayton saying "Only an OEM can grant this permission to an application". Does this mean there's no way for downloaded application to get DEVICE_POLICY_MANAGEMENT role and device's configuration files to be modified for granting this role (config_devicePolicyManagement)? Thank you!
Zero Touch Customer API Feature Request
{written in Gemini ;) who literally wrote this out perfectly} I'm requesting an enhancement to the Android Device Provisioning API (Zero Touch) to include filtering capabilities, specifically the ability to filter devices by serial number (and other relevant fields) in the initial API call. Current Situation: Currently, the API lacks direct filtering. As demonstrated in the code below, to find a device by its serial number, we must: Make a call to list all devices for a customer. Iterate through the entire list of devices in the response to find the specific device. Iterate through any following pages if not found on the first page. This is inefficient, especially for customers with a large number of provisioned devices. const listDevicesUrl = `https://androidprovisioning.googleapis.com/v1/customers/${customerId}/devices`; // ... const listResponse = await fetch(listDevicesUrl, { ... }); const listData = await listResponse.json(); let foundDevice = null; if (listData && listData.devices) { foundDevice = listData.devices.find(device => device.deviceMetadata && device.deviceMetadata.serialNumber === serialNumber); } Desired Feature: I propose adding a filter parameter to the device listing API, allowing us to directly query for devices based on specific criteria, such as serial number, manufacturer, model, and IMEI. For example, the API call could look like this: https://androidprovisioning.googleapis.com/v1/customers/{customerId}/devices?filter=serialNumber={serialNumber} This would significantly improve the efficiency of device management and reduce the amount of data that needs to be transferred and processed. Benefits: Improved Efficiency: Reduces the number of API calls and the amount of data transferred. Faster Processing: Speeds up device identification and management operations. Reduced Load: Decreases the load on Google's API servers and client applications. Simplified Development: Makes it easier for developers to integrate with the API. I believe that adding filtering capabilities to the Android Device Provisioning API would be a valuable improvement and would greatly benefit the Android Enterprise community. Thank you for considering our request.
AE managed apps are not auto installed on devices after device enrollment
Hello, We manage Android mobile devices with an Ivanti MobileIron MDM. For the past few days, we have been experiencing issues with forced installations—they are no longer being pushed to our devices (silent install). Ivanti has indicated that Google support tickets have been opened. Bug referenced at Ivanti: It shows gms complaining about bad authentication in bugreport: [RequestTokenManager] getToken() -> BAD_AUTHENTICATION. App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/experimentsandconfigs Current understand of possible cause is that when issue occurs, google play account failed to got authenticated and re-auth could not recover it properly in time. Resolution We have several tickets open with google for now, and working with google on this issue. Google ticket number: 399818918 398768257 395681748 393388830 Google is rolling out a backend fix. Do you perhaps have more information about the issue and/or its resolution ? Are other people affected ? Thank you in advance for your help :) Adam
Unable to connect an external fingerprint scanner on KIOSK mode while scanner is working fine in non-kiosk mode
Issue: We are unable to connect an external fingerprint scanner on KIOSK mode while scanner is working fine in non-kiosk mode. Below is the policy. With this same policy we are able to connect to external scanner when we just change from KIOSK to Force_Installed. https://api.npoint.io/15f073eed7df2239c25aThe Ongoing Evolution of Android: Where Do We Go From Here?
Android has come a long way since its early days, evolving from a basic smartphone OS to a powerful platform that powers billions of devices worldwide. With every major release, we see improvements in performance, security, design, and user experience. From Android’s open-source flexibility to the introduction of Material You and AI-driven features, the platform keeps pushing the boundaries. One of the strengths of Android has always been its customization. Users love being able to tweak their device—from launchers and widgets to ROMs and root access. However, as Android becomes more polished and secure, some of these freedoms have become more limited. Is the trade-off worth it? Another topic worth exploring is Android’s fragmentation. While it gives manufacturers flexibility, it also creates inconsistency in updates and app performance. With initiatives like Project Treble and Android One, Google has made strides, but are we seeing real results? And now with AI integration, foldable phones, and powerful chipsets becoming the norm, it’s exciting to think about where Android is headed next. What are your thoughts on the current state of Android? Are you satisfied with the direction it’s going, or do you miss the old Android freedom? What improvements would you like to see in the next version? Looking forward to hearing everyone’s thoughts!
