MyRoute Navigation app updates
- Thread starter Wapping
- Start date
Good innit. 
Synced 135 routes to my phone. Tried it today (in the car) might be my imagination but I think it didn't heat the phone as much as even the last iteration.
Synced 135 routes to my phone. Tried it today (in the car) might be my imagination but I think it didn't heat the phone as much as even the last iteration.
I haven't tried yet, but I did fire up CHIGEE last night on my bike and I can now see the mapping date much clearer. Will give it a go in wires car tonight if I have energy left to get myself out the house.
Some explanation and a changelog here.
forum.myrouteapp.com
New update! (4.3.2)
Hi everyone! An update is available shortly! I actually believe iOS is live already. It contains a few nice things App notifications You will now receive app notifications about the activity feed! Just as with the website you are now notified about wha...
forum.myrouteapp.com
One of the very good things about MyRoute, is that they are very public with the problems they (and others) find and, not least, how they plan on fixing things.
Had a few errands to run around Belfast today in the car and thought I'd test the new version of MRA. I set final outward and return destinations on android auto. My actual route varied from the plotted destination (deliberately) and it quickly recalculated a sensible alternate on every occasion and overall seemed a bit more snappy. Also it did not wrongly display roundabout directions on AA as it could do on the previous version. This was tested offline with my old phone so I don't yet know how effective its traffic avoidance is (I usually use google maps for that kind of thing). So I will need to test that and how its working with GPX files (Fine I expect as I didn't have any issues with the last version and GPX files other than the AA roundabout glitch.)
I haven't had an issue with phones not charging, when plugged in, or of significant overheating since the first couple of iterations of the app. Today's test was carried out on an old Motorola G7 (Android10) using AA. I'll give it a go with my Motorola Neo edge 40 (Android 14) in online mode when I get a chance.
I haven't had an issue with phones not charging, when plugged in, or of significant overheating since the first couple of iterations of the app. Today's test was carried out on an old Motorola G7 (Android10) using AA. I'll give it a go with my Motorola Neo edge 40 (Android 14) in online mode when I get a chance.
I had a run out yesterday, on the bike this time, using the new iteration of the MRA navigation app 4.3.2 in Android Auto mode.
I usually start my routes about 3 miles from home at a filling station and sometimes, in AA using 4.3.1, the directions panel (highlighted with the red ellipse) would buffer until the start of the route (and sometimes after a stop) or indicate the wrong directions. This was more of an irritation than anything else as the verbal instructions and map indicators were always correct. This did not happen using the app (4.3.1) directly on the phone.
For yesterdays test I had a route of around 85 miles plotted. My phone (Motorola Edge Neo 40 running Android14) was online and I had Spotify playing to give the phone as much as possible to do. The phone started with 53% charge and finished at 100%. There were no overheating issues, but it was 6-8 centigrade for the duration of the test.
The app behaved perfectly using AA. The directions panel never buffered even on the way to the route (which I started as I left home) and was fine when I stopped to get fuel and restarted the route. The directions shown including roundabouts were correct. I stopped about half way round the route to have coffee and when I came out it was bucketing down. I cancelled the route I planned and routed straight home via my favourites and as it has been in the car it took a sensible route home, which is an improvement on the previous iteration of the app, which could be odd at times. So, early days, but all in all, a successful test and the app does seem to be more stable and a bit more responsive.
For direct A-B routing google maps would still be my app of choice in AA as it is almost real time as regards road closures and congestion whereas "Here" mapping (Used by Garmin and MRA) has a poor reputation for up to date road information.
I usually start my routes about 3 miles from home at a filling station and sometimes, in AA using 4.3.1, the directions panel (highlighted with the red ellipse) would buffer until the start of the route (and sometimes after a stop) or indicate the wrong directions. This was more of an irritation than anything else as the verbal instructions and map indicators were always correct. This did not happen using the app (4.3.1) directly on the phone.
For yesterdays test I had a route of around 85 miles plotted. My phone (Motorola Edge Neo 40 running Android14) was online and I had Spotify playing to give the phone as much as possible to do. The phone started with 53% charge and finished at 100%. There were no overheating issues, but it was 6-8 centigrade for the duration of the test.
The app behaved perfectly using AA. The directions panel never buffered even on the way to the route (which I started as I left home) and was fine when I stopped to get fuel and restarted the route. The directions shown including roundabouts were correct. I stopped about half way round the route to have coffee and when I came out it was bucketing down. I cancelled the route I planned and routed straight home via my favourites and as it has been in the car it took a sensible route home, which is an improvement on the previous iteration of the app, which could be odd at times. So, early days, but all in all, a successful test and the app does seem to be more stable and a bit more responsive.
For direct A-B routing google maps would still be my app of choice in AA as it is almost real time as regards road closures and congestion whereas "Here" mapping (Used by Garmin and MRA) has a poor reputation for up to date road information.
My wife and I went out, both using iPhone 15 pro max phones and Chigee CarPlay. Both using same version and obviously both following the same route.
After 3.5 hours we stopped for lunch. Her phone had gone from 100% to 20%. Mine was down to 50%. We both charged back up to 100 during lunch.
On the 2.5 hour return, we both only dropped to 80%.
The power consumption issue is weird, especially when you consider that the same person with the same phone has a high draw problem in the morning and no issue in the afternoon.
I agree about closures. We had 2 massive diversions. MRA has no idea, but Google was spot on.
After 3.5 hours we stopped for lunch. Her phone had gone from 100% to 20%. Mine was down to 50%. We both charged back up to 100 during lunch.
On the 2.5 hour return, we both only dropped to 80%.
The power consumption issue is weird, especially when you consider that the same person with the same phone has a high draw problem in the morning and no issue in the afternoon.
I agree about closures. We had 2 massive diversions. MRA has no idea, but Google was spot on.
4.3.3 is now out for testing, too.
I have tried 4.3.2 and 4.3.3 both in the car. Other than getting used to Apple CarPlay, everything was fine with both.
Test of MyRoute App 4.3.3 - 357 on Android. I have used this wired and wirelessly in the car for the past couple of weeks for point to point navigation to test it and its been fine.
Yesterday I did 137miles over the Antrim Hills following a route on my Motorola edge Neo 40 connected to my Africa Twin On Android Auto using a wired connection. The route had 4 Via points and 26 additional waypoints to shape the route. I rode with Spotify playing via my Packtalk Bold and the route and instructions were faultless. I stopped in Cushendun at McBrides for a spot of breakfast(I didn't switch off the route) and it started up fine where it left off and navigated me home. I missed a couple of waypoints on the way back and the app stopped prompting me to to turn after I passed through the next waypoint on the route. The phone started with 26% charge and finished with 100%. So for me (and my set up) all in all a faultless performance. I'm now considering using MRA as my primary navigation method with my Garmin devices as backup rather than the other way round.
However, I still think that using Android Auto or Apple Carplay could add levels of trouble shooting if you are having problems. The head unit, the connection (wired or Wifi) and the phone (particularly AA or CP settings) or competing apps (Bluetooth) could all lead to issues that may not be connected to the app that you are using.
The two that I have encountered over the past year and a half of experimenting with MRA and OSMand are. The data cable not streaming enough data. This was cured by purchasing a high data transfer up to 10 Gbps Amazon Basics cable (about £7) I think. My newest phone glitching when it became charged to 100% and was switching off Android Auto. This was a setting in Android 14 OS which flashed a message on screen that the phone had reached 100% and simultaneously switched off AA. That took some googling to work out and switch off in the Android settings.
Yesterday I did 137miles over the Antrim Hills following a route on my Motorola edge Neo 40 connected to my Africa Twin On Android Auto using a wired connection. The route had 4 Via points and 26 additional waypoints to shape the route. I rode with Spotify playing via my Packtalk Bold and the route and instructions were faultless. I stopped in Cushendun at McBrides for a spot of breakfast(I didn't switch off the route) and it started up fine where it left off and navigated me home. I missed a couple of waypoints on the way back and the app stopped prompting me to to turn after I passed through the next waypoint on the route. The phone started with 26% charge and finished with 100%. So for me (and my set up) all in all a faultless performance. I'm now considering using MRA as my primary navigation method with my Garmin devices as backup rather than the other way round.
However, I still think that using Android Auto or Apple Carplay could add levels of trouble shooting if you are having problems. The head unit, the connection (wired or Wifi) and the phone (particularly AA or CP settings) or competing apps (Bluetooth) could all lead to issues that may not be connected to the app that you are using.
The two that I have encountered over the past year and a half of experimenting with MRA and OSMand are. The data cable not streaming enough data. This was cured by purchasing a high data transfer up to 10 Gbps Amazon Basics cable (about £7) I think. My newest phone glitching when it became charged to 100% and was switching off Android Auto. This was a setting in Android 14 OS which flashed a message on screen that the phone had reached 100% and simultaneously switched off AA. That took some googling to work out and switch off in the Android settings.
Snap. I do though use a sacrificial phone for the job.
Thanks for the update and good advice.
Lots of updates and things to try. See the beta test section on the MyRoute forum for full details.
Another new version of the app availiable today. No chance to test it yet. ........my attachment to garmin devices grows weaker by the day.
forum.myrouteapp.com
New update! (4.3.4) Massive navigation improvements
Good evening everyone! An amazing update is coming your way and I am sure you'll all enjoy this very much! It has been some time since the last release but...
forum.myrouteapp.com
Stupid Q but there does not appear to be an update app version on the App StoreAnother new version of the app availiable today. No chance to test it yet. ........my attachment to garmin devices grows weaker by the day.
New update! (4.3.4) Massive navigation improvements
Good evening everyone! An amazing update is coming your way and I am sure you'll all enjoy this very much! It has been some time since the last release but...
Updated my Ipad last night and Android today. The latest version is 4.3.4-375. Your device may have updsated itself automatically. If you click the account button on the app you can se what version you are on.Stupid Q but there does not appear to be an update app version on the App Store
I carried out a test yesterday on 4.3.4-375. The route was only 85 miles with 3 via points and 24 waypoints in total including the Start and Finish. I plugged my phone into the USB port on my Africa Twin and used Android Auto. Selecting the route on the AA screen using the bar buttons, navigating the route itself, restarting the route after stopping for coffee (On AA) and automatically skipping waypoints on the way home all worked perfectly and the route stopped automatically after passing the finish waypoint. With the phone plugged into the bike for AA the charge went from 63% to 100% with no noticeable phone heating despite the phone being transported in a small padded camera bag. On the Honda you can flip between AA and the bike information screen, I flipped back and forward several times and this didn't trip the app. I haven't tested routing via a track yet. All in all, the app is massively improved from its first iteration 18 months ago and easily as usable as my Garmin Zumo XT. The Honda takes a while to sort itself out with screen booting and connecting to the phone, (obviously this is not an issue with the app.) So I've been connecting the phone and starting the Honda screen while putting on my Helmet and gloves. Very slick and impressive.
Thank you.
I am entrusting my journey to the barren north to MyRoute. Though, it’ll hardly struggle, given the lack of complexity. I mean, even Roman legions managed it, let alone Medieval peasants.
I am entrusting my journey to the barren north to MyRoute. Though, it’ll hardly struggle, given the lack of complexity. I mean, even Roman legions managed it, let alone Medieval peasants.
It all behaved perfectly, running off an iPhone and into Apple’s Car Play.
The only slight oddity was it sometimes flashing up ‘traffic jam ahead’, when the ‘jam’ (such as it was) was behind me.
The only slight oddity was it sometimes flashing up ‘traffic jam ahead’, when the ‘jam’ (such as it was) was behind me.
4.3.5 is now available to test, though there seems to be no parallel announcement on the forum.
HERE is the map MyRoute uses. I have no idea what SDK is. I assume it is Geek Speak for ‘map’ or some sort of specific trademark, unique to HERE’s map?
HERE is the map MyRoute uses. I have no idea what SDK is. I assume it is Geek Speak for ‘map’ or some sort of specific trademark, unique to HERE’s map?
