The Following User Says Thank You to thegman For This Useful Post: | ||
|
2011-05-17
, 10:07
|
|
Posts: 335 |
Thanked: 51 times |
Joined on May 2010
|
#32
|
|
2011-05-17
, 10:16
|
Posts: 650 |
Thanked: 497 times |
Joined on Oct 2008
@ Ghent, Belgium
|
#33
|
|
2011-05-17
, 10:20
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#34
|
I'm still failing horribly at installing your tool....
the google-api-python-client doesn't install correctly. I went commandline and found out it is complaining about a simplejson package not being there (but it doesn't exist as separate package)
Any missing dependency?
Edit: the missing package is python-simplejson
The Following User Says Thank You to MasterZap For This Useful Post: | ||
|
2011-05-17
, 10:34
|
|
Posts: 335 |
Thanked: 51 times |
Joined on May 2010
|
#35
|
|
2011-05-17
, 11:22
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#36
|
The Following User Says Thank You to MasterZap For This Useful Post: | ||
|
2011-05-17
, 12:23
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#37
|
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?
python /opt/zaploc/zaploc-daemon.py -v
python /opt/zaploc/zaploc-daemon.py -d
|
2011-05-17
, 12:28
|
Posts: 51 |
Thanked: 48 times |
Joined on Jun 2010
|
#38
|
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.
|
2011-05-17
, 13:01
|
Posts: 650 |
Thanked: 497 times |
Joined on Oct 2008
@ Ghent, Belgium
|
#39
|
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)
LOCATION_METHOD_ACWP - Assisted Complementary Wireless Positioning: A method where device is located based on cellular base station to which device is registered to. SIM card and a network connection is needed for ACWP method. If no network connection is available, this equals to CWP. Application might receive MCC fixes before base station information from external location server is fetched and as a fallback if e.g. network is temporary unavailable.
|
2011-05-17
, 13:21
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#40
|
(from http://wiki.maemo.org/Documentation/...cation_methods)Code:LOCATION_METHOD_ACWP - Assisted Complementary Wireless Positioning: A method where device is located based on cellular base station to which device is registered to. SIM card and a network connection is needed for ACWP method. If no network connection is available, this equals to CWP. Application might receive MCC fixes before base station information from external location server is fetched and as a fallback if e.g. network is temporary unavailable.
so for a short time it may give the center of the country as position... *sigh*
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.