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 - poutnikl

Pages: [1] 2 3 ... 30
1
I confirm such a frequent behaviour.

If it was permanent, the cause is often a missing icon in the applied map theme. But this is not that case, being temporary.

Odesláno z mého Mi A2 pomocí Tapatalk


2
Troubles & Questions / Re: Phone Compatibility with 3.38+
« on: June 05, 2019, 06:02:02 »
Not sure if still valid, but @menion have mentioned using Google play feature to make the release available just to subset of randomly selected users, releasing it to all later. It can serve as a pilot testing, if some nasty bug sneaks through to the release.

Odesláno z mého Mi A2 pomocí Tapatalk


3
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 04, 2019, 08:32:01 »



@Andrew Heard
interesting observation. As @tommi correctly mentioned, if screen is off, there is no visible map = no matter what I changed, it should have no effect here. If only running is track recording (is it?) then it is surprising, because I did not touched anything regards track recording service for a long time. Please keep tracking and confirm this, thanks.

Do I understand it right that the Kalman filtering of position applies only to screen rendering, while track recording uses unfiltered data ? But even if not, I guess battery impact would be minimal.



Odesláno z mého Mi A2 pomocí Tapatalk


4
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 03, 2019, 13:04:06 »


But another idea, you could internally do a quality upscale when user downloads low resolution raster maps. You could do quality upscaling and offer such maps, if license allows, in your store and become wealthy.

High quality upscaling of high contrast edgy raster graphics is much more sophisticated than upscaling of photos.

Upscalers often use advanced, edge directed interpolation, some even with support of outputs of neural network training, like NNEDI3 library of Avisynth video frameserver.



Odesláno z mého Mi A2 pomocí Tapatalk


5
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 15, 2019, 12:15:57 »
I have noticed several times something similar, redrawn after forced zooming in/out. 

Odesláno z mého Mi A2 pomocí Tapatalk


6
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 15:19:15 »
Confirming beta.13 runs fine, without crashing anymore.

Odesláno z mého Mi A2 pomocí Tapatalk

7
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 11:11:56 »
Even reinstalling of beta does not help. The beta, after displaying the news and receiving file access privilege, immediately crashed again.

I have sent the debug log recently via Google dusk sharing to locus.map@asamm.com, I hope it arrived.

Odesláno z mého Mi A2 pomocí Tapatalk

8
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 12, 2019, 20:13:21 »

My crashing mentioned above may be related to the V4 map deletion as well, as I had previously installed both V3 and V4map of Austria from OAM, with the Elevate theme.  About the time I deleted V4 map, keeping just V3., the problems started.

Odesláno z mého Mi A2 pomocí Tapatalk


9
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 12, 2019, 05:24:23 »
While previous beta was perfectly stable for me while crashing for others, now 3.37.2.12 is exactly the opposite.

I was successful to launch and use it several times,  but now it has periods of reproducible crashing at the moment of appearing of the start checklist and periods of reproducible running.

I have not found patterns yet when they switch.

Odesláno z mého Mi A2 pomocí Tapatalk

10
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 11, 2019, 11:39:41 »
Interesting.
The beta from yesterday have not crashed yet on my Xiaomi MI A2 with Android 9.

Odesláno z mého Mi A2 pomocí Tapatalk


11
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 10, 2019, 20:19:16 »
Interesting, as it does run on Android 9. Could the issues be related to incidental parallel running both Pro and Beta ?

Odesláno z mého Mi A2 pomocí Tapatalk


12
Troubles & Questions / Re: Problems with navigating a route
« on: May 10, 2019, 19:00:23 »
The new beta route priority recalculation seems working fine, doing deviations along a precalculated city walking route.

For both GPX based and directly calculated routes.

Odesláno z mého Mi A2 pomocí Tapatalk

13
Troubles & Questions / Re: Problems with navigating a route
« on: May 10, 2019, 18:25:36 »
Hmm, I guess I have asked @Menion by other words about this possible undesired tailing recently as well. :-) ( not having opportunity to test it yet.)

Odesláno z mého Mi A2 pomocí Tapatalk


14
Themes - Vector maps / Re: [Theme] Waymark
« on: May 09, 2019, 11:33:35 »
It is still as a free item in the Locus Store / Graphics, to be installed directly within LocusMap.

Odesláno z mého Mi A2 pomocí Tapatalk

15
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 03, 2019, 22:57:18 »



This is what I thought. I just asked to be sure because 100 trackpoints isn't much for activities like car and even not much for bike in rural area.

When I analyzed GPX files of multiple bike routes, generated by BRouter, I realized, that as a "rule of thumb", the is in average 1 trackpoint about every 50 m. I suppose less dense for car routes, more dense  for hiking routes.

Trackpoints from recorded tracks will be probably much denser, depending on the recording settings.


Odesláno z mého Mi A2 pomocí Tapatalk


Pages: [1] 2 3 ... 30