New traccar issues and feedback
No, that's not a crash stack.
I took the phone I use for testing with the gps stuck constantly on on it for a walk. And traccar didn't detect the walking activity whatsoever and neither did the gps go off after being stationary one more time.
Will have to test with other devices as well to see what is going on, whether it is a device bug or traccar related one .
Regarding the issue with traccar not starting on device without play services, I am not sure how to get the crash stack you asked for honestly.
If you don't get any activity logs, it means either you didn't provide permissions or something is not right in your Google Play setup. Maybe this specific functionality is somehow disabled.
I am sure that the "physical activity" permission was granted and it isn't an issue with the device most probably as the old traccar was able to detect activities just fine, unless the method used to detect the activity changed. But the only way to be 100% sure about the root cause of the issue is when I replicate it on a bunch of devices I have for testing which I will try to do in the upcoming days.
May not be related to your issue at all, but I had some weird things happening with the new client until I cleared the app's cache and storage and configured it again. I figured it may have had some conflicting settings with the old client app or something. Worth a try...
Any new updates that you need to test?
Still working on some major changes.
My initial test with the new update that you just released.
1- Fixed, the gps doesn't remain constantly on despite that the device is completely stationary.
4- The test device I have without play services still can't open traccar, it shows the splash screen and crashes right away
Questions:
A- What is the new toggle "use system location" ? what does it do?
B- Won't you support stationary heartbeat ?
I will extensively test this new version within the upcoming couple of days to test how accurate it is compared to the current production version, and how fast it turns on GPS when starting to move (Highest accurancy) and how efficient it is when it comes to battery usage.
If the used server is down or the user's internet isn't working, traccar remain stuck on the splash screen when opening it after being cleared from ram for 30 seconds which means that it must probably is sending a http request and waiting for it to timeout before showing the traccar ui. The unique thing about this is it happens even when continuous tracking is toggled off !!
A - it's to not use Google Play services for location.
B - it should be supported.
The hanging is now fixed. It was actually unrelated to the new changes. It was a bug in the original app as well. New Android link:
https://traccar.nyc3.digitaloceanspaces.com/download/app-release.apk
These are logs from the device without play services that traccar crashes on start on.
These were obtained with
adb shell dumpsys activity exit-info org.traccar.client
Is this what you are looking for?
ACTIVITY MANAGER PROCESS EXIT INFO (dumpsys activity exit-info) Last Timestamp of Persistence Into Persistent Storage: 2026-06-07 17:13:37.153 package: org.traccar.client Historical Process Exit for userId=10163 ApplicationExitInfo #0: timestamp=2026-06-07 18:19:11.159 pid=11987 realUid=10163 packageUid=10163 definingUid=10163 user=0 process=org.traccar.client reason=5 (APP CRASH(NATIVE)) status=11 importance=100 pss=0.00 rss=0.00 description=crash state=empty trace=null ApplicationExitInfo #1: timestamp=2026-06-07 18:18:24.674 pid=11841 realUid=10163 packageUid=10163 definingUid=10163 user=0 process=org.traccar.client reason=5 (APP CRASH(NATIVE)) status=11 importance=100 pss=0.00 rss=0.00 description=crash state=empty trace=null ApplicationExitInfo #2: timestamp=2026-06-07 17:01:28.726 pid=30884 realUid=10163 packageUid=10163 definingUid=10163 user=0 process=org.traccar.client reason=3 (LOW_MEMORY) status=9 importance=400 pss=18MB rss=69MB description=null state=empty trace=null ApplicationExitInfo #3: timestamp=2026-06-07 16:35:01.230 pid=30741 realUid=10163 packageUid=10163 definingUid=10163 user=0 process=org.traccar.client reason=5 (APP CRASH(NATIVE)) status=11 importance=100 pss=0.00 rss=0.00 description=crash state=empty trace=null ApplicationExitInfo #4: timestamp=2026-06-07 09:42:05.023 pid=1214 realUid=10163 packageUid=10163 definingUid=10163 user=0 process=org.traccar.client reason=3 (LOW_MEMORY) status=0 importance=400 pss=18MB rss=62MB description=null state=empty trace=null ApplicationExitInfo #5: timestamp=2026-06-07 09:33:18.045 pid=856 realUid=10163 packageUid=10163 definingUid=10163 user=0 process=org.traccar.client reason=5 (APP CRASH(NATIVE)) status=11 importance=100 pss=0.00 rss=0.00 description=crash state=empty trace=null