Phone connected to Cardo Freecom 4X helmet intercom. The intercom is connected via Bluetooth to the phone and no other app is used such as radio or music.
When MapFactor issues an instruction the first 2-3 words are not coming through. For instance "for turn right at London Road" I will usually here "at London Road".
I was wondering if any other bikers experience this type of issue and mainly whether there is a solution such as a couple of faint blips before the voice message.
Yes, that helped. I switched from the standard channel to the Bluetooth headset channel.
The message 'You have reached your destination' comes 50 meters too early. I could also see that on the GPS track, so the GPS was accurate enough.
I can't work with this behavior. It is reproducible with a navigation simulation. I recall that this issue was not always this extreme. I will try using an older version.
@tomas Re. Missed beginning of announcements. You were 100% right. Changed from BT to the Default (Automatic) and worked. You are good! Seems the opposite to @Matthias worked for me.
"we have not changed any of this for years" - The same problem exists in PC Navigator for Windows. Why does the software generally work so inaccurately? How many years would I have to go back to get the old accuracy (maybe I'm mistaken)?
But 50 meters is a bit too much, especially because you generally drive more slowly before reaching an intermediate destination. It seems that a radius of 50 meters is also used for route optimization. At least, that would explain the optimization errors I noticed on a specific tour with many closely spaced destinations.
The route optimization skipped an entire block, moved on to the next one, then went back to the skipped block, and finally returned to the next one again. Something isn't working correctly there.
When the smartphone is locked, the GPS navigation is stopped. I have installed an older version that works correctly. BTW, I have DuraSpeed and battery manager turned off.
I have completely disabled DuraSpeed. I can't turn anything on or off. The Battery Manager is also completely disabled. With the older version, it works. Only the communication with the GPS will be disabled. Route simulation works even when the phone is locked. This is a MapFactor problem, not caused by my smartphone.
let me try to explain this with each release we have to declare which version of Android Navigator is for and it cannot be Android version older than one year Navigator 7.3.62 was declared for Android 13, Navigator 7.3.64 was declared for Android 14
as we made no changes, appart from the above mentioned declaration, it is obvious that Android treats apps for v14 differently when screen is off Navigator 7.3.64 keeps running if battery is set to unrestricted - unfortunately Android keeps changing this setting on it's own accord and there is not much we can do about it
role of Duraspeed is to keep selected apps in unrestricted battery mode, that is why it has been introduced - I have no problem with Duraspeed, not sure why you disabled it, but there may be other ways to keep battery settings on unrestricted setiings
" not sure why you disabled it," - I had disabled it when setting up Android 11 because it sends apps that are not explicitly set to "On" into battery management, even if this is disabled. So, when you had disabled the battery manager, DuraSpeed rendered that useless. But I want to try how it goes when I turn on DuraSpeed and configure the important apps accordingly.
I will conduct further tests in the coming weeks, also with Android 14, and will report my results here afterwards. However, because of this bug, I was late for an important appointment on Saturday. So it's not just a joke from me, but a real issue.
I was reading the Android Play Store comments, and there are other people who have the same problem: the GPS is turned off when the phone is locked. The response from MapFactor was, "GPS is controlled by Android." :( This is the wrong approach. When will this development gap end? What is going on with the developers?
Just updated to v.7.3.65 (from v.7.3.64) from Play Store. App crashes at splash screen. Gone back to 7.3.64 & all OK. Google Pixel 9 running Android 14.
I have version 7.3.48 installed because I haven't saved any other version. In this version, I am having issues with the map import; when I import all maps, the program crashes. However, I can import a single map.
Edit: Today it imported all maps, but it took a few minutes. The trick was to keep the smartphone unlocked and do nothing to disturb the process.