No Response After Submitting Android Enterprise Contact Form
Dear Android Enterprise Team and Community, I hope you're doing well. I submitted the “Get in touch” form on the Android Enterprise website and received the confirmation email on May 30, which I have already responded to. However, I haven’t received any follow-up or contact from a specialist since then. We are exploring Android Enterprise solutions for our business and are interested in understanding the next steps to get started. Could someone from the team or community please assist or guide me on how to proceed? If additional information is required from my side, I’d be happy to provide it. Thank you for your support. Best regards, Deepak Alobha Technologies Pvt Ltd (This post was edited to remove personal information, in compliance with our guidelines)
FYI - Chrome is dropping support for A8 and A9 in August 2025
138 will be the last version of Chrome that will support both A8 and A9 according to this recent announcement. https://support.google.com/chrome/thread/352616098/sunsetting-chrome-support-for-android-8-0-oreo-and-android-9-0-pie?hl=en There are very small populations of these devices left in the wild but I personally still support quite a number of them. The entire Atlas family from Zebra including the TC51, MC3300, and VC80x devices all max out on A8 with no higher upgrades available. This likely will lead to forced upgrades to those devices, especially given how many modern apps are hybrid web apps dependent on the WebView and/or Chrome (Chrome is the System WebView implementation on A8).
InTune Android connection "unexpected error"
Trying to follow this doc. We want to use InTune to control our corporate owned Android devices. https://learn.microsoft.com/en-us/intune/intune-service/enrollment/connect-intune-android-enterprise At step 7, it has me click "Launch Google to connect now" and I just get "Unexpected error. Please wait for some time and try again." Tried multiple browsers, incognito, multiple accounts, etc. All same results. We have a licensed Google Workspace tenant with Enterprise Standard licenses. The account has access to all Google apps/services. My account is both an Azure Global Admin and a Google Workspace Super Admin/Owner. Sat on chat with Workspace/Android Enterprise support trying all the obvious things for 3 hours with no resolution. They finally gave up and just said "call Microsoft" which doesn't help, it's literally an error thrown by enterprise.google.com. How do I get past this error to configure the connection? (This post was edited to remove personal information, in compliance with our guidelines)
OEM Unlock toggle not available
Hi all, Recently joined the community, first time poster here. TL;DR at the bottom. Hopefully my question has a simple solution but I've looked everywhere (except here of course). I'll try to keep this as simple as possible. Everything is in UAT if that matters. The important bits: Pixel 8a Build BP1A.250505.005.B1 No SIM or eSIM Android Enterprise registered to my UAT Tenant I'm testing some scenarios for automating device compliance with Omnissa using Workspace ONE Intelligence. To test this successfully I'm going to need to flash back to an older Build and probably more than once for demo purposes. The OEM Unlock toggle is not available however, and I this is preventing me from doing my testing. I've read conflicting posts elsewhere regarding carrier unlock, SIM and/or eSIM etc. ADB is working fine but flashing older images is just not working. Any help from the community on how to get OEM unlock enabled would be greatly appreciated. TL;DR: Need to flash a pre 250505 build to my Pixel 8a. Can't toggle OEM unlock as it's greyed out.
Play Protect Blocking Custom DPC Apps — How to Get Approval or Alternatives?
Hi everyone, I'm a developer who helps enterprises build custom DPC (Device Policy Controller) Reference Documentation apps to manage Android devices based on their unique requirements. Recently, Play Protect has started blocking the installation of custom DPC apps, even when these apps are signed and used internally. The warning claims the app may pose a risk due to access to sensitive data - even though it's strictly for enterprise use. To make things more difficult: Google is no longer accepting registration of custom DPC apps with Android Enterprise, which limits official distribution and management options. Android Management APIs don’t support all use cases, and also have quote limit. I’ve applied twice to join the Android Enterprise portal to build a SaaS-based device management platform, but both requests were rejected without a clear reason. My questions for the community: Is there any official way to get a custom DPC app approved or whitelisted by Play Protect? Are there any alternative ways to manage Android devices at scale (outside of AMAPI or legacy EMM)? How can new developers or startups gain access to Android Enterprise features when onboarding is currently restricted? Any help, direction, or shared experience would be greatly appreciated. Thanks, Kulwinderhow to be partner of Google’s Device Lock Controller (DLC)
We are certified Android Enterprise Mobility Management (EMM) provider and an authorized Zero-touch Reseller based in Bangladesh. We specialize in enterprise mobility, with our proprietary MDM platform, MobiManager, actively used by leading organizations for secure device management at scale. In line with the growing demand for secure and inclusive smartphone access, we’ve developed PayProtect—a custom Device Policy Controller (DPC) tailored to support EMI-based smartphone financing. This solution enables real-time compliance, device-level control, and robust protection against default, thereby minimizing risks for telcos, lenders, and retailers. Now we want to integrate Google’s Device Lock Controller (DLC) for built-in solution for better performance. So how can we make partnership Google’s Device Lock Controller (DLC). Thanks in advance.
How to Handle Delisted Apps in Google EMM During or After Device Provisioning?
Hi everyone, We’re facing an issue where managed Android devices get stuck, preventing app installations when an app included in a policy is delisted from the Play Store. For example, we had the package “com.Xplayer” in a device policy, but when calling Products: get, it returned: “googleapi: Error 404: No product was found for the given ID., notFound.” However, this app was available earlier, and despite its removal, using the Devices: update API still updates the policy without any error or warning. Additionally, there’s a possibility that an app is present on the Play Store when it is approved and added to the policy but later gets removed or delisted by Google. This could lead to installation failures and devices getting stuck. Has anyone encountered this before? How can we prevent devices from getting stuck when an app is delisted? Does EMM automatically remove such apps from policies, or do we need to handle it manually by checking each package ID? Is there any way to get notified when an app is removed from the Play Store? Without a proactive mechanism, devices remain in a stuck state, making large-scale device management challenging. Any insights or best practices would be greatly appreciated! Thanks!
Silent installation of applications on TELPO devices using Android Enterprise
I have an Android application that I want to use on TELPO devices, but in a way that updates are downloaded silently on the device, meaning the user does not have to intervene to update or install an application. I understand that with the configurations offered by Android Enterprise, it is possible to set up a device to allow the actions I require.
