[Enhancement Request] Allow push notifications during OOBE setup process
Android does not allow any push notifications during the OOBE (out of box experience) setup process. This presents challenges during Intune enrollment because we require users to satisfy MFA (SMS or MS Authenticator) in order to complete Entra AD device registration and device enrollment. The inability to receive push notifications on the new Android they are configuring requires users to configure their MFA on a secondary device before starting the setup of the new device, or obtain a temporary access pass from our Security Team. If OOBE supported push notifications it would resolve this and provide a much simpler and easier enrollment/user experience.
requirements for provisioning an app on android 13
I have an app that I designed private for my company .... which gets permissions imei android ID block the use of factory restore unlock OEM unlock lock and unlock screen kiosk mode , and I install it by adb command and work perfect with all devices I have more than 170 devices made in this way and takes a lot of time , I would like to provision my app and placed as device owner through the QR the problem is that I do not know how to do it correctly try many things I saw on the internet , like for example the signed app get the sha256 from the apk and pass it to base64 make the json but I don't understand if I have to configure something else in the app for the provisioning I tried to scan a generated qr with everything correct and it didn't work it says contact your IT support for more information if someone can guide me it would be great, android 12+ a friend sent me some java and kt files for provisioning that worked for him, but for my app it doesn't work. my app has no icon because I need to pass silently and already does but as I say the problem is that I do not know if I am missing a file or a specific configuration I am missing only this and I would be grateful if someone can help complete it or guide me, I saw options like google workspace but I could not modify the block screen to be customized, try with the api google managament android and also does not let you create the company by command then I'm desperate and do not know what to do Thanks for read
Audio management in Android Enterprise
From the feature list in Android Enterprise from https://developers.google.com/android/work/requirements#4.25.-system-audio-management_1, I want to discuss the feature 4.25.2. IT admins can prevent users from modifying device volume settings (go to adjustVolumeDisabled). This also mutes the devices. In theory a very good feature, in certain areas when you want to block users from either changing the volume to silent or the other way. Our goal was to use with Samsung Service Plugin where you can set the default volume, but since blocking the volume buttons on the phone, you are also stuck with a mute device. So my feature request would be to have the feature without muting the device.
ZTE don't enroll the device
Hello, I using ZTE to enroll all of our Android devices into our MDM Meraki. But I've noticed that I have to perform a manual action each time to complete the enrollment : Why ZTE don't enroll automatically the device into my MDM ? Regards, **Code hidden for security reasons
Disable prompt for the user's consent for an app that records screen
We are working on an app that is used to test our software and products. The app is constantly running on test Android devices. It starts recording the screen based on an event and sends the recording to our backend servers to verify that the test passed. Currently, the whole process halts if the app or OS is restarted until a human approves the screen recording dialog that pops up when the app opens. Is there a way to pre-approve the screen recording for this app using the Enterprise Management APIs. As mentioned before, the app only runs on test devices that are not used by any employees. Currently, we have to constantly monitor these devices just to press the screen recording approval button when the app crashes, has to be restarted, or when the os is updated. I am trying to find a solution so that this is automated. Thanks for any help
Intune - Google Managed Play issue cannot complete the bind
Hi Everyone, sitting with an issue on three O365 tenants at the at the moment that I have escalated to Microsoft. Was hoping that someone else experienced this issue as well or can point me in the right direction. After opening the connector to bind the EMM (Intune) to the google play store the I grant Microsoft permissions to send both user and device information to Google is greyed out. I can close and the window and then reopen it and I can then tick the box. After that the Launch Google to connect now Button becomes available and the windows that pops up asks me to sign in with my google account. I have created numerous accounts, personal, work and school and tested with them. After the login into the google account it does not continue with the EMM setup. the box displays "The Page has expired. To restart your registration, please reload the page from your EMM console. Only way past that is to log out of the Gmail Account and then log in again with the same issue "The page has expired......" I have tried the connection from different devices, browsers, incognito... on different networks and have even tried it from a device with a vanilla install, Windows 10/11 and nothing helps. I have created different accounts on Google, personal, work and school etc, and the same issue. After logging in I can click on the google play icon in the left upper side and it shows the apps in the play store. I have attached screen shots.
Allow only one domain in Work Profile
Hi All, We have registered Android EMM with Managed Play Account (gmail) in Workspace ONE. We use Google Workspace for Google apps like email, calendar etc. I need to allow only adding our domain (mycompany.com) in Google Apps inside Work Profile. Is this possible? If yes, please guide me. PS: We are not registering Android EMM with Google Workspace because the email domain is different from our IDP (Okta). Thanks.Provisioning a Android 11 device intended to be in Kiosk Mode
So I have these android 11 tablet devices with no camera and no nfc and I am trying to enroll the device under android management so we can push the singular app we need via managed google play and silently update said device when needed . 1) Do I have to provision the device under fully managed in order to use it in kiosk mode? 2) How do I do this with no camera or NFC?
