Hi Justin, **Setup** - Use case: oil palm pollination records, one sighting per palm, ~100–150 saves per device per day. Sabana de Torres, Santander, Colombia. No mobile coverage in the field; devices have no SIM and no data, so no A-GPS (they only see Wi-Fi occasionally at the office). - New devices: 11 × Ulefone Armor X13 (Android 13, MediaTek Helio G36), CyberTracker Classic build 607 installed from managed Google Play (ManageEngine MDM, location services forced on, Play auto-updates). - Old devices: Samsung J2 Core / A01 Core / A03 Core / A04e and Moto G04s, still on builds ≤ 571 (never updated, no connectivity). Same application on all devices. - Desktop: 3.533 (updating to 3.537). - Application: track timer = 1 s; “Take GPS” on the Save buttons; screens are a keypad (palm number) plus element lists. **Problem** Since the app updated to the new system screens (build 596+, now 607), every Save opens the new “Take GPS” satellite screen and waits from 5 s to several minutes before the sighting is saved. In a video of a worker under palm canopy the sky plot shows 14 satellites, 6 of them used in the fix, and it still waits more than 5 s before returning to the palm-number screen. Workers end up pressing “Skip GPS” (sightings saved without coordinates) or complain that the new phones are “slow”. On the old devices with build ≤ 571 and the same application, Save is instant: the 1 s track timer keeps the GPS connected and the sighting takes the current fix. What I tried on the Ulefone: - Required accuracy 1 m: waited ~20 minutes. 20 m and 80 m (default): almost the same long wait. So the wait does not seem to depend on the accuracy threshold; it looks like the screen waits for a new fix (or several fixes) after it opens instead of using the position the track timer already has. - We suspect the GPS is released between sightings (e.g. when the screen turns off between palms), so every Save starts a new acquisition; without assistance data that is 30 s to minutes here. - Location permission is “precise” and “allow all the time”, battery unrestricted. **Questions** 1. Is the new Take GPS screen designed to require a fresh fix (fix count / accuracy) after it opens, rather than using the last valid fix from the track timer as before? Is there any setting (app Options or Application Properties → GPS) to get the previous behaviour back, e.g. “use last track fix if younger than N seconds”? 2. With a 1 s track timer, does build 607 keep the GPS connected all the time (as the FAQ documents for intervals ≤ 60 s), including when the Take GPS screen is closed and the display is off? We see re-acquisition on every save. 3. “Skip GPS” and the X button were reported as not responding offline on build 596 in the “Improvements to CyberTracker Classic” thread. Is that fixed in 607? 4. As a fallback, is build 571 (Qt5) expected to work on Android 13, or is there a pre-596 Qt6 build (e.g. 595) available for download? We can pin the version through the MDM. I can send the application MDB, the video and device details privately. Thanks a lot for the work on Classic.
Hi Julian,
Could you please send me a CTX of your application?
Some things:
- Upgrade to build 610 as the GPS track timer was getting turned off in some cases
- Nowadays, regardless of the track timer frequency, the GPS track is always on in the background
- You should set the “Sighting fix count” to “1” in the “GPS” page of the Edit Application dialog
- Yes, 571 will probably work fine. Qt6 was required due to Play Store publishing requirements
Cheers,
-Justin