Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 15 hrs, 5 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 3 hrs ago - more...
|
2011-05-25
, 13:24
|
|
Posts: 650 |
Thanked: 497 times |
Joined on Oct 2008
@ Ghent, Belgium
|
#142
|
tried the manual latitude 'checkin' and it froze the app - had to kill it.
__________________
Affordable mobile internet in Belgium: Try Mobile Vikings
2 GB, 1000 SMS and 15 euro of talk time for.... 15 euro
Affordable mobile internet in Belgium: Try Mobile Vikings
2 GB, 1000 SMS and 15 euro of talk time for.... 15 euro
|
|
2011-05-25
, 13:26
|
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#143
|
Yes, read back a few pages, I decided to change the semantics of the settings:
- removed the "when to start" and "when to stop" crap (too many settings for the same thing, really)
- there is simply a single on/off button for "Background updates". When on, it starts at boot, and doesn't stop. When off, it doesn't start at boot, and if you run zaploc and it finds a running daemon it kills it.
Was this too much change...?
I could consider re-instating a "start at boot" checkbox if that helps.
/Z
- removed the "when to start" and "when to stop" crap (too many settings for the same thing, really)
- there is simply a single on/off button for "Background updates". When on, it starts at boot, and doesn't stop. When off, it doesn't start at boot, and if you run zaploc and it finds a running daemon it kills it.
Was this too much change...?
I could consider re-instating a "start at boot" checkbox if that helps.
/Z
|
|
2011-05-25
, 17:26
|
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#144
|
Originally Posted by LaptopU
Now hitting "F" on keyboard toggles fullscreen mode.
Couple of questions though please. I would like to switch between other apps and leave this running in the background. I can switch by pressing ctrl-backspace on the keypad, but some other apps (particularly web browser) allow the title bar to appear by tapping the bottom right of the screen, yours doesn't. Would you plan to add that?
Originally Posted by LaptopU
There is now a third mode which NEVER uses any non-gps coordinates. Instead of failing over to cell-tower, it simply doesn't post the location at all, if there is no GPS fix.
Also if I set the daemon to still run after the program exits, it seems to use a 'fast' GPS location which is generally the cell tower nearby. I can see the GPS fire up and shut down but it doesn't get a true lock, whereas if I leave the program running it gives an accurate lock.
/Z
 |
|
2011-05-25
, 21:36
|
|
Posts: 2,050 |
Thanked: 1,425 times |
Joined on Dec 2009
@ Bucharest
|
#145
|
Originally Posted by MasterZap
Could you add a delay at start? First, the network is still down, as posted, second, there's a lot going on at startup, why add to the pain? Add a wait 60 or something at startup, give the phone a chance to start fully, do the desktop, go though the tracker, browserd doing stuff.
- there is simply a single on/off button for "Background updates". When on, it starts at boot, and doesn't stop. When off, it doesn't start at boot, and if you run zaploc and it finds a running daemon it kills it.
Just rebooted, and it failed to lock, keeps blinking for minutes. Sometimes I'm low on battery and powering GPS on boot doesn't help.
Just a suggestion. May work fine for other people
__________________
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.
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.
|
|
2011-05-26
, 15:53
|
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#146
|
Originally Posted by ndi
Added to build 43.
Could you add a delay at start? First, the network is still down, as posted, second, there's a lot going on at startup, why add to the pain? Add a wait 60 or something at startup, give the phone a chance to start fully, do the desktop, go though the tracker, browserd doing stuff.
Tho on my device this is not a problem... I'm hooking the latest possible hook-point in event.d, which is when hildon-desktop has started.... but now there is an extra 60 seconds of "do nothing" until it turns the location subsystem on.
/Z
|
|
2011-05-26
, 19:16
|
|
Posts: 13 |
Thanked: 1 time |
Joined on Feb 2010
|
#147
|
Got a problem lately, where the daemon seems to be satisfied with cell location even though mode is on --gps. When starting the daemon, GPS icon flashes for a few seconds until coarse accuracy appears, then disappears and latitude is updated.
Verbose output of an example case:
(build 43, happened with earlier builds as well)
As you can see from the timestamps, the daemon doesn't even try to wait for a better fix.
Ideas?
Verbose output of an example case:
Code:
Starting ZapLoc daemon... Location method: GPS only 60 minutes between samples 22:07:38: Starting GPS... 22:07:38: Actual GPS interval 60 minutes 22:07:38: Got loc data <snip> (acc nan), Mode 1 - IGNORED 22:07:40: Got loc data <snip> (acc 53.763000), head nan, speed nan, Mode 2, Try 0 22:07:40: Latitude update <snip> (acc 53.763000) 22:07:41: Checked you in at <snip> on Latitude 22:07:41: General location update <snip> (acc 53.763000) 22:07:41: Searching for closest spot: 22:07:41: The closest AutoCheck spot is <snip> 22:07:41: Spot ignored because it is further than 50 meters away 22:07:41: Sleeping... Zzzzz 22:07:45: Got loc data <snip> (acc 53.763000), Mode 0 - IGNORED 22:08:08: A good location fix was acquired within the timeout: Good!
As you can see from the timestamps, the daemon doesn't even try to wait for a better fix.
Ideas?
|
|
2011-05-26
, 23:57
|
|
Posts: 2,050 |
Thanked: 1,425 times |
Joined on Dec 2009
@ Bucharest
|
#148
|
Why try better than 53 meters?
__________________
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.
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.
|
|
2011-05-27
, 05:39
|
|
Posts: 214 |
Thanked: 140 times |
Joined on Aug 2010
|
#149
|
Originally Posted by morti
Yep. Your tower claims to be closer to you than 53 meters... which I kind of doubt it is... I actually seen this myself, towers that obviously claim their accuracy is way higher than reality.
Got a problem lately, where the daemon seems to be satisfied with cell location even though mode is on --gps. When starting the daemon, GPS icon flashes for a few seconds until coarse accuracy appears, then disappears and latitude is updated.
Verbose output of an example case:
(build 43, happened with earlier builds as well)Code:Starting ZapLoc daemon... Location method: GPS only 60 minutes between samples 22:07:38: Starting GPS... 22:07:38: Actual GPS interval 60 minutes 22:07:38: Got loc data <snip> (acc nan), Mode 1 - IGNORED 22:07:40: Got loc data <snip> (acc 53.763000), head nan, speed nan, Mode 2, Try 0 22:07:40: Latitude update <snip> (acc 53.763000) 22:07:41: Checked you in at <snip> on Latitude 22:07:41: General location update <snip> (acc 53.763000) 22:07:41: Searching for closest spot: 22:07:41: The closest AutoCheck spot is <snip> 22:07:41: Spot ignored because it is further than 50 meters away 22:07:41: Sleeping... Zzzzz 22:07:45: Got loc data <snip> (acc 53.763000), Mode 0 - IGNORED 22:08:08: A good location fix was acquired within the timeout: Good!
As you can see from the timestamps, the daemon doesn't even try to wait for a better fix.
Ideas?
Basically, I'm now looking at accuracy, rather than the sample mode, but I think that in "--gps" mode, I should change it to still be looking at the mode=3 (which means "this value came from the GPS"). This is a trivial fix.
Curious; how far away would you guesstimate that tower actually is? I noticed that the tower I normally get connected to, which is about 2000m from me, claims to have "253 meter" accuracy. Dunno what's with the "53" at the end at all these
/Z
Last edited by MasterZap; 2011-05-27 at 05:43.
|
|
2011-05-27
, 06:42
|
|
Posts: 13 |
Thanked: 1 time |
Joined on Feb 2010
|
#150
|
Originally Posted by MasterZap
Sounds like a good idea, if we can't trust the accuracy of the tower. It's a shame though, I like your idea of first looking at the accuracy regardless of mode.
Basically, I'm now looking at accuracy, rather than the sample mode, but I think that in "--gps" mode, I should change it to still be looking at the mode=3 (which means "this value came from the GPS"). This is a trivial fix.
Curious; how far away would you guesstimate that tower actually is?
The tower is roughly 450-500 meters away in reality.
Now daemon starts at boot (--boot) which is not fun, because it doesn't have network yet and it doesn't lock.
Furthermore, exiting app leaves it running (-d). Setting seems gone. Did you give up trying to kill it?
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.