# App: Pause / Continue navigation **URL:** \ **Category:** Implemented features\ **Tags:** implemented\ **Created:** [May 11, 2020, 9:20am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184 "2020-05-11T09:20:30Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [May 11, 2020, 9:20am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/1 "2020-05-11T09:20:31Z")
Do you find useful in your travels a function for pause / resume navigation? With pause navigation halts at last state and need to resume it anywhere / anytime to continue. (idea comes from that [discussion](https://forum.kurviger.com/t/app-improve-rerouting-at-start/2875/25)) ---
**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\ **Post date:** [May 11, 2020, 9:30am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/2 "2020-05-11T09:30:24Z")
This could help with strict navigation. Resume would introduce the same issues as with flexible navigation? ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [May 11, 2020, 9:42am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/3 "2020-05-11T09:42:03Z")
> [@boldtrn](#): > > This could help with strict navigation. A big benefit would be for strict navigation. > [@boldtrn](#): > > Resume would introduce the same issues as with flexible navigation? What issues do you mean with flexible navigation? It’s not about resume route. But freeze navigation calculations, so navigation pauses at last state. When be ready to resume driving again, either on route or anywhere else, can resume navigation. ---
**Author:** ![zaphod\_42](https://forum.kurviger.com/user_avatar/forum.kurviger.com/zaphod_42/32/499_2.png) [@zaphod\_42](https://forum.kurviger.com/u/zaphod_42)\ **Post date:** [May 11, 2020, 11:00am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/4 "2020-05-11T11:00:40Z")
I didn’t really miss it, but I’d appreciate it. Not at the gas station, but on longer lasting stops for sightseeing or coffeebreaks. ---
**Author:** ![Wolf](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/w/e19adc/32.png) [@Wolf](https://forum.kurviger.com/u/Wolf)\ **Post date:** [May 11, 2020, 11:25am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/5 "2020-05-11T11:25:39Z")
> [@devemux86](#): > > Do you find useful in your travels a function for pause / resume navigation? Nein, finde ich nicht nützlich. Das wäre eine unnötige Funktionserweiterung. ---
**Author:** ![linux-user](https://forum.kurviger.com/user_avatar/forum.kurviger.com/linux-user/32/56_2.png) [@linux-user](https://forum.kurviger.com/u/linux-user)\ **Post date:** [May 11, 2020, 3:28pm UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/6 "2020-05-11T15:28:33Z")
Sorry I don’t get you. In what situation the “long press” should happen? 1. Do you mean, while navigation **is running** you can pause it via “long press” instead of stop it via “short press”? And then resume it later? or 2. do you you mean, at **start of navigation** instead of the normal “shot press” you can “long press”? Navigation would then **wait** until you hit the route, and then **continue from there on**. So that, “strict navigation” would behave like a **one time flexible** navigation? ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [May 11, 2020, 3:33pm UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/7 "2020-05-11T15:33:26Z")
Pause of navigation can only happen when it has already started. Resume of navigation can only happen when it has already paused. Similarly to how music / video players work - so more like your (1). So when navigation runs, can long press its button and pause it. Navigation freezes and sometime later can resume it via button. I’ll think for UI & button, more important now is if we need the pause / resume function. ---
**Author:** ![linux-user](https://forum.kurviger.com/user_avatar/forum.kurviger.com/linux-user/32/56_2.png) [@linux-user](https://forum.kurviger.com/u/linux-user)\ **Post date:** [May 11, 2020, 3:51pm UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/8 "2020-05-11T15:51:09Z")
> [@devemux86](#): > > more important now is if we need the pause / resume function. I don’t think that a “pause / resume function” is needed for _flexible navigation_. With _flexible navigation_ you can simply start navigation **anywhere on the route** , and you are done. This maybe different with **strict navigation**. I think, currently we have too few people who have actually tested _strict navigation_. ---
**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\ **Post date:** [May 11, 2020, 8:05pm UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/9 "2020-05-11T20:05:59Z")
> [@devemux86](#): > > What issues do you mean with flexible navigation? That parts of the route are skipped unintentionally. When I resume the navigation, the same could also happen? To me this sounds like we are making strict navigation flexible again 🙂. ---
**Author:** ![Tom](https://forum.kurviger.com/user_avatar/forum.kurviger.com/tom/32/168_2.png) [@Tom](https://forum.kurviger.com/u/Tom)\ **Post date:** [May 12, 2020, 5:33am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/10 "2020-05-12T05:33:14Z")
> [@devemux86](#): > > Do you find useful in your travels a function for pause / resume navigation? Absolutely. I had already asked for such a function at least 2 years ago. But as Robin says I would not like to make the strict navigation flexible again with it. Pausing navigation makes especially sense to me if we have a tour summary at the end of the tour with overall length and duration, pure journey or running time, duration of the break time, average speed including breaks and without breaks, maximum speed (all in km/h, not m/s; or other regional values depending on the settings), ---
**Author:** ![Wolf](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/w/e19adc/32.png) [@Wolf](https://forum.kurviger.com/u/Wolf)\ **Post date:** [May 12, 2020, 6:27am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/11 "2020-05-12T06:27:02Z")
> [@Tom](#): > > makes especially sense to me if we have a tour summary at the end of the tour with overall length and duration, pure journey or running time, duration of the break time, average speed including breaks and without breaks, maximum speed Das kannst du alles aus dem mitlaufenden GPS-Track auslesen. ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [May 12, 2020, 10:50am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/12 "2020-05-12T10:50:10Z")
> [@Tom](#): > > Absolutely. I had already asked for such a function at least 2 years ago. But as Robin says I would not like to make the strict navigation flexible again with it. Pause / resume in flexible navigation seems unneeded, as can exit / enter route anywhere. It could be useful in strict navigation to cover stops, as strict route following mandates that: _“Navigate along the route without shortcuts, i.e. follow the route strictly from one waypoint to another. When go off route, the rerouting tries to resume to the last omitted waypoint.”_ > [@Tom](#): > > Pausing navigation makes especially sense to me if we have a tour summary at the end of the tour That is irrelevant to this feature’s purpose. It was proposed / discussed elsewhere in forum: > [@Navigation statistics](https://forum.kurviger.com/t/motorcycle-statistics/1644): > > It will be great to have some logs/statistics at least for motorcycle riders track speed, routes, even lean angle, for example ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [May 12, 2020, 11:23am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/13 "2020-05-12T11:23:11Z")
> [@boldtrn](#): > > That parts of the route are skipped unintentionally. When I resume the navigation, the same could also happen? No, like mentioned above it is not related to resume route. - When (re)start navigation, strict mode expects to begin near start and pass all waypoints in order (that is the fundamental non-negotiable principle of strict route following) - So currently can start anywhere with strict navigation, only if manually skip all previous waypoints Pause / resume navigation is different, while strict mode remains active: - When resume strict navigation near previous pause, can continue strict route following - When resume on distant location omitting waypoints, it complains & considers off route Perhaps all these are complicated and not much useful to average user? ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [May 14, 2020, 9:47am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/14 "2020-05-14T09:47:10Z")
A post was split to a new topic: [Auto start navigation](https://forum.kurviger.com/t/auto-start-navigation/3207) ---
**Author:** ![linux-user](https://forum.kurviger.com/user_avatar/forum.kurviger.com/linux-user/32/56_2.png) [@linux-user](https://forum.kurviger.com/u/linux-user)\ **Post date:** [May 18, 2020, 12:33pm UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/15 "2020-05-18T12:33:11Z")
Continuing the discussion from [Routing issue with option "strict navigation"](https://forum.kurviger.com/t/routing-issue-with-option-strict-navigation/3250/2): 💡 Just an idea for a possible user interface for _pause / resume_: If implemented, the navigation would then have 3 states. - stopped - running - paused (new) 1. Let the user be aware of the 3 states. Maybe by changing the color of the navigation button. e.g. 2. What if _pause / resume_ would be the default behavior? 🤔 The disadvantage would be, that this would _change_ the behavior for _all_ users. But would it hurt? I don’t think, that it would make a practical difference for flexible navigation. _Flexible navigation_ would continue seamless, regardless if it has been paused before, or is starting fresh. 🤔 But it would be a win for _strict navigation_, to be able to continue after a break. ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [May 18, 2020, 12:49pm UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/16 "2020-05-18T12:49:59Z")
Thanks for the ideas. 1. Or could change the symbol e.g. ⏸ Anyway I still haven’t thought much the workflow or the appearance, as implementation and maintenance are also important for me for any new feature. ---
**Author:** ![Beemer](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/b/439d5e/32.png) [@Beemer](https://forum.kurviger.com/u/Beemer)\ **Post date:** [May 19, 2020, 7:21am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/17 "2020-05-19T07:21:35Z")
> [@linux-user](#): > > Just an idea for a possible user interface for _pause / resume_ : > If implemented, the navigation would then have 3 states. > > - stopped > - running > - paused (new) Introducing a state machine is a very good idea ! This will finally make it possible to distinguish between the first start (after the route was loaded and/or changed) from a pause. Question is what transitions will lead to the paused state. You could try: - speed below a certain value for a certain amount of time, or - input via the start/stop button (long or short as suggested in a previous post in this thread) Conversely, the transition from paused to running: - speed above a certain limit ([like suggested here](https://forum.kurviger.com/t/auto-start-navigation/3207)), or - start/stop button pressed I think that this would allow for a great improvement of the user experience. ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [May 19, 2020, 5:47pm UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/18 "2020-05-19T17:47:01Z")
Thanks for the detailed thoughts! > [@linux-user](#): > > What if _pause / resume_ would be the default behavior? 🤔 > > - _short press_ would then switch between stopped - running - paused - running … > - after beeing started, navigation would only stop automatically if end point is reached. > - If user wants to _stop navigation_ before, would need to _long press_ . Looks like a nice intuitive workflow, that also protects navigation from accidental touches. Also the more frequent actions belong in tap & the more rare actions belong in long press. (similar to how the location button works) > [@linux-user](#): > > The disadvantage would be, that this would _change_ the behavior for _all_ users. > But would it hurt? > I don’t think, that it would make a practical difference for flexible navigation. > _Flexible navigation_ would continue seamless, regardless if it has been paused before, or is starting fresh. 🤔 > But it would be a win for _strict navigation_ , to be able to continue after a break. Indeed that would also change slightly current workflow. 🤔 _Anyway nothing in app is set in stone!_ How pause / continue navigation works in other navigators? ---
**Author:** ![Tom](https://forum.kurviger.com/user_avatar/forum.kurviger.com/tom/32/168_2.png) [@Tom](https://forum.kurviger.com/u/Tom)\ **Post date:** [May 20, 2020, 8:26am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/19 "2020-05-20T08:26:04Z")
> [@devemux86](#): > > How pause / continue navigation works in other navigators? In Calimoto there is a Pause/Resume Button, pausing shows the overview mode without stopping the tour In TomTom Go there is an arrow for switching between the Overview/Planning Mode without stopping the tour (tour can only be stopped via menu actual route → stop route) ![InkedSmartSelect_20200518-124224_GO_LI](https://forum.kurviger.com/uploads/default/original/2X/b/bd2414e91a1cda6e9bdee6c0fff8f307ec66020a.jpeg) In Navigon Cruiser you tap and swipe to the right, then you have an own GUI site with big easy to use (also with gloves) squares with own functionality for example “insert new wp”, “skip road blocking” “skip next waypoint”, “pause/resume navigation”, “pause/resume recording”, “show complete route”, “stop route”, “planning mode”, “WOW button for automatic storing of beautiful locations or roadways”, “voice output”, “Glympse”, “save location”, “map view”, … these direct funktions are configurable by the user (max. 6 per site). ![Screenshot_20200420-141729_Cruiser 1](https://forum.kurviger.com/uploads/default/original/2X/f/f1f649c344bed4b4a18d5e6e300f5f458c92c4db.jpeg) Navigon Cruisers method is the best fail safe mode to my point of view because it prevents operating errors. Pausing automatically based on Zero speed for more than 15 secs for example sounds also to be a nice feature. … The Wow button is placed in the middle of the bottom ![Screenshot_20200520-103112_Cruiser](https://forum.kurviger.com/uploads/default/original/2X/8/8c39bae5f9820fbcf50b097a8547047f90643128.jpeg) Wenn pressing while driving, you have the option to automatically save - nice location (this saves a favorite for the actual GPS position that you can rename later) - driving pleasure (this saves the actual road section that can also be renamed later) ![Screenshot_20200520-102951_Cruiser](https://forum.kurviger.com/uploads/default/original/2X/0/0082f554b1db8a848de1043a7684caf8bd07f87e.jpeg) ---
**Author:** ![Tom](https://forum.kurviger.com/user_avatar/forum.kurviger.com/tom/32/168_2.png) [@Tom](https://forum.kurviger.com/u/Tom)\ **Post date:** [May 20, 2020, 8:55am UTC](https://forum.kurviger.com/t/app-pause-continue-navigation/3184/20 "2020-05-20T08:55:47Z")
> [@linux-user](#): > > - _short press_ would then switch between stopped - running - paused - running … > - after beeing started, navigation would only stop automatically if end point is reached. > - If user wants to _stop navigation_ before, would need to _long press_ . This is exactly what I have also posted here and this is inuitive for my point of view : > [@Strict navigation improvement - fail safe design](https://forum.kurviger.com/t/strict-navigation-improvement-fail-safe-design/3255): > > While navigating in “strict navigation mode” I discovered the effect that when pressing the navigation button, the actual route is cancelled, pressing again the navigation button drops “the knowledge” of already visited waypoints and starts the navigation again from the beginning. Pressing the navigation button can also happen unwillingly. I would therefore propose (maybe this is only necessary in strict navigation mode) to stop an already started navigation only by long-press the navigation bu… Additionally with temporary fail safe handling via local files (if technically possible and not too complicated to develop). [Next page](https://forum.kurviger.com/t/app-pause-continue-navigation/3184.md?page=2)