thegman | # 31 | 2011-05-17, 09:07 | Report

Hi MasterZap,

Could I request a feature to back off on the frequency of location updates as the battery life decreases and perhaps even turn it off completely if it drops below 15% charge (this is what google maps on Symbian does, I believe -- update only if cell tower changes, slowly falling back on update frequency as charge drops)

Having all those values use configurable would be even better

Thanks for your work so far. Much appreciated.

CasTTeLLo | # 32 | 2011-05-17, 10:07 | Report

this is so cool mate.......tq....

---

Last edited by CasTTeLLo; 2011-05-17 at 12:32. Reason: my mistake...

petur | # 33 | 2011-05-17, 10:16 | Report

I now have ZapLoc running fine, and updating my latitude location using cell only. Works great

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?

MasterZap | # 34 | 2011-05-17, 10:20 | Report

Correct, I'll add this as a dependency.

It's suprisingly hard (unless there is a bleeding obvious method I am unaware of) to figure out what *debian level* packages are dependencies on a python app... :/

/Z

CasTTeLLo | # 35 | 2011-05-17, 10:34 | Report

how to move and add new location on foursquare or fb?

MasterZap | # 36 | 2011-05-17, 11:22 | Report

You can't create spots for the other services, you can only create ZapLoc's from existing spots.

At least... not yet (and I'm not sure I plan to do that - don't hold your breath for that feature any time soon)

For now:

• For gowalla, use http://m.gowalla.com
• For foursquare, use http://www.cotchin.com/m/
• I don't know about facebook, sadly, touch.facebook.com used to sort-of work, but now they broke it

/Z

MasterZap | # 37 | 2011-05-17, 12:23 | Report

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)

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)

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:

Could be fun if you are bored

/Z

thegman | # 38 | 2011-05-17, 12:28 | Report

I used this bit of python code (uses dbus) for listening to CellID changes when I threw together "Rest in Peace": http://talk.maemo.org/showthread.php...628#post428628

It could be modified for your needs to only ask location updates when the CellID changes

petur | # 39 | 2011-05-17, 13:01 | Report

(from http://wiki.maemo.org/Documentation/...cation_methods)

so for a short time it may give the center of the country as position... *sigh*

MasterZap | # 40 | 2011-05-17, 13:21 | Report

Right, but that comes in with "mode=0" which I ignore (each fix comes in with a "mode", where 0 is "crappy guess like center of coutry", 1 is... donno what... 2 is a celltower fix and 3 is a gps fix)

I only bother about mode 2 and 3 in GPS mode, and only mode 2 in cell mode.

/Z