{"action":"created","issue":{"url":"https://api.github.com/repos/tananaev/traccar-client-android/issues/315","repository_url":"https://api.github.com/repos/tananaev/traccar-client-android","labels_url":"https://api.github.com/repos/tananaev/traccar-client-android/issues/315/labels{/name}","comments_url":"https://api.github.com/repos/tananaev/traccar-client-android/issues/315/comments","events_url":"https://api.github.com/repos/tananaev/traccar-client-android/issues/315/events","html_url":"https://github.com/tananaev/traccar-client-android/issues/315","id":294391280,"number":315,"title":"Fused location provider giving very inaccurate positions","user":{"login":"garyvdm","id":352175,"avatar_url":"https://avatars2.githubusercontent.com/u/352175?v=4","gravatar_id":"","url":"https://api.github.com/users/garyvdm","html_url":"https://github.com/garyvdm","followers_url":"https://api.github.com/users/garyvdm/followers","following_url":"https://api.github.com/users/garyvdm/following{/other_user}","gists_url":"https://api.github.com/users/garyvdm/gists{/gist_id}","starred_url":"https://api.github.com/users/garyvdm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/garyvdm/subscriptions","organizations_url":"https://api.github.com/users/garyvdm/orgs","repos_url":"https://api.github.com/users/garyvdm/repos","events_url":"https://api.github.com/users/garyvdm/events{/privacy}","received_events_url":"https://api.github.com/users/garyvdm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-02-05T13:24:19Z","updated_at":"2018-02-06T07:20:27Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"The new fused location provider, added by commit e0296a9, is returning very inaccurate positions.  \r\n\r\nWhen on medium accuracy, the data is useless. Every position received is inaccurate. \r\n\r\nWhen on high accuracy, the situation is much better. Most positions are accurate, but we still get occasional position that is inaccurate.\r\n\r\nCompared to before when the fused location provider was added, and we could select the GPS provider, we would get an accurate position on every point received.\r\n\r\nThe following images show tracks recorded by Traccar android client running on a Samsung. The black line is the route that the rider is known to have followed. So anything off the route shows an inaccuracy.\r\n\r\nGPS Provider (Dec 2017)\r\n![old](https://user-images.githubusercontent.com/352175/35806356-e0bcbb58-0a87-11e8-9dc7-1d00e24d5cb6.png)\r\n\r\nFused location provider on Medium accuracy (Feb 2018)\r\n![new_medium_accuracy](https://user-images.githubusercontent.com/352175/35806426-2183eab2-0a88-11e8-8459-2a34d6263523.png)\r\n\r\nFused location provider on High  accuracy (Feb 2018)\r\n![new_high_accuracy](https://user-images.githubusercontent.com/352175/35806439-2ce667fe-0a88-11e8-8762-5fec24be9d37.png)\r\n\r\nPlease can we restore option to select a provider, so that we can select the GPS provider? I'm happy submit a patch, but I want to ok it with you first.\r\n"},"comment":{"url":"https://api.github.com/repos/tananaev/traccar-client-android/issues/comments/363332978","html_url":"https://github.com/tananaev/traccar-client-android/issues/315#issuecomment-363332978","issue_url":"https://api.github.com/repos/tananaev/traccar-client-android/issues/315","id":363332978,"user":{"login":"garyvdm","id":352175,"avatar_url":"https://avatars2.githubusercontent.com/u/352175?v=4","gravatar_id":"","url":"https://api.github.com/users/garyvdm","html_url":"https://github.com/garyvdm","followers_url":"https://api.github.com/users/garyvdm/followers","following_url":"https://api.github.com/users/garyvdm/following{/other_user}","gists_url":"https://api.github.com/users/garyvdm/gists{/gist_id}","starred_url":"https://api.github.com/users/garyvdm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/garyvdm/subscriptions","organizations_url":"https://api.github.com/users/garyvdm/orgs","repos_url":"https://api.github.com/users/garyvdm/repos","events_url":"https://api.github.com/users/garyvdm/events{/privacy}","received_events_url":"https://api.github.com/users/garyvdm/received_events","type":"User","site_admin":false},"created_at":"2018-02-06T07:20:27Z","updated_at":"2018-02-06T07:20:27Z","author_association":"CONTRIBUTOR","body":"> I'm not sure why you even trying medium.\r\nWhen upgrading from v5.5 to newer, the settings change from using GPS provider to Medium accuracy, as that is the default.  So when upgrading, you need to go change the accuracy. I was not aware of that.\r\n\r\n>  High accuracy should use GPS when available, so if you get inaccurate location it probably means that device didn't have GPS signal.\r\n\r\nI do understand the intent for the FusedLocationApi. It is nice to get a position when indoors. But for the data that I posted, the phone was outdoor the whole time, admittedly the weather was overcast. \r\n\r\nMaybe the FusedLocationApi can be configured to try get a gps fix for longer. I'm going to go read the code for the lostzen FusedLocationApi, to see if this is possible, or if I can find some other way to make an improvement.\r\n\r\nThank you for the response.\r\n"}}
{"actor":{"display_login":"garyvdm"}}