View Single Post
Posts: 214 | Thanked: 140 times | Joined on Aug 2010
#37
Originally Posted by petur View Post
I now have ZapLoc running fine, and updating my latitude location using cell only. Works great
Glad you like it. I think there may be room for improvement on the cell-mode, though.

Now, it polls the cell just like it was previously polling the GPS. However, you don't NEED to poll the cell at intervals, because it doesnt' take any new power to keep that on. So the idea is to simply turn the "cell mode" location on, keep it on, and only change when it changes. I havn't figured out the details of that yet, but I think I will do that eventually.

Also for GPS mode, I want to have a mode where it instead of stopping completely, switches to cell tower, then waits for cell-tower switch, and THEN does a new try on the GPS (this is what I had planned for the UI option "only when cell tower changes" for interval, but this isn't implemented yet)

Originally Posted by petur View Post
I had one weird update for a completely wrong location. It seems to be some kind of default location that is set before the cell tower location is found - I've seen this flash by shortly in map apps.

Could it be ZapLoc is not correctly waiting for the cell position?
ZapLoc itself ineed DOESN'T wait, but defaults to "last position used", but it's not ZapLoc that posts to latitude, it's the ZapLoc-Daemon, and that *DOES* wait for a mode=2 (celltower) fix (run it with verbose to see it spew stupid amounts of details about what it is doing)

Code:
python /opt/zaploc/zaploc-daemon.py -v
That will shut down the old daemon and start a new one in XTerm, spewing crap.

When you are done reading it, you can CTRL-C it and restart the background daemon with:

Code:
python /opt/zaploc/zaploc-daemon.py -d
Could be fun if you are bored

/Z