Danke hat geklappt. Toller Support hier Gruß Frank

het lijkt me dat het niet kunnen berekenen er 2 oorzaken kunnen zijn 1 GPS heeft geen goede ontvangst 2. positie heeft een te grote afstand to een bekende weg die Here kent. als je online bent in huis dan help voor positie bepaling ook de wifi en meestal heb je een bekende weg voor de deur. ik kan het mis hebben maar dat hoor ik het graag.

@Arjan-de-Vries This is a known bug. Corjan has discovered that this bug is caused by Here map data. The bug is expected to be fixed in the next update from ‘Here’.

@Lex.Kloet.RX said in Map "spinning" when standing still: @Bouke-Ent I often had the experience, but in the middle of Barcelona and Madrid with a 7,5 meter camper. That is really no fun at all when driving it works but standing still for a moment then..... it seems Here thinks it normal.

@rob-van-willigen Je reageert op een onderwerp dat al twee jaar oud is en bovendien in de verkeerde categorie staat. Ik raad je aan een nieuw onderwerp te starten in de rubriek 'Website'. You are replying to a topic that is 2 years old and also in the wrong category. I suggest that you start a new topic in the website section.

@Markus-Hellenthal-Dr. Interesting. Our apps does exactly the same as it does on every Android device and I don’t see these issues on our test Caretta Regarding GNSS, they do manage that on hardware level and even mentioned changes in the latest OS update: https://carpe-iter.com/caretta-initial-os-update/

My DMD T665 also shows this behauvior.

To come back at this shortly: It is clear that the closure in your case is still there after updating. We have another example at hand where the closure indeed disappeared after a map upgrade. That seems to support my theory that closures sometimes are in the map data instead of the traffic info. I think we must reconsider this. I think what we see is a caching method in action. Map updates do not seem to influence closures afterall. App updates however do. So at an app update apparently the cache is deleted.

Helemaal top. Ben zelf een autodidact maar kon dit niet vinden. Bedankt.

Yeah, that's why I hope that the new app version will arrive soon, since it should also have a lot of CP/AA improvements. Last news I have is that it should be available at the end of this month.

@Corjan-Meijerink Ik heb gisteren alle combinaties geprobeerd, na de nieuwe installatie staan ze weer op de standaard waarden, vermoed ik.

Thanks, Ill try that!

i agree with peter. a solution would be give option to recalculate off. i understand that in a2b recalculation is always on. even if you stick on route on a selected route/track ( track if it is curved) in a few situations the app thinks it is off route/track

@reinier.beenengmail.com, nee ik zou niets anders adviseren, hooguit een app die gericht is op logistieke navigatie misschien. Het skip algoritme is ingericht op scenic navigatie.

@Jörgen Yes, I stated it in the title and body

I think you have to distinguish between two scenarios when faced with sudden road closures. On minor roads, you can try to bypass the closure ‘by sight’. It’s not the most elegant solution, but it’s doable. On the motorway, this is more difficult, as the map showing the route scrolls off the small display. If the app now wants to divert me at the next exit, I don’t know whether it’s trying to take me back or whether that’s a way back onto the route (somewhere past the closure). That’s why I think it’s so important to be able to mark a closure in some way (e.g. by pressing a button), so that the app definitely doesn’t try to take that exit again.

@Nick-Carthew Nee, niet gelukt was aan het rijden

@Corjan-Meijerink Thanks for your answer. I can sleep better now and are awaiting version 5.1.

I did my first ride of the year today and used verion 5.0.4 (451). Till the lunch the audio seems fine, but i'm not sure. I did not pay much attention to it. After the lunch i noticed a missing part at the beginning of the instructions. My audio delay was already set to 1 sec. Therefore i started playing with the delay and hoped to hear some difference. I did hear differences but not what i expected. I did not matter if I set the delay to 0 or 2 seconds. The first small part of the directions was always missing. The only thing what happens was the delay when the instructions were spoken. With the of 2 sec delay, the instructions came 2 seconds later. B.t.w I have a Sena SRL 3 headset.