Recent discussions
Do Not Have Permissions To Add Device
Hello, We are a reseller and recently we've been trying to add devices onto clients AZT. We've ran into an issue trying to add devices onto a new client. We tried to add the client to our portal, but the customer number we get doesn't match theirs. We've had this happen before with a previous client, but we resolved it by having them add us on their portal. Worked just fine. I got on a call and guided the customer to add us. Found us easily and was able to add us. I found them on our portal and I uploaded the CSV file. 2 of the 12 devices added. The other 10 did not. I then tried to add them individually. No issue. It seems to not be able to add them in bulk. I'm not sure how to resolve this issue. Does anyone know how to fix this problem? We plan to add more devices in the future and doing it one by one is going to take a long time.You're Invited! Join us for the upcoming Android Enterprise CAFÉ Takeover!
Hello Community Members, The Android Enterprise team is excited to invite you to our upcoming in-person CAFÉ Takeover events in New York City and Paris! What is the Android Enterprise CAFÉ? The Android Customer Advisory Forum for Enterprise (CAFÉ) is an exclusive, invite-only group of customers who actively engage with the Android Enterprise Product team. As a member, you get a front-row seat to the future of Android Enterprise. Look out for more details about the Android CAFÉ in a future post. Join Us for the CAFÉ Takeover! We’re opening the CAFÉ experience to non-CAFE members with two in-person events. This is a fantastic opportunity to meet the Android Enterprise team, network with your peers, and share your feedback directly with us. These events are exclusively in-person. CAFÉ Takeover: NYC Date & Time: October 14th 10:00am (9:30 Check-in) Location: Google NYC RSVP here CAFÉ Takeover: Paris Date & Time: October 21st 10:00am (9:30 Check-in) Location: Google Paris RSVP here Please note: These are customer-only events and registration confirmation is required to attend. Space is limited, so please RSVP at your earliest convenience to secure your spot. We look forward to seeing you there! Best, The Android Enterprise Team
Can't enroll the Samsung to Intune after removing from Google MDM
Hi experts, I'm pretty new to managing Android devices using MDM solution and I went to the issue that need advises. I have a Samsung Android for testing & evaluating the MDM solutions. I was testing on Intune & Google MDM. Here are step by step I have done to lead to this issue. I enrolled it to Intune by using the QR code successfully and finished the first test, then I wiped it fully I added it to corporate-owned device under Google MDM by using csv with serial number Enrolled it to Google MDM and finished the test with MDM. Then, I removed this device from corporate device, deleted it from devices tab from Google MDM and fully wiped (factory reset) this device I scanned the QR code again (the same one I scanned in step 1) but failed After few screens, like connect wifi, this device belongs to org, etc... it ended up with 'Something went wrong, please contact to your IT administartor. I tried to scan it multiple times without luck; other device still be able to scan the QR code for enrollment. There is no logs can be found in the Microsoft. Is there anything that I was missing? Thank you !!!
Activating Device Owner in Android 16
I’m building a parental control app that relies on Device Owner mode. This worked fine on older devices (e.g. Samsung Galaxy S8 running Android 8/9), but it fails on a Pixel 10 Pro running Android 16. Process: I factory reset the Pixel. At the welcome screen, I scan a QR provisioning code. The QR downloads my signed APK, installs it, and should activate it as the Device Owner. Problem: On Android 16, the app is installed but Device Owner is not activated. In Settings > Device Admin, my app is listed, but the toggle is off. My MyDeviceAdminReceiver never fires — I see no provisioning broadcast (PROVISIONING_COMPLETE or PROVISIONING_SUCCESSFUL) and no debug logs. Here is my provisioning json as a starter - juyst in case I am doing something stupid!! { "android.app.extra.PROVISIONING_MODE": "device_owner", "android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.xxxx.yyyy/.MyDeviceAdminReceiver", "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://test.app.com/app-release.apk", "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM": "rePWsxWwsW2wycUDiE_hVHSczS3qaJIdk7fnzDMPDV0", "android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": false, "android.app.extra.PROVISIONING_SHOULD_LAUNCH_RESULT_INTENT": true, "android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE": { "provision_token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx......." } }Android 15 Setup Wizard loops at “Accept Google Services” on Lenovo Tab M11 (TB311FU)
Hi all, I'm running into a blocking issue provisioning brand-new (and factory-reset) Lenovo Tab M11 - TB311FU devices on Android 15 with Android Management API (fully managed / dedicated, kiosk). On Android 14 everything worked fine with the exact same policy and enrollment flow. The issue only started after updating to Android 15. (this is my test device, i constantly factory reset it) Expected behavior: Standard QR (6-tap) provisioning to proceed past the “Accept Google Services” screen, install Android Device Policy, enroll to my enterprise, and apply the kiosk policy, install app, and done. What happens instead: After Wi-Fi and scanning the AMAPI QR token, Setup Wizard reaches “Accept Google Services”. Tapping Accept shows a spinner, then it returns to the same screen (loop). I simply cannot get past this point. If I reboot at this point, on the very first Welcome screen the device sometimes becomes unresponsive (neither 6-tap nor “Next” reacts) until I factory reset again. Is there a known Android 15 Setup Wizard issue that can cause a loop at “Accept Google Services” on Lenovo TB311FU? Any workarounds you'd recommend to get past the acceptance loop? When factory resetting, and setting up the tablet without scanning the qr code, i get past the Google Services no problem. When i install via qr-code on new fresh never used before tablets, that come pre-installed with Android 14, i don't have any issues. Same policy, same everything... except the Android version. Thanks in advance! /B
Enrollment failing - Could not update Webview
We have reports of devices no longer being able to enroll. Our policy has a FORCE_INSTALL of Android Webview (com.google.android.webview), with a minimum version set to 593815300. Reproduced here with an Acer ACTAB10KB24. If I remove the minimum version requirement, I can enroll the device, and also update the webview to 139.0.7258.158. Why isn't the configuration with minimumVersionCode set working? We have previously enrolled many of these, but from our logs the latest successful enrollment was on the 16th of August (2025).
Way of implement the following feature '3.24. Managed Google Play Account upgrade'
We are enterprise solution EMM partner. We want to validate the following feature 3.24. Managed Google Play Account upgrade Anyone please describe how to do this actually. Not understand way of integration in our solution. Thanks in advance.
Android Enterprise
I had upgraded my account to Google workspace Business Plus and wish to use the Android Enterprise function within Google platform. I had followed the steps and set to Advance mode in the mobile management "Custom" setting but the Android Enterprise did not appear for selection. Do i need a third party EEM or can i activate the Android Enterprise with Google Admin console without a third party one.
Updating the Device Art Generator (Device Frame)
The Device art generator is a great tool for people who don’t want to install Android Studio just to take some framed screenshots for documentation use. There are third-party apps that can do this too (Snapmod), but I was wondering if the developers at Google could give the Device art generator some well-deserved love and update it to include Pixel 10 frames? Thanks. (Google) Device art generator: https://developer.android.com/distribute/marketing-tools/device-art-generator 3rd party option: https://play.google.com/store/apps/details?id=cn.gavinliu.snapmod
Known issues with Android System WebView 139.0.7258.160?
Hi everyone we have some reports about OAuth2 Login issues on Android devices with Microsoft Conditional Access rules. Some device (very small amount) are not able to login to some specific apps where the OAuth Login is being made with an embedded Browser session. During investigation we found out, that all users are on Android System WebView version 139.0.7258.160. Users without issues are running 139.0.7258.158. We don't know whether this is the issue but I wanted you asked whether other admins here are having similar issues in the last couple of weeks. Are there any known issues about certificate based logins with Android System WebView currently? Thank you! Kind Regards Daniel
