Vector charts are not displayed / free memory / close apps / auto-routing crashes
If there is not enough memory available on the device, this can lead to various problems in the NV Charts app. For example, the charts display cannot load and only a grey background is visible. Or the vector charts are not displayed and in the upper right corner you can see a message indicating insufficient memory.
Or t
It is possible that there are too many apps open on the device at the same time and therefore not enough memory is available. Please try to close all apps with the task manager (swipe in the screen from the bottom of the screen / use the button next to the home button on Android) and, in case the issue remains, also try restarting the device.
Now reopen only the NV Charts App. This should make more memory accessible to the NV App.
Also make sure that the device meets the hardware requirements and has at least 2 GB, better 3-4GB+ of RAM available.
It may be that there are just less than 2GB free, after the operating system. The vector charts will then not be activated automatically. However, you can activate the vector charts manually. To do this, go to Settings > Chart Settings and activate the topmost switch for vector charts.
If you don't see the button, the app has not detected enough free memory when it starts.
The battery optimization can also play a role here using Android. Using Android, the operating system performs battery optimizations to increase battery life. This can lead to a significant slowdown of the display in the NV Charts app. Deactivate the optimization for the NV Charts App in the operating system settings.
Go to Android Settings > Battery > Battery optimization > Show all apps > deactivate optimization for NV Charts App.
In addition, the following steps may help:
- In the app there is a setting "Reduce resolution" in Settings > Boat and App.
- Disable autorouting to avoid using additional memory.
- Satellite imagery and currents and wind should not consume too much extra resources, except for the fact that they require an internet connection, but they can be a bit of an extra burden even if it is very scarce, especially when switching back and forth quickly.
- Long tracks with dense point intervals can also consume additional resources. Here you could stop the tracks at least at the end of the day and leave the interval at the default values.
he auto-routing crashes when creating (longer) routes.