View Single Post
Posts: 214 | Thanked: 140 times | Joined on Aug 2010
#327
Originally Posted by wurtel View Post
I don't have mr_jrt's problems, but I do have a request.
Could more options for shorter update periods be added? 5 minutes is now the minimum, but I often don't find that enough. 2 minutes or perhaps also 1 minute would be much appreciated.

I'd fix this myself but unfortunately the so-called source package only contains compiled python files. I also wanted to add a filter for updates, as when I'm home about 50% of the updates say I'm at a house 150 meters away. (There's no cell tower there!), In the old zaps-new-latitude-updater.py I had hacked in some code to filter such updates, but that script doesn't handle the new oauth authentication to Google
As for the accuracy, I'd suggest to do what I do - assuming you have WiFi in your house. Set your house as a ZapLoc and set it to auto-check-in based on WiFi. it will use the GPS position you set in the WiFi for as long as you are within that WiFi range.

The lowest time is actually 2.5 minues coz it doubles the speed on charger.

You could probably edit the boot startup file to set the interval w. the command line option (which will override the config file), i.e. edit /etc/event.d/zaploc and add something like "-i 1" before "--boot"

/Z
 

The Following 2 Users Say Thank You to MasterZap For This Useful Post: