mendhak
commented
5 years ago Not doing anything at the moment about this but wanted to write my thoughts in case I can revisit this later.
So I like this idea for what it does, which is the heartbeat. I tried to figure out who it would be implemented. I think to add such a feature, it would be added in here:
This increases complexity though, the app is already dense with logic and adding additional exceptions and bypasses already makes it quite hard to test and maintain.
On one hand I could hardcode to 5 minutes so that a position is logged anyway, but users who are looking to conserve battery may want that to be optional. If I make the duration configurable it will increase confusion and introduce an expectation that a log should have appeared at that interval, whereas Android OS does not really perform the movement check at regular intervals.
Eeeeeediot
Hi - I use GPSLogger to keep track of my kids location by feeding the data to restdb.io (custom URL feature) and working on it from there (I have geofence alerts and the like so we can stop them running in the house caked in mud;-). It works great but for one niggle, if they are stationary it saves power by not logging (good battery preservation) but then I cannot tell if they are just stationary or if the phone has died / app is turned off. Ideally it would be possible to force a log entry every X seconds but have this set much higher than the standard logging interval. e.g. I log every 5 seconds as standard but even if no movement want a log entry every 5 minutes and even if GPS is not available. I'm aware this will only work for so long due to dozing but kids rarely take their phone out of their hands so it usually has some movement to stop it sleeping.