Android auto uses default profile (pedestrian possible)

[guerda]

Description

Today I wanted to navigate via Osmand on Android Auto. I was surprised to have an estimated travel time of 6 hours instead of 20 minutes. It seems that the navigation used the pedestrian profile, even in the Android Auto mode. We hen I changed the profile manually on the phone, the route changed to the more realistic 20 minutes.

How to reproduce?

1. Set your default profile to pedestrian in the settings
2. Connect phone to Android Auto
3. Let Osmand calculate a new route
4. Be surprised about estimated travel time 😁

I would expect that Android Auto would automatically use the car profile, no matter which profile is active.

Your Environment

OsmAnd Version: OsmAnd+ 4.3.3, veröffentlicht: 2022-12-13 Android/iOS version: Android 13 Device model: Pixel 7

Maps used (online or offline):
If you have an issue related to offline maps, tell us the exact name of the map file where the issue occurs and its edition date.

Deutschland Nordrhein-Westfalen, 01.12.2022

[hakuchi]

~This is not only a Android Auto issue. Also reproducable during phone navigation. OsmAnd is calculating the route always in pedestrian mode, not working if I change profile after calculation. For me is no recalculation after changing the profile~

There was mapped a footway with motor_vehicle=permissive so it used wrong routing

[Zirochkabila]

OsmAnd~ 4.4.0#14059mqta, released: 2022-12-29

• [ ] Make the profile automatically change to " Driving" when connecting to the AA

If the "Pedestrian" profile is selected on the device (before connecting to AA), the route is calculated as for a pedestrian.

[sonora]

Instead of "Make the profile automatically change to " Driving" when connecting to the AA" we could also just change it to "Browse map", which is more apt to map viewing because many people would have that in mode "North is up", while they have "Driving" in mode "Movement direction", which may be more useful only if a navigation is ongoing?

[markwmuller]

FWIW, I think google maps does this very well. When I'm looking at the map on my phone, it's north up. That's useful as it isn't clear to me how I'm holding my phone, or moving, when I'm looking at it in my hand. However, when the map is attached to the car (because it's displayed on the car screen thru Android Auto), it aligns with the movement direction automatically (which I find helpful, as "the street I'm looking for is to my left" is more intuitive to me in the car than "it is to the north").

[guerda]

What is really annoying with this bug is that you cannot change the profile within Androiden Auto. You have to open the app all the smartphone and change it there.

There's also no indicator in the Android Auto view which profile is active. You only notice subtle differences in the map display and the strange route duration.

I would appreciate if Osmand would switch to the car profile as soon as Android Auto is used.

[dmpr0]

ToDo

We need to add new option that allows to set default profile for Android Auto, selected profile will be used when device will be connected to Android Auto.

• [ ] Add new option Android Auto profile in OsmAnd Settings
• • [ ] By default set it to Default profile
• [ ] Switch App profile to selected when device connected to Android Auto.
• • [ ] if Android Auto profile profile is different then profile was used on device, show toast App profile changed to [Profile name], string application_profile_changed

    OsmAnd Settings	Android Auto profile

[guerda]

While I appreciate the flexibility with a default Android Auto profile, I am wondering if this adds too much complexity. Is there a need for Android Auto being in "pedestrian", "bicycle" or "public transport" mode? I was wondering if it would be easier (and intuitive) to switch automatcially to the "Driving" mode. Especially if users cannot switch it on the Android Auto screen.

[sonora]

I also have doubts if we really need yet another setting here! Why can we not offer on the Android Auto interface being able to change to the desired profile? Like users would expect, and like @guerda says above?

And yes, may even default to use the Driving profile the first time the app connects to Android Auto, but then remember if the user then changed it manually (user may e.g. have a Truck profile), so next time Android Auto is connected it automatically defaults to the profile the user had used there last time?

So here's the user story I suggest we implement:

• [ ] User connects the app to Android Auto for the first time. App selects the Driving profile.
• [ ] User can change to any app profile via an Android Auto button, similar to how it can be done on the phone. (User may e.g. prefer Browse map, or may have a Truck profile.)
• [ ] Next time app connects to Android Auto it will remember the last profile user had selected for Android Auto, and will use that.

More intuitive, and no additional exposed setting needed on the phone UI.

[dmpr0]

@sonora Android Auto has limited set of buttons and layouts, we can't add similar set of buttons like in Android app.

[sonora]

@dmpr0 Ah, ok, thanks. But I guess we could still implement the above user story, only that step 2 (profile change) would have to be performed on the device?

[vshcherb]

There should a behavior change:

• we should change to selected driving profile when AA connected and change back to default profile (similar to navigation finished) [or to previously selected in the phone ???] when AA disconnected.
• Default option could be - keep current profile if it's driving like or switch to the first available driving-like.

[guerda]

Are there any updates on this?

[vshcherb]

well no good solution yet, thinking for 4.5

[vshcherb]

To do

• If current profile is "Driving" (derived from Driving - Truck, Car, Motorcycle...), then AA should stay the same
• If current profile is not "Driving", then it should change first in the list Driving.

[shurasmiling]

https://osmand.net/docs/user/navigation/auto-car

[EugeneZmeuk]

10.04.2024 Review

• [x] section