Messages

Getting external sensors to sync nicely can be a bit of a headache depending on the Android version and Bluetooth protocols. One thing that helps narrow down connection bugs is testing the phone's baseline sensor accuracy outside of OruxMaps.
Sometimes I'll open a lightweight tool like https://pocketspeedometer.com/ in the browser just to cross-reference if the phone's native GPS/speed data is updating smoothly in real time. If the live data on the site looks stable, it usually confirms the hardware/OS side is fine, meaning you just have to tweak the background battery optimization or specific sensor refresh rates inside Orux's settings. Hope this helps you narrow down where the drop-off is happening!

The tip about moving OruxMaps data to the public folder and then refreshing/reloading profiles is especially useful. It can save a lot of trial and error when setting up OruxMaps on Windows via WSA.

Remapping the rotation axis depending on whether the phone is mounted flat on a bike or held vertically is always a tricky math problem, especially across different hardware brands (the Samsung A-series sensor changes are a classic example!).
If anyone else lands on this thread while trying to isolate a weird heading glitch, a good way to double-check if your phone's physical hardware sensors are acting up is to run a quick test on https://123compass.org/. It's a minimal, browser-based compass with calibration checks that helps you instantly verify if your phone's native orientation readings are accurate before you start digging around in the app's internal sensor settings. Safe travels!

You could also try converting the route to a track first, edit/cut the section you don't need in the track editor, and then save it as a new route if required. It's a bit of a workaround, but it has helped me a few times when I wanted to trim the end of a planned route without rebuilding the whole thing. It would definitely be a handy feature to have directly in the route editor.

I ran into something similar a while back and it turned out to be a permissions/storage access issue after an Android update. Re-selecting the map folder inside OruxMaps and giving it full file access fixed it for me. Might be worth checking that before digging deeper.

Offline maps are honestly one of the best features in apps like this, especially when traveling or hiking in areas with weak signal. Saves a lot of frustration later.

I've had OruxMaps act strangely before when map indexes or cached files got corrupted. Rebuilding the map database or removing old cache files fixed a couple of weird issues for me without needing a full reinstall.

I remember running into something similar after an Android update changed storage permissions. Re-selecting the map folder inside OruxMaps fixed it for me without needing to reinstall everything. Definitely worth trying before going down the full reset route.