Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - bongo

Pages: [1] 2 3 ... 7
1
hi menion
maybe, we misunderstood...or i didn't write correct enough what i'm doing.
what i do is not importing waypoints to a folder. i only load them as temporary objects (i think they are called like that in locus).
so whenever i load these objects, the map centers and zooms out.
so each time after loading objects, i again have to find the position on the map i was watching before and where i wanted to know if there are any objects close to this point.
so therefore, i would like to get rid of this auto-zoom/auto-center feature.
i hope i wrote this a bit more clear this time ;-)

2
having an option to disable this auto-zoom-out and keep the actual view while importing waypoints would really be an advantage, but i would prefer to have this option permanent in the tool settings!

3
sure, i'm patient - i was just curious to know if there is any progress ;-)

so now, this is quite bad news ;-(

but one question:
did you have the problem about "no database set" only with your reworked version, or also with the original version of the addon, taken from google play?
i think if the database is placed in a wrong folder, you get this result as the addon is not able to access it (i think i once had this problem too).

what i can say for the actual situation is, that the addon is able to access the database independent of the android version.
this is because it is able to manually load the waypoints from the database to locus.
so if this also does not work in your test, it might be a config problem.

so maybe, the problem you noticed is not really the actual problem of the addon.

on my phone, the database has to be located under:
Android/data/net.kuratkoo.locusaddon.gsakdatabase/gdaklocus/sqlite.db3

if i put it somewhere else, it does not work.

still hoping that there will be a solution...

regards & thanx for your support!

4
hi menion
"next week" is almost over. did you already have time to take a look at this problem?
regards
bongo

5
hi menion

nice to hear that you'll have a look at this problem - hope this will end up in a good solution ;-)

as far as i understand, when doing an import, this action is initiated by tapping on a symbol within locus, i.e. in the end it is locus that starts the addon for this one-time-action.
so i would expect that locus should be able to automatically launch this one-time-action after moving around the map - just as a possible workaround if it's really impossible to get the legacy way working again.

thank you very much for your support!

6
hi c.s.g.
sounds interresting, but i really don't think that this problem has something to do with this "improvement".
i don't think that the gsak addon retrieves the user's location, as it doesn't really need to know it.
the gsak addon has to provide waypoints around the location actually shown on the map, and not around your actual position. so i think that the gsak addon get's the coords to be used from locus, and from nowhere else!
...but menion would really know how this works...
regards
bongo

7
hi menion

this sounds quite strange to me - can you be a bit more specific?
there are a few things i really don't understand...

import or live update:
according to my understanding, when importing from locus, locus sends a request to the addon with the actual center coords and gets back a set of waypoints to display on the map.
when using live update within locus, so whenever the map is moved around, locus periodically sends a request to the addon with the actual center coords and gets back a set of waypoints to display on the map.
this does not look that much different to me. do i completely misunderstand?

<<it is also not possible to have a running service in the background without visible foreground notification>>:
according to my understanding, the "background service without foreground notification" you mention is the gsak addon.
so why does this seem to run when importing data (as it obviously works then), but shall not run when trying to do a live update?

if the addon is blocked by android in any way, why should this be blocked for live update, but not for manual import?

i remember that there was a similar behaviour 1 or 2 years ago, when live update did not work anymore after a locus update. i think something went wrong then as some code was missing within this locus version. right?
is it possible that the dataformat you get from the addon is inconsistent in any way because of "bad coding" in the addon, resulting in slightly different formatted data when arriving within locus (after passing some android functions). then locus does reject this data because format check fails?
i think you've already checked if we don't have such a problem?

thinking further...
if there are really 2 different interfaces for importing and live update, and only the interface for importing works for android 8, why not using this interface too for live update?

sorry for asking that many questions... ;-)

regards
bongo

8
yep, that works...
thanx very much for your help!

9
hi menion
yes, this is what i tried to do. navigation-apps shows
- here we go
- tomtom go
- google maps

when using navigate from gdak, the apps to select are
- maps.me
- navogator
- dynavix
- tomtom go
- here we go
- google maps

i.e. while gdak shows all navigation apps installed on the device, locus only shows a few of them.

i'm actually evaluating a new navigation app for car navigation, and i think it would really be nice if this one could be used from within locus to select a destination.

10
i would like to launch a navigation app for car navigation from within locus, to navigate to a certain waypoint.
how can i add a navigation app to the navigation menu of locus?

so far, locus only displays tomtom navigation and google maps, while other navigation apps don't show up.
i would like to add e.g. maps.me navigation.

i don't think that launching this app is prevented from the app itself.
when i use gdak to select a destination waypoint, this allows me to launch any of my installed navigation apps to navigate to the waypoint, including maps.me.


11
seems to work fine again. thanx for the fix!

12
hope this will work with 3.22.1, as it was working fine so far.
if not, is there a way to go back to locus 3.21.x and keep this version?

13
since updating to 3.22.0, locus does not show any geocaches, i.e. it looks like live update from the gsak database addon does not work anymore.
is there anything that has to be reconfigured in the settings or is this a bug in locus 3.22.0?

14
when running locus (with the gsak addon) on a multicore device, how many cpu cores is locus (with gsak adddon) able to use?

i wonder which device will be the better solution for running locus

- quadcore 32 bit Qualcomm Snapdragon 801 MSM8974AC v3 (4x Qualcomm Krait 400 at 2457 MHz (galaxy S5, G900F))

- octacore 64 bit Samsung Exynos 7 Octa 7580 (4x ARM Cortex-A57 MPcore + 4x ARM Cortex-A53 MPcore at 1600 MHz (galaxy S5neo,l G903F))

thanx your your help!

15
i think if there is no way to transfer a license from androidpit to playstore, and all locus licenses have to be purchased again, there should at least be a way to get it at a discount rate.
i bought multiple copies of locus pro (because i run multiple accounts) and i don't really like to buy multiple copies from playstore again!
regards

Pages: [1] 2 3 ... 7