New traccar issues and feedback
On Android we don't use geofences. We use activity monitoring. But there are some known issues that we're working on.
Form-based protocol is the original protocol Traccar Client used for years, so it's not something new.
This is unrelated to server, but I've seen this issue, so need to investigate.
Do you have access to logs to see the crash stack?
1- Hopefully it will fix it because as of right now. New traccar is unusable due to high battery usage while user is stationary . This is a deal breaker
2- Yes it was the default for the old traccar before switching over to the previous sdk. I guess it isn't a big deal to switch back to form based payload parsing over an application/json one. However since I would imagine that everyone who used traccar within the past year had to migrate to parsing the payload as application/json rather than a form data it would have been nice to keep it this way so that servers don't need to be updated in order for things not to break for those who have their own servers. But again it isn't a deal breaker and easy to simply update on the server.
3- I disagree. I think it is related as I had tested with a local server and as long as I had that server up and running traccar would open in less than a second. The moment I killed the server and closed traccar from the recents page on android, it took around 10 seconds to get past the splash screen and this is consistent for at least the 10 times I tested this. Maybe there are other variables as well leading to this issue that you are looking into but the one mentioned in the original post is certainly another one
4- Will get them for you later on when I have access to that device again
1-On the highest accuracy, traccar constantly keeps the GPS active and in use even after more than 30 minutes of being completely stationary (phone sitting on a desk). I think you are encountring the same bug that the previous sdk used to encouter with play services until they released the workaround that fixed it https://github.com/transistorsoft/flutter_background_geolocation/commit/590b457b645c8598375019c3afe87d93a3518041 for reference : https://www.traccar.org/forums/topic/2-bugs-in-traccar-for-android/page/2/
2-The old traccar used to send the data as a json object with headers content-type application/json, now it switched over to application/x-www-form-urlencoded . Which is okay if someone inspects the payload and edits the server logic parsing location updates, but it would be better if it remained application/json payload in order to avoid having some servers being unable to parse location updates reducing the update friction for users.
3-With the new traccar, if the server used is down when the user opens traccar it will remain stuck on the splash screen for ages. I think it tries to send a location update first and waits for the request to time out before giving the user access to the app. However this isn't ideal, the app shouldn't wait for the request to timeout in order to give the user access to the app.
4- Device on lineage os 18.1 without google play services: Traccar crash on start, it doesn't even show the splash screen