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

In previous versions of OsmAnd streets with access restrictions (e.g. "private" or "destination") were highlighted in different colors on the map (e.g. red or blue). This is no longer the case in the current version. Possibly related to the switch to opengl?

How to reproduce?

Configure map --> Details --> Show access restrictions and toll - activate No change on display of access restricted roads.

Your Environment

OsmAnd Version: OsmAnd+ 4.3.5 Android/iOS version: Android 8, MIUI Device model: Redmi Note 5

Maps used (online or offline):
Experienced on offline maps of Germany, Switzerland and Malaysia.

Description

There is a grey line across the map, where there shouldn't be on purpose.

How to reproduce?

Activate Contour lines addon in Hungary and check it yourself.

Your Environment

OsmAnd Version: 4.3.5 Android/iOS version: Android 12 Device model: 1+ 8

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. Both

Description

How to reproduce?

Your Environment

OsmAnd Version: 4.3.5 Android/iOS version: 12 Device model: 1+ 8

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.

09.12.2022 2:35:07
Apk Version : 4.2.7 4207
Exception occured in thread Thread[pool-7-thread-8,5,main] : 
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object java.lang.ref.WeakReference.get()' on a null object reference
 at net.osmand.map.MapTileDownloader.fireLoadCallback(MapTileDownloader.java:279)
 at net.osmand.map.MapTileDownloader$DownloadMapWorker.run(MapTileDownloader.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
 at java.lang.Thread.run(Thread.java:1012)```

If possible include the federal waterways in Germany in the nautical charts. The maps with signage are provided by the WSA on its homepage: https://www.gdws.wsv.bund.de/DE/service/karten/00_FGeoWSV/FGeoWSV.html?nn=1716478

🚀 feature request

Description

I absolutely love the new Elevation Widget, which is a great aid for riding bicycles with OsmAnd. In the present version, I find the following 3 problems:

1. When the navigation is started, the current position starts from 0% of the x-axis (then gradually moving to 20%). This makes it impossible to read the y-axis labels (covered by the position marker) and to see the first part of the graph (covered by the y-axis labels).
2. The values shown on the y-axis are quite random and not so useful
3. The values of uphill (climbing) and downhill (descending) integrate the altitude data from the gpx route shown in the graph, but are often meaningless because the gpx altitude is rough.

Describe the solution you'd like

Referring to the problems above, I suggest the following improvements:

1. Fix the current position at 20% of the x-axis, even when the navigation is started, so that all labels/current-position-graph are always visible. Data before km0 can be white (so that the first 20% of the widget graph would be empty when starting navigation)

2. Show on the y-axis labels for the highest and lowest points of the graph. These are usually the most important points (summit/lowest-point) that one wants to quantify.

3. Solution for this is more tricky. Ideally, you could use a function for detecting peaks (p0, p1, p2, etc) and valleys (v0, v1, v2, etc.) in the graph, then calculate

• "current uphill" as vertical distance between current elevation and next peak
• "current downhill" as vertical distance between current elevation and next valley In the most ideal case, you could detect if p0_x < v0_x (currently climbing or descending?) and show
• "current climb" as horizontal distance to the next peak (i.e., 2km remaining)
• "current descent" as horizontal distance to the next valley Whether to show information for climbing or for descending could be changed according to the current position.

4. Peaks and valleys could be indicated on the graph with a dot, and maybe with a label indicating the peak/valley elevation

5. When navigating with a gpx, the graph x-axis could display the distance of the gpx (i.e., 98.5km in the example above) instead of starting from 0km.