new app doesn't work PERIOD. :(

Antony7 days ago

I was really excited to try the new app, if it improves the battery usage as intended without sacrificing quality it would have been prefect specially that the concept of only using GPS while moving and dynamic distance updates based on the speed are neat. However I tested the new app on 3 different android devices (Nokia running pure android, a xiaomi with lineageos and a xiaomi with miui) all of which used to have the old traccar client on which worked as intended

The new app however, unfortunately doesn't work at all on any of these devices. The first attempt was to set
accuracy : high
distance : 30
Heartbeat : 0
offline buffering : off
disable elasticity: off
stop detection : on

walked about 1 km which means that it should have updated the location about 30 times .
Result: logs show that walking is detected but didn't end up sending post requests to update the location at all!


So I did another test

accuracy : high
distance : 30
Heartbeat : 0
offline buffering : off
disable elasticity: on
stop detection : off

walked about 2 KMs which means that it should have updated the location about 30 times .
Result: logs show that walking is detected but didn't end up sending post requests to update the location once only !


Did another test

accuracy : Medium
distance : 30
Heartbeat : 0
offline buffering : off
disable elasticity: off
stop detection : off

walked about 1 km which means that it should have updated the location about 30 times .
Result: logs show that walking is detected but didn't end up sending post requests to update the location at all!


I have noticed that even though accuracy was set to high and walking is detected, but the gps was never turned on. So I thought maybe if I foced the gps to remain on with another app, maybe traccar will end up sending the updates once ever 30 meters

and did one last test

accuracy : high
distance : 30
Heartbeat : 0
offline buffering : off
disable elasticity: on
stop detection : on

walked a distance of about 1.5 km
and the result is also 1 or 2 location updates were sent as http requests only.

Made sure no background restrictions for traccar. persistent notification showing as usual. GPS is turned on, no power saving options enabled on device. replicated on 3 devices with the same result. Internet working just fine. logs don't show that http request is even being attempted to be sent.

As much as I would have loved the new app to deliver on improving the battery usage while adding new useful features, and I am sure you will continue working on trying to improve it, but I will revert back to the old version on my main device (with an apk I took as a backup) and will be more than happy to test the upcoming versions when you release them on one of the devices I use for testing.

Anton Tananaev7 days ago

Thanks for the feedback. Can you please try version 9.2.0. It has some fixes, but also more logging. Send us logs if it still doesn't help.

panhard7 days ago

It works for me on IOS. What's not so good is that it starts sending data after 100 meters. It also lacks the setting that would allow it to send data based on time, not distance.

Buaya-kun7 days ago

Confirmed the heartbeat is working on v9.2.0, currently I'm doing field testing to see if there any other issue.

panhard7 days ago

Why isn't version 9.2.0 available in the Appstore yet?

Anton Tananaev7 days ago

Waiting for Apple approval. It'a already submitted for review.

Antony7 days ago

Will run a couple of tests later on with 9.2 and share the logs if needed. Thanks for the swift update and the frequent, quick engagement with us on the forum

panhard7 days ago

What makes my speed about a quarter of the actual speed? At 130km/h it shows 36km/h.

Anton Tananaev6 days ago
panhard6 days ago

One more comment: GPS positions used to have 6 decimal places. Now they have 12 decimal places. I think it's completely unnecessary, it doesn't improve the accuracy at all.

Anton Tananaev6 days ago