Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 20 hrs, 5 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 8 hrs ago - more...
|
2011-05-30
, 08:58
|
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#162
|
Originally Posted by Xudonax
Ah, right. The code tries to get your profile image before you are authorized.... apparently, facebook still returns SOMETHING in that case (the other services just causes an error, which my code handles, but it seems that facebook gives some odd result, and then my code tries to load that as an image)... anyhoo... fixable.
Well, this happens as soon as I tick the Facebook Places checkbox. So at this point the app doesn't even know what kind of profile picture I have...
/Z
 |
|
2011-05-30
, 09:19
|
|
Posts: 168 |
Thanked: 206 times |
Joined on Apr 2010
@ Finland
|
#163
|
Originally Posted by MasterZap
Updated to v45 and started Zaploc from X-term.
I would suggest you re-test 45 in verbose mode, i.e. open XTerm and type
...and read that after 30 seconds it should say one ofCode:python /opt/zaploc/zaploc-daemon.py -v
a) "A good location fix was acquired within the timeout: Good"
or
b) "No fix acquired for X seconds - doing a forced location push"
EITHER WAY, at that point it should turn the GPS back off.
Let me know if that happens or not. It sure happens here...!!
/Z
Code:
~ $ python /opt/zaploc/zaploc-daemon.py -v Starting ZapLoc daemon... Location method: GPS only 30 minutes between samples 12:02:46: Starting GPS... 12:02:47: Actual GPS interval 75 minutes (low battery!) 12:02:47: Got loc data xx.388344,yy.100560 (acc nan), Mode 1 (Estimate) - IGNORED 12:02:48: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0 12:02:48: Sample mode 2 (Cell-tower) - IGNORED 12:03:02: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0 12:03:02: Sample mode 2 (Cell-tower) - IGNORED 12:03:17: No fix acquired for 30 seconds - doing a forced location push! 12:03:17: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0 12:03:17: Sample mode 2 (Cell-tower) - IGNORED 12:03:17: Force-Sleeping [*bonk!*].... Zzzzzz 12:03:20: Got loc data xx.388344,yy.100560 (acc 404.265000), Mode 0 (Cached) - IGNORED
Code:
4335 user 50076 S /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
Last edited by Gusse; 2011-05-30 at 09:29.
|
|
2011-05-30
, 09:24
|
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#164
|
Originally Posted by Gusse
Just dumb question to be sure, but you closed ZapLoc itself, right? That also uses the GPS.
Then GPS is all the time ON.
This is incredibly strange, because there is no functional difference whatsoever between you running the daemon on the command line, and starting it in background.... it's the exact same code doing the same thing (except the background mode doesn't print out a bunch of crap to nowhere)
Very Very Strange. Especially if you see a difference w. version 44, because there IS no difference in the daemon (except it reads the number "30" from the config file instead of being hardcoded) ....
Edit: Actually I found a bug in that code, it DOESN'T read it properly from the config file, it is ALWAYS 30 seconds. Which means there is even less of a difference!!!
Sorry, I have zero explanation what is going on
/Z
Last edited by MasterZap; 2011-05-30 at 09:28.
|
|
2011-05-30
, 09:28
|
|
Posts: 168 |
Thanked: 206 times |
Joined on Apr 2010
@ Finland
|
#165
|
Originally Posted by MasterZap
Zaploc is closed and there is no other application using GPS. Only zaploc-daemon is running in background.
Just dumb question to be sure, but you closed ZapLoc itself, right? That also uses the GPS.
This is incredibly strange, because there is no functional difference whatsoever between you running the daemon on the command line, and starting it in background.... it's the exact same code doing the same thing (except the background mode doesn't print out a bunch of crap to nowhere)
Very Very Strange. Especially if you see a difference w. version 44, because there IS no difference in the daemon ....
Sorry, I have zero explanation what is going on
/Z
Code:
4335 user 50076 S /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
|
|
2011-05-30
, 09:40
|
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#166
|
This is very strange. As I said in the edit above, a bug causes 45 daemon NOT to read the fix timeout correctly. Which means it is always 30 seconds. Which means... it is completley identical 100% to build 44.
I don't quite understand why you find a difference
/Z
I don't quite understand why you find a difference
/Z
|
|
2011-05-30
, 09:59
|
|
Posts: 168 |
Thanked: 206 times |
Joined on Apr 2010
@ Finland
|
#167
|
Code:
python /opt/zaploc/zaploc-daemon.py -v
Code:
python /opt/zaploc/zaploc-daemon.py -d
Edit:
Code:
python /opt/zaploc/zaploc-daemon.py -d -v
Last edited by Gusse; 2011-05-30 at 10:08.
|
|
2011-05-30
, 10:01
|
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#168
|
That's... odd. Very very very very very very very very very odd.
What about without the "-v"? (Only difference is it should print less crap than with "-v")
/Z
What about without the "-v"? (Only difference is it should print less crap than with "-v")
/Z
|
|
2011-05-30
, 11:12
|
|
Posts: 13 |
Thanked: 5 times |
Joined on Apr 2010
|
#169
|
Very nice application and it works quite well, but why all selection buttons are empty/without any text? Anyone else seen this?
|
|
2011-05-30
, 11:39
|
|
Posts: 168 |
Thanked: 206 times |
Joined on Apr 2010
@ Finland
|
#170
|
Originally Posted by MasterZap
That's... odd. Very very very very very very very very very odd.
What about without the "-v"? (Only difference is it should print less crap than with "-v")
/Z
Code:
~ $ python /opt/zaploc/zaploc-daemon.py Starting ZapLoc daemon... Location method: GPS only 30 minutes between samples 14:29:05: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0 14:29:19: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0 14:29:33: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0 14:33:02: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0 14:35:57: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0 14:35:59: Got loc data xx.388344,yy.100560 (acc 404.265000), head nan, speed nan, Mode 2 (Cell-tower), Try 0
Last edited by Gusse; 2011-05-30 at 11:42.
At least, that's what's supposed to happen.... maybe there is an issue w. the default of the timeout or something....
I would suggest you re-test 45 in verbose mode, i.e. open XTerm and type
a) "A good location fix was acquired within the timeout: Good"
or
b) "No fix acquired for X seconds - doing a forced location push"
EITHER WAY, at that point it should turn the GPS back off.
Let me know if that happens or not. It sure happens here...!!
/Z
Last edited by MasterZap; 2011-05-30 at 09:13.