Android Enterprise General Discussions

Issue Description : After device enrollment, Devices.get() and Devices.list() intermittently return “No Device was found”/an empty list for the same device for an extended duration greater than 15 mins.This behavior persists beyond the propagation delay described in the documentation, which is 2 mins. Impact: App Distribution affectedOur EMM supports incremental app distribution:Fetch current device policyMerge additional appsRe-apply policy using Devices.update() When devices.get() / devices.list() are unavailable:We cannot retrieve the current device policy --> Incremental app distribution failsDetailed Reproduction Steps:Enroll device (afw#DPC_IDENTIFIER managed accounts method)Call Devices.update() to distribute apps that were pre-configured for installation during the enrollment process. Call succeedsCustom DPC adds managed Google Play account on DeviceCall Devices.List(enterpriseId, userId) → Returns empty for 15+ minsCall Devices.get(enterpriseId, userId, deviceId)

Hello Android Enterprise Community,We are currently building a custom MDM solution based on Android Management API and have completed the full end-to-end workflow, including enterprise creation, policy creation and assignment, enrollment token (QR) generation, device command lifecycle testing, Pub/Sub notifications, and admin panel and backend integration.The enterprise is created successfully, however the initial device limit shows as 0, so we are unable to enroll any test devices at the moment.We have already submitted the Android Management API initial quota request form with a detailed business use case and supporting architecture documentation. Due to the holiday period from December 19 to January 5, we understand there may be delays in review.I would like to ask:Is there any recommended way to test device enrollment while the initial quota request is under review?Is a temporary or development test quota ever enabled for validation purposes?Are there any best practices to validate

Hi,We want to use GBoard on kiosk devices but we aren't able to remove the suggestion strip using managed configurations.All other settings can be configured fine though.The show suggestion strip configuration is set to disabled.But with versions 15.x and 16.x of GBoard it's still visible on the devices.And when checking the setting locally on the device it's still enabled (Disabling manually works fine)Back in version 14.x this configuration worked fine.Anyone else who has experienced the same thing?We've tested this on devices from Samsung, Bluebird, ELO, and Zebra.Android version doesn't seem to have any impact, just the GBoard version.// Magnus

Hi Android Enterprise Community Team,   We are currently blocked from the partner onboarding process due to a system error that seems to have locked our DUNS number in a "ghost" application state.   Here is the chronological sequence of the issue:   First Attempt: I initially applied using a generic Gmail address and was correctly declined. Second Attempt (Corporate): I followed the instructions and re-applied using my corporate email. The Error: This second application was marked as "Declined - Further information was requested but not received". However, I never received any email requesting further information (I have checked all Spam/Junk folders multiple times). The process seemingly timed out on the server side without notifying me. Current Blocker: Now, when I try to "Resume Onboarding" or start a fresh application via androidenterprise.dev with my corporate email, the system allows me to log in but throws a generic "Oops Something went wrong" error immediately af

Apparently, Google has a new policy that only approved DPCs can be installed through QR Provisioning; otherwise, their installation will be blocked.Link: https://developers.google.com/android/play-protect/warning-dev-guidance#android_enterprise_dpc_enrollment The problem is that I am not able to understand how to apply for DPC approval. I found this page, but still not able to find out where to apply. Your help is appreciated. Thanks

Hello AE community, Our users encounter screen sensitivity issue while using a screen proctection on their devices,Device impacted is Samsung A9+, There is a setting to enhance screen sensitivity but it is not manageable thought Ivanti NMDM, or Knox Service Plugin. We also use Bluebird devices, for this manufacturer, sensitity setting is manageable using their OEM Config app. Is there another method to manage this setting ? Should i make a FER (Feature Enhancement Request) to Samsung directly ? Regards Batlac

Hi everyone, As of some weeks, Intune started showing the tenant name on the lockscreen. Where it used to say "this device belongs to your organisation" it now says: " This device belongs to company name" . Since this is a big no for most of our customers, I was wondering if other people noticed this as well and maybe even found a solution for it. Microsoft support admitted that they changed this, but they will now help us getting it fixed or even giving us the option to enable or disable this.  Showing the company name on a device can make a device more interesting to people who might find a lost or stolen device. Therefore, we never show company names or logo's on the lock screen. And most customers we work with expect that kind of behaviour. We currently have to project on hold because if this detail. (And its costing us extra business because they are not buying the hardware that comes with it &#x1f605) I hope someone else is having more luck! In the m

I am the developer of Headwind MDM, the open source MDM for Android. In December 2025, many of our users reported the same issue. While installing an MDM app by the QR code method, it is blocked by Play Protect: "This app can request access to sensitive data". A detailed description of the issue is here. As per Play Protect guidelines, this may happen if an app uses sensitive permissions—RECEIVE_SMS, READ_SMS, NOTIFICATION_LISTENER, and ACCESSIBILITY. We removed these permissions in May 2025, and at that time the issue was resolved. Unfortunately the issue re-appeared again in December, and we were unable to determine why Headwind MDM agent is blocked at the enrollment stage. Even removing all permissions from the manifest didn't resolve the issue! Looks like there is an AI which automatically blocks software in an opaque way (by signature or code similarity). Interesting - sideloading and installing the same MDM agent APK on a non-managed device doesn't trigger Google P

So I am trying to enable Managed Google Play in Intune to use for Android device management.We already have a managed Google domain, but we have device management turned off. To my knowledge we only use it for Workplace. When I try to enable managed google play in Intune I get two different error messages Any ideas or tips of what we need to enable or open up in the Google admin console to enable third party EMM? Does the account I am using to enable managed google play have to be a google super admin or something?

Hi everyone we received some reports from our users in the last couple of month that suddently the phone app on COPE devices (Samsung A-series) starts to show "Can't call from a personal app" - Your organisation only allows you to make calls from work apps. Workaround: Reboot the device. For most of the reports this workaround has to take place once and the message is gone forever. A very small amount of devices starts to show this message again after a couple of weeks. Rebooting is resolving the issue again. Any idea of how to prevent this? Even emergency calls are not possible if this error is appearing! Does anyone else have seen this behavior? Raised a case with Samsung today. Thanks!Daniel

we are asked to verify our google developer accounts on the console. however, when trying to do so, our DUNS number was not working. we know it's the correct number as it's used in a different portal.

Since mid-November '25, forced auto install is not functional for our organization.  Apps are loaded and installable as work apps but do not progress as an auto install from our policy. Has anyone experienced a similar issue?  No policy changes, no SW updates on the MDM client.  Functionality just stopped working.

Hi, We recently moved to android enterprise with work profile (using Intune) for all of our android users. And we just found out that with android enterprise with work profile does not support wearOS yet so that our users cannot add their corporate email account (O365) to the outlook app on their samsung watch or pixel watch.we tried to contact microsoft about this and microsoft said that this is not up to Microsoft but it is up to Google Android whether they would like to support wearOS for work profile. Can Google confirm if they would like to provide some support for work profile in the future for wearOS as well? I know that any development of newly feature in android system are fully confidential but it would be good for android end users to know if Google has a plan to support this in the future or not.

If a policy is configured with:DeviceConnectivityManagement > bluetoothSharing=BLUETOOTH_SHARING_DISALLOWEDandbluetoothContactSharingDisabled=FALSE will the first setting override the second, thereby preventing contact sharing via bluetooth? If so, it could be good to have that documented like it's done in other places (e.g. "This setting is ignored if {SettingName} is set to X"

Hi everyone, I just trying to find out whether other Android Enterprise users/admins are struggeling with the same issue than we do. Our pain point is the user experience on making phone calls to (remote) contacts from an Android Enterprise device.  Today, you can search personal and company / work profile contacts if they are saved to the local contact databases on the device. BUT you have to switch to another app (in our case MS Outlook) to search for remote contacts if you did not save/export the contact to the local contacts database. My DCR with MS is about a feature implementation into MS Outlook app to answer search requests for contacts from the dialer app directly into GAL. As far as I can see in the developer API of Android Enterprise this should be possible: Work profile contacts  |  Android DevelopersAnd: I did see this thing working on Android Enterprise enrolled devices on Google workspace! Are other admins thinking about this as we

Hi everyone, I’m implementing a custom DPC (device owner) and integrating AMAPI locally on the device.  On Android 8 / 8.1, calling:val request = PrepareEnvironmentRequest.builder() .setRoles( listOf( Role.builder() .setRoleType(Role.RoleType.DEVICE_POLICY_CONTROLLER) .build() ) ) .setAdmin(admin) .build() immediately fails with:com.google.android.managementapi.common.exceptions.ApiLevelException On Android 10 and above, I don't have this exception. According to the AMAPI documentation:If the device's SDK API level is insufficient for certain requested roles (this may be in addition to a general minimum API level requirement for the call itself).{@code Role.RoleType.DEVICE_POLICY_CONTROLLER} requires API level 23 or above. Any other roles require API level 28 or above.  I am using the latest AMAPI client library:com.google.android.libraries.enterprise.amapi:amapi:1.7.0&nb

Hi!   Mobile devices are quite complex and fast- changing. Errors sometimes sneak in and as a UEM administrator you often have to find a solution.If in doubt, the UEM manufacturer is the first point of contact, but if it is an app or OEM-specific error, a ticket to the right place can also speed up the solution. In addition, any support team will appreciate it if you look into the problem before creating a ticket, provide specific log files and perhaps even roughly narrow down the problem.   But... How? The commands for logs and the sheer mass of log lines can be quite overwhelming!In this topic I would like to provide some information about logging for Android Enterprise, which will hopefully help some of you in the future. I will not cover all commands or segments in log files. If there is something that you think is important for logging, please feel free to add it. 😀 ADB - Android Debug Bridge Get the tools The ADB is a versatile command-line tool with which you

Hello Community,I recently read an article about connecting a Windows PC to an Android phone, which got me thinking: we need a similar focus on connecting Chrome OS (via Crostini) to Android devices.Since both Android and Chrome OS are Google products, the integration should be seamless. If Google wants to grow Chrome OS adoption, developers are the ideal first target. However, making it easy for developers to build Android apps on Chrome OS must be a priority, and currently, there are significant friction points.The Technical BlockersMy Android development on Chrome OS has been halted for over a month due to persistent issues:ADB Debugging on Managed Devices: My managed Chromebook (I am the admin) has the "Enable ADB debugging" toggle locked. Despite a month of searching, I haven't found a fix.Connection Instability: Both USB and Wi-Fi debugging work intermittently and then fail. I have tested this with a modern Android 15 phone and an older Lollipop tablet; the co

Hi Everyone, I am trying to set up a fully managed device for my organization. I have completed the process of enterprise creation, but as I generate the enrollment QR and begin setup of my Android, I get an error stating "Since your organization reached its usage limits, this device can't be set up". What am I missing as I can't see any graph or option to increase my limit. Furthermore, I have deleted all the devices from my enterprise. My organization needs a scalable solution so that we can manage thousands of device . Please let me know how to proceed forward.Thanks 

If people have not heard. Google is working on bringing AndroidOS to PC's. Google's new 'Aluminium OS' project brings Android to PC Just hope the AE management stays the same or even will expand on its capabilities. ChromeOS needs Google Workspace for management and not everybody is familiar with this.  but I look forward testing it when its ready for public or maybe private testing 🤐.

In a rapidly changing industrial landscape, innovation now hinges on fully integrated mobility at the heart of digital tools. The transition from Windows to android devices is no longer simply about swipping devices; it requires rethinking the work environment itself, freeing it from the constraints of fixed workstations in favor of mobile, agile solutions grounded in real-world situations.   With this in mind, our SMART MOBILITY project addresses the growing demand for efficient and secure mobile solutions in industrial environments as a first step. We have designed a secured work environment natively for smartphones, capable of covering all the daily tasks of a field worker.   This comprehensive, fully mobile approach aims to replace PC use where it becomes cumbersome, providing a high-performance, sustainable alternative that better aligns with the expectations of new generations, who prioritize intuitive, mobile interfaces accessible in all circumstances.    

We are enrolling devices using AMAPI by generating a QR code with an assigned policy either for work profile or fully managed enrollment.   During enrollment, the device prompts for a require for setup app, which, after configuration, returns RESULT_OK, marking the setup as complete and finalizing the device enrollment.   Before returning RESULT_OK, To identify the enrolling device, the backend gets the device ID and enterprise ID from the Pub/Sub provisioning notification. The device ID (which matches the GSF ID) is then sent by the require for setup app to the backend for validation. This identifier is also used to enforce enrollment limits based on the enterprise license count.   The Issue: Up to Android 14, retrieving the GSF ID was possible. However, in Android 15, it now returns null.   Question: Is there an alternative identifier that can be used to identify the enrolling device—one that the backend can retrieve and that the setup app can also access during e

This issue was documented in 2021 but with no solution.My Chromebook is managed by my company and I am the manager.But Google tries to find the managed option to unlock for this to work in the administration interface for more than 15 days without success.By the way there are thousands of options in the admin interface it could be a clever feature to number them.If you are in front of the same issue please add your comments to this post.I hope that Google support will succeed to solve the issue soon because I developed my first app for Android on my Chromebook with Android Studio and I was able to download it to my phone before these 15 days.

i had this weird issue while trying to auto provision the devices , i created one configuration to auto redirect the devices to an enrollment profile, added the Jason file of the token to it and assigned it to certain devices , yet it didn't work  the device realize that it is  belong to organization and i see my  company support  contact  means it been recognized on my zero touch portal but it ask me to scan QR code for enrollment and not detect the token  Jason  text in the DPC extras also the profile works fine if i scanned the QR, any suggestions ??😅  

Dear All I'm Enrollment Device for managing organization via 7Time Tap and Scan QR Some Step Complete but after some steps Give This Error So Please Give the suggestions Please