hi
not sure if the drive app only works when it knows a physical garmin device. at least once it knows a device, there is no need for the drive app to be connected to the device to communicate with locus (to get position from locus).
i don't know how i can monitor what locus exactly sends to the drive app.
when sharing a text message instead of sharing with other map apps, i can see that when the shared text is "route principale, orvin," this position works when shared with other map apps garmin drive, but when it is just "orvin," it does not work.
this for sure looks like a garmin issue, as it does not seem to be very tolerant to the label it gets with the coords.
unfortunately i don't expect a quick solution from garmin :-(
btw: where does locus take the label from, it adds to the coords?
and is there a way for me to monitor what exactly locus sends to the map app, to further debug and give a more accurate error description to garmin support?
not sure if the drive app only works when it knows a physical garmin device. at least once it knows a device, there is no need for the drive app to be connected to the device to communicate with locus (to get position from locus).
i don't know how i can monitor what locus exactly sends to the drive app.
when sharing a text message instead of sharing with other map apps, i can see that when the shared text is "route principale, orvin," this position works when shared with other map apps garmin drive, but when it is just "orvin," it does not work.
this for sure looks like a garmin issue, as it does not seem to be very tolerant to the label it gets with the coords.
unfortunately i don't expect a quick solution from garmin :-(
btw: where does locus take the label from, it adds to the coords?
and is there a way for me to monitor what exactly locus sends to the map app, to further debug and give a more accurate error description to garmin support?