The latest version of OruxMaps was not the reason (sorry for the wrong assumption from my side). There was by accident only a timing correlation
The background is the following (maybe also interesting for some of you):
The
the tricky thing in that case is, that GPS data is not used anymore and for location information only "WiFi, Mobile Data, BT" data is taken.
It seems that OruxMaps is looking only to "real GPS" data and doesn't accept location data (provided by Android) based on "WiFi, Mobile data, ect.).
R.