Author Topic: Re: [APP] - version 3.37.+ ( 18. 3. 2019 )  (Read 16515 times)

Offline CabrioTourer

  • More than Newbie
  • *
  • Posts: 26
  • Thanked: 1 times
    • View Profile
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #105 on: May 01, 2019, 14:45:34 »
During my comparison between old/new recalculation logic I had the problem that Locus simple stopped and smartphone returned to launcher. It didn't show crash or anything else it just stopped.
This happened multiple times. Because time between locus or navigation start and stop issue were different each time I don't think it is because Firmware accu optimization or something similar. To be sure I disabled Doze mode completely but didn't fix the issue.
Don't know if this helps but I add three logs.

Happens on OnePlus 6, Rom (LR) based on AOSP.
« Last Edit: May 01, 2019, 14:47:48 by CabrioTourer »
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11478
  • Thanked: 323 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #106 on: May 01, 2019, 15:57:09 »
@tramp20
ok thanks. I'll have to play with it a little more than...

@poutnikl
I was of course also thinking along the route, not as a projection, don't worry. It is additional logic to the current system, so let¨s firstly try this first system and we will see.

@CabrioTourer
thank you for such precise testing! I just a few days back did some more tests and another small improvement that may affect this test as well, sorry for this.

Thanks also for crash logs. Unfortunately, I'm unable to perfectly find the reason of this issue but seems to be somehow connected to some active dashboard. Is this possible? If so, may you share this dashboard with me as well? Dashboard files are in Locus/data/dashboard directory. Thank you!

Method for navigation simulation

With the Beta version, there is a nice method of how to test the navigation system. I just improved it little more so the current method will work correctly in next Beta version (probably tomorrow):
  • plan a route you want to ride (that will simulate real movement) in the route planner.
  • save it and set it's "activity type". This will affect simulation speed
  • in skyplot screen (screen with satellites) in top menu choose simulation > track > and choose your track
Now it's possible to test navigation with "Navigate to" function or also on the route, planned with route planner.

You may also start the simulation with own recorded track > nice for repeating field problems.

In case of the problem with navigation, best is to share the track used for simulation and navigation route itself. Then, everybody may simulate exactly the same what happens to you on your device.
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline CabrioTourer

  • More than Newbie
  • *
  • Posts: 26
  • Thanked: 1 times
    • View Profile
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #107 on: May 01, 2019, 16:07:08 »
Regarding comparison old/new recalculation
While checking my videos I noticed I start navigation in Beta in a wrong way.

In release I selected a specific track point while map view and start navigation from this specific point (near sharp point 2).
But it navigates to end point, not specific point.

In Beta by accident I start navigation in track menu. Nevertheless it navigates me to nearest point which was between 1-2 which is very nice.

Redult is even worse for release.
Even if it knows which point I want to start navigation it selects end point by themselves and ignores User.

(Just a comment because it might be forgotten by all the error reports.
Locus is the most powerful navigation software I ever saw. Not only for smartphones. It has unbelievable features. Don.'t be afraid and keep up the great work)
 

Offline CabrioTourer

  • More than Newbie
  • *
  • Posts: 26
  • Thanked: 1 times
    • View Profile
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #108 on: May 01, 2019, 16:11:39 »
@tramp20

Thanks also for crash logs. Unfortunately, I'm unable to perfectly find the reason of this issue but seems to be somehow connected to some active dashboard. Is this possible? If so, may you share this dashboard with me as well? Dashboard files are in Locus/data/dashboard directory. Thank you!

Method for navigation simulation

With the Beta version, there is a nice method of how to test the navigation system.

dashboard was active and same as in release. Its appended.

Nrw simulation :
Wooowwww that's great.
 

Offline jajaballard

  • More than Newbie
  • *
  • Posts: 56
  • Thanked: 4 times
    • View Profile
  • Device: Nokia 8 (TA1004) with Android 8.1.0
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #109 on: May 01, 2019, 21:44:57 »
Hello Folks,
during my ride to I observe some strange behavior of Locus Map:

I usually have switch on: "Center map at GPS Position" after 5 sec.
Now in the current Beta, if I look at the map and pan a little around (moving the map), the map is not centering back after 5sec as before. The button is still highlighted.
To center back to GPS Position , now I have to manually switch off and on the "Center Map at GPS Position" button   ( for me at lower left corner)
This is very uncomfortable to handle, special in rougher terrain.
Regards
Ralf
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11478
  • Thanked: 323 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #110 on: May 01, 2019, 23:37:24 »
@CabrioTourer
thanks for dashboard file. It helped and issue found & fixed

Well, navigation in the app is somewhere ... in the middle. It works well in the case, you ride based on instructions correctly along the road. But once something happens, like a shortcut, change in directions, pause in GPS signal ... bad things sometimes happen.

I currently have priority in finishing updates in improved map system, anyway the number of complaints on navigation is growing so rather start now and improve it till the main season starts :).

@jajaballard
ah damn, thanks, fixed!
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 
The following users thanked this post: CabrioTourer

Offline Andrew Heard

  • Master of Locus
  • ****
  • Posts: 694
  • Thanked: 24 times
    • View Profile
  • Device: Samsung Galaxy A5 Oreo/8, Lenovo Note 4 Nougat/7.1
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #111 on: May 02, 2019, 02:02:01 »
Method for navigation simulation With the Beta version, there is a nice method of how to test the navigation system. I just improved it little
@menion - nice feature - my only suggestion is some way to speed up the simulated speed. I changed the recorded track activity from Not Specified or Cycling to Car, but still often too slow for testing. Some form of dynamic speed control would help. But very low priority.
 

Offline Žajdlík Josef

  • Padavan of Locus
  • ***
  • Posts: 332
  • Thanked: 14 times
    • View Profile
  • Device: Xperia M, Alcatel One Touch II, Samsung A3 (2017)
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #112 on: May 02, 2019, 12:36:50 »
Zoom lock on Pro: First tap on button restores the last zoom lock magnification immediately. Second tap reverts to initial unmagnified view...

Maybe it's related.  Manually zoom the map while driving will cause it to lock in one place.  The map is not in doubt.  When the screen goes out, the movement resumes.
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11478
  • Thanked: 323 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #113 on: May 02, 2019, 14:51:38 »
@Andrew Heard
speed problems > I wrote "I just improved it little more so the current method will work correctly in next Beta version" ;)

@Žajdlík Josef
hmm should be related thanks. I'll probably not be fast enough to create version today, so hopefully tomorrow.

----

Geocaching question

When logging a cache, there is an option "Log date only". Is there any reason for this setting now? When we enable this settings, defined time is used to replace {t} parametr in log, but on geocaching server is send log with time set to 12:00.
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline c.s.g.

  • Padavan of Locus
  • ***
  • Posts: 315
  • Thanked: 24 times
    • View Profile
  • Device: Samsung Galaxy Note 4
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #114 on: May 02, 2019, 15:15:39 »
Hi menion,
Geocaching question

When logging a cache, there is an option "Log date only". Is there any reason for this setting now? When we enable this settings, defined time is used to replace {t} parametr in log, but on geocaching server is send log with time set to 12:00.

For me it never makes sense, to log a geocache without the exact found time. So for me the checkbox could be removed. Then I expect the exact log time in {t} parameter and in online log at groundspeak when sending log to geocaching server or exporting it to a fieldnote-file . I. e. exact the same way the checkbox is not checked.

As far as I know the time is not storred at groundspeak server. Maybe it is changed with the new API, I do not know But I am using the time part of the log to get a chronological order of my founds per day. An, thanks to the {t}-parameter the found time is present at least in my logs.

In this forum there are even two posts about this checkbox I have answered. There the checkbox was accidentally checked and the user wondered why all logs where set to 12:00 at groundspeak server. Unfortunately the checkbox is hidden under the keyboard. So the state of that checkbox is not visible immediately.

c.s.g.
« Last Edit: May 02, 2019, 15:22:13 by c.s.g. »
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11478
  • Thanked: 323 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #115 on: May 02, 2019, 15:31:51 »
Yes, exactly because of these problems (hidden checked settings etc), I'm thinking about removing this setting and always log caches with an exact defined date. So I'm asking here if there may be any possible problem when logs will be sent with defined time and not with 12:00.
Thanks for answer c.s.g.
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline JoxM

  • More than Newbie
  • *
  • Posts: 86
  • Thanked: 6 times
    • View Profile
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #116 on: May 02, 2019, 19:59:39 »
For me the exact time for logging is absolutely necessary while fixed logging time 12.00h makes no sense at all to me.
The main reason for that is to keep the online logs in the right order (like found outdoors) even when logging in disorder (happens sometimes when logging additional (special/very good) caches done during a trail )
So no need to keep the checkbox from my side. Honestly I already wondered why it could possibly be there...
 

Offline jonny.blue

  • More than Newbie
  • *
  • Posts: 97
  • Thanked: 5 times
    • View Profile
  • Device: SM-G901F 6.0.1
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #117 on: May 02, 2019, 20:46:18 »
... 12.00h makes no sense for me too.
 

Offline T-mo

  • More than Newbie
  • *
  • Posts: 32
  • Thanked: 2 times
    • View Profile
  • Device: One+3
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #118 on: May 03, 2019, 00:10:31 »
Menion, congrats to this great step and your efforts to rework the vector-engine for improved dpi-awareness and adaption to newer mapsforge, happy to see this.

I am also using some raster-maps with limited zoom-levels, Z13 and Z16,to keep the map-size low and as Z14+Z15 doesn't brought a real gain in informations. But this only works if the zoom-transition between Z13 and Z16 is fine tunable, may depend on screen-dpi and personal taste. Sometimes I would prefer Z16 with value lower 50% instead of Z13 at 200%.
i guess currently I'm not able to finetune this or? Maybe in the future, not high prio, just realized this while using the new beta.
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11478
  • Thanked: 323 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Reply #119 on: May 03, 2019, 06:10:06 »
Geocaching
if I remember correctly, 12:00 time was needed to keep logs from people on geocaching.com in correct order under one cache. Something like this, but not perfectly sure now as it's really really long history.

Oki, so if even geocaching master @balloni55 :) does not have anything against it, I'll remove this option to next (Beta) version.

@T-mo
Understand that with a new system, this may be a little worst then before. Currently there is no settings that affect this behavior. I'll look at it if there isn't any option how to improve it in app and give a little higher priority to use in your case Z16 instead of Z13 if possible. Good point, thanks.
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!