[Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;) - Page 10 - maemo.org

Active Topics

U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 4 hrs, 30 mins ago
List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 1 day, 4 hrs ago
Maemo repository (5)
to Community by dredlok706 - 2 days, 23 hrs ago
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 3 days, 2 hrs ago
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 3 days, 19 hrs ago
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 5 days, 8 hrs ago
more...

Page 10 of 35

Thread Tools

MasterZap	2011-05-20 , 10:55
Posts: 214 \| Thanked: 140 times \| Joined on Aug 2010	#91

Originally Posted by Storm_11

just tested exclusively with facebook places. Seems to work out. One thing to point out. On facebook, it does not show the username on the location checkin.

Uploaded with ImageShack.us

Idea for a future feature.... in heavily cluttered places it can be hard to find the icon for the place youre in.... so maybe a search function?

This is simply how facebook posts checkins. Post another one you'll see that THAT is preceeded by your name. Actually, facebook takes the name out of the first post on anything, I think.

Also the text before "at" is whatever you type in as you check in, not you.

/Z

Quote & Reply |

MasterZap	2011-05-20 , 10:57
Posts: 214 \| Thanked: 140 times \| Joined on Aug 2010	#92

Originally Posted by petur

After two hours it eventually did a latitude update, but that was because it seemed to have picked up another cell tower finally.
Log available on request

So it looks like there is an issue with the code to force an update after xx time.

I'd love to see the latter part, the important bit is if it is sleeping/awakening the GPS or not. If something breaks that cycle, well... then the cycle is broken *duh*

Again, the whole code is backwards compared ot what it needs to be for cell tower anyway, GPS continously feeds coordinates, and never stop until I tell it, so I can simply measure time until X time has past and stuff like that. For cell, it only sends data if it changed. Having the "on-changed" callback as the root of my code is the root of the problem.

Will be fixed at some point, but I don't know when or how.

/Z

Quote & Reply |

	cjp	2011-05-20 , 11:00
	Posts: 762 \| Thanked: 395 times \| Joined on Jan 2010 @ Helsinki	#93

Wow just blown away by this. Where the hell did this come from?

Really a great app. Enter the competition!

__________________
--
Find me on Twitter: @creip

Please read my blog: "PeakMobility", which deals with MeeGo/Maemo, Windows Phone and mobile technology in general from a hedonistic user point-of-view: http://peakmob.blogspot.com/

Quote & Reply |

petur	2011-05-20 , 11:09
Posts: 650 \| Thanked: 497 times \| Joined on Oct 2008 @ Ghent, Belgium	#94

Originally Posted by MasterZap

I'd love to see the latter part, the important bit is if it is sleeping/awakening the GPS or not. If something breaks that cycle, well... then the cycle is broken *duh*

It really keeps printing the wakeup line and all, so I would expect it to work... Log below....

Code:

2011-05-19 15:39:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 15:39:45: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 15:39:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 15:44:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 15:44:45: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 15:44:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 15:49:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 15:49:45: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 15:49:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 15:54:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 15:54:45: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 15:54:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 15:59:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 15:59:45: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 15:59:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
^[[5~Starting GPS...
2011-05-19 16:04:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:04:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:04:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:09:45: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:09:45: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:09:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:14:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:14:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:14:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:19:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:19:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:19:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:24:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:24:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:24:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:29:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:29:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:29:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:34:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:34:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:34:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:39:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:39:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:39:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:44:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:44:47: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:44:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:49:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:49:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:49:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:54:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:54:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:54:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 16:59:46: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
Updates within 100 meters - not sending
2011-05-19 16:59:46: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 16:59:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 17:04:47: Got loc data 51.028131,3.770349 (acc 96.017000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
2011-05-19 17:04:47: Latitude update 51.028131,3.770349 (acc 96.017000)
{'latitude': 51.028131299999998, 'kind': 'latitude#location', 
'accuracy': 96, 'longitude': 3.7703494000000002, 'timestampMs': 
'1305817491146'}
2011-05-19 17:04:51: General location update 51.028131,3.770349 (acc 
96.017000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 17:04:51: Got loc data 51.028131,3.770349 (acc 96.017000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
Starting GPS...
2011-05-19 17:09:47: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0
2011-05-19 17:09:47: Latitude update 51.029902,3.764234 (acc 
206.965000)
{'latitude': 51.029901500000001, 'kind': 'latitude#location', 
'accuracy': 206, 'longitude': 3.7642340000000001, 'timestampMs': 
'1305817792390'}
2011-05-19 17:09:52: General location update 51.029902,3.764234 (acc 
206.965000)
Searching for closest spot:
Sleeping GPS for approx. 5 minutes
2011-05-19 17:09:52: Got loc data 51.029902,3.764234 (acc 206.965000) 
alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0
^CTraceback (most recent call last):
  File "/opt/zaploc/zaploc-daemon.py", line 8, in <module>
    if __name__ == '__main__': app.zdaemon.main(sys.argv[1:])
  File "/opt/zaploc/app/zdaemon.py", line 470, in main
  File "/opt/zaploc/app/zdaemon.py", line 337, in init
KeyboardInterrupt

__________________
Affordable mobile internet in Belgium: Try Mobile Vikings
2 GB, 1000 SMS and 15 euro of talk time for.... 15 euro

Quote & Reply |

MasterZap	2011-05-20 , 11:28
Posts: 214 \| Thanked: 140 times \| Joined on Aug 2010	#95

Ok, got it... every time it got a tower-sample, it re-set the timer REGARDLESS if it actually had sent an update to latitude or not (*argh*).

Now I only reset the latitude timer if it ACTUALLY sends a latitude update.

New build will take a little while, though, I have the program dissected for other changes right now....

/Z

Quote & Reply |

petur	2011-05-20 , 11:32
Posts: 650 \| Thanked: 497 times \| Joined on Oct 2008 @ Ghent, Belgium	#96

no worries... I'm keeping off updates as much as I can because the CSSU causes the voip package to be uninstalled on every update :/
(autoremove bug)

__________________
Affordable mobile internet in Belgium: Try Mobile Vikings
2 GB, 1000 SMS and 15 euro of talk time for.... 15 euro

Quote & Reply |

	ndi	2011-05-20 , 11:53
	Posts: 2,050 \| Thanked: 1,425 times \| Joined on Dec 2009 @ Bucharest	#97

Originally Posted by MasterZap

Knowing my N900 as I do, losing only 30% over night would be fantastic (I always charge overnight)

/Z

My N900 loses 8 percent overnight. 900 MHz, connected to wifi over WPA. 30 is huge.

Also, daemon doesn't exit. Just 2 minutes ago, my N900 fired up GPS, got a lock and then closed it. There is only one app that does GPS on its own on my phone.

Let's see.

Code:

Nokia-N900:~# ps | grep zap
 9958 user     49768 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
11590 user     49752 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
11648 user     49752 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
11681 user     49748 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
17789 user     49480 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
18714 user     48944 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
18746 user     48944 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
18827 root      2832 S    grep zap
Nokia-N900:~#

That's one mystery down.

__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.

Quote & Reply |

MasterZap	2011-05-20 , 12:10
Posts: 214 \| Thanked: 140 times \| Joined on Aug 2010	#98

Originally Posted by ndi

My N900 loses 8 percent overnight. 900 MHz, connected to wifi over WPA. 30 is huge.

Also, daemon doesn't exit. Just 2 minutes ago, my N900 fired up GPS, got a lock and then closed it. There is only one app that does GPS on its own on my phone.

Let's see.
Code:
Nokia-N900:~# ps | grep zap
 9958 user     49768 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
11590 user     49752 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
11648 user     49752 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
11681 user     49748 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
17789 user     49480 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
18714 user     48944 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
18746 user     48944 S    /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
18827 root      2832 S    grep zap
Nokia-N900:~#
That's one mystery down.

Hmm, it's supposed to kill any running copies of itself when launching. If you do

Code:

python /opt/zaploc/zaploc-daemon.py -t

What does it say

/Z

Quote & Reply |

Storm_11	2011-05-20 , 12:43
Posts: 183 \| Thanked: 98 times \| Joined on Mar 2011 @ Brisbane, Australia	#99

Originally Posted by MasterZap

This is simply how facebook posts checkins. Post another one you'll see that THAT is preceeded by your name. Actually, facebook takes the name out of the first post on anything, I think.

Also the text before "at" is whatever you type in as you check in, not you.

/Z

sure? I just tried checking in with a different facebook application, and it shows:

Uploaded with ImageShack.us

Name "blue-d" out for privacy reasons. But on this application it shows my name in the newsfeed. Versus Zaploc in its current build, which even in the general newsfeed, does not show the username associated with the activity, only the avatar.

and just checked in for a second time with Zaploc, and it exhibits the same behaviour that i previously reported. Does not show the username

Last edited by Storm_11; 2011-05-20 at 12:48.

Quote & Reply |

MasterZap	2011-05-20 , 14:39
Posts: 214 \| Thanked: 140 times \| Joined on Aug 2010	#100

Originally Posted by Storm_11

sure? I just tried checking in with a different facebook application, and it shows:

Uploaded with ImageShack.us

Interesting. I don't know if I have any control over that, though... I just do a checkin over the API... :/

Have to check if I can feed in some extra parameter or something...

/Z