Hi, I have a pixel 7a that I use to track my location. It seems like sometimes, the app fails to send new location to server when resuming from detected stop. I noticed today that my location was still showing at a grocery store in another city (that I visited yesterday afternoon). The device continued to send heartbeats with no change in location even as I drove 40 miles.
All that out of the way, I think the client logs do not go back far enough to see what happened in that moment of time. I will try to catch it earlier next time. Do you have any advice for me when looking at these logs. Would it be appropriate to add an option minimum interval of location update that ignores everything else and sends location anyway?
Feel free to post the logs here to check. In normal case it should detect movement within 200 meters.
I feel pretty sure that this is because I am using grapheneos. Seems that the physical activity only works when I allow Google play access permission to my location all the time.
^ which makes perfect sense as the activity recognition API is part of Google play services. I just figured all it needed was permission to physical activity. That was incorrect assumption.
Hi, I have a pixel 7a that I use to track my location. It seems like sometimes, the app fails to send new location to server when resuming from detected stop. I noticed today that my location was still showing at a grocery store in another city (that I visited yesterday afternoon). The device continued to send heartbeats with no change in location even as I drove 40 miles.
All that out of the way, I think the client logs do not go back far enough to see what happened in that moment of time. I will try to catch it earlier next time. Do you have any advice for me when looking at these logs. Would it be appropriate to add an option minimum interval of location update that ignores everything else and sends location anyway?