Application report not getting collected on Xiaomi mix fold devices
We have couple of users who have the Xiaomi Fold device and in the application report section of status report notifications we are only getting the android device policy app. None of the other applications are getting returned. Is this a known issue? How can we debug the issue? I was not able to see anything obvious in the device logs. We are getting the full application report for the other devices.
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 !!!
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
Chrome is crashing again and again since few days
Hello, A colleague of mine has its chrome application crashing after few minutes of usage. It is on a COPE device and happens both on personal and pro area. We removed completly the data of the app and restart the phone but the issue persists since few days. I've opened a case at Samsung as it is on a samsung device but does some of you face the same issue ? I see a last update of chrome from the 2nd of september on this device. Corey, the day has come, my colleage is switching back to Microsoft Edge ;) Best regardsActivating 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......." } }
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
Google Messages App: SMS to shortcode not able to send
Our Provider (Vodafone Germany) is using a SMS shortcode number to be able to order an upgrade on dataplans by sms. Once the monthly contract plan (e.g. 1 GB) have been used users will receive a sms from 70997 to inform that you can answer the SMS with "1" or "2" to restore your data connectivity. We ran into the issue that the Google Messages app seems to have some sort of bug with sending SMS to this kind of shortcode number as it alway says "Not sent" in red error text. Provider tech support told me that the Google messages app is prefixing the number with "49" resulting in a wrong / unknown number (4970997). They cannot fix that from their side as the issue is within Google messages app and asked me to install a 3rd party messages app.... *ugly* Is this something I can request to investigate from here? I will also create a case with Samsung tech support as we are mainly using Samsung devices as our corp. device fleet. Thank you! Kind Regards DanielManaged Google Play API Error
We manage our mobile device through Intune; we also manage multiple tenants. I didn't know when I did this, but I made the mistake of signing into a new tenant with our Managed Google Play account that we use for our main tenant. Still, unaware of my error, I decided to disconnect the Managed Google Play account from the new tenant and create a new Google Play account for them. The new tenant works fine. I'm able to enroll Android devices and manage apps. However, in our main tenant, under Tenant Administration | Tenant Status for Managed Google Play, it shows a warning: Management Service Error. If I try to go to Android Apps to add an app, I get the following message: "It looks like your tenant has been unbound via the Google Play console. To browse Managed Google Play, your Intune account needs to be connected to your Android Enterprise account." But, in Devices | Android | Android Enrollment | Managed Google Play, it shows the account as Setup (with the green check). I'm also unable to create a new Corporate-Owned, Fully-Managed profile. I get an error. I reached out to Microsoft and they say this is a Google issue. I've tried to find ways to contact Google without success. So, we're kind of stuck in the mud. Is there a way to fix this?