[APP] - version 4.29.+ ( 4/2025 )

[Menion]

@freischneider
track previews > thanks

@Morris75
If I see correctly, the time of the track is at the start in the "metadata" section and is correctly set to real time when the route was created. Times at trackpoints should not be important.

@Graf Geo
crash when editing track > it is the same problem as with previews. Fixed, thanks.

@Sonny
Google translate > well, I do not have this under control. It just forward text to the other app.

Live map > it displays content based on center + radius and not the visible bbox. So probably remaining 6 caches is simply out of visible box.

[Sonny]

Google translate: do you have an idea if there's another sharing-method to make Google translate recognize that second sent text (once the app already opened) is new text to translate?

Live map import: are you able to use visible BBOX instead of radius instead? GC4L-addon somehow was able to do this. Cause if we just want to import the 2 Caches seen on Live-map we don't want to get 6 Caches, which are unvisible also in the "radius" ;-)

[Graf Geo]

Coincidentally noticed: Beta 4.29.0.3 out now.

Track overview and edit bugs are fixed. 👌👍

[Tapio]

Coincidentally noticed: Beta 4.29.0.3 out now.

How's GDrive download for you guys recently? For me, downloads aren't mostly starting, as in screenshot.

[T-mo]

Hello,

I've discovered a problem with the route planner.
When I create and save a route, my route is saved with the date 1970-01-01T and the time 00:00Z, see attachment.
...
I don't know which version this is from. I just noticed today that I exported a GPX file and another app displayed it with the date 01/01/1970.

Mystical 1970-date.
Just search the forum for 1970
I temporarily struggled with it with LM 4.28 and some older db-entries.

I guess it's hardcoded somewhere in Locus-code and used as fallback-date by Menion at some function-calls. Or whatever. Obviously it also seems to be used for those waypoints-time-stamps during generation.

Yes, no-one needs those 1970-dates. Though it indicates some lack and outdated handling  

[wollewolle]

Hi,

not sure if it's only beta version related (4.29.0.3) I get several times the attached error. Not sure if the last sync worked only with the release or also with a previous beta version.

Wolfgang

[Graf Geo]

Nope, I synced without any problems.

[Graf Geo]

Hmm, recently (with 4.29.0?) the tracklines in the mini-overviews in the library have been made thicker so that they are more visible. That's ok.

Unfortunately, this also affects the large track overviews and the image & stats that you can share. The track lines are now much too thick, so that the underlying map details are covered... See screenshot.

[Andrew Heard]

Yes, no-one needs those 1970-dates. Though it indicates some lack and outdated handling  

@Morris75 @T-Mo 1970 - as posted - Unix/ Linux "time zero". Also as posted @Menion explained the metadata timestamp is the important one.

How's GDrive download for you guys recently? For me, downloads aren't mostly starting, as in screenshot.

@Tapio - download to Windows 11 worked for me & unlike false "virus" detection with 4.29.0.2, Microsoft Virus scan didn't complain this time ;-) BTW to clarify, I mean working with Google Drive webpage not GDrive app.

[michaelbechtold]

How's GDrive download for you guys recently? For me, downloads aren't mostly starting, as in screenshot.

@Tapio - download to Windows 11 worked for me & unlike false "virus" detection with 4.29.0.2, Microsoft Virus scan didn't complain this time ;-)
[/quote]
I stopped using the GDrive app for downloads as it fails consistently; using FireFox on my smartphone does work with some extra clicks (no virus check, bla, bla).

[Graf Geo]

I always do this on my smartphone. I have created two favourites for the two GD drives (versions and testing). Confirm "download anyway" once and then the download always works without any problems.

[Graf Geo]

Hmm, recently (with 4.29.0?) the tracklines in the mini-overviews in the library have been made thicker so that they are more visible. That's ok.

Unfortunately, this also affects the large track overviews and the image & stats that you can share. The track lines are now much too thick, so that the underlying map details are covered... See screenshot.

As I assume that the track lines for different purposes (thumbnail-oveviews in MyLib and track overviews / image & stats) cannot be generated with different thicknesses, here is an overview of the current situation: The older thumbnail-overviews compared to the new ones.

In my opinion, the new ones are definitely too thick. Perhaps a middle way can be found so that they are easily recognisable for all purposes, but do not obscure too much map detail.

The tracks shown in the screenshots have a thickness of 3 px in the original. The colour, patterns and transparency are adopted, but the thickness is not.

[Tapio]

I stopped using the GDrive app for downloads as it fails consistently; using FireFox on my smartphone

Download via browser works. I did the same now, disallowed starting the GDrive app (cleared its cache, no success) on clicking a gdrive URL. I'm using Soul browser.

[Agus]

Hello.
In the new beta version 4.29.0.4 , when searching for a LoPoints category with connection I get a wifi error warning and it doesn't search but I don't have any wifi problem. Other online searches work fine.You cannot view this attachment.

[Menion]

Thanks, there indeed was an issue in the public version. 4.29.0.5 should fix it.

Please consider this implementation as the first testing version that has not been tested by anyone except me for now. I need it for a weekend trip, so I thought it should be useful for others as well 

@Graf Geo
thumbnails > I'll look at it next week.


Problem with Google Drive > hmm, hard to help on my side. The solution may be restoring the publication of the app over the Google Play Beta channel. There is anyway problem with slower reaction on problems and also inability to downgrade (I have to increase the version code by one with every new APK file).