Thanks again for making it available for 4.1 – but now I found a minor "incident" with that. There's a method referenced not available before Android 4.2 concerning cell-based geolocation (for details, see this issue for the Mozilla backend).
You can find a stack-trace here at pastebin.com for what's happening. Seems not to be that crucial, though, as a location is still found:
I/org.openbmap.unifiedNlp.Geocoder.OnlineProvider(11635): JSON response: {"source":"wifis","accuracy":30,"location":{"lng":11.570856997514667,"lat":48.166475879909996},"measurements":104}
A solution would be an additional option in the module's settings to discable cell-based location. E.g.
[ ] use cell-based location (4.2+)
[x] use WiFi based location
and initially disable the first option on lower Android versions, but still give the user the chance to check it on "own risk", as some 4.1 devices indeed seem to support it – if I understood Marvin correctly:
Using gsm cells to geolocate is not possible on Android version 4.1 and below because of missing API support on most devices.
(emphasis mine).
I'm still jumping between the different projects here at Github with my issues "mixing things up": Though OBM finds a location, UnifiedNlp doesn't seem to pick it up – but reports the Google location instead (details in the linked issue; and yes, I do have the Xposed UnifiedNlp module installed and loaded – as in all my tests, it reports having found a location, but it's not a UnifiedNlp one) … Or could it be your module doesn't "hand it through" here? The above line is the only proof I have OBM found a location – and after all it only reports "JSON response", not "location found".
Ah, yuck: See a longer excerpt at this pastebin: Looks like after finding the location, it simply crashes :(
java.lang.NoSuchMethodError: android.location.Location.getElapsedRealtimeNanos
DeviceInfo: This time a tablet running stock 4.1.2, so no cell module/SIM (if you need closer info on the device, just let me know).