CAT S61 — FLIR Lepton thermal camera
| Manufacturer | Bullitt Group Ltd (CAT-licensed) |
| Chipset | Qualcomm Snapdragon 630 |
| Android version | 9 (BSP frozen — no path to Android 10+) |
| Camera stack | Dual-HAL — standard rear camera + FLIR Lepton thermal module |
| Sectors | Building inspection, electrical fault-finding, leak detection, search and rescue, field survey |
| Device status | EOL software support. Hardware operational. |
The install path
Both apps arrived via Google Play Store — the official Android distribution channel. This is not a sideloaded APK story. This is the primary install path used by hundreds of millions of users, on a device that Google's own platform allowed the install to proceed on.
Google Play's compatibility filtering works by reading publisher-declared manifest attributes: minSdkVersion, uses-feature, and device catalogue exclusions. When a publisher doesn't declare requirements, Play has nothing to filter against — the device looks compatible because no incompatibility was asserted. The CAT S61 is a Play-certified Android device. Sonos declared nothing. Play installed it.
Google bears responsibility for a distribution system that passes the entire burden of compatibility declaration to publishers, with no independent verification, no device-profile matching against known non-standard hardware stacks, and no friction added for EOL devices with specialist sensors. The gate exists. It was left open.
What happened
Two apps were installed on the same CAT S61 device within the same testing window. The outcomes were opposite.
✗ Sonos (ACR)
Force-installed without compatibility check. Probed microphone and sensor APIs on startup — almost certainly for Trueplay acoustic calibration. On the dual-HAL camera stack, this destabilised cameraserver. Multi-hour crash-recovery cycle followed.
✓ State Farm
Checked compatibility at install. Identified the CAT S61 as incompatible. Declined cleanly. Clear dialog, direct path to uninstall. Thirty seconds. No device impact.
The crash cycle
After the Sonos app destabilised cameraserver, Android's exponential backoff recovery ran as follows. Click the sequence to understand the technical term for what this produces.
→ cameraserver crash → restart in 60 000ms
→ cameraserver crash → restart in 120 000ms
→ cameraserver crash → restart in 240 000ms
→ cameraserver crash → restart in 480 000ms
During this period the device was non-functional for its primary purpose. The user had no indication the app was the cause. They could not use the thermal camera. They could not use any camera-dependent feature.
Uninstalling the app after the fact did not immediately resolve the degraded system_server state.
What should have happened
The Sonos app is not a camera app. It had no legitimate reason to access the camera HAL. A uses-feature declaration with required="false" and a runtime check on first launch would have prevented the installation from proceeding on this device.
Alternatively, the Play Console device catalogue allows publishers to exclude specific device models by name. catmobile_s61 could have been excluded without any code changes.
The cost of either fix: low. The cost of not doing it: paid entirely by the user.
Inference note
The assertion that the Sonos app was probing sensor APIs for Trueplay calibration is inference based on Trueplay's documented behaviour and the timing of the crash. The crash trigger is confirmed. The specific internal mechanism is not. This page does not assert more than the evidence supports.