Android Enterprise General Discussions

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 

how to open account to start to develop google find my product?we are one find tag factory in China and want to develop Google find my products.but do not how to contact google to start this.

I have enabled netrworkinfo so that I can get the phone number from telephonyInfos but find only carrier name. What is the problem actually from my end?

I would like to understand the specific reasons for the decline so that I can address any issues or deficiencies in my application. Any detailed feedback or guidance you can provide would be greatly appreciated.Understanding the reasons for this decision will help me make the necessary improvements and potentially reapply in the future. If there are specific areas that require attention or additional documentation needed, please let me know.Thank you for your time and assistance.

When i go into the google messaging app on my android and add a photo there is a work profile. In this work profile there have are photos that have been deleted from the rest of the phone. They aren't in a google drive, one drive or on the phone itself.  Please help. 

Hello,I have new model devices Samsung Galaxy Tab A9+ and Galaxy Tabe S9 FE+ and the Zero-Touche Enrollment (ZTE) is not working. Nothing happens and ZTE doesn't appear. It works with the Galaxy Tab A8 model.Is it the issue related to Android client portal ?Can you help me ?Regards

Is it possible to set/enforce the DNS resolver using an EMM/MDM? 🤔 🤔 I am thinking about using a custom DNS resolver like NextDNS, opentext/webroot DNS Protection or DNSFilter on smartphones and tablets that move between different WiFi and mobile networks to block certain contents. Thanks for your input.

Google won’t let me remove my account from galaxy phone I don’t have any more

I dont have qr code or code for work profile 

Hello I'm trying to provisioning a device into a fully managed dedicated device in Kiosk mode, and I have done it using Android Management Api and 6 tap method and QR code on welcome screen during factory reset.However, now I have device that after factory reset does not display welcome activity. How to provision device line this?Thanks!

Been using Android Enterprise for a little while and generally got things working well. But I am finding a few apps that won't make it to the Managed Google Play Store for no apparent reason. I appreciate some apps are only available in certain countries, but some of the ones I can't get to appear just seem a bit weird, they work on my own personal phone:-BBC NewsRecorder (from Google)Are two examples. For both, I have done exactly the same as others, made them available to the same Group under "available for enrolled devices"Any help, as always greatly received.Thanks.I

The ultimate Google Apple Killer!The Google Pixel 8 has USB C port that allows USB to HDMI in the same way my chromebook does.  However it is disabled currently in the android OS.  Here is what I think you should do with it.  I think you should allow the port to be plugged into a monitor or better yet a hub like the one linked below that I currently use for my chromebook.  The great part is I have a phone when I need a phone and if I sit down at a desk I plug it in and It will take all of my open Chrome browsers and send it to my monitors while connecting into my mouse and keyboard.   Here are the advantages I see for this:Great phone when you need a phonePortable chromebox that is also my phone and doesn't require me to carry another deviceI realize you have a small portable chromebook but it is a seperate device that is useless unless it is plugged in unlike your phone.I also realize you have Chrome Flex but the terminals Egan has doesn't support it

Hi all! I'm want to start testing the AMAPI via the testing options provided by Google. Just to test policies that are not yet embedded in mainstream EMM solutions.  I'm following this guide: Android Management API - Quickstart - Colab (google.com) as a starting point. All goes well until the step "provision a device". And cannot get a token or QR code visible.  When running the code in block 22, no token is returned.  I tried entering the policyname mannully but that returned a long error haha, so I'm assuming I just need to run the code and it will generate a token that I can use in block 23. Correct? If so, why is it not returning anything?  Hope someone is able to help, thanks! Michel

For years now, we have wanted to enroll our company-owned Samsung smartphones with Google Zero Touch (COPE) and adapt our service to move away from the work profile enrollment via company portal, which is time-consuming for the user. Since we are responsible for several thousand devices, we obviously test extensively and over a long period of time before we actually make a change to the productive service. We are mainly using the A-Series Enterprise models. Unfortunately, for years now, we have been repeatedly encountering problems as soon as there is an OS, MDM or Samsung OneUl update. It now almost feels as if stable operation is not possible with this trio. We've had better experiences with other device manufacturers, but unfortunately we've never had the feeling that we could run a stable productive service. It would be a nerve-wracking experience every time an update was due. Has anyone had similar experiences, or does anyone here use the desired scenario descr

I'm trying to make a basic MDM service for Android TV. In the beginning, I was testing everything on an Android phone, but when I started working with TV, I realized that TV devices are not supported by "Android Management API". I know that I'm not the first person who asked a similar question, but there was only one answer pointing out that it's not possiblehttps://support.google.com/work/android/thread/158930652/how-can-i-enrollment-android-tv-with-android-api-management?hl=en Maybe something has changed recently and now there is a solution.

Hi, we are trying to use Customer API according to the documentation: https://developers.google.com/zero-touch/reference/customer/rest/v1/customersMethod: customers.list works fine (GET https://androiddeviceprovisioning.googleapis.com/v1/customers)I am able to use Oauth2 authentication, get access token and use it for the above.When trying to use other methods (e.g.Method: customers.configurations.list) with my access token, I always receive a ToS error:​{"error": {"code": 403,"message": "The user must agree the terms of service for company id XXXXX at https://partner.android.com/zerotouch","status": "PERMISSION_DENIED","details": [{"@type": "type.googleapis.com/google.android.device.provisioning.v1.TosError","latestTosAccepted": false}]}}How can accept these terms of service and fix the above error? When I open the zero touch portal with the same user, there's no option to accept anywhere (I have the owner role). When terms of service are opened from the bottom left of the screen, the

We are using Microsoft Intune MDM to manage over 2000 Android devices and are having difficulty allowing devices to communicate with Intune from within our network.  We have followed several network requirements docs including the following: Network endpoints for Microsoft Intune | Microsoft LearnAndroid-Enterprise-Migration-Bluebook_2019.pdf (googleusercontent.com)Android Enterprise Network Requirements - Android Enterprise Help (google.com) We must have checked and double checked the URLs and ports from these documents a dozen times. We were able to get devices to check in at one point but after a few months they all stopped checking in again. For this reason, we believe that there must be a URL that points to an Endpoint or Endpoints that change periodically.  If we whitelist the entire *.google.com domain all devices are able to check in immediately however we are unable to do this as it would mean allowing access for every single device that connects

Hello, I have access to https://partner.android.com/zerotouch (or to the nice new portal 🙂) to manage which configuration I want to send to our devices. The account I use is "owner". I have created a project with Partner API in Google Cloud. For now I try to query my device list with androiddeviceprovisioning.googleapis.com using OAuth 2.0 Playground with that URI : https://androiddeviceprovisioning.googleapis.com/v1/partners/my_company_ID/devices/*But all I succeed is to have an access denied :{  "error": {    "status": "PERMISSION_DENIED",     "message": "Request had insufficient authentication scopes.",     "code": 403,     "details": [      {        "reason": "ACCESS_TOKEN_SCOPE_INSUFFICIENT",         "@type": "type.googleapis.com/google.rpc.ErrorInfo",         "domain": "googleapis.com",        

Hi all, I have a simple question:Are there touchpanels or whiteboards (75 inch and larger) that can be managed by Android Enterprise?Thanks in advance. Robert

Hey! We have encountered a potential problem with a few devices. The devices use automatic enrollment. Users have to continue in the setup wizard and enroll the device against the MDM before it can be used.For some devices, we have found a way to break out of the setup wizard. Without a restriction payload, apps can be sideloaded and data can be modified in the main user. Although the navigation bar, app drawer and some other features are restricted, this is sufficient for manipulation.If you go back in the navigation bar, you end up back in the setup wizard and the device looks like it has just come off the production line.My expectation with COPE enrollment was that the enrollment would fail because data had already been changed in user0. However, the enrollment could be completed without any problems and the previous adjustments were retained.Does anyone know when CO enrollment is no longer possible? Does this restriction depend solely on whether the setup wizard has already be

Hello, We've just started testing Zero Touch and one of our AZT early adopter device users recently left the company. We're trying to give his device to another tester however after a wipe of the device it's prompting to verify identify and asking for the previous users PIN / Google account (which we don't have) before the AZT assigned MDM enrollment kicks in... We were not expecting Zero Touch enrolled devices to be locked to previous users at all. Expected this to be similar to Apple DEP enrolled devices where we can easily wipe and re-issue those without any hooks to the previous users apple ID.Is this expected behavior for Zero Touch that a Corporate Device registered in Zero Touch is still hooked in to a users Google account and we cannot wipe and reissue the Corporate Device to a different user?

Hello everyone,Currently, we are using Android Enterprise devices enrolled (COPE) on the Workspace One MDM. We have started migrating to Microsoft Intune and would like to add the same Google account for the Managed Play Store that we are using on Workspace One, as the two EMMs will need to coexist for some time. Additionally, on this account, many developers have made privately developed applications available for our company, so we would like to avoid having to create a new account. Is it possible to simultaneously use the same Managed Play Store account on two different EMMs?

Hi, I had previously made a policy for a device and provisioned it. I made a second policy and tried to provision another device, but when I ran the code to generate the QR code it generates a link for me but when I click it, it says 404 Not Found - I did it through the Android Management API Quickstart notebook. What could cause this? All the previous code for executing the policies and generating the token worked fine with no errors.

can I check if this is still the latest Bluebook from 2019? https://static.googleusercontent.com/media/www.android.com/en//static/2016/pdfs/enterprise/Android-Enterprise-Migration-Bluebook_2019.pdf it looks like a couple of the URL's are still incorrect as listed as *gstatic.com and *gtv1.com without the additional "." enforcing the subdomain, this could cause a misconfiguration and possible security issue. and if any new URL's need to be excluded from proxy and firewalls thanks 

[Personal information hidden]   *Personal information hidden for privacy reasons in line with the Community Guidelines