MRA Community Forum

@Adrian-Avram said in MRA lagging and freezing on AA: From the tests I performed with other apps, my best guess is that they are all using the phone’s internal GPS sensor rather than the external GPS from the Android Auto device. I'm not sure if you are on the right track with that guess. The basic idea of AA and ACP that it takes care of it all. AA and ACP by default uses as much vehicle sensors and info as possible. At least as much as the vehicle manufacturer allows AA and ACP to use. The idea is that AA and ACP can be more "intelligent" than the normal phone apps. Because AA and ACP can have access to the vehicle which your phone doesn't have. But that is the idea. I also noticed that MRA has diffuclties to use the vehicles GPS data in their app. This is a problem onwards from day one. And yes it seems only MRA is affected by this issue. Compared to other navigation apps. which i've tried. Because of the GPS problem with MRA i bought a separate GPS receiver to test things. This was a few years ago. The idea was that a special GPS receiver is more accurrate compare to one in the Phone. At that time i had also a GPS logger running in the background to record my movements and upload them to my Google Drive. Because TomTom Go (Expert nowadays) doesn't have this abillity. After some testing i noticed MRA behaves exactly the same and the GPS logger shows the same shaped tracklogs. So the special GPS receiver did not do anything. This was the moment i learned, the GPS data comes from the vehicle and from the phone. @Con-Hennekens could be right that the size of the development team has something to with this. But it can also be a choice of the development software itself which causes this. Why it think this? Besides this GPS issue. There is still an issue with volume of navigation directions. MRA is the only navigation app, i found, which can not separate the navigation volume from the media volume (if your AA/ACP device supports it). MRA is based on the Here dev kit. The Here navigation app itself does not have any problems with both issues mention above. So i can only assume the problems are not in the Here dev kit. And therefore the software which the development team uses to built MRA is causing this.

I understand, I was just wondering if anyone knew. Congratulations on your work, I'll enjoy my trip and your app.

I like driving with a 8" screen and it seems to be the perfect size (for me). Depending on your liking you can think of a Android Auto device or a dedicated android tablet. Then you you think about a DMD, Hugherock, Samsung active tab 5 or other rugged (IP rated) device.

@Nick-Dawson said in Long Distance Testing using Android Auto: I have found that when using Android Auto, what is presented on the screen is a limited version of the application that is presented on the phone. It is not the application that is limited, but merely the GUI. That counts for literally ALL apps being used through Carplay or Android Auto. You can start routes just fine from the AA screen though (tap screen so menu appears and press the looking glass icon). Zoom also works, but you need to enable dynamic view mode. It may be needed to adapt the zoom settings (this can only be done on the phone indeed) to better suit your AA screen. Some of the GUI elements will be added in version 5.1 (iirc). You are correct that AA is great for A2B routes. Personally I prefer the full app on a native phone for scenic routes indeed.

@Lary Open a support ticket so it can be investigated. https://www.myrouteapp.com/support

@Th-Lee Thank you Carl for this detailed explanation. I did try the option 3 via Tread and it worked ok on a very simple route - I would guess that if you were building something complicated then you might run into issues with Tread trying to second guess what you wanted. The tip about using the SD card for file storage is a good one. It's nice to have all your files on hand and available to be reloaded anytime when you're on tour and I wouldn't want them being messed with by the Zumo. I used the XT3 for the first time on Tuesday for a trip of about 200 miles and it worked well. The screen is super clear, bright, easy to read. I liked it. Compared with my old Zumo 660 this is a great leap forward and it is much faster and easier to create routes on the device than it ever was on the 660. That does open up some new possibilities for route planning, but I will still prefer to build on MRA first and transfer to the Garmin later. Thanks again for your help.

The TS exported the route to GPX 1.1. Maybe that is the issue for you?

I also would be very happy, if such option could be considered.

@Corjan-Meijerink Congratulations to you both. May you have a ️ blessed life together with healthy kids and exciting trips ️ .