OTA cache host is down
Hello peeps I fancied running automated network connectivity checks in one of my apps. Pulled in the list from the Devices category of network requirements and it looks like one of the OTA cache servers has been down for at least a week. ota-cache2.googlezip.net I raised it quietly but figured it was worth calling out here also.
Is there an alternative way to perform the same function as UpdateApplication on Android 15?
Hi everyone, We are currently managing Samsung enterprise devices via Knox Manage under Android Enterprise DA mode (Device Admin) . Our in-house application previously used the UpdateApplication API to update itself silently without user interaction. This worked well under Android 14. However, after updating to Android 15, this API no longer functions. Based on the Samsung Knox SDK documentation, it appears that UpdateApplication is now restricted to Device Owner (DO) and Profile Owner (PO) apps. We have tried to assign all delegated scopes to our app via Knox Manage policy settings (Android Enterprise → App Restrictions → Delegated Scopes for Apps). Unfortunately, the API call still fails. ✅ What we’re looking for: - Is there any alternative methods that allows silent or managed updates of enterprise apps on Android 15, without being a DO/PO app? - Or is DO/PO elevation now the only viable path? - If so, is there an official onboarding flow or protocol to request DO/PO designation for an app via Knox Manage? Any guidance, references, or examples would be greatly appreciated. Thank you! — Environment: - Android 15 - Knox Manage (latest) - Samsung A9+ tablets - Device Admin mode
AMAPI Provisioning Stuck on Registration Screen
I'm facing an issue with AMAPI device provisioning. I created a policy, generated a token, built a QR code, and scanned it on a tablet. The device successfully got added under my enterprise (I verified this using the API). However, for the past 2–3 days, while the QR code scanning works, the device gets stuck on the registration screen with a large circular loader for at least 15–20 minutes. After that, I get an option to factory reset the device. Even after the failure message, when I run my script to check for new devices, I can see that the failed device appears under my enterprise. The device's state from the AMAPI response is PROVISIONING. Despite being stuck on the failed screen, I tested sending commands to the device (like reboot and wipe), and surprisingly, they work. This has left me very confused if the device setup failed, how are commands still working? Initially, I thought it might be a device-specific issue, but I tried it on another device (which was never enrolled before), and I’m seeing the same behavior. For reference, here's the structure of the QR payload I’m using: { "android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE": { "com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "20Characters" }, "android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.google.android.apps.work.clouddpc/.receivers.CloudDeviceAdminReceiver", "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://play.google.com/managed/downloadManagingApp?identifier=setup", "android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM": "I5YvS0O5hXY46mb01BlRjq4oJJGs2kuUcHvVkAPEXlg" }
5 overlooked benefits of Android Enterprise
Android Enterprise is more than just a set of management tools; it's designed to address the complex needs of modern businesses. Here are 5 insights that often go overlooked: 1. Privacy you can trust Ever worried about mixing work and personal life on your phone? Or, as a business, concerned about invading your employees' privacy? Android Work Profile acts as a secure, separate container on your device. Think of it like having two phones in one, but without the extra bulk! Your work data stays within this container, completely isolated from your personal apps and information. This means: Employee privacy: Your company only sees and manages work data, not your personal photos or messages. Did you know you can see exactly what data your IT admin can see? Simply go to: Settings > Security & privacy > Your work policy info > Device info your IT admin can see. Data security: Your company's sensitive information is protected from accidental leaks or unauthorized access. Peace of mind: You can use your personal device for work without compromising your privacy or security. It's not just about security; it's about building trust. 2. Instant deployment Zero-touch enrollment allows for rapid and consistent configuration. It's not just about saving time; it ensures every device is configured correctly from the start, minimizing errors and getting your team working faster. Zero-touch enrollment enables efficient device rollouts, minimizing setup errors for a smoother user experience. Direct shipping to employees is a strategic win for businesses, bypassing central warehousing and significantly reducing costs. 3. Security that runs deep Android Enterprise isn't just an add-on; it's built into the core of the Android operating system. This means security policies are enforced at a system level. This deep integration allows for very precise control over device settings and data access. Explore Android’s multi-layered approach to security and granular control in our security paper and community podcast series. 4. Secure app distribution Think of Managed Google Play as your own private app store. You can curate and distribute approved apps to your employees, ensuring they only use safe and compliant software. This eliminates the risk of employees downloading malicious apps from unknown sources. Remote app management and updates simplify administration. 5. Future-proofing The Android ecosystem is vast and constantly evolving. By choosing Android Enterprise, you're tapping into a platform that's backed by Google's continuous investment. Plus the open nature of Android naturally enables constant innovation. This means you'll have access to a wide range of compatible devices, EMM solutions, and support - explore our partner ecosystem. As Android evolves, so will Android Enterprise, ensuring your mobile strategy remains relevant and effective. What's Next? Join the community discussion to share your insights and experiences. We'd love to hear from you: What are your experiences with Android Enterprise? What features are you most interested in? Share your thoughts in the comments below!
In-house app is not being distributed to a specific device
Hello, I am facing an error for a several months in the MC33ax from Zebra. I have an in-house app that was uploaded to Play Console, to be further linked to Microsoft Intune. The MDM is managing corporate devices by providing the app to many ones, as MC94, MC93 and MC33ax. However, everything works fine for 93 and 94, I can see the app in the Play Store, which is not happening to 33ax. In the Google Play Console, it seems that MC33ax is not part of the device catalog. Zebra support said something about reaching out GooglePlay Developer support to add the part number, and they said I should contact Android Enterprise. Is there someone able to provide assistance? Thank you in advance, Regards,
