Can't add a private app to devices
I'm being very confused when trying to add a private app into the Stix EMM, and I'm not sure where the problem lies, so I'm asking here! I successfully loaded it in: But when I then click on that and then try to click Select app... nothing happens. Nothing on screen, nothing in the dev console, no network traffic... Nothing. And so I can't add this app to my devices. And I'm entirely lost as to what's going on. Is this a Stix thing? Or an Android Enterprise thing?
The Ongoing Evolution of Android: Where Do We Go From Here?
Android has come a long way since its early days, evolving from a basic smartphone OS to a powerful platform that powers billions of devices worldwide. With every major release, we see improvements in performance, security, design, and user experience. From Android’s open-source flexibility to the introduction of Material You and AI-driven features, the platform keeps pushing the boundaries. One of the strengths of Android has always been its customization. Users love being able to tweak their device—from launchers and widgets to ROMs and root access. However, as Android becomes more polished and secure, some of these freedoms have become more limited. Is the trade-off worth it? Another topic worth exploring is Android’s fragmentation. While it gives manufacturers flexibility, it also creates inconsistency in updates and app performance. With initiatives like Project Treble and Android One, Google has made strides, but are we seeing real results? And now with AI integration, foldable phones, and powerful chipsets becoming the norm, it’s exciting to think about where Android is headed next. What are your thoughts on the current state of Android? Are you satisfied with the direction it’s going, or do you miss the old Android freedom? What improvements would you like to see in the next version? Looking forward to hearing everyone’s thoughts!
Help Needed: Issue with Deploying Managed Google Play private App
I'm trying to deploy a Managed Google Play app on Samsung Galaxy tablets using Intune. The devices are enrolled as Corporate-owned with a work profile. The app is uploaded to the Play Console, approved by Google, and synced with Intune, but it's not deploying. Intune reports the devices as not applicable, and the app isn't visible in the work-badged Play Store. I've tried different assignment settings, switching between "required" and "available," and tested both user-based and device-based groups separately. I also experimented with BYOD enrollment types, but none of these approaches worked.
Common identifier between AMAPI & Require for setup app for validation
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 enrollment? Below is the information we receive from Pub/Sub when a device is enrolled: { "name": [*Hidden for privacy reasons] "managementMode": "PROFILE_OWNER", "state": "PROVISIONING", "enrollmentTime": "2025-04-04T06:17:02.751Z", "lastPolicySyncTime": "2025-04-04T06:17:02.817Z", "softwareInfo": { "androidVersion": "15", "androidDevicePolicyVersionCode": 10323580, "androidDevicePolicyVersionName": "128.32.3 (10323580)", "androidBuildNumber": "AP3A.240905.015.A2", "deviceKernelVersion": "5.15.149-android13-8-00010-gc2e0ba41ba85-ab12040008", "bootloaderVersion": "unknown", "androidBuildTime": "2025-03-11T13:26:50Z", "securityPatchLevel": "2025-03-01", "primaryLanguageCode": "en-IN", "deviceBuildSignature": "c9009d01ebf9f5d0302bc71b2fe9aa9a47a432bba17308a3111b75d7b2143456", "systemUpdateInfo": { "updateStatus": "UP_TO_DATE" } }, "hardwareInfo": { "brand": "Redmi", "hardware": "mt6835", "deviceBasebandVersion": "MOLY.NR17.R1.TC8.PR2.SP.V1.P51,MOLY.NR17.R1.TC8.PR2.SP.V1.P51", "manufacturer": "Xiaomi", "serialNumber": [*Hidden for privacy reasons] "model": "23124RN87I", "enterpriseSpecificId": [*Hidden for privacy reasons] }, "policyName": [*Hidden for privacy reasons] "memoryInfo": { "totalRam": "5865836544", "totalInternalStorage": "806965248" }, "userName": [*Hidden for privacy reasons] "enrollmentTokenName": [*Hidden for privacy reasons] "securityPosture": { }, "ownership": "PERSONALLY_OWNED" } *Updated by Community admin - removed due to privacy reasons 4 April
ATOK installation Failed in Corporate-owned devices with work profile
Hi, I have enrolled 2 samsung devices to intune using the Corporate-owned devices with work profile and assigned many applications to the devices. However, 1 specific application has failed to install stating the "country or region doesn't support this application." This is strange because in the same tenant I have other samsung devices enrolled as BYOD which is assigned this same application can install. I tried to reach out to intune support and they cannot do anything about this and asked me to raise ticket to google and I don't really know where I can raise the ticket to google regarding. Please help as I have to figure this out and deploy the application. PS: This application is available in the play store for the region and country. So the error message doesn't make sense. Thank you
Android Management Api limit extension
Hello! Everyone, Greetings of the day!I would like to have some information about the Android device management API. I'm developing an solution using Android Management apis for my client. I've gone through the documentation and all the device APIS they have. My client has a plan to launch 5000 devices initially which can be upto 50,000 in future. I've read somewhere in google documentation about the quote of request uses. My question is, Does google have an api request quota or a limit to enroll the number of devices?Does it come under paid plan or is there any restriction? I just want to have complete/full information about this before we start integrating this solution. Can anyone help me with my questions?Can we set beta channel of public app in policy?
We have an application published on the play store that is used as require for setup app, I have different channels in play console, production and beta/closed. In AMAPI policy, we can set "accessibleTrackIds": [ string ] so that a particular channel is used to download the application. Here is the issue, when we go to the advanced settings in the play console for the app and turn on Managed Google Play, it shows that the app will become private and this can not be undone. Is this the way or we can use the public application's testing channel by specifying its track id in the policy and it will download for eg. if beta is added then it will download the beta channel app and if there is no track id mentioned then it will default to the production application? Another thing is that, how to get the track id in case we can do this?Device Admin App not present in work Profile
Hey Guys, I am enrolling a device in my MDM app as profile owner. A work profile was created but the MDM app with the device admin privilege is missing from the work profile . Has anyone come across such an issue before? If yes any help would be really appreciated . This is a Samsung M05 .Android 14 device.
Unable to add additional owners and administrators to Manage Google Play Store
We recently disconnected our Managed Google Play account from Intune, which was initially set up with a standard Google Account. Now, we are reconnecting Intune to our Managed Google Play account using a Managed Google account that is synchronized with our Entra ID SSO. This means we can sign in with our company domain (@mycompany.com) using our Entra ID password. We are able to enroll our Android phones into Android Enterprise and publish apps to our Managed Google Play store without issues. To ensure redundancy, Google highly recommends creating a secondary owner account in case the primary account is compromised. See Google KB . I'm following the guide on assigning roles in enterprises from the Managed Google Play Help. However, my Play Store account admin screen appears quite limited compared to what I should be seeing. Here’s a screenshot of my current view: Previously, when we used a personal Google account for our Managed Google Play Store, I could invite other users to become owners. This option seems to be missing since we switched to the managed account. Could there be additional permissions in the Google Workspace admin portal that we need to grant to the Managed Google Play account to enable the option to add additional owners?
