Special Alert: Customer Challenges When Implementing Android 11 Devices

CSSI Technologies has recently encountered numerous customers who have run into major challenges when attempting to deploy mobile computers running Android 11. These customers discover that applications which have worked with prior versions of Android suddenly will not function.

This problem can occur either when attempting to deploy newly purchased Android 11 devices, or even when older devices return from a manufacturer repair depot upgraded to Android 11, as commonly occurs.

Even if you have not yet upgraded to Android 11 devices, this issue is still relevant to you… because you will face it when you eventually upgrade.

The Android 11 Problem

The root issue results from Google’s implementation of ‘scoped storage’. This is a security measure which changes the way apps can store and access files on a device, with the goal of protecting the privacy of app and user data. Scoped storage was originally introduced with Android 10, but new enhancements delivered with Android 11 enforce greater data protection and have played havoc with some companies’ operations.

Typical issues and questions associated with an Android 11 / scoped storage issue:

1. Why won’t my provisioning barcodes work on my Android 11 devices?
2. Why are my device’s configurations no longer working on my Android 11 devices?
3. Why are my MDM deployment packages not working on my Android devices?
4. Why won’t my WMS application work on my Android 11 devices.
5. What new firmware works with my current applications?

Scoped storage is a new Android reality and will be present in future OS versions. So, companies which might skip Android 11 will still encounter it in 13 and beyond.

Working the Scoped Storage Problem With CSSI

The CSSI team has recently worked with numerous companies to solve the scoped storage challenge. We have developed a number of configuration and upgrade methodologies which have enabled customers to get back up and running. We are well-prepared to help you resolve your own Android 11 issues.

Consider the following recent case study…

Case Study – Android 11 Fixed

A major industrial manufacturer with a broadly distributed fleet of mobile devices managed with SOTI MobiControl (MDM) asked CSSI for help. Device configurations had been stable for some time, but when attempting to deploy new handhelds, critical applications would suddenly not work. CSSI researched the issue and determined that it was caused by configurations which would not work under Android 11, the OS installed on the recently purchased devices.

CSSI’s technical team examined the customer’s deployment environment and designed Zebra StageNow and SOTI MobiControl profiles which successfully worked around the issue. This customer is now able to run Android 11 devices side by side with devices on older versions of Android and is prepared for future Android updates as well.

Contact CSSI To Prepare for Android 11

Whether you are already experiencing issues, or are planning to upgrade to new devices, you are welcome to contact CSSI to discuss your configuration. We can help you to determine what issues you will experience with Android 11 and develop a plan to proactively resolve the problem. To learn more, please contact CSSI Technologies.

FAQ – Frequently Asked Questions About Upgrading Mobile Devices to Android 11

Q: How can we tell whether our current applications and configurations will break when we move to Android 11?

A. Start with an inventory of everything that reads or writes files on your devices: line-of-business apps, WMS clients, terminal emulators, industrial browsers, MDM agents, and staging profiles. Ask each software vendor directly whether their current release is certified for Android 11 and scoped storage. Then pay close attention to anything that relies on shared folders such as the root of internal storage or the SD card, which is the most common point of failure. Apps that store settings files, log files, or import/export data in common locations are the most likely to stop working. Finally, check which Android API level each app targets, since apps updated to target Android 11 (API level 30) lose the “legacy storage” exception that let many older apps keep working under Android 10.

Q: Should we test before rolling out, and what should a pilot look like?

A. Yes. Never let your first Android 11 device be one headed to the warehouse floor. Set aside a small number of devices in a test environment that mirrors production, including the same Wi-Fi network, MDM policies, staging barcodes, and back-end systems. Run each critical workflow end to end: enrollment, provisioning, app installation, login, scanning, printing, and data sync. Document every failure and its fix before you expand to a pilot group of real users at one site. Only after the pilot runs cleanly through a full shift cycle should you schedule a broader rollout.

Q: Our staging barcodes and MDM packages have worked for years. What has to change?

A. Provisioning tools such as Zebra StageNow and MDM platforms like SOTI MobiControl often push configuration files, certificates, and app settings to specific folders on the device. Under Android 11’s stricter scoped storage rules, many of those destinations are no longer accessible to the apps that need them. In most cases the profiles must be rebuilt to deliver files to approved locations, grant the right permissions, or use the vendor’s managed configuration options instead of loose files. Plan to maintain separate staging profiles for Android 11 devices and for older devices until your fleet is fully transitioned.

Q: Can we run Android 11 devices alongside our existing Android 8, 9, and 10 devices?

A. Yes, and most organizations will have to, since fleets are rarely replaced all at once. Running a mixed fleet successfully requires OS-specific configuration profiles, app versions confirmed to work on every OS in use, and MDM grouping that delivers the correct package to each device. Also keep in mind that devices sent out for repair often come back from the manufacturer’s depot upgraded to a newer OS, so a device that left as Android 10 may return as Android 11. Your process for returning repaired devices to service should include a check of the OS version and re-staging with the correct profile.

Q: Can we avoid this by skipping Android 11 and waiting for a later version?

A. No. Scoped storage is a permanent part of Android, and its restrictions continue in Android 12, 13, and beyond. Skipping Android 11 only delays the work, and in some cases makes it bigger because more changes accumulate between versions. Delay also carries risk: older OS versions eventually stop receiving security patches, and new devices from Zebra, Honeywell, and Datalogic ship with current Android releases. The better approach is to make your applications and configurations scoped-storage compliant now, so future OS upgrades become routine rather than disruptive. CSSI can review your current deployment and help you build a migration plan.