Guidance along route - sometimes no alerts for waypoints with Samsung S7

Wolfgang shared this problem 4 years ago
Closed

I use "guidance along routes" together with alerts/notifications on navigation-waypoints and screen on/off during biking. It's my most battery-efficient way of bike navigation. I create routes with BRouter with navigation instructions or I add navigation-waypoints manually on existing tracks.


I use guidance with screen on/off and TTS notifications on navigation-waypoints for several months with my LG G2 (Android 5.0) without any problem. Now I use a Samsung S7 (Android 7.0) and on 10-20% of the navigation-waypoints I get no notification and the screen remains off.


On the LG G2 and on the Samsung S7 I use Locus Pro 3.24.3 together with exactly the same track and same settings.


In both cases Locus switches the guidance from a waypoint to the next waypoint according to the setting "Set next trackpoint" (in my case 100m) - but sometimes I get no notification with the Samsung S7.


Is the Samsung S7 too fast for Locus? Is it a problem of Locus? Is it a problem with the Samsung S7?


best regards

Wolfgang

Replies (14)

photo
1

Good day Wolfgang,

little complicated task. I have reported few issues with TTS system in latest Locus Map version(s). I made some changes, but not sure if it helps. In next week will be published new Locus Map version 3.25, so give it a try and let me know if same problem happen again. If so, I may prepare special test version that will print out some useful information into log file, which should tell us more.

Thanks!

Btw: I develop Locus Map mainly on SGS7, so it won't be a device-dependant problem.

photo
1

Hi Menion,

in the last few weeks I have had little time for more tests, but I think I have an idea for a possible reason of the problem:

Now with the SGS7 I also use the function ANT+, which the LG G2 did not have. I use ANT+ with 3 sensors: Cadence, Speed and HRM.

When I record the track with the values of the ANT+ sensors this problem occurs.

Maybe Locus or an ANT+ service is busy with the sensors (or with something else) and misses the change of the trackpoint or at least the triggering of the notification.

If I record without the ANT+ sensors, the problem does not occur.

Is the "snap radius" too small for the notification? If Locus has processed the data of the ANT+ sensors or did something else, is the current position out of the "snap radius" for the notification?

best regards

Wolfgang

photo
1

Doesn't matter if 3.24.x, 3.25.x or 3.26.x

photo
1

Good day Wolfgang,

sorry for a delay in my answer. Let's solve this issue.

I'm checking source code of Locus Map, mainly part that generate sound notifications ( which result in screen on event ). There is a few requirements that needs to be full-filled to make this work.

So best configuration should be:

  1. enabled guidance notification in settings > guidance > set notification on next direction change
  2. in above settings selected Sound settings > Text-to-speech
  3. rather checked correctly set TTS system in settings > language > Text-to-speech
  4. and finally valid navigation waypoints along the track

Are all these conditions met? I expect so, but rather asking.


If all seems still correct, I'll have to create a test version for you, that will print us some information into text file, so I may see reason for this behavior. Let me know if I may create one, thanks and sorry for a complications.

    photo
    1

    Hi Menion,

    thank you for working on this issue!

    Yes, my configuration is as listed in 1-4. And most of the time Locus Map works as expected: Screen on/off and TTS notifications on navigation-waypoints works fine in 80-90% of the navigation-waypoints. The issue is: not in 100% ...

    I'd be very happy if I could help solving this issue using your test version. Maybe it takes a few days to collect the test data, because I don't use my bike in bad weather.

    I currently have few problems with this issue, but it would be important to me that the issue is resolved until spring 2018 when the season of the long distance biketours (Brevets, 200-600 km) starts.

    photo
    1

    I've left a similar question and just found this one. I use Samsung Galaxy S7 Edge.

    I have the settings as described all correct. But my waypoints placed in my track do nothing. If I select the waypoint on the map and select guidance to the point, I get the beeping alerts as I approach but the track is not part of the action. If I select guidance on the track, it's as if the waypoints don't even exist.

    photo
    1

    Good day Alan, Wolfgang,

    thank you for a little push here, I've completely missed this unsolved problem, sorry Wolfgang.

    As I read our previous communication, I believe most easy method to fix problem will be to simulate on own device.

    How are you creating track for navigation? In route planner? If so, are you able to write me start and end location and parameter ( routing engine (like BRouter) and type of routing )? So I may simulate it. Thank you.

    photo
    1

    Hi Alan, hi Menion,


    Alan, I think our concerns are different. As I understood you get no navigation notifications in general. I think this could depend on the guidance settings in the section "Tracks". I use "Set next trackpoint": 100 m, "Set notification of the next direction change": Sound (Text-To-Speach), "Out of route notification": Sound (10 Beeps), in "Advance Settings": Strict route: off, Number of alerts: Medium, Notify on every trackpoint: off.


    In addition you need "navigation waypoints" in your track which you can get (depend on settings) from BRouter or insert them manually in Route Planer.


    In my case normally I get the navigation notifications in guidance - but when I use several ANT+ sensors in Locus, Locus misses the notifications sometimes (in 10-20%). When I don't use the sensors I get all notifications. At least that's what I think I found out...


    Menion, thank you for working again on this issue! I'd like to send you an exported GPX-file with the coordinates. I recorded the track and then I added navigation waypoints with the (old) Route Editor. That's my main usage. For the long distance Brevets we get tracks which we have to follow and I add the navigation waypoints to be able to use guidance with TTS and normally disabled display. The navigation notification switchs the display on for 15 seconds. It's a battery saving way of navigation.


    I try to send the file per PN.

    photo
    1

    Actually this is the current sequence of events under navigation:

    I have auto-recalc ON, I use BRouter (offline) but it's the same with GraphHopper.


    1. The route is calculated and I hear a first instruction

    2. 100-200m later, the ? question mark comes up and locus beeps.

    3. Several seconds later, the voice says "track has been re-calcuated" and gives me a nav instruction.

    4. 100-200m later, the ? question mark comes up and locus beeps...

    repeat all the way along the track...

    Alan

    photo
    1

    What's the difference between helpdesk and forum? How do I use them so I get the best result without annoying anyone?

    photo
    1

    @Alan McDonald

    in your case, it looks more like a new problem in latest version. Please check your settings > navigation > advanced > strict mode. If this option is enabled, just disable it! I'm sure, it will help.

    About forum vs help desk. Offical main site is this help desk, so use it until you wants directly communicate with advanced users or just chat about something related to Locus Map app.


    @Wolfgang

    thanks for additional information. In your case, it will be more complicated. I'm really really sure, that ANT or BT sensors connected to device should not have any effect on navigation instructions. They are really completely independent.

    Hard task. I'm thinking about special version for you as I mentined before, but I'm worried it won't help in this case as well. There happen too much tasks too quickly so it is hard to read problem from a simple text file. Have to ask ... do you use some modified time values when Locus Map should notify during navigation (it ma ybe set in config.cfg file)?

    When I ride a bike, I always use track recording usually with ANT+ speed sensor and almost always a navigation as well and I can't remember any troubles that some notification was missed. I'll try to think about it and let you know if I find something, sorry for now.

    photo
    1

    Hi Menion,

    thank you for thinking about this issue.

    On the bike I use guidance - not navigation. I tried navigation and this works without problems. I like guidance because I get only one navigation notification.

    For me it looks (reasonably) reproducible when I use ANT+ with my three separate sensors: speed, cadence, HRM. I believe to remember I have less/no problems with only one sensor - but I'm not sure now. These test were several weeks ago.

    I didn't modify time values for navigation in the config.cfg file. In the guidance settings I use "Set next trackpoint": 100 m, "Set notification of next...": Sound/TTS, "Out of route...": Sound/Beep and in Advanced settings: "Strict route...": off, "Number of alerts": Medium, "Notification on every trackpoint": off

    Locus switches to the next point of the navigation waypoint list - but it doesn't initiate a notification (in some cases, 10-20%). Locus seems to "forget" to notify. It looks like Locus (or the OS) is too busy with the ANT+ stuff and when it comes back to the guidance operations it doesn't remember it should have to notify...

    If you have an idea how we could find the problem please let me know if I can test something.

    best regards

    Wolfgang

    photo
    1

    "I tried navigation and this works without problems"@Wolfgang. Did you compare with single notify Navigation ?

    photo
    photo
    1

    Just an idea for debugging: a special version of Locus could write to a logfile each switch to a next navigation waypoint and each notification Locus initiated. When I ride with this version we should see in the logfile switching to navigation waypoints without corresponding notifications... Would it help to see it in a logfile?

    photo
    1

    Good day Wolfgang,

    8 months old topic. I was previous days (finally little sunny here) to test this problem in the field and no matter what I do, I'm unable to simulate this problem on own device.

    I was thinking about mentioned special tests version, but logic behind guidance is quite complicated and you are the only one who reports to me such problems with notification. So sorry, I cannot simply help here. S7 is definitely not a problem, because Locus Map is developed mainly on S7 device and no such problems so far.

    For now, I'm sorry, but till I'll be able to simulate this problem on own device, I cannot fix this. Thanks for understanding.

    Leave a Comment
     
    Attach a file