On Android, expo-sensors stops every sensor when the activity goes to the background. SensorProxy.onHostPause stops it, and onHostResume starts it again: https://github.com/expo/expo/blob/d543d6a0932c00b67d670ca0663fe582a8901446/packages/expo-sensors/android/src/main/java/expo/modules/sensors/SensorProxy.kt#L55-L65 On iOS, BarometerModule keeps listening.
Use case: Snowmap records hiking and ski-touring tracks with expo-location's background updates. Those run a foreground service. Snowmap also logs the barometer once a second, because its altitude changes are far steadier than the GPS's. The recording runs with the screen off, so the barometer has to keep going in the background.
Android allows this. Since Android 9, an app in the background gets no events from a continuous sensor, unless it runs a foreground service. The recording already runs one. Only expo-sensors stops the readings.
Request: an opt-in, per sensor, to keep listening in the background. For example Barometer.setUpdatesInBackground(true), or an option on addListener. The default stays as it is. The app remains responsible for a foreground service, without which Android withholds the events anyway.
What we ship today: a patch that spares TYPE_PRESSURE in onHostPause and onHostResume. Measured on a Pixel 8 on 2026-11-01: a 36-minute drive, screen off, on battery, gave 2,089 readings, none more than 1.1 s after the last.
One trap for anyone patching it the same way: expo-sensors ships a precompiled AAR, which Gradle links instead of the patched source. The patch only takes effect with expo-sensors listed under expo.autolinking.android.buildFromSource in package.json.