I keep on getting this popup error message.
What does it mean?
What can I do to prevent it?
This object is in archive!
OVER_QUERY_LIMIT & map losing bearing
Answered
Okay I'm still having a problem with intermittently getting this message OVER_QUERY_LIMIT which appears if I shift focus to another app and return to Locus, or after the calculating message appears on screen. So do I have to keep on erasing my temporary files in settings > miscellaneous > clear temporary data and restart Locus or is there a fix for this? As I have set Brouter as the default router period.
When Brouter is set as the default router (route computing) and I'm online (3/4G) will Locus try and use an online source such as mapquest instead or will it stick with Brouter all the time?
When I used the rotate map to point map in the direction I was travelling on occasions the map would behave as if it was having a seizure by going left and right manically. Any idea why or what?
Thanks
The same question
Good day Fergus,
I've read that first major troubles are already solved, that's fine. Let's tune it little bit more.
Error message you see > I have no idea where it comes from and why it happen. It is definitely not directly from Locus. Anyway only solution I see now, is creating error log, right after this error happen, with hope, there will be something useful. How to create a log is wrote here.
If BRouter is set as default, then it will be used everytime, no fallback to another routing engine.
Rotation of map > isn't this problem happen only in moments, you leave track for longer distance then defined in settings > navigation > advanced > maximum allowed deviation? Because in this moment, Locus Map should not be anymore stick to navigation track and also rotation of map starts to be defined by gps/compass (as you have defined) and not track itself.
Good day Fergus,
I've read that first major troubles are already solved, that's fine. Let's tune it little bit more.
Error message you see > I have no idea where it comes from and why it happen. It is definitely not directly from Locus. Anyway only solution I see now, is creating error log, right after this error happen, with hope, there will be something useful. How to create a log is wrote here.
If BRouter is set as default, then it will be used everytime, no fallback to another routing engine.
Rotation of map > isn't this problem happen only in moments, you leave track for longer distance then defined in settings > navigation > advanced > maximum allowed deviation? Because in this moment, Locus Map should not be anymore stick to navigation track and also rotation of map starts to be defined by gps/compass (as you have defined) and not track itself.
Hi Menion,Well the weird thing was it was doing this when I was actually on the route. I can only assume there maybe was a glitch with the gps and Loucs thought I was off route. Maybe I will just turn off the max allowed deviation for now.
Yes I will have a look at doing this when I get an opportunity to get out on a ride next. It would be great to get to the bottom of this.
One more thing on my rides I noticed even though I was on the planned route the "Calculating" message would appear periodically on screen for a few seconds. Is this normal?
Hi Menion,Well the weird thing was it was doing this when I was actually on the route. I can only assume there maybe was a glitch with the gps and Loucs thought I was off route. Maybe I will just turn off the max allowed deviation for now.
Yes I will have a look at doing this when I get an opportunity to get out on a ride next. It would be great to get to the bottom of this.
One more thing on my rides I noticed even though I was on the planned route the "Calculating" message would appear periodically on screen for a few seconds. Is this normal?
Really ("Calculating" message)? Hmm, I found this problem as well few weeks ago with previous version. Issue was, that by accident, Locus reported GPS location and network (wi-fi, cell-id), both at once.
Anyway it should be already fixed in new 3.19.0 version. Maybe this was also cause of previous mentioned problems. Give please new version a try during your rides and you will see. Thanks!
Really ("Calculating" message)? Hmm, I found this problem as well few weeks ago with previous version. Issue was, that by accident, Locus reported GPS location and network (wi-fi, cell-id), both at once.
Anyway it should be already fixed in new 3.19.0 version. Maybe this was also cause of previous mentioned problems. Give please new version a try during your rides and you will see. Thanks!
Will do. Will be a while before I'm out on the bike next but will report back any problems when I do manage to get out :)
Will do. Will be a while before I'm out on the bike next but will report back any problems when I do manage to get out :)
Perfect Fergus, thank you very much and enjoy your bike rides!
Perfect Fergus, thank you very much and enjoy your bike rides!
Good day Fergus,
Uwe, I've merged your problem to this topic, as both of you see same error message "over_query_limit". Unfortunately this message is not produced by Locus, but by any service that has this problem. Any idea, why which service you use that may cause it?
Good day Fergus,
Uwe, I've merged your problem to this topic, as both of you see same error message "over_query_limit". Unfortunately this message is not produced by Locus, but by any service that has this problem. Any idea, why which service you use that may cause it?
Replies have been locked on this page!