Restart not working after a stop with AA

[Marco Strani]

In the past long weekend I had the chance to test MyRoute-app and AA with Carpuride.
I was able to solve most of the issues I had in the past by setting the correct configuration (so many options available ).
One issue is still open to me: if I stop and disconnect AA (i.e. filling up with gas), when I reconnect the navigation does not work anymore and I need to stop and restart the app on my mobile phone. I a couple of occasions I tried not to start the app on the phone and noticed thaat in that case the problem was not happening. I will test again this scenario, but the problem remains if the app is open on the phone.

[Con Hennekens]

@Marco-Strani, this is default behaviour. If you start a route from the routes menu, it will start (depending on your setting) from closest point or from start (from within the native app). The menu structure of AA and CP devices lacks many settings, partly through development, but also by restrictions from Apple/Google. If I remember correctly, starting a route from the routes menu in AA/CP will use the last know setting used in the native app (but I am not sure, I have not re-tested this).

Another feature of the app, is that when you stop a route, it gives you a resume button. By pressing this button, the route restarts at the target waypoint you where you stopped it. For this, most people using AA/CP devices start, stop and resume their routes through the app instead of through AA/CP.

Some things will likely be added to the AA/CP interface, but also some will not. To be honest, I don't think it has priority at the moment.

[ginogino]

With the latest version of the Android app, if I start a route from Android Auto, the navigation doesn't start. I have to start it from the phone app, and then everything works on Android Auto and Carpuride.

However, on my last two-day trip, on the way back I decided to remove Carpuride and use the app on my smartphone. The Android Auto functionality still has a long way to go before it matches the smartphone app.

[Marco Strani]

@Con-Hennekens said in Restart not working after a stop with AA:

@Marco-Strani, this is default behaviour. If you start a route from the routes menu, it will start (depending on your setting) from closest point or from start (from within the native app).

I probably was not clear in the description of the issue. What I observed is that starting a route from the app, when restaring the ride after a stop and a temporary disconnection, the Carpuride screen freezes and does not follow me anymore until I reboot the app. While, if I start the route from AA everything seems to work correctly and the navigation continues from where I disconnected few minutes earlier

cheers
Marco

[Con Hennekens]

@ginogino, I think it is not realistic to expect an AA/CP experience ever to match the native app. That's not how it works for any AA/CP compatible app.

[ginogino]

@Con-Hennekens said in Restart not working after a stop with AA:

That's not how it works for any AA/CP compatible app.

This is because the apps (all apps) for Android Auto and CarPlay are still lagging behind in development compared to their basic versions.
However, I must admit that on the return trip, I missed the 7-inch display compared to the smaller one on my smartphone. An Android Auto app that mirrors your smartphone would be a good idea, but I don't think one exists.

[M. Schrijver]

On my Goldwing i connect with a wire. When i switch off the bike. The AA connection is disconnected. Especially when disconnected the phone from the cable. The last few times i used MRA ony my bike i had 0.0 problem restarting MRA after a stop.

Screens like Carpuride and Chigee are connecting wireless with your phone. I suspect those devices first go back to a kind of sleep mode just to start up more quickly. In this sleep mode the connection between the screen and the phone is not really there but it isn't disconnected either. Also a sort of sleep mode.
I think this is what confuses MRA after waking up the AA device. It is possible other app has some dificulties also. I don't know because i don't have this type of AA device.

In my Car i have a Chinese AA device connected to factory builtin media device of my Volvo. Sometimes i have some wireless connections issues which are alike the one in this topic. I need to switch of my car and lock the doors to solve this issue. This means the AA device is made powerless or switched off.

[Marco Strani]

This could be an explanation. But, why is it not happening with, for example, Google Maps?

[M. Schrijver]

Just like other things in MRA it still needs finetuning. Overall it works but in the details, there are things not as far developed as other apps.

[Marco Strani]

Clearly myRouteApp is still an evolving application. Just another point to add to the list of improvements.

thanks for jour great job

[Paul Steinberg]

@Con-Hennekens I'll disagree.

Every app that I routinely use with Android Auto (wideband bluetooth connection from my Pixel 10Pro XL to my 2023 Ford F150 or Chigee AIO6) behaves the same on the phone as it does on the vehicle. Google Maps, Podcast Addict, Youtube Music, Amazon Music, Weather&Radar. Messages, Facebook Messenger etc... are a mix of large and small developers. The interfaces may be a little more streamlined for in-vehicle use + safety but the experience is effectively seamless.

@Marco-Strani
Do you have MRA full screen on your Carpuride or 60/40 with podcast/music/messages open on the right side of the screen? I found that when I stop for gas (turn bike and my Chigee AIO6 off) I don't get the prompt from MRA to restart navigation (leaving the phone in my jacket) when I start the bike unless the MRA app is full screen on the Chigee.

[Con Hennekens]

@Paul-Steinberg said in Restart not working after a stop with AA:

I'll disagree.

That's perfectly fine, but to illustrate I have put some pictures of the AA screens of some Navigation apps:

Don't you think they all look rather the same? That's because they are all bound to the same limitations, while the native apps don't.

[Marco Strani]

@Paul-Steinberg I generally use it with navigation app in full screen mode. I will check if in 60/40 mode I have the same behaviour