Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Navigation Turn Alert - Can someone comment pre 19.XX FW methodology (OP Updated)

S.M.R.

Hello All.

I would like some feedback from someone on an earlier than 19.XX version please.

Through the beta cycle of 19.XX there was a bug with the Turn notification (during a course) as there would be an audio notification incorrectly.(link below for information) This was corrected in 19.18. (NOT CORRECTED , SEE UPDATE BELOW)

forums.garmin.com/.../navigation-turn-direction-audio

The issue I now experience is that although the Turn ahead notification appears on the face of the map, there is no vibration when the direction changes is appearing. I am very sure this was what used to happen before - otherwise one would have to look at the watch all the time in map mode. (VIBRATION WORKS SEE UPDATE BELOW)

The "of Course"/ "on Course" works as one would expect i.e. appears on watch face and vibrates.

Thanks for your inputs. 

UPDATE: I was pretty sure that i had turned the "Turn Alert" back on in navigation when installing 19:18 in order to test the 19.xx Beta Bug, but it appears I didnt,

SO we still have the reported Beta 19.xx Bug... There is an Audio Comment on TbT that is somehow linked to the TbT alert toggle in error.

Effectively there needs to be a Navigation subset under Audio Prompts.

  • 0

    There was a vibration for tbt alerts. (can't check now, my watch is being replaced by garmin. again.)

    However...

    It's hard to lay a finger on it, but I have a strong suspicion vibration alerts don't always work.

    Quite often I miss alerts for incoming messages, and I do sometimes miss 1k autolap  alerts, specially on longer runs, after 15k or so.

    But I have this for quite some firmwareversions.

  • 0 in reply to S.M.R.

    I'm in 19.18 firmware version and still there is an audio notification in turns from my phone. I still not tried to disable turn prompts

  • 0 in reply to 3332987

    Thats interesting , let me try it again tomorrow  ...Soemtimes the settings revert back for no reason from GC...

  • 0 in reply to 3332987

    Hi, Thanks tested again and you are correct the 19.XX Beta error still exists,

    I updated the OP...clearly I'd missed switching the TbT Alert toggle back on when testing it! (silly me, although I was pretty sure I had!)

    Effectively there needs to be a Navigation subset under Audio Prompts.

  • 0 in reply to S.M.R.

    You can report it in the next beta, so  can reject it as too old to fix.

  • 0 in reply to Elbo

    Sierra has been very helpful in assisting with the issue since I identified and reported the Beta Bug and having a Ticket opened. I have also updated Sierra with my findings today. 

  • 0 in reply to S.M.R.

    I have different experiences. The autozoom bug, that's in the firmware for ages, just gets rejected as not related with the 19 firmware. The manual end of sleeptime not working is just rejected as not related with the 19 firmare. And so there are more. Quite a lot more.

    I get it that those bugs are not planned for finalizing a firmware version, but at least but them on the proper list to be fixed. A garmin support employee should be able to do that. All sierra does is tell me is to file it as a suggestion.

    Have to say, I try to report the same bugs to the dutch garmin support. And it isn't any better. Bug reports never make it to the developers. I strongly suspect garmin sees bug fixing as costs and support employees are urged to reject as much as they can to save costs.

    And yes, I'm super annoyed by how garmin deals with bug reports. And yes, I'm aware I experience more bugs or are more bothered by them than other users. Maybe it has something to do with my work. I'm a software developer myself and do everything I can to produce high quality software.

  • 0 in reply to Elbo

    Agreed. A good listing of issues would be very nice and a better way of reporting and managing reported bugs would help, so we know what is what. Sometimes something looks like a bug because we misunderstand the intention of the change so better description of changes would also be useful.

    I think we also all add a lot of value to the processes (or could do really) if we had more clarity and understanding.

    I think this post is on point also.

    forums.garmin.com/.../fix-backlog