Locus Map - forum

Development => Versions => Topic started by: menion on January 30, 2019, 14:43:06

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on January 30, 2019, 14:43:06
Important links
- list of news (http://help.locusmap.eu/announcement/version-3-36-30-1-2019) of public versions

Versions
30. 1. 2019 - Locus 3.36.0
1. 2. 2019 - Locus 3.36.1
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Erelen on January 30, 2019, 15:02:10
(sorry, can't reply to old topic)

Menion, January 28, 2019, 16:21:27 (https://forum.locusmap.eu/index.php?topic=6406.msg54108#msg54108):
Quote
Its main purpose is for quick access to functions over hardware controller mounted on the bike for example.
So, what about adding hardware buton for this menu to config.cfg?
And several more commands (https://help.locusmap.eu/topic/external-bluetooth-controller-more-commands)? ;)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: jonny.blue on January 30, 2019, 22:37:11
Hi,
sorting points by geocaching->favorites doesn't work for me.
They remain unsorted.

Other sort options are working correct.

PS: it seems as if there is a confusion between favorite and gcvote option.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: tapio on January 30, 2019, 22:42:15
Awesome release. I must admit: now with the possibility to sort by elevation gain, I wish it would calculate, display and allow sorting by elevgain/distance. I.e. elevation gain per km. So we can easily plan and see, at least it is a hint, on how exhausting a track is...
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on January 30, 2019, 23:19:33
It is really interesting with your notifications. Isn't possible, it was a notification from for example "GPS lost fix"?
@menion (actual quote from 3.35+) - my "GPS lost" notification is custom 5-beep OGG file, so no, I have no explanation of source for this single-short-beep other than the POI alert system. It is the only when POI alerts are enabled this single-beep will be heard. Is there any change to POI alerts in 3.36.0 Pro (other than button color) for testing - it appears the Beta POI alert UI hasn't been migrated to Pro?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: tapio on January 31, 2019, 07:43:11
Bug? Track manager in lock screen, tracks sorted by elev. gain.
Unlock device, bring another app to front, go back to Locus: Track screen says it has no data.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on January 31, 2019, 10:06:28
@Erelen
this and many other commands are already possible ;)
https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts)

@jonny.blue
precise estimate: switched sorting for favorites and GCVote, thanks solved.

@tapio
hmm this is close to some "universal difficulty index" (something like IBP index) that should display next to every track and that will inform about optimized difficulty, easily comparable with other tracks.

Bug? Ah, yes, thanks!

@Andrew Heard
how POI alert looks in Pro or Free (beta) is not too important here. Service that takes care about notification is the same in both versions. Anyway, I'll try to test it a little bit as well.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: tapio on January 31, 2019, 10:16:56
Maybe a bug. I was editing the presets, because of the new possible settings... and Locus always decided to freeze after a while.
Title: Re: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on January 31, 2019, 16:29:24
Bug?: After searching for points with the new search, there is a tool in the search result for selecting all points and for inverting the selection. This tool is still visible after going back to the search form.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 01, 2019, 12:48:20
Ah thanks, fixed.

@tapio
I was just playing with it maybe 5 minutes and no problem so far. For you, app completely freeze that you see "Application not responding" dialog?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: tapio on February 01, 2019, 16:23:14
Yes exactly. And before my patience ended I killed the instance. Which was maybe after 15s
Will test more thoroughly and after a device restart.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: tapio on February 01, 2019, 16:38:20
It also happens after a restart. I edit a preset, then in it I edit what is part of the preset. The page with the checkboxes. I scroll up and down, check and uncheck entries, after maybe 10 seconds it freezes.
It is on an older device, Sony Z1.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: tapio on February 02, 2019, 14:08:35
hmm this is close to some "universal difficulty index" (something like IBP index) that should display next to every track and that will inform about optimized difficulty, easily comparable with other tracks.
Yeah, would be great to by able to sort "by difficulty" (in terms of exhausting) for all the sportive enthusiasts, who e.g. do hiking for preparation of more difficult tracks, or just for the sports side of life.

IBP, quite interesting stuff. Lots of attributes mixed for an index number. But is their algorithm open?Here's the analysis of a day trip I had, oh I had a bad day I remember...
https://www.ibpindex.com/ibpindex/ibp_analisis_completo.php?REF=37582812591524&LAN=en&MOD=HKG
Edit: I'm not convinced about the algorithm. A hiking trip in Germany Sauerland hat a higher Index than one in the Austrian Alps. Which was way harder.

Least and simple value you could offer is "positive elevation gain divided by distance". I fand someone here thinking about it a bit more: http://topofusion.com/forum/beta-testing/new-feature-difficulty-and-effort-index/
And Oruxmaps has IBP index according to https://www.oruxmaps.com/oruxmapsmanual_en.pdf - however they did it. I did not find the algorthmic details being open...
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: tapio on February 02, 2019, 18:32:18
I am slowly trying to switch to mf v4 maps. Mapsforge themes cannot be picked in preset manager.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 05, 2019, 16:29:36
I'm not saying that IPB is ideal. It is just proof of concept if something similar should not be useful create. The algorithm of IPB value is private thought.

Petr for some time works on new system how to publish tracks over Locus Store and we will need also some method how to say to users how difficult certain track is, so it is an actual topic for me.

MapsForgeV4 themes: in the current version, you need V4 maps.

@all
What do you think about visible top-right value in list of tracks for every track? Currently, there is average speed as base value (when sorted by name, dist, time or date). What about change to "elevation gain" as asked here https://help.locusmap.eu/agent/object/14703#comment-67047 ? Anyone against it?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 05, 2019, 18:16:52


MapsForgeV4 themes: in the current version, you need V4 maps.
The question was about presets. Even if I have selected a V4 map and V4 theme, when I create or edit a preset, it only offers me standard V3 themes.



Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 05, 2019, 21:01:17
Ah right sorry. Current presets system support only V3 themes.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on February 06, 2019, 00:42:10
What do you think about visible top-right value in list of tracks for every track? Currently, there is average speed as base value (when sorted by name, dist, time or date). What about change to "elevation gain" as asked here https://help.locusmap.eu/agent/object/14703#comment-67047 ? Anyone against it?
@menion - great idea.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: tapio on February 06, 2019, 07:00:21

@all
What do you think about visible top-right value in list of tracks for every track? Currently, there is average speed as base value (when sorted by name, dist, time or date). What about change to "elevation gain" as asked here https://help.locusmap.eu/agent/object/14703#comment-67047 ? Anyone against it?

YES please. Also, I have many planned tracks with zero distance and speed. In that case avg speed and distance are wasted space.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 06, 2019, 07:14:42
Regarding Locus Map and V4 maps. Read the comments.....

https://www.openandromaps.org/en/locus-direct-install-link-for-multilanguage-v4-maps/comment-page-1#comment-9599
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 06, 2019, 08:15:40
@Andrew Heard & @tapio
thanks, I'll change it

@locus.sv@heime.org
Read the : https://forum.locusmap.eu/index.php?topic=6434.0
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 06, 2019, 08:58:55
@Andrew Heard & @tapio
thanks, I'll change it

@locus.sv@heime.org
Read the : https://forum.locusmap.eu/index.php?topic=6434.0

Thanks. I wasn't aware of this thread. Anyway, that is good news. Looking forward to see it in the beta version later this spring.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 08, 2019, 12:16:50
New beta version 3.36.2.1

Geocaching API
I've finally completely rewrote Geocaching API system. Why this? Groundspeak till 1.5.2019 remove support for the old system (used all these years till now). Instead of, they prepared new more modern API. In the first step, I need to 1:1 convert old system to new and this is the first version of Locus Map, where all should be set & ready for the testing.

 What are Locus Map functions that use this API?
- all around logging of caches & trackables (screen with logging, drafts manager)
- download & import of Pocket Queries
- GC Offlinizer
- upload of notes
- and few tiny functions here and there

Geocaching4Locus has own version and will need update to new API as well, but it's business for Arcao (add-on developer).

It was not easy conversion so I rewrote whole "Geocaching tools" screen and also "Send logs screen". As a side-effect of new API, it is possible to log drafts also with images (so all three options now support images).

Import & export of Garmin FIT files
finally? FIT files should be fully supported anyway testing is needed as I'm not yet perfectly familiar with this format.

Looking forward to useful feedback and wish a nice weekend!
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 08, 2019, 17:00:27
Locus Beta 3.36.2.1. CRASH to android 8 when accessing Google Drive.
If I open the Google Drive access menu, Beta will close the application. See Scr. Because the app stops right when you enter a folder, it is not possible to get this loop anywhere and import the route or retrieve the settings from the backup.
The PRO version works seamlessly with Google Drive. Your Google Drive is not installed on your phone.

CZ: Locus Beta 3.36.2.1. CRASH na android 8 při přístupu na Google Drive.
Pokud otevřu menu s přístupem na Google Drive, Beta ukončí aplikaci. Viz scr. Protože k ukončení app dojde hned při vstupu do složky, není možné se z této smyčky nijak dostat a naimportovat trasu nebo načíst nastavení ze zálohy.
Verze PRO funguje s Google Drive bez problémů. V telefonu není nainstalována aplikace Google Drive.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on February 08, 2019, 17:37:20
i am not able to login GS
log out of service > "logout"> no action
can´t load
- PQs
- offlinizer
- log visit or upload draft

if i click top left X > message problem with internet code 10100
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 08, 2019, 18:45:08
Ah thanks Josef & Balloni, I'll try to fix as soon as possible.

Seems that login to geocaching.com returns a weird error message, that something that already worked a few days ago and that is exactly by their documentation, does not work now. Have to write to America for help :).

About Google Drive ... also interesting, but I think I see something. Will try to fix it, thanks.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 08, 2019, 18:51:14
Not able to log in, either.

The message in the picture is "Firefox was not able to find the server at locus.oauth.callback.geocaching

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 09, 2019, 07:14:56
@Žajdlík Josef
hmm seems to be some issue in build tools. Anyway please try to disable internet and open this "import" screen. It should work. Then in the top menu choose "logout" and then you may try to enable internet and login again. It should work.

@balloni55
seems you use DEV geocaching server enabled in expert settings right? With the main server it seems to work correctly. Definitely something new on Groundspeak server.

EDIT: ah, now it seems to work

@locus.sv@geime.org
hmm this may be a real problem. I'm testing it mainly with Chrome. Will test other browsers as well, thanks.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 09, 2019, 08:06:04
@Žajdlík Josef
hmm seems to be some issue in build tools. Anyway please try to disable internet and open this "import" screen. It should work. Then in the top menu choose "logout" and then you may try to enable internet and login again. It should work.
Unfortunately, the application crashes even when you disconnect the Internet. I tried it in Airplane Mode. Is there any way to unlink a Google Drive without having to go to a folder?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 09, 2019, 08:14:00
So, today, Beta is also crashing on the Android 5 tablet. Yesterday it worked because I linked it to my account for the first time. Version Pro again without any problems. If necessary, I will send the protocol.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on February 09, 2019, 08:39:58
Quote
@balloni55
seems you use DEV geocaching server enabled in expert settings right?
please watch screencast
https://www.dropbox.com/s/ovg1aatpotax8v6/2019_02_09_07_41_01.mp4?dl=0
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: jonny.blue on February 09, 2019, 09:33:02
When I want to log a visit a cache in beta ... an error occurs while authorisizing to geocaching.com:

Die Website ist nicht erreichbar
Die Server-IP-Adresse von locus.oauth.callback.geocaching wurde nicht gefunden.
DNS_PROBE_FINISHED_NXDOMAIN
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 09, 2019, 09:42:26
Thanks for video balloni. It anyway looks that opened web browser (chrome) is still loading. Did you tried to leave it a little longer? Click on "cross" button and visible error 10100 is only incorrectly displayed result of login task. 10100 = canceled.

EDIT: ah, some problems with login simulate on second device, oki, leave it for now, thanks :)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 09, 2019, 11:24:37
@Žajdlík Josef
when you will have a moment, please try this improved version: https://asamm.myqnapcloud.com/share.cgi?ssid=06gjnIt

I've updated few Android libraries with hope, it will help. Thanks
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 09, 2019, 11:51:58
Test on tablet with android 5 unfortunately unsuccessful. Beta still crashes. Pro works. I apologize for the inconvenience. If my problem is unique, I can still use the Pro version.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 09, 2019, 20:11:49
1. I can't find any way to clear the cached images for mapsforge V4 themes. That is to say, I've changed the icon for "ruins" in a theme and the V3 theme displays the new image but the V4 theme doesn't. I've tried clearing the caches within Locus.
Edit:. The beta version displays ok.
2. The latest full and beta versions seem to crash an awful lot in use. Mainly on redrawing the screen on moving our zooming, I think.
3. "Sort tracks by nearest" doesn't work. All my tracks show "0" (in blue). I don't even understand how this is meant to work, compared to "sort by distance" to start and "sort by distance to end". Both those show a valid distance and sort correctly.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 09, 2019, 21:45:40
@Žajdlík Josef
hmm damn. It may be unique here because we have a really limited number of users with Beta version. But such issue published to the public of few thousands of users may cause a mess, so I rather fix it. I see the issue in Firebase Crashlytics system, but still can't find any clue, why this happens... give me a while please :).

@john_percy
1. as I see, the cache will be probably somewhere in /sdcard/Android/data/menion.android.locus/cache directory. Maybe subdirectory "mapcache".
2. hmm nothing un-usual reported as I see. Log needed, thanks.
3. In this case, also "Search in tracks" display also "0 m" distance and some non-sense results right? Maybe when you will do a log for case 2., do one more right after the search or this sort, because there have to be some issue visible in log too. Thanks
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on February 09, 2019, 22:38:57
3. "Sort tracks by nearest" doesn't work. All my tracks show "0" (in blue). I don't even understand how this is meant to work, compared to "sort by distance" to start and "sort by distance to end". Both those show a valid distance and sort correctly.
@menion I see exactly the same issue as @john_percy with Locus Free & Pro 3.36.2 & beta 3.36.2.1. Other methods of sorting appear OK.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 09, 2019, 23:04:25
@john_percy
1. as I see, the cache will be probably somewhere in /sdcard/Android/data/menion.android.locus/cache directory. Maybe subdirectory "mapcache".
2. hmm nothing un-usual reported as I see. Log needed, thanks.
3. In this case, also "Search in tracks" display also "0 m" distance and some non-sense results right? Maybe when you will do a log for case 2., do one more right after the search or this sort, because there have to be some issue visible in log too. Thanks
1. I've closed Locus, cleared all the files in the cache directory, restarted the phone, but the incorrect map icons persist.I read somewhere that svg files are bitmapped and cached at different sizes. That's what I want to clear, though it ought to happen automatically,
2. I've sent system crash reports. Do these come to you via Google?
3. Do Andrew's screenshots help? That's what I'm referring to.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Bucky Kid on February 10, 2019, 11:34:15
Hello, I report a minor visual bug: in route planner, if the points stack is empty, the remove point button [-] isn't grayed which may act confusing. The geayed remove button always served me as quick indicator that I'm starting from scratch.

________________________
Sent from my phone using Tapatalk

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: zossebart on February 10, 2019, 14:41:33
Hey menion,

in the last version's beta some guys found a nice little "quick functions panel" which could be added to the top or side panel. It is also present in the current Beta but not in Pro as far as I can see.
You said it was published by accident and was meant to be activated by hardware buttons only.
I am very interested in this feature! Is this already possible in current beta? If yes, how to enable it in config.cfg? I assume I could trigger it with bluetooth hid device?

I'm not so much interested in adding it to a panel, but it should not hurt anyways?

Gesendet von meinem D5503 mit Tapatalk

Title: Geocaching
Post by: jonny.blue on February 10, 2019, 16:47:32
Quote
New beta version 3.36.2.1

Geocaching API
I've finally completely rewrote Geocaching API system. Why this? Groundspeak till 1.5.2019 remove support for the ...

Is it really ready for testing?

I can't authorisize Locus to my account.  :(
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 11, 2019, 13:09:06
@john_percy
sorry but I do not know. Because you may test your themes on Free version, the solution should be to simply just un-install application and install it from Google Play again. This should clear all internal cache directories that may not be visible on not-rooted devices.

About reported problems: if you report issue over dialog that appears in the device, it ends in some tool from Google where I see all reports at once. Currently, there are maybe 1000 crashes per week. These that repeat mosts are currently out of our skills. These crashes are usually in Android itself and I have absolutely no idea how to solve them. It usually happens during simple moving or zooming with the map and it is probably your case as well.

Problem with sorting: I understand where is a problem, same as in the case of Andrew, I just do not have the same issue on own device. We have again the company meeting this week, so I'll try it on Petr or Milan devices.

@Bucky kid
ah, you are right. I noticed a similar problem with incorrectly display "disabled" buttons on more places is app. It will be fixed once I get rid of support for Android 4 (so a few months later).

@zossebart
If you are familiar with for example Tasker application, you may already use it. Documentation how it should look on Locus Map side is published here (https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts)).

@jonny.blue
login really seems to be a problem. I think I have a working solution, but I now wait till Geocaching guys in America wake up and change something for me :). In next days, I'll publish new version.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 11, 2019, 14:42:04
@menion. Thanks for response. Uninstalling and reinstalling Locus Pro worked, using back up and restore.
However:
- Restore did not restart the app, despite saying it would in 5 seconds
- Backup/Restore mangled some of the directory locations that I had set
- It's not user-friendly way of updating themes!
I understand your comments on bug reports.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: zossebart on February 12, 2019, 13:58:15
@zossebart
If you are familiar with for example Tasker application, you may already use it. Documentation how it should look on Locus Map side is published here (https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts)).

I'm familiar with tasker. I use a NFC-triggered Tasker-Task to start recording and custom livetracking and apply a preset and activate a dashboard when my phone is mounted on the handlebar of my bike. So I guess I'm also quite familiar with the Action Tasks. However, I don't get from the documentation how to activate this "quick actions menu" from tasker. Maybe there is a new undocumented value for the "function" task?


Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: lor74cas on February 12, 2019, 14:50:40
New beta version 3.36.2.1
Import & export of Garmin FIT files
finally? FIT files should be fully supported anyway testing is needed as I'm not yet perfectly familiar with this format.

Looking forward to useful feedback and wish a nice weekend!

tested with fit file from my garmin forerunner 235 all works correctly, good job.
Now I can uninstall gpsbabel from the pc?  ;D
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 12, 2019, 17:30:32
Under certain circumstances the (cubic-curved) contour lines on vector maps are drawn twice, differently. I think it may be to do with zooming in quickly from the world overview map when there is a high density of contours. See attachment. This is using a Mapsforge v3 map from OAM.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on February 12, 2019, 19:37:30
hello menion
due to geman thread
https://forum.locusmap.eu/index.php?topic=6465.new#new
i confirm problem with not recognized changes in settings of "POI alert"
count of beep can be changed and tested, but the value is not stored an stay allways by 1 in function
BTW, i compared settings in BETA :-[ are they gone :o
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 13, 2019, 09:34:57
@john_percy
at least restart should be solved now, maybe :)

Anyway, I thought you wanted to do the clearing of theme cache this because of some own experiments. Doing this by users is of course nonsense. I'll have to look into source code of whole V4 mapsForge, because this cache for icons (if any) have to be fully automatic.

Contour lines ... uh. I'll forward this to Petr with hope he will have any idea :)

@zossebart
this (https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts)#start-function) sample does not work for you? Do not forget to set "Package"

@lor74cas
perfect. I've found one more small issue with import

@balloni55
hmm thanks, I'll look at it. Setup of notifications: just click on the line (title) with toggle button
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: voldapet on February 13, 2019, 09:51:55
@john_percy Regarding contour lines. Maybe stupid question but are you sure that  the theme is correctly defined? Is there only one definition for contour line (with parameter curve="cubic" )?  It seems that the contour lines have different thickness. So I think that there is second definition in your theme for contour lines without curve=cubic parameter.
Maybe one more question: is the the world overview map raster or vector map?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: michaelbechtold on February 13, 2019, 12:07:41
Just looked at Hill of Gairney example for John's contour issue:
Test:
- OAM Great Britain
- W1-10 world map
- Elevate LE or Hilo V10
Result: no duplicate contour lines whatsoever.
Good luck
Cheers
Michael
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 13, 2019, 13:02:38
@voldapet, @ michaelbechtold
Thanks for the feedback. Normally the display is perfectly OK. I've done some more trials and I can reproduce the effect fairly reliably by a series of rapid "flings" of the map, moving the map before it has a chance to redraw completely. (In real life, this occured when moving quickly to a new location.) I can get the effect maybe one time out of ten or twenty. It seems to require an area with many contour lines but does not depend on zooming out to the world map. I have made it happen with OAMaps of GB and of UK_Scotland, and with the LoMap of Scotland. I have made it happen with my Voluntary theme and with the built in Hike & Bike theme. (By the way, I checked and contour lines are not duplicated in my theme.)
Once Locus is displaying the double contour lines, they continue to be displayed on zooming in or out, scaled appropriately. The duplicate set disappears on reloading the theme or the map.

@menion Thanks.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on February 13, 2019, 14:30:57
Quote
Setup of notifications: just click on the line (title) with toggle button
thanks,
puuh, well hidden ???

EDIT: change values in Beta work :)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: voldapet on February 14, 2019, 07:42:52
@john_percy
Thanks for detailed description. Unfortunately I'm not able to simulate it...and if we can't simulate it, we can't solve it :-/
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 14, 2019, 12:24:01
@voldapet
Try this, which reproduces every time for me:
Map: LoMap Scotland
Theme: Internal Hike & Bike
Location: N 56.72078° , W 006.03068°
1. ZL 14
2. Now zoom out to ZL 13
3. Then zoom back to ZL 14. (Despite what I said earlier, no need for speed.) For me, extra contour lines appear, which can be noted by the increased darkness of the map
4. Lock the zoom and magnify the screen to see this more clearly.
Reset the theme or the map and the map image corrects itself.
The screenshots below are in this order.
 The "fast fling" whereby I encountered the effect originally is unnecessary. The same effect happens with other themes and maps of the same area, and with or without hardware acceleration.

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: zossebart on February 14, 2019, 12:49:54


@zossebart
this (https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts)#start-function) sample does not work for you? Do not forget to set "Package"

Ahh thanks for the example, of course it works! I must have been blind to not see this in the list of supported functions, although I searched it before...

In general, is this the preferred way for HW-Buttons interaction now? Will the method over config.cfg be deprecated in the future?

Gesendet von meinem D5503 mit Tapatalk

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 15, 2019, 12:01:41
Finally Groundspeak fixed some problem in setup of Locus Map on their server, so new version 3.36.2.4 published with the second version of login to Geocaching API, so let me know if it works, thanks!

@zossebart
I think that both systems are needed. In config is predefined few methods and you may directly attach hardware buttons to them. Useful for direct support of BT controllers for example. Configuration over API (tasker for example) is a lot more flexible and possibilities are almost unlimited (limited only by what I offer over API), but they need a lot skilled user to setup it properly :).
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 15, 2019, 13:31:27
Google Drive vs. Locus Beta 3.36.2.4
After installing Locus Beta, you need to unregister your Google Account at Locus. After newly created logins, Google Drive in Locus Beta works. Unfortunately, at the same time, the sign in the PRO version was canceled. This is not a way out of the Beta, so now you can not sign in with the PRO version on Google Drive.

CZ:
Po instalaci Locus Beta bylo třeba zrušit přihlášení k účtu Google v Locusu. Po nově vytvořeném přihlášení už Google Drive v Locus Beta funguje. Bohužel současně došlo i ke zrušení přihlášení ve verzi PRO. U ní už postup z Bety nefunguje a nyní tedy nelze se s verzí PRO přihlásit do Google Drive.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on February 15, 2019, 14:05:46
Beta 3.36.2.4
Geocaching tools "Login requiered" > no reaction if i click anywhere  :-[
LoadPocket Queries, new window open "Geocaching"  www.geocaching.com, waiting....
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 15, 2019, 15:32:32
@Žajdlík Josef
I believe I've found a reason for your issues and they are solved in Beta ... you confirmed it, perfect.
In Pro, login most probably expired and usually, it is automatically restored, but because of your issue, it does not work anymore. Sorry for this, Beta needed :).

@balloni55
not clear from UI, I know, but the top panel with "Login required" is not clickable. It is the same as in Pro version > just information panel. Login is automatically called at the moment, you use the function that  needs a login, like load of PQ files.
Anyway even here, you see only "loading", hmm. In which browser login opens? Or you see a browser with the same blue top panel as is in Locus (and "Powered by Chrome" visible under top right three-dot menu)?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 15, 2019, 17:37:03
I am not logged in and whatever I try to do regarding access to groundspeak, Locus map is crashing. I have sent in two crash reports.

My address is stig.vi......@gmail
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Viajero Perdido on February 15, 2019, 17:55:48
whatever I try to do regarding access to groundspeak, Locus map is crashing.

You are referring to the beta, I hope.

I need to be sure 3.36.2 (non-beta) works properly.  I have a trip coming up, so it's mission-critical for me right now.  I've disabled auto-update to prevent mid-trip surprises.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on February 15, 2019, 18:03:56
Quote
Anyway even here, you see only "loading", hmm. In which browser login opens?
if i click top right 3dot button "Opera" or "FF" is available.
First i tried Opera, login on browser ok, but im not logged in inside locus
next i tried it with FF, since that time locus crash alway as reportet from @ locus.sv@heime.org
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 15, 2019, 18:11:33
Ah thanks guys, got it. I'll prepare one more version with hope. it will finally work ...
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 15, 2019, 18:24:05

You are referring to the beta, I hope.

Yes, I am
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 15, 2019, 19:45:06
Ah, more complicated then I expected anyway new version 3.26.2.5 published. So third try ...

@balloni55 , I'm worried that Opera browser will be, as usual, causing troubles. So at least for now, try to use any different browser for login, thanks.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on February 16, 2019, 07:13:01
V 3.36.2.5
login to GS work  :)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: jonny.blue on February 16, 2019, 08:57:46
Yes, now I'm connected with my account. It seems as if the permission of Pro is used because I didn't need to allow a connection ....

Several things are working ... but if I use "log a trackable" I receive an error :
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: jonny.blue on February 16, 2019, 09:03:04
When loading trackables within the log dialog similar error occurs:
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: jonny.blue on February 16, 2019, 09:05:18
BTW 🙄.. would be (very 😊) nice to have the ability to upload a picture directly with a trackable log.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 16, 2019, 13:45:42
Login works, finally :)

Forbidden error: hmm nothing like this happen to me. What should I do exactly to simulate it? If some tracking code needed, send me it over PM, thanks.

And images for trackables ... we may discuss improvements once all existing functionality works as before ;).
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 16, 2019, 15:56:28
Beta 3.26.2.5, navigation warnings do not work. I will describe it in Czech because it is very complicated for my English. Sorry.

V poslední betaverzi mi nefungují navigační příkazy. Navigace trasu vytvoří a správně se zobrazují i vzdálenosti k místu odbočení. Zobrazení zvýrazněné šipky přímo v mapě je taky v pořádku. Nezobrazí se ale symbol šipky v okýnku nahoře (je tam nějaký divný kruh na silnici) a navigace nevydává hlasové pokyny. Nastavení hlasu je v pořádku protože na začátku trasy jsem dostal hlášení: "Můžeme vyrazit", pak celou cestu nic až na konci trochu podivné: "Čárka po XXX metrech budete u cíle". Správně asi mělo být: "Odbočte doprava a po XXX metrech budete u cíle". Vypadá to tedy na nějaký problém předávání příkazů vytvořených Broutherem Locusu. Ve verzi PRO je vše v pořádku, přikládám dva SCR stejné trasy z verze PRO a BETA.
PS: nový dialog pro zobrazení POI je moc hezký. Má to být náznak budoucí grafiky, kterou se bude Locus ubírat?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 16, 2019, 17:23:44
Really interesting. These small red arrows usually indicate "via-points".
You use default config for car routing? So Car >Fast, routing profile: Car-FastEco?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 16, 2019, 18:08:35
I first noticed the CarFastEco profile for the first time. Then I tried it with my own bike profile but with the same result. In the Pro version, I have the same settings and there it works.

Cz: Poprvé jsem si toho všiml opravdu u profilu CarFastEco. Pak jsem to zkusil i s vlastním profilem pro cyklistiku, ale se stejným výsledkem. Ve verzi Pro mám úplně stejné nastavení a tam to funguje.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: jonny.blue on February 16, 2019, 18:19:56
Quote
Forbidden error: hmm nothing like this happen to me. What should I do exactly to simulate it?
For me the error always occurs when
- I log a cache as found/or note and within that log dialog I want to load my inventory
- when I'm in a cache detail and I want to log only a TB visit. Entering the code works: the TB is found and shown. Ican choose visited, drop etc. But when I press "Log" the error occurs.

What works is just a log in a TB, such as discovered, note ...


Quote
we may discuss improvements later ..../quote] O.K.👍
Title: Import pocket query
Post by: jonny.blue on February 16, 2019, 18:21:35
The import of a pocket query looks as if it stops in the middle of loading ....🤔
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 16, 2019, 20:16:51
I get the same errors as Jonny.blue regarding trackables.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: alezy on February 17, 2019, 10:03:57
Some issues:
1. Track style editor opens very-very slow, about 8 seconds.
2. If I'll configure line slyle in route planner, it is not applied on manually drawn segments, only for calculated. And sometimes style editor is "frozen", so I cann't edit values or select checkboxes and it is automatically closed.
3. And in Pro version I've seen one dialog box with confusing text, I cann't reproduce it again. It was shown after I've changed track style and press back key some times. Text on sceenshot is translated like "You have unchanged changes. Do you really want to cancel". And two buttons Cancel and Cancel :)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 17, 2019, 10:33:52
If anyone has encountered a problem with connecting to Google Drive in the PRO version after updating the Beta, then I offer a solution. Just create a backup in the Beta version and then open it in the Pro version. Access to Google Drive will resume.

Cz: Jestli někdo narazil na problém s připojením ke Google Drive ve verzi PRO po aktualizaci verze Beta, pak nabízím řešení. Stačí ve verzi Beta vytvořit zálohu nastavení a pak ji otevřít ve verzi Pro. Přístup ke Google Drive se obnoví.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: voldapet on February 17, 2019, 18:28:33
@john_percy
Thank you for detailed steps but I can't still simulate it. However it seems that in the 3th step (when you zoom back to the level 14),  the same map or maybe another one is also rendered. If you want to play with it - please disable automap loading (Settings > Maps > Offline maps), check that map overlay is also disabled and try it again. Thanks, Petr
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 17, 2019, 18:40:36
@voldapet: turning off automatic map loading for vector maps does indeed stop this effect.

Edit: furthermore, it is connected with the fact that I have maps with overlapping coverage in this area. LoMaps Scotland, OAMaps UK_Scotland, and OAMaps Great Britain. If I disable any two of the maps, the effect doesn't happen. (It may be worth noting that UK_Scotland has contour intervals of half the other two maps.)

Edit2: I can confirm that the extra contour lines are due to *both* the standard and the higher resolution sets displaying at the same time.
Title: Re: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: lor74cas on February 17, 2019, 20:26:29
Hello,
today my wife was looking fom my position with locus on his 5.1 androd device.
She was able to follow me all the time, at the end exited locus but live tracking notification was still present. No way to delete it, not with the stop button, not with swipe, not with starting and exiting again form locus.
Just a reboot of the devicee did the trick.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on February 18, 2019, 00:57:55
1. Track style editor opens very-very slow, about 8 seconds.
@alezy - OK for me

2. If I'll configure line slyle in route planner, it is not applied on manually drawn segments, only for calculated.
confirmed - but maybe this is intentional to distinguish manual from calculated? I don't mind that.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: alezy on February 18, 2019, 07:36:45
@alezy - OK for me
Maybe problem with my device (Android 5.0.1 on MediaTek X10 processor), but I think that showing editor is rather simple operation and it must be completed more quickly.
confirmed - but maybe this is intentional to distinguish manual from calculated? I don't mind that.
Even if it is made  intentionally line width and color must be applied to all route segments.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 18, 2019, 19:20:48
@Žajdlík Josef
thanks very much. You have found quite a serious issue in parsing GPX files (that are received from BRouter as well), will be fixed!

@jonny.blue, @locus.sv@heime.org
I've found a few issues related to "Forbidden" error > improved. Anyway it's because of some missing info in the request but there is so many combinations ... you have item, somebody other has tb item, it's in some cache where you are now, different cache .. ah ... next version and we will see :). The error message should be now exact text from Groundspeak so hope it tells more if the error appears again.

Problem with the import of PQ, if any, is definitely not related to Geocaching itself. If you download your PQ file and start import manually, the same issue happen? It will be most probably the same issue as I fixed based on Josef feedback (start of this post). So please test the next version.

@alezy
1. "slow open" > only in Route planner or also in detail of already stored tracks? I see no similar issue. Does it happen also when the route planner is clean, with no track planned yet?
2. hmm, this is most probably correct, good observation. I have a todo list of bigger tasks to improve in Route planner when there will be "Route planner work-time". Even if this does not look, it is a more complicated task. As also @Andrew Heard wrote, it is not a big problem. On the second side, even manually draw long line colored by elevation from HGT should be really useful, so I consider this as something, that should be improved.
3. dialog ... heh, nice, but I tried for a while to find it, but no success so far

@lor74cas
really interesting, never saw this problem :/. Will be watching it, so thanks for the report.

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: alezy on February 19, 2019, 07:29:46
@menion
"slow open" - always, in route planner with or without route and in track details too. I was looking for logcat, but no any interesting info found.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 19, 2019, 14:20:20
Version 3.36.2.6 published.

@alezy
hmm let's try one thing ...
- update to new beta version
- after start, long! click on the main menu icon a in new "Dev menu" click on the "measure method usage". Right after this open any track or Route planner and be ready to just once click on "Line style" to open editor.
- after you will see "Tracking started" (after 10 seconds), just once click on "Line style" to open editor and leave it be until you will see another green toast with "Tracing finished into file ..." (after one minute).
- send me or attach here generated file (placed in root of Locus folder).
Thanks
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: alezy on February 19, 2019, 15:47:46
@menion, done
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 19, 2019, 16:20:06
Beta 3.36.2.6
Navigation from both internal and user profiles is fully functional again. Good job.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 19, 2019, 16:58:12
I tried to log found it on a cache and also log visited on two trackables. The trackables failed and the app also tried to log found it twice.

If I log the cache without any trackables, it is logged only one time.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: slarti76 on February 19, 2019, 17:55:14
In the track editor, when I e.g. delete points, there's a big green "Process successful" toast.
a) That's pointless - I can see that the process was successful. Only makes sense to show when something goes wrong.
b) It stays on way too long, and as long as it's there I can't use the < and > buttons. Slows quick deleting of track parts down a lot.
I don't know if that's new in this version, but it wasn't like this from the beginning.
Title: Trackable logging
Post by: jonny.blue on February 19, 2019, 19:04:50
If I just use "log a trackable" then this is now working.

But the "load trackables" - button (to load the inventory) within a cache log page results in an error:
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 19, 2019, 19:08:01
I am not able to log trackables from the blue button inside log manager. The window listing the trackables is flashing briefly and closes immediately.

Stig Vidar

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 19, 2019, 22:31:48
@alezy
this will be complicated :/. Thanks for tracelog, I see there some issue in creating the view, but unfortunately, from this Beta version, it is not clear why this happens. I'll firstly try to ask my colleagues if they won't be able to simulate it. Does same issue happen also with the Pro version? Does this happen before? You are the only one who wrote to me about it.

@locus.sv@heime.org
ah, this helps (two screenshots), thanks! Seems that all trackable logs now needs a text message wrote by user. Not sure why I did not notice before. Anyway, it complicates UI a lot for quick "visited" and "dropped off" logs. Can you (or other active geocachers, @balloni55) imagine some automatic text always inserted into these quick logs?

Like simply for "visited" log insert "visited" and for "dropped off" insert "dropped off"? I know, you will want to configure these texts ... later :).

The second error is also nice, seems even a geocaching server had some problems with it. Why this happens is not clear to me. Did you tried to send the same log again or was this done by Locus itself automatically?

Log trackables from "Logs manager": I've found this as well and also found an issue here with logging. Fixed, thanks.

@slarti76
good point with this notification. Removed, thanks.

@jonny.blue
I've found that in certain cases, Locus did not marked send trackable log as really send. What happens to you is that Locus Map tries to firstly upload not yet send logs (which were already sent) and then try to load your inventory. Just press left button to throw away this log. Anyway will be fixed in the next version.

---

Thanks all for testing of this geocaching stuff. As I wrote, Groundspeak decided to completely change it's old API so I had to completely rewrite little-complicated logic around logging & few other stuff in the app. So already quite well-tested system needs to be re-tested again. Appreciate your time, because I know this is a problematic topic for testing mainly because no one wants to spam other caches or trackable.

Do not forget, that in Beta version is possible to enable communication with staging.geocaching.com (in the app expert settings), which is testing copy of original Groundspeak server where everybody may do whatever wants ;). Ideal place for testing.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: voldapet on February 19, 2019, 23:07:57
@john_percy
I had short talk with menion about this issue and it's problematic to use overlapping maps with autoloading. It can really cause this issue. Unfortunately I don't have any solution for it...
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 20, 2019, 00:13:05
@voldapet. Understood, but it seems very strange to me that this is only initiated on going from ZL13 to ZL14. If it's so difficult to control, why does it not happen under other circumstances? Ah well.


Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on February 20, 2019, 04:10:39
Is the Locus World live tracking webpage working? I get an error for https://www.locusworld.com/. Also the Locus Map website link @ https://www.locusworld.com/ simply redirects back to https://www.locusmap.eu/live-tracking-chat/. Confusing.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 20, 2019, 07:17:25
@locus.sv@heime.org
ah, this helps (two screenshots), thanks! Seems that all trackable logs now needs a text message wrote by user. Not sure why I did not notice before. Anyway, it complicates UI a lot for quick "visited" and "dropped off" logs. Can you (or other active geocachers, @balloni55) imagine some automatic text always inserted into these quick logs?

Like simply for "visited" log insert "visited" and for "dropped off" insert "dropped off"? I know, you will want to configure these texts ... later :).

The second error is also nice, seems even a geocaching server had some problems with it. Why this happens is not clear to me. Did you tried to send the same log again or was this done by Locus itself automatically?

Log trackables from "Logs manager": I've found this as well and also found an issue here with logging. Fixed, thanks.

A quick solution would be to use "visited" and "dropped off" as you suggests.

Regarding the second error, I was only sending this log a single time and the double log was done by the app itself. Has it something to do with the failed trackable log?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: alezy on February 20, 2019, 09:03:06
@menion, the same behavior on the pro version. I have checked the spring versions - the dialogue opened 1.5-2 times faster. If resolution of problem is complicated and there are no more messages from other users, then you can be consider it as a problem of a separate device/firmware and does not take into account.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 20, 2019, 11:10:30
@Andrew Heard
from where comes locusworld.com address?
Just a few days ago we published a new page for live-tracking on: https://live-tracking.locusmap.app ... it's not yet 100% finished, but most for version 1 is already done (mainly "users guide" is in preparation).

So @all ... if anyone uses LT, feedback is welcome of course :).

@locus.sv@heime.org
hope that duplicate send was made by the problem with trackables. Anyway, even with the current Pro version, it should be possible over logs manager to send twice "found log". Never tried it before :).

@alezy
I'm mainly curious why this happen. We will have to find it over logs. New beta version now have some error logs ... so try it, create log after you open style editor and then in log, should be few lines with text "createDialog, step..." so extract them or just send me full log, thanks.

And new Beta with few more fixes 3.36.2.7 is out.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: alezy on February 20, 2019, 13:57:10
@menion, in log last step is 6, but after it Locus is waiting something.
Total time to show "Line style" dialog with "use style of folder" enabled is 8 about seconds. Swithing off "use style" takes about 3 seconds. Subsequent on/off of this option works immediately.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Christian on February 20, 2019, 18:08:06
I'm not saying that IPB is ideal. It is just proof of concept if something similar should not be useful create. The algorithm of IPB value is private thought.

Petr for some time works on new system how to publish tracks over Locus Store and we will need also some method how to say to users how difficult certain track is, so it is an actual topic for me.
I'm a little late but i would like to point to an algorithm (https://www.climbbybike.com/climb_difficulty.asp) used for cycling in the mountains. I tried different methods to compute the difficulties of different sports but I'm not satisfied. All I know is that different sports need different algorithm. But it would be nice to have an index...

@all
What do you think about visible top-right value in list of tracks for every track? Currently, there is average speed as base value (when sorted by name, dist, time or date). What about change to "elevation gain" as asked here https://help.locusmap.eu/agent/object/14703#comment-67047 ? Anyone against it?
The list page of the track manager is a pain in my neck since the useless thumbnails were introduced, the name of the tracks are shortend, important information are hidden a.s.o. :(
I would prefer to be able to decide by myself what should be displayed. Distance, elevation gain, difficulty like IBP and some lines of the description would be fine and enough for me. (What about the old idea of track ratings = 5 stars?). No thumbnails are needed. An icon if the track is circular or not would be nice.
A configurable display in track managers list as a template for each folder / group would be fine.

my 5 cents.
Christian

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 20, 2019, 18:18:00
It would be easier if this list was scrollable :-)

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 20, 2019, 18:30:57
I was sending in houndreds of trackables and tens of found it logs. For every 30 trackables I got an error I could retry, but for every 30 found it log I had no other option than aborting and open log manager and continue.

In both cases I would prefer if Locus Map could slow down so much that this error didn`t happen.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 20, 2019, 18:41:15
I know I shouldn`t log found it on own caches, but wanted to try. I think Locus Map should catch this error and don`t place the cache in the queue in the log manager. I have not found a way of deleting caches from log manager, but have to mark them as found to get rid of them.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on February 20, 2019, 22:21:59
I don't think this is a new bug but just observed in Pro: track time for new created route is 430,584:13:25. Steps: route planner > create route > save > track time should be 0? Also why navigation data source offers car, and route planner therefore estimates travel time for car, but from the track details > More > Travel Time there are 15 options, none of which are related to a car or other transport modes available for selected navigation data source. See related topic .  (https://help.locusmap.eu/topic/new-route-planning-ad-car-time-estimate#comment-62800[/url)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 21, 2019, 09:49:37
@alezy
hmm between step1 and step6 is only 200 ms! So in creating UI won't be a problem. Your log is full of some information about "FwkPlugin". Not sure what is it but seems it may slow down the display of the screen. Anyway "step6" is last moment before screen should be visible, so sorry, I have absolutely no idea what happens here :/.

@Christian
thanks for the algorithm, I'll look at it.
About the list of tracks: well, I was doing just a tiny improvement not some huge changes.

@locus.sv@heime.org
- scrollable list ... heh sorry, fixed
- problem with "Too many requests". In the app is already defined pause between requests, but seems not to be enough. So next version ...
- logging own cache: I've firstly removed "found" and "not found" option from list of logging options in the case, user is the owner
- delete log in logs manager ... best probably long click on the log and in opened point screen just delete log at top of the screen.

@Andrew Heard
what about mentioned locusworld.com domain? Where you get the info that this page is somehow related to live tracking?
The issue with time ... I'm trying to simulate this issue and still no success. I know about it, but still not found exact steps to reproduce it. Does this happen always for you?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: lor74cas on February 22, 2019, 22:31:24
In the attachment I post a formula for a self made IBP
Distance in km
Positive Gain m
Terrain (from 1, scale to be defined)
H1 altitude at start m
H2 altitude at end m
bpm optional but usefull for comparison of multiple session on the same track

It's just an idea I did just few tests with my runs

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 24, 2019, 20:04:12
Regarding the last beta version, while logging online and after I have refreshed my inventory, the trackable list is as shown in the first picture.

When I decide to log the second cache, I expect the inventory list to be the same as while logging the first cache, but instead I have to refresh again. The list is shown in the second picture. And it has to be refreshed on each and every found it log. The list is not persistent.

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 24, 2019, 20:15:05
If I by mistake try to log a trackable as visited which is not in my posession, I am correctly warned about this. But afterwards I get not expected double log error message.

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on February 25, 2019, 13:37:15
Hello menion,
i didn´t know behavior is only on BETA
while offline logging my found i attached a image to the log and wrote a title.
After upload the log to GS, on PC the title of the image isn´t there instead of is visible "Uploaded from Locus Map"
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 25, 2019, 19:17:49
@lor74cas
thanks for the tip. Will consider it!

@locus.sv@heime.org
Locus can't know if there were meanwhile any change in your inventory. That's why it always needs to reload your current fresh data. A big problem in the field? If so, then it may be better to log "visited" in batch over "Logs manager".

And to problem in second post. How did you do that "log a trackable as visited which is not in my posession"? :)

@balloni55
ah thanks, good point. I see that now it is supported only single text value for uploaded images, not two. So I'll remove "Description" field (which is used in Beta) and only "Title" will be used and correctly send, thanks!
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 26, 2019, 07:33:52
@locus.sv@heime.org
Locus can't know if there were meanwhile any change in your inventory. That's why it always needs to reload your current fresh data. A big problem in the field? If so, then it may be better to log "visited" in batch over "Logs manager".

And to problem in second post. How did you do that "log a trackable as visited which is not in my posession"? :)

My inventory does not normally change every 5 seconds  :) The problem was that the inventory list wasn't persisted in the app after I refreshed it. But I tried today while walking to the office and was not able to reproduce it. When I refresh my inventory, the list is now properly saved in the app so that I don't have to refresh it again a few seconds later when logging a new cache.

Regarding the second problem, I simply logged a cache as found without refreshing my inventory list. The Locus inventory list then contain trackables which is not in my Groundspeak inventory. When I try to log, I got correctly the error that the trackable could not be logged as visited. I also got this double found it log error.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 26, 2019, 15:19:41
Sorry, but I'm still unable to simulate something like this. May you please write me some steps to follow to simulate this error? I mainly do not know how to get to state when "The Locus inventory list then contain trackables which is not in my Groundspeak inventory".
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 26, 2019, 19:02:34
Sorry, but I'm still unable to simulate something like this. May you please write me some steps to follow to simulate this error? I mainly do not know how to get to state when "The Locus inventory list then contain trackables which is not in my Groundspeak inventory".

1. Log a cache online in Locus and make shure you refresh your trackable inventory and log them as visited.
2. Go to staging.geocaching.com and drop one of your trackables in a cache.
3. Log a cache online in Locus and DON'T refresh your inventory before you log your trackables as visited.

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Spartaner on February 26, 2019, 21:38:37
1. I can't find any way to clear the cached images for mapsforge V4 themes. That is to say, I've changed the icon for "ruins" in a theme and the V3 theme displays the new image but the V4 theme doesn't. I've tried clearing the caches within Locus.
Edit:. The beta version displays ok.

@john_percy
1. as I see, the cache will be probably somewhere in /sdcard/Android/data/menion.android.locus/cache directory. Maybe subdirectory "mapcache".
1. I've closed Locus, cleared all the files in the cache directory, restarted the phone, but the incorrect map icons persist.I read somewhere that svg files are bitmapped and cached at different sizes. That's what I want to clear, though it ought to happen automatically,

I have the same problem (https://www.openandromaps.org/oam-forums/topic/theme-variationen-elements-spinnen-warum), and hope it will disappear with the next Update of Locus Pro.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 26, 2019, 21:49:47
I'm afraid I had to uninstall Locus and reinstall it to solve the problem.

Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 27, 2019, 09:00:52
@locus.sv@heime.org
ah ok, so you made some changes directly on the web page. Then what happens in Locus is partially correct in the current system, when Locus use the list of trackables used in the previous log (as do now) without loading always fresh list. I may change this and always load the list of all available trackables ... but does it worth it? It will prevent this error but slow down a little logging system because it will need to download the whole list from gc.com.

@john_percy, @Spartaner
wanna solve it? I may try it just need to push to correct direction. So what should I do?
- download any map from OAM, also latest theme from OAM?
- then try it in app, close app
- change any icon and re-open app
... and icon remains same as before, that's the problem, right?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 27, 2019, 09:24:15
@menion
Thanks. Those are the correct steps, except it is any OAM Mapsforge V4 map.
I don't think the source of the theme mattered - I was working with my Voluntary Mapsforge theme.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 27, 2019, 12:08:35
@locus.sv@heime.org
ah ok, so you made some changes directly on the web page. Then what happens in Locus is partially correct in the current system, when Locus use the list of trackables used in the previous log (as do now) without loading always fresh list. I may change this and always load the list of all available trackables ... but does it worth it? It will prevent this error but slow down a little logging system because it will need to download the whole list from gc.com.

It's not about the message that the trackable cannot be logged. I expected that.

This is all about the error message that Locus is trying to log "found it" twice on the cache.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 27, 2019, 14:02:02
@john_percy, @Spartaner
the issue will be fixed in the next version. I've found a method how to specify where will be SVG images cached. So I've set Locus internal directory which is cleaned after app closes. Believe it will be good enough.

locus.sv@heime.org
hehe oki, but then I'm still unable to simulate it. If in your third step, I choose different cache, app firstly sends this "found" log, then tries to send trackable log and that's all. After closing first error with cancel, no additional "log found it" for the cache is send.

Ah maybe I see it ... you pressed "retry" when this error in logging trackable happen right? Hmm oki, I've fixed it now, hopefully :). Thanks.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on February 27, 2019, 14:07:50
@john_percy, @Spartaner
the issue will be fixed in the next version. I've found a method how to specify where will be SVG images cached. So I've set Locus internal directory which is cleaned after app closes. Believe it will be good enough.

locus.sv@heime.org
hehe oki, but then I'm still unable to simulate it. If in your third step, I choose different cache, app firstly sends this "found" log, then tries to send trackable log and that's all. After closing first error with cancel, no additional "log found it" for the cache is send.

Ah maybe I see it ... you pressed "retry" when this error in logging trackable happen right? Hmm oki, I've fixed it now, hopefully :). Thanks.

Actually, I pressed "discard log" on the trackable error
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 27, 2019, 14:53:25
New Locus Map Beta 3.26.2.9

Among many fixes and news, these are highlights:

- added horizontal filter for GPS locations! Needs testing anyway. To enable it, choose it's strength in expert settings (https://docs.locusmap.eu/doku.php?id=manual:advanced:customization:config#expert_settings). After that, best is to start track recording. On map will be drawn line created by track recording service and also dashed line created from original locations!! So you may really easily compare the difference.

- manually draw segments in route planner are now correctly colored and also saved in generated track (so elevation chart is also correct). Also, compared to the previous version, relative altitude coloring in route planner is over the whole route, not every segment separately (as was before), better?

- fixed few remaining problems with new Geocaching API

- more in news

EDIT: btw, did anyone checked "notes" in geocache detail? Now it is possible to get and use notes defined of the web page. Is this usable? If so, what app should more offer ... check if notes contain coordinates and offer to create of waypoint(s)?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on February 27, 2019, 19:38:15
Beta 3.36.2.9 crashes upon application termination. An interesting problem. Beta works seamlessly. But after closing the application with the Back button, an application termination error message will shortly be missed. Tested on Android 5 and 8. I tried sending an error message.
Cz:
Beta 3.36.2.9 havaruje po ukončení aplikace. Zajímavý problém. Beta bez problémů funguje. Ale po zavření aplikace tlačítkem Zpět krátce problikne chybové hlášení o ukončení aplikace. Testováno na Androidu 5 a 8. Zkusil jsem odeslat chybové hlášení.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: lor74cas on February 27, 2019, 22:29:14
Beta 3.36.2.9 crashes upon application termination. An interesting problem. Beta works seamlessly. But after closing the application with the Back button, an application termination error message will shortly be missed. Tested on Android 5 and 8. I tried sending an error message.
Cz:
Beta 3.36.2.9 havaruje po ukončení aplikace. Zajímavý problém. Beta bez problémů funguje. Ale po zavření aplikace tlačítkem Zpět krátce problikne chybové hlášení o ukončení aplikace. Testováno na Androidu 5 a 8. Zkusil jsem odeslat chybové hlášení.
Confirmed, it's the same with Android 7

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: john_percy on February 27, 2019, 22:32:47
Same for me on Android 8.0.0.
Also Menu > Exit gives green toast asking me to "Press 'back' again to exit".
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: zossebart on February 28, 2019, 05:44:41
Beta 3.36.2.9 crashes upon application termination. An interesting problem. Beta works seamlessly. But after closing the application with the Back button, an application termination error message will shortly be missed. Tested on Android 5 and 8. I tried sending an error message.
Cz:
Beta 3.36.2.9 havaruje po ukončení aplikace. Zajímavý problém. Beta bez problémů funguje. Ale po zavření aplikace tlačítkem Zpět krátce problikne chybové hlášení o ukončení aplikace. Testováno na Androidu 5 a 8. Zkusil jsem odeslat chybové hlášení.
Also confirmed on Android 5.1.1!

Manual drawn parts in Routeplanner are nicely handled now!

Gesendet von meinem D5503 mit Tapatalk

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on February 28, 2019, 07:30:27
@Andrew Heard
from where comes locusworld.com address?
Just a few days ago we published a new page for live-tracking on: https://live-tracking.locusmap.app ... it's not yet 100% finished, but most for version 1 is already done (mainly "users guide" is in preparation).
@menion - sorry I can't now recall exactly where the locusworld.com link comes from. It was related to getting live tracking working. However as I said, the page https://www.locusmap.eu/live-tracking-chat/ has a link "Locus Map website" which links to http://www.locusmap.eu/live-tracking/ but then redirects back to the same page. The link is broken.

When trying to enable live tracking (Wifi enabled, flight mode) there was a Locus login screen with title "Locus World"? And I got various error codes as shown in the screen captures. All was resolved when flight mode was disabled, and data enabled.

I also note that www.locusworld.com redirects to http://www.wivara.com/?

It appears the page http://www.locusmap.eu/live-tracking/ has changed to https://live-tracking.locusmap.app/.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on February 28, 2019, 09:17:57
The DOWNLOAD & MENU buttons on the live tracking web page when displayed on a phone take up considerable screen space. Can the DOWNLOAD button be incorporated into the menu, and the MENU button float over the top of the map similar to the right side << group button?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on February 28, 2019, 12:04:35
Ah thanks for "closing app" bug. Should be fixed now.

@Andrew Heard
I've added the redirect to mentioned post to new live-tracking web page so it should work correctly now, thanks.
- when you find a place where we mentioned "Locus World" page, let me know. It is not even our domain so it should not exists anywhere.
- problem with login over wi-fi ... hmm hard to solve. Will try it, but I'm worried it was mostly some local Earth disturbance :).
- and feedback to live-tracking site, perfect, finally someone! Good point, we will think about it, but make sense!
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on March 01, 2019, 01:06:38
@Andrew Heard
- and feedback to live-tracking site, perfect, finally someone!
@menion - no other feedback? weird. Maybe everyone already 100% happy ;-)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on March 01, 2019, 02:58:51
the current user list on live tracking web page (https://live-tracking.locusmap.app/online-trackers/) (from Vivaldi browser on Windows 10) looks a bit rough
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on March 01, 2019, 07:46:10
Smaller problem with map loading in Beta. When I launch Locus, the map will be immediately displayed. However, if I have a GPS turned off and I turn off the phone now, only a white area will appear when I turn on. To view the map, I have to click on the white area. The GPS is turned on and the problem is drowned. The PRO version is all right.

CZ: Menší problém s načítáním mapy ve verzi Beta. Když spustím Locus, mapa se ihned zobrazí. Pokud ale mám vypnutou GPS a vypnu nyní telefon, po zapnutí se zobrazí jen bílá plocha. K zobrazení mapy musím kliknout na bílou plochu. Pokuj je zapnutá GPS tak tento problém nanastává. Ve verzi PRO je vše v pořádku.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on March 02, 2019, 18:59:38
I have done some testing of the latest version and I haven't found any issues with it  :)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on March 05, 2019, 18:09:38
I have mentioned it before that I have to refresh the inventory for each found it log I make. Then I was not able to reproduce it, but I was able to record a video of it now. Each time I try to log found it, I have to refresh the inventory.

http://download.heime.org/ScreenReord_2019-03-05-17-37-06.mp4

Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on March 07, 2019, 15:34:17
New Beta version 3.36.2.11 > candidate for release

Changes are summarized after app start. I would like to focus on fine-tuning before release, so feel free to report whatever you want to improve/fix ;).

@locus.sv@heime.org
thanks for the video, but I'm still unable to simulate it :/. Seems that Locus Map loads still same old inventory, weird.
Currently, when you start creating a new log, Locus Map finds latest "found it" log, extract from it all "visited" trackable logs and add it into "trackables" panel. But not for you, hmm.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on March 07, 2019, 20:50:35
Unfortunately, the issue with the map persists. Android 8, OSM map.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on March 07, 2019, 23:36:59
@menion - a very minor & cosmetic request - but it would be nice if when the new release notes are displayed by the beta, and you scroll down the list but then switch to a different app or tum off the display, when you return to Locus Beta it doesn't repaint the list starting with the first line i.e. it forgets the scroll position within the displayed list. Do the release notes need to be repainted at all?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: jonny.blue on March 08, 2019, 20:48:19
Quote
so feel free to report whatever you want to improve/fix ;).
Tried several geocaching functions (log online/offline/as fieldnote ; TB logs;  picture upload; bulk log via logmanager)... and all worked well.😎 (for me😉).
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on March 08, 2019, 21:21:34
@Žajdlík Josef
I noticed the same issue maybe twice, but was never able to simulate it, weird. Will try it once more, thanks for the reminder.

@Andrew Heard
sure, I'll check it. Believe it's "fixable" :)

@jonny.blue
very glad to hear it

Btw. please @balloni55 or anyone other who play geocaching more then me (very little now), try to play little with "notes" for caches. I need to know if it makes sense and if small improvement is usable. And ... maybe, if there is something more app can do. Thanks!
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on March 09, 2019, 07:12:48
Experience. If I turn off the phone and turn on before On Screen Display appears, the map will be displayed correctly. But if I turn it on later, only POIs will appear, but no map. GPS must be turned off.

Cz: Zkušenost. Pokud vypnu telefon a zapnu dřív než se objeví On Screen Display tak se mapa zobrazí správně. Pokud ho ale zapnu později, tak se zobrazí jen POI, ale mapa ne. Musí být vypnuta GPS.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on March 11, 2019, 12:52:40
Quote
try to play little with "notes" for caches.
for me it´s well usable
- if i run "update cache" text of note from GS is loaded but message online is furthermore "not loaded yet"
- upload note with no content isn´t possible
- no hint "uploading note overwrite note on GS"
- only cosmetic... after save/upload a note the cursor is blinking furthermore
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on March 12, 2019, 10:41:56
@Žajdlík Josef
perfect, got it, fixed thanks!

@balloni55
thanks for feedback!
- "update cache" downloads all data from gc.com anyway between this update and between moment you display "Notes" dialog, you may change notes on the web. So this small dialog is completely independent and it's always needed to load fresh new notes. Which is correct I believe.
- upload without content is not possible in GC API. Make it sence to fake it with just " " (space) character?
- "hint" ... hmm is it needed? I'll risk it :). Uploading is there for quite a long and till now no problem.
- and cosmetic problem ... when I tap "save", dialog is dismissed immediately right? In case of upload, it's little weird, agree. I'll try to improve it.



So thanks all for quite an intensive testing. Seems there is no serious issue, so I'll risk and release new version during next days ...
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: balloni55 on March 14, 2019, 11:08:38

puplish "notes" as it is, we will see ;)

there is a small difference in topbar of beta
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on March 15, 2019, 16:43:51
Last Beta version 3.36.2.13 published.

The release of the new version is planned on Monday, because I really want to use a sunny weekend for some field testing.

@balloni55
nice obsevation, improved
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on March 15, 2019, 18:54:21
Last Beta version 3.36.2.13 published.

I am not able to do anything groundspeak related with this version.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on March 15, 2019, 20:29:12
Omg, I'm in love to GC even more. Yesterday I received an email from Groundspeak with

Quote
Today, hardware issues caused OAuth2 flows to fail around 3:28pm PST. To resolve, we are using the version of the OAuth2 code from before the changes that were announced in the last release. We are planning to re-release the code at 2pm PST tomorrow (March 14 2019). We apologize for the inconvenience.

Seems that changed something that worked to something that does not work so they reverted it back to something that also does not work?! ... I'm going to write to them. Thanks for the notification!

EDIT: hmm maybe it is something on my side :). Seems their change (reverted) on their side caused invalidation of existing logins and Locus is unable to correctly offer "re-login".

EDIT2: fixed version uploading on Google Play. It will most probably notify to "check internet connection", so just try it again. Not an ideal solution, but I consider this as a rare case.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on March 16, 2019, 11:02:52
Tried 3.36.2.14 and able to log in with this version. But I am not able to load the online cache note from GC to the phone. Uploading the other way from phone to GC works.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: erfi on March 16, 2019, 11:55:39
Beta version 3.36.2.14: The Track-Name of Export-File isn't correct.
(https://i.postimg.cc/Hc94ccv9/Locus-beta-3-36-2-14-Track-Export.jpg) (https://postimg.cc/Hc94ccv9)
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Andrew Heard on March 17, 2019, 00:00:41
latest beta: tracks sorted by Nearest - all distances are 0m, but when sorted by advanced > distance to Start, the distances are valid. Note - performed inside office test with GPS turned off.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: skwal on March 17, 2019, 00:35:58
When will the normal Version get an Update?
The strava Auto Export mistake is really annoying
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on March 17, 2019, 09:47:03
@locus.sv@heime.org
same problem with the download of notes with all caches? Some error message visible?

@erfi
ah thanks, seems that custom name is completely ignored, fixed!

@Andrew Heard
interesting, I can't simulate it with any folder. Does this happen to your will just a single folder with tracks or will all you checked?

@skwal
most probably (90%) tomorrow
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: locus.sv@heime.org on March 17, 2019, 10:41:25
@locus.sv@heime.org
same problem with the download of notes with all caches? Some error message visible?

Same with all and no error messages

I recorded a video of it
http://download.heime.org/ScreenReord_2019-03-17-10-29-24.mp4
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on March 17, 2019, 13:48:16
Thanks for the video. I've found based on this video that there has to be some error but is never displayed on the screen. I'm more then sure, there will be a need for some bug-fix version a few days after release. So, please test release version tomorrow and I'll try to fix it then based on the visible error message, thanks.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: Žajdlík Josef on March 17, 2019, 17:48:39
I confirm that the display map issue has been resolved.
Today, while riding my bike, I felt that the dashoboard slope was more accurate than last year. Instead of SRTM data, Locus would have taken the data from the barometer. Is it just my feeling or has there been a change over the past six months?
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: LocusUser#1 on March 17, 2019, 18:34:16
In the track list, only zero is displayed for all values.
When editing a track or new recording a track, the correct values are displayed.
This affects all tracks in all folders. Both in the Pro and in the current beta.
Title: Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
Post by: menion on March 18, 2019, 14:51:26
So new version 3.37 is finally out. Today, only for 25% of all users for the test, tomorrow rest. It was long as I see by dates ... 6 weeks since the last release.

Thanks all for the very useful help as usual. Can't imagine continuing in work after all these years without this interest on your side :).

@Žajdlík Josef
don't remember if I did any optimizations in slope ... maybe, based on discussion with Andrew, there were some smaller filtering & minor changes. If you feel it's better = perfect :)

@LocusUser#1
ah thanks, got it, should be fixed