OsmAnd (OSM Automated Navigation Directions)

It would be very nice if Osmand could be used inside "Android Auto" application instead of Google Maps. Or, at least, that "ok google" could be used during Osmand navigation, to call someone via bluetooth or anything else.

Just updated a Nexus 6P to Android O and reinstalled all apps including OsmAnd+ in the current version v2.7.5. The app shows up and GUI elements just work as inteded. However, when interacting with the map itself the app becomes unbearable slow and unresponsive. Especially zooming is extremly slow. Eventually the map reacts and the app doesn't freeze/crash. But a normal usage is not possible under this condition.

Since some time the new search is active, called by magnifier glass (new) and with main menu (old). In this search I am missing search for Address, Location and Favourite. See screenshot with old search 2.4.0#18556 and new search 2.5.0#19192 Regards Peter

I noticed a bad bug in current release: during navigation Osmand very frequently shut down when running in background. I have installed Osmand+ 3.0.4 on Huawei P10 with Android 8.0.

The issue is that during navigation after some time Osmand close instead than keep running in background and consequently the navigation stops. I do not think it is related with strict battery optimization policy of Huawei phones, because it never happen before.

I started to notice this only with last version.

Turn screen off no longer works - Since the update, I can set the screen to turn on automatically but no matter what seconds I set the screen doesn't tun off. #7315

I recently upgraded both osmand (to 3.3.4) and android (to 9.0 pie) and can no longer find the "turn on screen before turn" feature in settings > navigation.

Should it still be there? Or was it moved?

On long distances the route calculation is slow. This wouldn't be a problem but if a road is closed it seems to take the same amount of time to recalculate the route. In my case this was about 10 minutes. Maybe you miss the next possible route because of this.

Maybe both issues can be fixed if you assume that you usually use motorways on long distances so keeping the route after the motorway link and just recalculate the route to the link. On first calculation it might be possible to start navigation after finding a route to the next motorway link. the rest of the route could be calculated in background.

I am having issues with getting OSMAnd to use my SDCard for data storage. It worked on my android 4.4, but after my upgrade to my Z5 that is running 5.1.1 its not anymore. It defaults to: /storage/emulated/0/Android/data/net.osmand.plus/ which is the internal storage of the phone which i DON'T want to use since I already have a lot of mapdata on my SDCard from the S5.

However I get a an error that OSMAnd can't write maps files to the folder when I try to change it to: /storage/(name of SDCard)/Android/data/net.osmand.plus/ which was the folder that OSMAnd used to use.

I have been googling the issue and when Android 5 was released THAT was the intended behaviour, google however has since then readded SDcard security into the system so that individual apps can ask for permissions to have access to certain folders. It works by popping up a file manager and asking the user to select the root folder that you want to grant access to on the SD card, and any folder further down that particular branch is what OSMAnd would get access to.

OSMAnd however doesn't do this and it should, as the latter is the new intended behaviour and how its supposed to be so that people like me can use their actual SD card and not phone internal memory.

More on the issue can be found here: http://www.techtimes.com/articles/19510/20141106/android-5-0-lollipop-comes-with-better-sd-card-support-hoorah-google.htm & http://www.ibtimes.com/android-50-lollipop-update-includes-fix-microsd-card-restrictions-1719958

If available and valid, the turn:lanes tag will be used to determine the symbols to show for each lane. Support for all values except U-turn and lane merges have been added; however, the symbols are not aligned yet and may look bad.

Unfortunately, there isn't enough usage of this to get a good testing ground, but this way looks good.

Description

When Android Auto launches in the car, OsmAnd asks for location permission (see photo below). Tapping on "Grant Access" does not do anything. Simply unlocking the phone (without granting any permissions) makes the message go away.

(EDIT: Behaviour is actually slightly different, which I only noticed later. If I tap "Grant access", nothing happens - but unlocking the phone AFTERWARDS immediately switches to the OsmAnd app on the phone and the permission is granted. If I do not first tap "Grant access" on the car screen, unlocking my phone does not achieve anything. So I need to do both: tap the car screen AND unlock the phone.)

This is a bit inconvenient, since the phone is oftentimes in a pocket or bag and needs to be found and unlocked to be able to use OsmAnd.

How to reproduce?

1. start car
2. Android Auto launches automatically
3. OsmAnd asks for permission

Your Environment

OsmAnd Version: 4.3.2 Android/iOS version: Android 11 / Oxygen OS 11.0.9.1GM57BA Device model: OnePlus 7

Maps used (online or offline):
offline

Hi. Since the latest monthly map update for England dated 1 July 2016 I'm seeing "OsmAnd+ has stopped working" error message every few minutes, often less. OsmAnd+ did not crash when using the June maps prior to the July update.

The crash occurs either during navigation or driving in "browse map" mode with no destination set. Others have reported crashes by simply manipulating the map. The destination is irrelevant as the crash occurs regardless of the destination, however should you wish to test, the first route I observed crashes with the July map was from departure Lat 52.60085 Lon -1.68302 to destination Lat 52.47364 Lon -2.10563

I have run simultaneous side by side tests to the same destination using a Note 4 on 6.0.1 Marshmallow, a Note 4 on 5.1.1 Lollipop & a Galaxy Tab 3 on 4.4.2 Kitkat & OsmAnd crashed on all 3 devices. All 3 devices were running OsmAnd+ 2.3.5

During the test process I also set a destination but remained at home & did not travel. In this test OsmAnd+ remained stable on all devices & did not crash during the 30 minute test period. The crash does however occur during a simulation using OsmAnd Development & Debugging plugin.

I have tried:

• Re-downloading maps
• Clearing app cache & data
• Uninstall/reinstall app
• Factory reset device & start from scratch

Please see this thread for further crash reports & additional information: https://groups.google.com/forum/#!topic/osmand/QCsaE48ITRU

A user has also reported the same issue with Republic of Ireland map. It seems potentially there is an issue with the maps whilst they are being compiled.

Thank you

Description

I'm searching for some places by their coordinates: I have a list where they are written in format DDD MM SS.sss.

When I open the Coordinate search panel, I see the default format set is DD.DDDDD, so I change it to DD MM SS.S and type in the values for the first point, I confirm and the map is properly centered on the selected location.

When I get back to search for the second location, however, I see the coordinate format has switched back to DDD.DDDDD: I would expect to find it set to the format I chose previously, as this would speed up my search.

How to reproduce?

1. Start OsmAnd and wait for current position to be fixed.
2. Open the menu Search -> Address -> Coordinates search
3. Note that Coordinates format field is set to DD.DDDDD
4. Set Coordinate format field to DD MM SS.S.
5. Type in the coordinates and confirm: the map is centered on the chosen location
6. Get back to menu Search -> Address -> Coordinates search
7. Note that Coordinates format field has been reset DD.DDDDD : DD MM SS.S (the same as the last search) would be expected as this would make it easier for the user to search for another spot. Setting should be retained at least until the app is closed.

Your Environment

OsmAnd Version: OsmAnd+ v. 4.3.5 Android/iOS version: Android 11 Device model: Samsung Galaxy A50 (SM-A505FN/DS)

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.

Description

After upgrading from 4.2.7 to 4.3.3 the tiles at zoom level 19 no longer load.

Also instead of loading lower res maps, some of the tiles load and some don't. The ones that don't show a X in a circle. Sometimes lower zoom levels also do not load, like when zooming out.

How to reproduce?

Zoom in, tiles saved in the tiles directory that used to load fine, only load down to zoom level 17 now.

Your Environment

OsmAnd Version: 4.3.3 Android/iOS version: 10.3.12 and 7.1.2 Device model: OnePlus and LG both

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. Only tested with offline maps.

This shows aerial tiles, top is showing level 17, bottom didn't load any tile. Zoom level is high enough level 19 should load. I don't have level 18, Saves memory, and the snap lets me know what zoom level I'm at. I will have to test further.

Here is zoom out.

Next is after zoom in, you can see tiles at level 17 did load, but every time I press Back... this is happening on the LG H932 only:

Description

After upgrading from 4.2.7 to 4.3.3 the Center is now at the bottom. Researching the new features I find in Configure profile, Browse map, General settings, Display position is already set to center.

After much toggling of settings, changing rendering engine from 1 to 2, and Setting driving to bottom, while leaving browsing and walking set to center, I finally got it to switch back to center one time by switching profiles. But on next load, it was back to the bottom, and the earlier trick no longer works. I also tried setting Center to all profiles, but radius ruler is still at the bottom.

Switching profiles with different Display position does not change that setting on the map/screen.

How to reproduce?

I'll list the settings, and any differences between the 3 profiles I have turned on: Browse map: Dark, Fixed north up, 2.5D off, Center, Same as device Driving profile: 2.5D on, Bottom Walking profile: Center Then tap the upper left profile icon to switch profiles. Check if the center changes also.

Your Environment

OsmAnd Version: 4.3.3 Android/iOS version: 7.1.2 Device model: LG-H932

Maps used (online or offline): 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.

Description

When using app in car via AA screen, after a short while (1-2 minutes since launching) location gets very inaccurate. It mostly stops at the place of last known location. When I unlock the phone (still connected to AA), I see there is a message about Google Play Services ANR (crash). When I switch location source to Android API, this does not happen, but location is less accurate and have huge lag - impossible to use in a city with complex navigation route.

How to reproduce?

Use Google Play Services as Location Source.

Your Environment

OsmAnd Version: 4.3.5 (beta apk from Play Store) Android/iOS version: Android 12 with MIUI 13.0.4.0 (SJIEUXM) Device model: Xiaomi Mi 10 Lite 5G (M2002J9G)

Maps used (online or offline):
Using offline map but with 4G data connection.

Unfortunately, I cannot test with any other phone model to check if the problem is with my phone only. However, any other navi app don't crash Play Services. Also, during navigation outside of AA, everything is working without issues. I also cannot get logcat at that moment, because I am already driving..

Description

Good morning and a happy new year.

Because of some issues (like #16081) I wanted to start the new year with a fresh install of my Osmand +Version. Before that, I did, about one hour ago, a complete online-backup (and deleting all previous online-files before, so all backup data has to be current) to the Osmand Cloud.

First step after the online-backup: uninstalling and reinstalling +V4.3.5 Next expected step: getting all my data back from this new online backup, but that remained a "pious hope". Even the backup was created recently, the cloud now tells me, that the last sync was at Dec 27th. and with the additional information, that it "failed to fetch the file list from the server". Great.

How to reproduce?

I dont know.

Your Environment

OsmAnd Version: +4.3.5 Android/iOS version: 13 Device model: S20+ 5G

I downloaded the latest OMC 3.0 but it doesn't support {bbox} {q}? Just only zxy. I can't define new source. The error msg. is "Please specify all placeholders {$x} {$y} {$z} in URL" Could you update OMC?