Device
- Model: Samsung Galaxy Tab S10 FE, SM-X520 (Wi-Fi)
- Android: 16 / One UI 8.0
- Build fingerprint:
samsung/gts10fewifixx/gts10fewifi:16/BP2A.250605.031.A3/X520XXS7BZB7_OXM7BZB7
- Google Play Services for AR: 1.54.260890093
Symptom
Session.resume() throws FatalException unconditionally on every launch. Native log:
android_data_source.cc:1073 Failed to register sensor to queue 0
android_sensors.cc:139
Failing sensor type varies: gyro uncal (handle 16, type 16) under client SDK 1.50/1.54; accel uncal (handle 43, type 35) under client SDK 1.44. Pattern is identical: enable → storm of SetPollTimeout inf → disable → register fails.
Device profile lookup falls back to generic (Found nothing for gts10fewifixx/gts10fewifi; falls back to Pw1Lu8:15).
Stack trace
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to resume activity: com.google.ar.core.exceptions.FatalException
at com.google.ar.core.Session.nativeResume(Native Method)
at com.google.ar.core.Session.resume(Session.java:1)
at com.google.ar.core.examples.java.helloar.HelloArActivity.onResume(HelloArActivity.java:302)
Minimal reproducer
Google's own unmodified hello_ar_java sample (samples/hello_ar_java from this repo), compiled with com.google.ar:core:1.54.0, installed on the device. Crashes on every launch. No custom session config, no custom camera config — stock sample, stock settings.
Timeline — this is a regression, not a pre-existing condition
- Through Apr 19: app worked correctly through multiple field sessions. ARCore client SDK was 1.44.0, no issues.
- Apr 19–22: No code changes on our side. Play Services for AR silently auto-updated on the device (current version: 1.54.260890093).
- Apr 22 onward:
Session.resume() fails on every launch with the above error.
- Play Services for AR version confirmed as the trigger: Version 1.53.2603406 was released April 19 (last known-good date). Version 1.54.2608900 was released April 22 (first broken date). The device auto-updated from 1.53 to 1.54 between April 19 and April 22 and has not worked since. Current device version: 1.54.260890093.
Critical observation: older ARCore apps still work on this device
AR Toolbox (a third-party ARCore app, presumably compiled against an older client SDK) runs successfully on the same device. Plane detection, surface tracking, and the calibration flow all work correctly. This confirms that:
- The device hardware is functional
- ARCore can work on this firmware
- The failure is specific to the new session initialization code path introduced in recent Play Services for AR versions
What was already ruled out
- Per-device state corruption (full factory reset performed — did not fix it)
- Per-package state (full
adb uninstall, new UID, fresh reinstall — did not fix it)
- Play Services for AR installation (storage cleared + reinstalled from Play Store — did not fix it)
- Our Session configuration (Google's own
hello_ar_java stock sample fails identically)
- Client SDK version (1.44, 1.50, and 1.54 all fail with the same native error)
Request
Please investigate the sensor queue registration code path introduced in Play Services for AR around version 1.54 for Samsung SM-X520 / One UI 8.0. The generic device profile (Pw1Lu8:15) may be enabling uncalibrated sensor features that this Samsung firmware cannot register to the sensor queue. A guard for devices where uncalibrated sensor registration fails, or a corrected device profile entry for gts10fewifixx, would fix this.
Additional context: the Samsung Galaxy Tab S10 FE is listed on Google's official ARCore supported devices page at developers.google.com/ar/devices (listed as supporting Depth API), confirming it is a certified ARCore device. Despite this, the native library logs Found nothing for gts10fewifixx/gts10fewifi and falls back to the generic profile Pw1Lu8:15. The device is certified on the webpage but absent from the internal device profile database — the generic fallback's changed behavior in 1.54 is what breaks it.
Device
samsung/gts10fewifixx/gts10fewifi:16/BP2A.250605.031.A3/X520XXS7BZB7_OXM7BZB7Symptom
Session.resume()throwsFatalExceptionunconditionally on every launch. Native log:android_data_source.cc:1073 Failed to register sensor to queue 0
android_sensors.cc:139
Failing sensor type varies: gyro uncal (handle 16, type 16) under client SDK 1.50/1.54; accel uncal (handle 43, type 35) under client SDK 1.44. Pattern is identical: enable → storm of
SetPollTimeout inf→ disable → register fails.Device profile lookup falls back to generic (
Found nothing for gts10fewifixx/gts10fewifi; falls back toPw1Lu8:15).Stack trace
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to resume activity: com.google.ar.core.exceptions.FatalException
at com.google.ar.core.Session.nativeResume(Native Method)
at com.google.ar.core.Session.resume(Session.java:1)
at com.google.ar.core.examples.java.helloar.HelloArActivity.onResume(HelloArActivity.java:302)
Minimal reproducer
Google's own unmodified
hello_ar_javasample (samples/hello_ar_javafrom this repo), compiled withcom.google.ar:core:1.54.0, installed on the device. Crashes on every launch. No custom session config, no custom camera config — stock sample, stock settings.Timeline — this is a regression, not a pre-existing condition
Session.resume()fails on every launch with the above error.Critical observation: older ARCore apps still work on this device
AR Toolbox (a third-party ARCore app, presumably compiled against an older client SDK) runs successfully on the same device. Plane detection, surface tracking, and the calibration flow all work correctly. This confirms that:
What was already ruled out
adb uninstall, new UID, fresh reinstall — did not fix it)hello_ar_javastock sample fails identically)Request
Please investigate the sensor queue registration code path introduced in Play Services for AR around version 1.54 for Samsung SM-X520 / One UI 8.0. The generic device profile (
Pw1Lu8:15) may be enabling uncalibrated sensor features that this Samsung firmware cannot register to the sensor queue. A guard for devices where uncalibrated sensor registration fails, or a corrected device profile entry forgts10fewifixx, would fix this.Additional context: the Samsung Galaxy Tab S10 FE is listed on Google's official ARCore supported devices page at developers.google.com/ar/devices (listed as supporting Depth API), confirming it is a certified ARCore device. Despite this, the native library logs Found nothing for gts10fewifixx/gts10fewifi and falls back to the generic profile Pw1Lu8:15. The device is certified on the webpage but absent from the internal device profile database — the generic fallback's changed behavior in 1.54 is what breaks it.