Lizzie
Warren

Mastering the art of managing non-GMS devices

Lizzie Warren Lizzie Warren

Sep 3, 2026

15 min read

non-GMS devices

TL; DR

  • Non-GMS Android devices lack Google’s apps and infrastructure, requiring a different management approach than standard Android fleets.
  • Without GMS, enrollment, remote command delivery, and app distribution all work differently, often slower and more manual than on GMS devices.
  • Hexnode UEM addresses this with ADB-based enrollment, MDM-hosted app catalogs for APK sideloading, and remote management built for non-GMS constraints.
  • With the right setup, IT teams can secure, provision, and maintain non-GMS devices just as effectively as standard Android fleets.

Lost in the labyrinth of managing non-GMS devices? ??

Fear not, as we’ve got a solution that’ll steer you in the right direction! ?

Managing Android devices can be a challenging task in itself, but it can be even more daunting when you have to manage non-GMS (Google Mobile Services) devices. They may not have access to the suite of Google apps and services that most Android devices come with, making it difficult to manage them efficiently. In a world where we are very convenient with using Google’s ecosystem, what happens when these devices don’t come with the support of Google Mobile Services? ?

Confused? Don’t let this puzzle leave you scratching your head. With this blog, let’s uncover the secrets to seamlessly provision and manage non-GMS devices. Also, on the go let’s look at some interesting facts about them! ?

Let’s get started! ?

Understanding more about GMS and non-GMS devices ??‍?

Before starting our journey to simplify the art of managing non-GMS devices, it is important to note the two distinct categories of Android based smart devices, each with varying levels of functionality and compatibility. This information may be uncharted territory for those who haven’t explored these terms before. No worries let’s make it simple!

The term “GMS” refers to “Google Mobile Services,” which is a collection of exclusive software and APIs. These services include Gmail, Google Maps, Google Play Store, and others. On Android-powered devices such as smartphones, tablets, and smart TVs, these Google Services are often pre-installed at the system level and have the ability to run Google’s apps and services.

The Android Open-Source Project (AOSP) operating system without the GMS Package is known as a non-GMS based Android OS. Since an OS without GMS is a lightweight alternative, fewer resources are used, including storage, RAM and background processing. Devices running this type of OS, such as the Amazon Fire Tablet or Xiaomi Mi Box, even use less battery power compared to those with GMS.

What is Google’s motive in GMS devices? ?

Simple! Offer a seamless experience. ?

To maintain consistency across all Android devices, Google mandates certain baseline functionality through the Compatibility Definition Document (CDD), which compels manufacturers to comply. To bundle Google Mobile Services (GMS), manufacturers must obtain a license from Google and ensure that their devices meet a minimum set of criteria outlined in the certification (also known as Mobile Application Distribution Agreement (MADA)). These criteria include pre-installing certain Google apps such as the Chrome web browser and the Play Store.

While the eligibility tests for GMS certification are extensive and the requirements are strict, most manufacturers still choose to comply because GMS has become the industry standard for Android devices.

Possibilities of upgrading non-GMS Android to GMS ?

Now are you curious about upgrading non-GMS Android device to GMS? Well, it’s possible, but it’s important to proceed with caution. It is currently viable to install basic GMS components on non-GMS AOSP releases. By default, all Android operating systems are AOSP which after receiving GMS licensing and certification change to GMS Supported OS. However, Google doesn’t permit the commercial sale of non-GMS devices with GMS components and services.

Compatibility issues, and potential warranty consequences should be carefully considered before attempting to upgrade a non-GMS Android device to GMS. If you’re looking for a longer, much more in-depth perspective of GMS and certification, what it is, and what you can do with it, we’ve got the map to guide you through! ?? Learn about GMS certification.

Choosing the best Android for your organizational needs ?

Are you torn between choosing a GMS or non-GMS Android device? ? This decision can be crucial for the development and management of your enterprise! So, let’s light up and check which device suits the best.

GMS Android devices are the go-to option for most users who seek convenience and integration with Google services. For the enterprise sector, non-GMS devices offer more freedom and flexibility for provisioning, deployment, and customization to meet specific requirements. The enterprises can exercise greater control over their devices by using APIs from multiple services, rather than solely relying on GMS services. This allows for more precise management of update schedules, stability, and other critical factors.
Ultimately, the decision between GMS and non-GMS devices depends on several factors, that includes:

  • Type of hardware
  • Hardware specifications
  • API requirements
  • Target user needs and many more…

Remember, when it comes to choosing the best Android device for your needs, it’s important to consider all the factors that are most important to you and your enterprise, including privacy and security. With the right device in hand, you’ll be well on your way to a successful and productive future!

Did you know ?

The Chinese market is a unique case for Android devices as most smartphones sold in the country do not come with GMS at all, and this is not just a recent trend. The reason for this is the fact that Google is banned in China, and so Google services are inaccessible to Chinese users.
Despite the absence of GMS, Chinese Android devices have continued to sell well in the country and have even gained popularity in other parts of the world. As a result, many app developers have had to create versions of their apps that are compatible with non-GMS devices, leading to a more diverse Android ecosystem.

Challenges of managing non-GMS devices in your organization ?

If you’re opting for non-GMS devices for your enterprise, then there can be many obstacles in your way. Even though this might seem like a challenge, it’s not something that hasn’t been tackled before. To ensure effective management, it’s important to understand these challenges beforehand. So, let’s have a look at them!

  • Lack of Google services: One of the main challenges of managing non-GMS devices is the lack of access to Google’s popular apps and services such as Gmail, Google Maps, and the Google Play Store.
  • Customization: Non-GMS devices offer more freedom and flexibility for provisioning, deployment, and customization, but with greater freedom comes greater responsibility. Managing and customizing these devices can be a complex and time-consuming process.
  • Security concerns: The absence of Google’s security measures can also pose a significant challenge for managing non-GMS devices. It is essential to take additional security measures and keep them up to date to ensure the safety and privacy of the device’s data.
  • Application support: Another challenge of managing non-GMS devices is the limited access for third-party applications. This can make it difficult to find and install the apps you need to get your work done.
  • Updating and maintenance: Unlike GMS devices, non-GMS devices do not receive automatic updates from Google. This means that it is the responsibility of the IT admin of your organization to ensure that the device’s firmware and software are up to date.

Despite these challenges, managing non-GMS devices can be a rewarding experience for those who are willing to put in the effort. By understanding the device’s limitations and taking the necessary steps to overcome them, you can unlock the full potential of non-GMS devices and make the most of your investment. So, are you ready to take on the challenge?

Cover - Hexnode Android management datasheet
Featured resource

Hexnode Android Management Solution

Get started with Hexnode’s Android Management solution to improve efficiency, increase productivity, save time and overhead costs of managing your corporate devices.

Download the datasheet

Provisioning and managing non-GMS devices using Hexnode UEM ?

Keeping all these challenges in mind, are you struggling to find a solution for them? Then Hexnode UEM can help you out!

Try out Hexnode’s Android device management capabilities

Enrollment

Devices can be enrolled using a variety of techniques, but some popular techniques are not supported by non-GMS AOSP (Android Open-Source Project) devices. For example, enrollment process cannot be done through methods such as the 6-tap QR code, Android Enterprise or Zero Touch Enrollment.

The usual manual enrollment of Android devices to Hexnode UEM involves two steps. They are the installation of the Hexnode app on the device, followed by the enrollment process where the user fills in the necessary information in the app. However, there may be instances where a device doesn’t support a specific enrollment method. For example, if the Google Play Store is disabled on the device, downloading the Hexnode app becomes impossible. Another scenario is when the device lacks a camera or it is disabled, which is common in hazardous areas, military facilities, or sensitive workplaces. This makes it impossible to use the QR code enrollment method as it requires access to the camera.

For all these scenarios, Hexnode UEM offers an answer for you and your organization! The IT admin can use the following method supported by Hexnode UEM for the smooth onboarding of non-GMS devices:

Enrollment of non–Android Enterprise device owner via ADB:

With this approach, Android devices running version 5.0 or later, as well as devices using AOSP or other Android-based operating systems, can be enrolled in Hexnode UEM. For this enrollment process, follow the steps below:

  1. Go to Settings > System > About phone and tap the build number 7 times.
  2. Enable USB Debugging in Settings > Developer Options.
  3. Install ADB on your computer and download Hexnode UEM to the ADB folder.
  4. Start ADB server in the Command Prompt by navigating to the ADB folder and entering “adb start-server“.
  5. Connect the non-GMS device to the computer and use “adb install HexnodeMDM.apk” to install Hexnode UEM.
  6. Make Hexnode UEM the device owner with “adb shell dpm set-device-owner com.hexnode.hexnodemdm/com.hexnode.mdm.receivers.HexnodeDeviceAdminReceiver“.
  7. Open the Hexnode UEM app in the device. Enroll by either scanning the QR code or entering the server’s name.
  8. Now, follow the on-screen instructions.

Apart from this IT admins can also use the Enrollment using Hexnode for Work app method. We can utilize this method in two ways for non-GMS devices. It includes:

Case 1: Enrollment of device without Google Play Store but has Camera

Case 2: Enrollment of devices without Camera or Play Store Service

How Remote Commands Work Differently on Non-GMS Devices

Enrollment isn’t the only thing that changes on non-GMS devices. Command delivery does too.

On standard GMS devices, MDM platforms rely on Google’s push notification infrastructure to send remote commands almost instantly. Lock a device, push a policy, or trigger a wipe, and the action typically executes within seconds.

Non-GMS devices don’t have access to this infrastructure. Without GMS, there’s no push notification channel to lean on.

Instead, management platforms fall back on periodic device check-ins, often called a “heartbeat,” where the device polls the server at set intervals to pick up pending commands. This means remote actions on non-GMS devices may take longer to execute compared to GMS devices, depending on the configured check-in frequency.

For most day-to-day policy enforcement, this delay is a non-issue. But for time-sensitive actions, like locking a lost device immediately, it’s worth factoring into your security planning.

IT teams managing non-GMS fleets should configure check-in intervals as tightly as the device and network allow, and treat non-GMS devices with slightly more built-in latency when designing incident response workflows around lost or compromised hardware.

Key features of Hexnode UEM for non-GMS device management ?

With Hexnode UEM, organizations can ensure that their non-GMS devices are secure, compliant, and used effectively. Here are some of the key features of Hexnode UEM that make it a top choice for non-GMS device management:

  • Remote management:

    Hexnode UEM allows administrators to remotely manage and secure non-GMS devices, including smartphones, tablets, and laptops, from a centralized console.

  • App management:

    IT admins can manage and distribute apps to non-GMS devices, including both in-house and public apps, and enforce app policies to enhance device security. Using Hexnode UEM, they have the ability to remotely manage applications. This include installing and uninstalling, marking apps as mandatory, deploying app catalogs, and more.

  • File management:

    With Hexnode UEM, corporations can manage their data efficiently with its powerful file management feature. It provides a simple and secure solution for managing data, while improving workplace efficiency and allowing employees to access corporate content easily.

  • Network management:

    IT admins can effortlessly set up Wi-Fi connectivity on non-GMS devices using Hexnode UEM. Users can connect to the enterprise Wi-Fi without having to manually enter the password. This ensures a more secure network and eliminating the need for them to have access to sensitive login information.

  • Kiosk management:

    Hexnode UEM’s kiosk management feature provides a comprehensive solution for organizations to secure and manage their public-facing devices, ensuring that the users only have access to the content and functions that are intended for them.

  • Security:

    Hexnode UEM provides robust security features such as device encryption, device lockdown, and password policies to keep non-GMS devices secure.

  • Compliance management:

    The solution allows organizations to enforce compliance policies, such as device restrictions and security requirements, to ensure that non-GMS devices are secure and compliant with organizational, and government specified standards.

  • Data usage management:

    Using Hexnode UEM, IT admins have the power to monitor and control the data consumption of enrolled devices, making it ideal for enterprises. This feature allows administrators to set data usage limits for individual apps or for the device. If the limit exceeds, the admin will receive notifications, providing valuable insight into the data usage habits of their users.

  • Reporting and analytics:

    Hexnode UEM provides detailed reporting and analytical capabilities that help organizations understand device usage patterns and identify areas for improvement.

  • Integration:

    The solution integrates with popular enterprise tools, such as Microsoft Active Directory, to provide a seamless experience for administrators and users.

App Distribution Without Google Play: How It Works

Without GMS, there’s no Google Play Store and no Managed Google Play. So how do apps actually get onto these devices?

Enterprises typically rely on three approaches:

  • Direct APK sideloading – IT admins push app installation files (APKs) directly to devices through the MDM console, bypassing any app store entirely.
  • OEM-specific app stores – Some non-GMS device manufacturers, like Amazon with its Appstore, maintain their own app marketplace as a Play Store alternative.
  • MDM-hosted app catalogs – Platforms like Hexnode can host enterprise APKs in a private app repository and silently deploy them to enrolled devices; apps update the same way, with no user action required.

This distribution model has a tradeoff. It gives IT admins tighter control over exactly which app versions run on which devices, since nothing installs without going through the MDM. But it also means admins take on the responsibility that Google Play normally handles automatically, like vetting app updates and managing version rollouts.

For fleets built entirely around in-house or line-of-business apps, this isn’t much of a hurdle. For fleets that depend on public consumer apps, it’s a bigger planning consideration, since not every app is packaged for sideloading or available through OEM stores.

Additional info ?

Hexnode UEM also empowers your organization with multiple methods of enrolling Fire OS devices. Fire OS is a mobile OS crafted on the foundation of Android Open-Source Project, crafted by Amazon for their devices. With proprietary software, a content-focused custom interface, and strong ties to Amazon’s storefronts and services, Fire OS is a unique blend of technology and convenience.

FAQs

Yes, but non-GMS devices don’t get automatic updates from Google, so the OEM or IT admin is responsible for delivering firmware and software updates. An MDM platform can help by scheduling and pushing these updates remotely, but the update cadence depends on manufacturer support rather than Google’s release schedule.

Since there’s no Play Store to vet apps automatically, IT admins should source APKs directly from verified developers or trusted enterprise repositories, not third-party download sites. Checking digital signatures and using an MDM-hosted private app catalog reduces the risk of installing tampered or malicious APKs. This vetting responsibility shifts entirely to the organization once Google Play is out of the picture.

Standard Firebase Cloud Messaging, which relies on GMS, isn’t available on non-GMS devices, so enterprise apps can’t use it for real-time push notifications. Developers typically need an alternative messaging service or must rely on the device’s periodic check-in cycle instead. This is a separate limitation from MDM command delivery, though both stem from the same missing GMS infrastructure.

Let’s get this show on the road! ?

In conclusion, the availability of GMS on an Android device can often be a deciding factor in one’s choice of device. The two main situations that could prevent devices from having access to GMS are when the devices do not come with GMS (like the Amazon Kindle) or when they join a closed network. So, whether you’re an individual or an enterprise, it’s important to weigh the pros and cons and choose the best Android device that fits your needs.

Hexnode UEM provides a comprehensive solution for organizations looking to manage their non-GMS devices effectively. It also offers seamless device management by supporting various enrollment methods and tackling non-GMS device challenges. So, get ready to take control of the technology for your enterprise with Hexnode UEM and launch it into action!

Share
Lizzie Warren
Lizzie Warren

A lil clumsy and a whole lot smiley, I'll bump into you with a smile...