Android Field App Fails on Older Chromebooks
Field services uses 300 Acer Chromebook Spin 511 devices and 45 older Lenovo 100e Chromebooks. The team relies on an Android app, FieldOps, which captures photos, scans Bluetooth asset tags, and caches work orders offline. FieldOps is published as an Android app and a responsive web app; the web app cannot use Bluetooth scanning and has no offline cache. The Android app is force-installed for the Field Services OU and works on the Acer devices. On the Lenovo devices, users see 'App not available for this device' in the Play Store, and the force-install policy shows a failed status. The Lenovo devices are still under warranty but are three years old. The team has 10 weeks before peak season and cannot change the workflow; supervisors need photo and Bluetooth evidence offline.
1. What are the most likely reasons the Android app fails on the Lenovo devices, and what should be checked first?
Read the worked answer
A force-install policy cannot override app compatibility. The most likely causes are that the Lenovo model is not Play Store certified for Android apps, its Android runtime or ChromeOS version is below the app's minimum requirement, the app is restricted by device model or country in managed Google Play, or Play Store is not enabled for that OU. The message 'App not available for this device' points more strongly to device compatibility than to a simple policy typo, but policy still needs to be eliminated.
Check the Field Services OU to confirm Play Store and Android app support are enabled. In managed Google Play, confirm FieldOps is approved for the domain and not limited to a device allowlist that excludes the Lenovo model. Compare the app's minimum Android SDK and hardware requirements with the Lenovo's ChromeOS and Android runtime versions. Test with one Lenovo device: confirm whether Play Store itself opens, whether other Android apps install, and whether FieldOps appears in the store. If Play Store works but FieldOps is absent, the issue is app compatibility or distribution; if Play Store is absent, the issue is device or OU enablement.
2. What remediation options exist for the 45 Lenovo devices, and which is most defensible given the workflow requirements?
Read the worked answer
There are three realistic options. First, replace the 45 Lenovo devices with a model certified for Android apps and compatible with FieldOps. Second, keep the Lenovo devices but change the workflow to the web app, which fails the Bluetooth and offline requirements. Third, attempt to sideload or repackage the Android app, which is unsupported, creates update and security problems, and is unlikely to work if the device lacks Android app support.
Given that supervisors need offline photo capture and Bluetooth scanning, the web-app fallback does not meet the requirement. The most defensible remediation is to replace the 45 incompatible devices with a supported model and standardize on the Acer configuration. Before purchasing, validate FieldOps on one replacement device with a real offline work order and a Bluetooth scan, not just a Play Store install. If replacement is impossible, the only honest option is a documented exception with a different device or workflow; do not claim that a force-install policy will make an incompatible device work.
3. What policies and rollout controls should be verified before expanding the fix to all field devices?
Read the worked answer
Verify that Play Store and Android app support are enabled in the Field Services OU, that FieldOps is approved in managed Google Play, and that the force-install policy targets the correct app package and OU. Check that the app's permissions are allowed, especially camera, Bluetooth, and storage, and that any runtime permission blocks are not silently preventing scans. Confirm that offline caching is not blocked by a policy that clears local data or restricts storage.
Use a pilot group of five devices across the Acer and replacement models. Test install, first launch, camera capture, Bluetooth scan, offline work order completion, reconnect and sync, and app update. Verify the app version reported by policy and confirm that failed installs generate a visible status rather than silently disappearing. Keep the web app available as a read-only fallback, but do not describe it as equivalent. Finally, document the device model requirement in the purchasing standard so the same incompatibility does not return in the next refresh.