First experience with MRA as a navigation tool
-
@Con-Hennekens said in First experience with MRA as a navigation tool:
It does that in the menu where you can select your voice. There is a play button that produces a test sentence.
Ah, good point Con. But that's on iOS only, at the moment.
The 'pseudo' test sentence on Android is a bit short: 'Voice instructions are enabled', but you can keep repeating it by tapping the medium and then high volume buttons repeatedly, and that gives you a chance to increase the volume.A 'Play audio sample' button on Android similar to iOS would be appreciated.
Having experimented with that (on A54) it's still not as loud as Google Maps audio, and both are quieter than music (to my ears).
I will give it another try next time I'm out.
@richtea999 said in First experience with MRA as a navigation tool:
Ah, good point Con. But that's on iOS only, at the moment.
Not completely true
The current Beta has a choice of voice within the app, also for Android. Each voice has a play button. This will be in the announced public version as well.Having experimented with that (on A54) it's still not as loud as Google Maps audio, and both are quieter than music (to my ears).
I agree. I use a JustSpeak helmet-set (Caberg) and I max out the volume on BT and on the device itself too. For scenic riding that's completely fine, but for riding highways not so much. The relatively low volume on the voice has been a problem from the get go.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@richtea999 said in First experience with MRA as a navigation tool:
Ah, good point Con. But that's on iOS only, at the moment.
Not completely true
The current Beta has a choice of voice within the app, also for Android. Each voice has a play button. This will be in the announced public version as well.Having experimented with that (on A54) it's still not as loud as Google Maps audio, and both are quieter than music (to my ears).
I agree. I use a JustSpeak helmet-set (Caberg) and I max out the volume on BT and on the device itself too. For scenic riding that's completely fine, but for riding highways not so much. The relatively low volume on the voice has been a problem from the get go.
@Con-Hennekens said in First experience with MRA as a navigation tool:
@richtea999 said in First experience with MRA as a navigation tool:
Ah, good point Con. But that's on iOS only, at the moment.
Not completely true
The current Beta has a choice of voice within the app, also for Android. Each voice has a play button. This will be in the announced public version as well.
The Google TTS Norwegian voices speaking English are very pleasant!
Welsh - almost broken, but not MRA's fault.
-
Again a discussion about skipping waypoints. This shows the developers have some work to do.
Manually skipping points should not be necessary. Only real waypoints should be skipped manually.
When start a route. Only one question.Would you ride to the start of the route or closest point?
Make your choice and from there on it should not be neccesary to touch your phone again. The software should take care of your choices while riding
(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
Today I made a test in my car with MRA app. Mainly to verify the advice given about changing volume while getting spoken road instructions.
- Volume emitted by Samsung A54 smartphone is sufficient in my car.
- Volume cannot be changed during emitting instructions.
- Road instructions work well in my car.
So far so good.
But my problem with spoken instructions in my helmet is not solved. This seems to be a completely different technical issue.
-
Again a discussion about skipping waypoints. This shows the developers have some work to do.
Manually skipping points should not be necessary. Only real waypoints should be skipped manually.
When start a route. Only one question.Would you ride to the start of the route or closest point?
Make your choice and from there on it should not be neccesary to touch your phone again. The software should take care of your choices while riding
@M-Schrijver said in First experience with MRA as a navigation tool:
Manually skipping points should not be necessary. Only real waypoints should be skipped manually.
That's a rather big contradiction, isn't it?
Would you ride to the start of the route or closest point?
Choosing the waypoint from where you want to drive the route yourself is much more flexible. The closest point is often not where I want to start the route.
from there on it should not be neccesary to touch your phone again.
In almost all cases that's exactly how it happens. My Garmins needed much more user input during a ride than the MRA app...
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@M-Schrijver said in First experience with MRA as a navigation tool:
Manually skipping points should not be necessary. Only real waypoints should be skipped manually.
That's a rather big contradiction, isn't it?
Would you ride to the start of the route or closest point?
Choosing the waypoint from where you want to drive the route yourself is much more flexible. The closest point is often not where I want to start the route.
from there on it should not be neccesary to touch your phone again.
In almost all cases that's exactly how it happens. My Garmins needed much more user input during a ride than the MRA app...
@Con-Hennekens said in First experience with MRA as a navigation tool:
@M-Schrijver said in First experience with MRA as a navigation tool:
Manually skipping points should not be necessary. Only real waypoints should be skipped manually.
That's a rather big contradiction, isn't it?
No, In my opnion shaping points should always be skipped automaticly when neccesary (i.e road works). Manual involvement should never be required for shaping points.
For those Hand symbols (waypoints i presume) a manual action is not strange. Because waypoints are chosen for a reason.Please be aware that user input on Android Auto is very limited compared to the phone interface
Would you ride to the start of the route or closest point?
Choosing the waypoint from where you want to drive the route yourself is much more flexible. The closest point is often not where I want to start the route.
With TomTom Go i make use of one of the two options mentioned before or i drive to my prefered starting point and there i start the route. When starting the route when i'm on the route or in close proximity TomTom Go doesn't ask anything it just start navigating. Very nice.
from there on it should not be neccesary to touch your phone again.
In almost all cases that's exactly how it happens. My Garmins needed much more user input during a ride than the MRA app...
With TomTom Go, i start the route and normally i'm done touching my phone for the rest of the day. TomTom nearly fixes al my problems i create while riding. The rare moments i need to touch my phone is mostly when i 'm on a route deviation and i think TomTom does something wrong but in 95% of these cases TomTom did a good job. So basicly i can trust TomTom. This is a relaxed idea.
My neighbor still use a Garmin and just like your Garmin it needs more user input. This is something i don't miss (i also did drive with Garmins in the past).
I suspect a part of the required user input has something to do with the stability of MRA. Which will be improved over time.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@Con-Hennekens said in First experience with MRA as a navigation tool:
@M-Schrijver said in First experience with MRA as a navigation tool:
Manually skipping points should not be necessary. Only real waypoints should be skipped manually.
That's a rather big contradiction, isn't it?
No, In my opnion shaping points should always be skipped automaticly when neccesary (i.e road works). Manual involvement should never be required for shaping points.
For those Hand symbols (waypoints i presume) a manual action is not strange. Because waypoints are chosen for a reason.Please be aware that user input on Android Auto is very limited compared to the phone interface
Would you ride to the start of the route or closest point?
Choosing the waypoint from where you want to drive the route yourself is much more flexible. The closest point is often not where I want to start the route.
With TomTom Go i make use of one of the two options mentioned before or i drive to my prefered starting point and there i start the route. When starting the route when i'm on the route or in close proximity TomTom Go doesn't ask anything it just start navigating. Very nice.
from there on it should not be neccesary to touch your phone again.
In almost all cases that's exactly how it happens. My Garmins needed much more user input during a ride than the MRA app...
With TomTom Go, i start the route and normally i'm done touching my phone for the rest of the day. TomTom nearly fixes al my problems i create while riding. The rare moments i need to touch my phone is mostly when i 'm on a route deviation and i think TomTom does something wrong but in 95% of these cases TomTom did a good job. So basicly i can trust TomTom. This is a relaxed idea.
My neighbor still use a Garmin and just like your Garmin it needs more user input. This is something i don't miss (i also did drive with Garmins in the past).
I suspect a part of the required user input has something to do with the stability of MRA. Which will be improved over time.@M-Schrijver, may I ask what your motivation was to leave TomTom?
-
I am always curious about new product and the MyRouteplanner is a good product. So MRA Next could also be this good.
I bought a lifetime membership for the navigation app at the moment is was a real sale.
While TomTom Go is a really good product for me (hard to beaten). It is just route with a start and endpoint. No visible shaping or waypoints in between. When i am on vacation is miss those visible points sometimes. I can't remember all the interessesting things along a route for a whole vacation even not for a whole day.
This is where MRA Next scores some very good points. To hear the text written at a way/shaping point through my headset is a very nice featureLet be fair.
- MRA Next is still a young product. So stablity is still not what some mature app (like TomTom GO) offers.
- Android Auto is also a very good feature. This feature narrows the choice of apps a lot. There are only a few good apps which can handle routes and Android Auto (Apple Carplay) properly. MRA Next is one of those few apps
- While the smartphone app looks good and seems to work pretty well. Android Auto and Apple Carplay still needs a lot of development. Partially due to the limitations set by Google and Apple, partially because the foundation (the apps itself) needs to be solid to work well in AA and ACP and partially my Android Auto headunit has no touchscreen (Honda Goldwing)
Those limitations set by Google and Apple are a big reason why i'm so on top the auto skipping function.
Once you exeperience a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job. You are gonna appreciate the comfort of not having the need fiddeling with your navigation through the day.
B.T.W
TomTom Go is still my main navigation app.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
I am always curious about new product and the MyRouteplanner is a good product. So MRA Next could also be this good.
I bought a lifetime membership for the navigation app at the moment is was a real sale.
While TomTom Go is a really good product for me (hard to beaten). It is just route with a start and endpoint. No visible shaping or waypoints in between. When i am on vacation is miss those visible points sometimes. I can't remember all the interessesting things along a route for a whole vacation even not for a whole day.
This is where MRA Next scores some very good points. To hear the text written at a way/shaping point through my headset is a very nice featureLet be fair.
- MRA Next is still a young product. So stablity is still not what some mature app (like TomTom GO) offers.
- Android Auto is also a very good feature. This feature narrows the choice of apps a lot. There are only a few good apps which can handle routes and Android Auto (Apple Carplay) properly. MRA Next is one of those few apps
- While the smartphone app looks good and seems to work pretty well. Android Auto and Apple Carplay still needs a lot of development. Partially due to the limitations set by Google and Apple, partially because the foundation (the apps itself) needs to be solid to work well in AA and ACP and partially my Android Auto headunit has no touchscreen (Honda Goldwing)
Those limitations set by Google and Apple are a big reason why i'm so on top the auto skipping function.
Once you exeperience a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job. You are gonna appreciate the comfort of not having the need fiddeling with your navigation through the day.
B.T.W
TomTom Go is still my main navigation app.@M-Schrijver said in First experience with MRA as a navigation tool:
a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job. You are gonna appreciate the comfort of not having the need fiddeling with your navigation through the day.
Yep, this should be the target!
Although I love that barbutton idea, we should not need to play with the navigation tool while riding
-
I am always curious about new product and the MyRouteplanner is a good product. So MRA Next could also be this good.
I bought a lifetime membership for the navigation app at the moment is was a real sale.
While TomTom Go is a really good product for me (hard to beaten). It is just route with a start and endpoint. No visible shaping or waypoints in between. When i am on vacation is miss those visible points sometimes. I can't remember all the interessesting things along a route for a whole vacation even not for a whole day.
This is where MRA Next scores some very good points. To hear the text written at a way/shaping point through my headset is a very nice featureLet be fair.
- MRA Next is still a young product. So stablity is still not what some mature app (like TomTom GO) offers.
- Android Auto is also a very good feature. This feature narrows the choice of apps a lot. There are only a few good apps which can handle routes and Android Auto (Apple Carplay) properly. MRA Next is one of those few apps
- While the smartphone app looks good and seems to work pretty well. Android Auto and Apple Carplay still needs a lot of development. Partially due to the limitations set by Google and Apple, partially because the foundation (the apps itself) needs to be solid to work well in AA and ACP and partially my Android Auto headunit has no touchscreen (Honda Goldwing)
Those limitations set by Google and Apple are a big reason why i'm so on top the auto skipping function.
Once you exeperience a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job. You are gonna appreciate the comfort of not having the need fiddeling with your navigation through the day.
B.T.W
TomTom Go is still my main navigation app.@M-Schrijver said in First experience with MRA as a navigation tool:
Once you experience a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job.
Does a 7 day trip count? I did that in september, and basically did what you say: only start the route in the morning. Honesty makes me admit that it was in offline-mode. Concerning online-mode I must say that this young product still has to mature indeed
But hey, the 3 Garmins I owned were also offline. The more features it has, the higher the expectations get.I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@M-Schrijver said in First experience with MRA as a navigation tool:
Once you experience a 14-day motorcycle trip where you have only start the route in the morning, after this let the software do it's job.
Does a 7 day trip count? I did that in september, and basically did what you say: only start the route in the morning. Honesty makes me admit that it was in offline-mode. Concerning online-mode I must say that this young product still has to mature indeed
But hey, the 3 Garmins I owned were also offline. The more features it has, the higher the expectations get.@Con-Hennekens said in First experience with MRA as a navigation tool:
Does a 7 day trip count?
we could think about that
Where did you go?
It is not difficult, it is easy, it's a hobby
-
@Con-Hennekens said in First experience with MRA as a navigation tool:
Does a 7 day trip count?
we could think about that
Where did you go?
@Drabslab, haha, thanks. We stayed at Hotel Sonnenblick in Bebra, and toured through Hessen, Thüringer Wald and Harz.
https://maps.app.goo.gl/689SyTszHG6pMtQd7
The hotel is commendable, but their website is not
