Android is an open-source mobile operating system developed by Google. It powers a wide range of smartphones, tablets, and other devices. With its customizable nature, Android offers users the flexibility to personalize their device, choose from a vast selection of apps on the Google Play Store, and customize settings to suit their preferences. Android provides seamless integration with Google services, including Gmail, Google Maps, Google Drive, and Google Assistant, enhancing productivity and convenience. It also supports features like multi-tasking, notifications, and various customization options. Android's versatility, extensive app ecosystem, and frequent updates make it a popular choice for users seeking a diverse and user-friendly mobile experience.

Android EMM Known Issues


Issue Notes Reference
Can not import or create placeholders FileWave hopes to implement in future release  
Devices do not show in smart groups    
No paid app distribution (AKA group license purchases) Paid apps not currently implemented in Google API  
Free Disk Space inaccurate FileWave hopes to implement in future release GOOG-194
Fileset Report - Empty FIXED: FW v 13.2 GOOG-219
Wiping device, but not removing from FW does not get previous associations FileWave hopes to implement in future release GOOG-216
Automatic add of mobile device does not add EMM Android FileWave hopes to implement in future release

FIXED: FW v 13.2
Wipe a device with WiFi off creates duplicate devices FIXED: FW v 13.2 GOOG-163
Devices are hidden (or show and then hide) in the new mobile UI Workaround: Change sorting (e.g. by time or model).

Code fix already in future release.

FIXED: FW v 13.2
Compliance policy breaks model update

Error at model update:

[ERROR] 2019-06-07 15:50:56,075 (exception): Internal Server Error: /android/emm/process_pending_emm_calls/<br>Traceback (most recent call last):[...]googleapiclient.errors.HttpError: <HttpError 400 when requesting returned "complianceRules are deprecated. Use policyEnforcementRules instead."
Google API was suddenly changed.

Code fix already in future release.

If you were on 13.1.0 when EMM was enabled in your license, then you will need a fix before or after upgrading to 13.1.1.

To request a patch use the Feedback Portal : Question (must be apart of the EMM program to use)

Minor (Aesthetics) Issues

Issue Notes Reference
Device status can not be changed from "Not Tracked" Geolocation not currently implemented in Google API FB-40
You cannot put the FileWave Client APK on an EMM enrolled device    
Fileset Status - delay between Google API has its own un published timers GOOG-199
Fileset Status - Does not show version FileWave hopes to implement in future release GOOG-196
Android Service preferences window sometimes cuts txt FileWave hopes to implement in future release

FIXED: FW v 13.2
Closing and reopening the Android signup window before completion will display the wrong Google Org Name FileWave hopes to implement in future release GOOG-187
No Command History in device details FileWave hopes to implement in future release FB-42
The Serial Number I see in FileWave does not match the Serial Number I see on the device. Some devices (Predominately Samsung) have two serial numbers, to see these on the device: Settings > Google > Device Policy > ⋮ (vertical ellipse) > Device Details. Scroll to the bottom to see the serials.  

Android EMM Zero-Touch Enrollment


Android Zero Touch Enrollment (ZTE) is a method for automatic device enrollment based on the device's participation in your organization's Zero-Touch Enrollment Portal. 

ZTE Portal

The portal is located at :

But requires enrollment into the program before you can login.


We'll want to use ZTE to ensure that devices are enrolled and are under Enterprise management.  (Opt-in enrollments will almost always end up with some devices not being enrolled. and we would like to ensure our devices are all managed, preferably without us ever touching them).  ZTE ensures that the device is enrolled when first setup.


Much of the setup for ZTE is done from outside of FileWave, but the Android ZTE portal must know about your FileWave MDM server, hence there is some configuration necessary.

You must have an Android ZTE Configuration created in your portal to configure your ZTE devices to point to FileWave.  You'll find detailed information on setting up your ZTE portal and configuration here:

When you create the configuration, you'll fill out the names and such for your organization, but two pieces of information will be driven from your use of FileWave.  First, you'll set the EMM DPC as Android Device Policy and second you will copy/paste in the FileWave JSON into the DPC extras field.  You get this JSON text from the FileWave Admin in Preferences→ Google→ Configure Enterprise → Copy ZeroTouch Configuration.  You'll see the FileWave Admin and Portal Configuration below: