Due to site maintenance, Forum interaction has been disabled until August 13. For support, please search existing forum posts or check the support page.
Map is slightly behind
I had this problem starting as soon as the new version of the app came out. Same problem with iPhone 6S and 8. I found that changing to 2D view instead of 3D nearly eliminates this issue.
It would not surprise me if the root cause is in the phone (iOS) and not in the app. Apple is known for increasing resource demands such as memory and processor power release after release. That is why you need a new iphone after couple of years :-D.
After a simple google, I found tons of articles on iphone slowing down and what to do about it.
If you find Scenic responding slow, and as I understand it is not a common issue, than you might want to have a close look at your iphone first and do some of the following:
Follow These Quick Tips To Get GPS Working Again on your iPhone or iPad
- Move to a new location, preferably open space
- Toggle Location Services Off and On
- Open your phone Settings > Privacy > Location Services and toggle the switch OFF
- Perform a hard reset on your iPhone
- Return to Settings > Privacy > Location Services and toggle the switch back ON
- Toggle Airplane Mode On and Off
- Set Date & Time to “Set Automatically” via Settings > General > Date & Time
- Turn off LTE
- Reset network settings
- Set Do Not Disturb While Driving to Manually
- Drain your battery completely
- Update or Restore your device using iTunes
- Burp your iPhone, just like a baby
Have a look at sites like this: https://www.macworld.co.uk/how-to/iphone/speed-iphone-3463276/
Maybe we can narrow down the cause of this by elimination other iphone related issues first?
My two cents. I love this app by the way, I bought it today after trial.... cant wait until we can ride for the full again.
Stay safe, stay healthy
Ron
Hallo Guido,
Mega cooles App und ich benutze es mit dem Wunderlinq. Bin eigentlich sehr zufrieden und habe schon sehr grosse Touren damit gemacht.
Ich hatte letzte woche und heute aber genau auch diese Probleme, dass die Postion verzögert ist und ich nicht abgebogen bin. Ich hoffe du findest das Problem und kannst es beheben da für mich kein anderes App in Frage kommt. Danke.
Schöne Grüsse aus der Schweiz
Dani
Hi Guido,
benutze Senic seit letztem Jahr und bin sehr zufrieden damit.
Gestern habe ich bei meiner Ausfahrt auch dieses Problem gehabt, dass die Positionsanzeige ca. 100-200m bzw. 2-3 Sekunden hinten dran war.
Habe jetzt mal die Tipps von Ron bzw. Macworld.co.uk durchgeführt.
Morgen fahre ich wieder ne Runde und schau mal, ob´s besser geworden ist.
Die Linke zum Gruße
Prinz A
Today I did a ride and used Senic for navigation and as second try for tracking only. At both occasions the App was round about 50m behind.
Also recorded the app about 18 km more then in real was driven.
greetings
Hi Guys... still working on the 'lag' problem with the beta testers. Sorry about all that. It seems to be a problem in the 3rd party routing framework so might have to wait for a fix from them, or find a workaround for it.
Quote from Prinz A on May 18, 2020, 12:31Today I did a ride and used Senic for navigation and as second try for tracking only. At both occasions the App was round about 50m behind.
Also recorded the app about 18 km more then in real was driven.
greetings
Would you mind sharing the link to the ride with me? Would like to have a detailed look. You can create a link by using the 'share' button above the map preview. If you prefer you can send the link to me through the 'email me' button at bottom of the support page.
Hello Guido,
Would you be so kind and give me your eMail address?
I can‘t use the button eMail me, because I use a third party email app.
greetings
Quote from Prinz A on May 18, 2020, 12:31Today I did a ride and used Senic for navigation and as second try for tracking only. At both occasions the App was round about 50m behind.
Also recorded the app about 18 km more then in real was driven.
greetings
Regarding the 18km more... something went wrong with the track recording. It's jumping from Altheim to Bissingen (see screenshot). That explains the 18km. I'll look into why this happened. Did you do a stop at any of these two locations by any chance?
- You need to login to have access to uploads.