OpenGL rendering isn't enabled by default installation (F-Droid)

[vichvich4444]

Description

Map rendering on fresh install of Osmand is noticeably laggy
It's fixable by re-enabling OpenGL rendering in settings

Steps to reproduce

Get a fresh Osmand install (From f-droid, for example. I couldn't manage to remove configs from Google Play version, but that's another issue)

Actual result

Moving the map stutters (as long as you are using an average phone, I guess)

Expected result

OpenGL rendering is actually enabled

Your Environment (required)

OsmAnd Version: 5.2.13
Android version: 14
Device model: Galaxy A13 5G

[Zirochkabila]

@vichvich4444 This may be specific to F-Droid builds. Please try installing OsmAnd from the official website and try again https://osmand.net/docs/versions/

[yuriiurshuliak]

OsmAnd Nightly 5.3.0#7137m, released: 2026-02-10

On a fresh install, OsmAnd defaults to Rendering engine v1, even though users expect OpenGL to be enabled by default.

I can reproduced the issue.

Reproduction steps

1. Install a fresh OsmAnd nightly build: https://osmand.net/docs/versions/nightly_versions/#nightly-builds
2. Ensure it’s a clean install (no old app data/configs).
3. Open OsmAnd → Menu → Settings → OsmAnd settings → Map rendering engine.
4. Check which rendering version is selected.

Actual result

After a fresh install, Rendering engine v1 is enabled by default.

video_2026-02-10_13-03-31.mp4

Expected result

The app should enable the intended/default OpenGL out of the box (to avoid stuttering on first launch).

[vichvich4444]

@Zirochkabila It is an issue also on Google Play version. I tried installing nightly version but it isn't "compatible with my phone"

[Zirochkabila]

In my case, V2 (Android 12) is always displayed.

@yuriiurshuliak please double-check and specify the Android version of your device and its specifications - perhaps V1 applies to relatively less powerful devices.

Details

5.2.13 - V2	OsmAnd Nightly 5.3.0#7146m, дата випуску: 2026-02-11 - V2
2026-02-11.16.57.58.mp4	2026-02-11.17.04.43.mp4

[vichvich4444]

@Zirochkabila V2 will be displayed in settings as enabled. Try checking if it's enabled by moving the map around. It should stutter, unless your phone's software rendering is too fast to notice any difference

[yuriiurshuliak]

Re-checked on a clean install and could not reproduce the issue.

How to verify on a truly clean state

1. Install a fresh OsmAnd Nightly or OsmAnd release from Google Play.

2. Ensure no old data/config remains:

   • Long-press app icon → App info → Storage usage → Clear data → Delete

3. Open:

   • OsmAnd → Menu → Settings → OsmAnd settings → Map rendering engine

4. Check which rendering engine version is selected.

Result
After Clear data, Rendering engine v2 is enabled by default.

[vichvich4444]

@yuriiurshuliak As it happens, I did try deleting user files from Google Play version with App info -> Storage usage -> Clear data, but it just didn't work for some reason. Try enabling dark style in Osmand, for example, delete data, reinstall again and see if it's still in dark mode.

[yuriiurshuliak]

OsmAnd 5.2.13, released: 2025-12-01

On some devices, after Clear data → uninstall → reinstall, OsmAnd can start with Rendering engine v1 (and default theme), even if the user previously had v2 (OpenGL) selected — but if you Clear data again after reinstall, the app then starts with v2 as expected.

From what you described, it looks like the key point is when the data wipe happens:

What your latest test shows

Case 1 — Clear data → uninstall → reinstall (problem):

1. Install OsmAnd (Google Play release).
2. Change App theme:
   Menu → Settings → App profile → General settings → Appearance → App theme
3. Ensure Rendering engine v2 is selected:
   Menu → Settings → OsmAnd settings → Map rendering engine → v2
4. Android: App info → Storage → Clear data, then Uninstall
5. Reinstall from Google Play

Result:

6. On first launch after reinstall:

   • Rendering engine is v1
   • Theme is reset to original/default

✅ This matches the report: after reinstall, v2 is not the default, even if it was previously selected.

Case 2 — reinstall → Clear data after reinstall (works as expected):

1. Reinstall OsmAnd
2. Then Android: App info → Storage → Clear data
3. Launch OsmAnd again (fresh onboarding appears)

Result:

4. Now Map rendering engine shows v2 selected by default

QA takeaway

This suggests the “clean reinstall” path can behave differently depending on whether any residual state is restored or applied during the first launch after reinstall .

video_2026-02-16_12-17-40.mp4