Closed mvglasow closed 9 years ago
This bug is quite crippling because the backend also reports moderate position accuracy overriding other position backends until essentially a GNSS source locks in
Are you using online or offline mode?
The online mode should use cell information as fallback, when no known wifi is in range, thus normally you shouldn't get 0°N/0°E results if at least one known cell is in range, but there still might be some bug.
I would be happy, if you could provide some further details to track that issue down..
Cheers Toby
I would begin with my apologies, I just realized the tone could be misread as aggressive, it wasn't absolutely my intention. I've tested both offline and online mode: with online, i would guess it indeed uses cell reporting since everything works smoothly and a position is being reported, only the offline mode exibiths the problem. eversince my first report I've installed openbmap's client and logged some wifi of the uncovered area and the online mode still reports it correctly with even higher accuracy now, howrever the offline map didn't seem to be updated yet and i still encouter the 0-position being reported, is there a way i could log extra info? i only have a very limited experience with logcat and adb
I would begin with my apologies, I just realized the tone could be misread as aggressive, it wasn't absolutely my intention.
No problem, didn't read it that way, I agree this is a serious bug ;-)
Did you already had the chance to test whether the recently released 0.1.4 addresses this issue (see https://f-droid.org/repository/browse/?fdfilter=radiobeacon&fdid=org.openbmap.unifiedNlp)
I upgraded yesterday (so far still with the old wifi catalog, hence no offline cell data) and did a few tests. So far things look good, no more positions in the middle of the ocean. What does remain is the issue with moved wifis – when I'm in the office, I still get positions somewhere between the old and the new office – but that's a separate issue. Since the issue was a sporadic one, I would suggest testing this issue for a little longer and, if the issue doesn't reappear, close this ticket after that.
I upgraded to 0.1.4 as well and I couldn't reproduce the 0-position problem anymore
Glad to here! If you still find any problems, feel free to re-open...
I am on version 0.1.11, which I use together with microG 0.2.0 (newest version) on CM 12.1 on a Nexus 7 (2013). I experience the same problem as mvglasgow. My location is always marked as 0°N/0°E in the middle of the ocean. This happens both in online and offline mode. This even doesn't change when I switch on GPS, as openbmap seems to prevent the finding of the correct location. The correct position can only be found when I disable openbmap.
Any suggestions what I can do?
I am using same Nexus with cm13 and I also saw this bug before. But with osmand~ but i also had location somewhere in the middle of ocean.
I am not using openbmap.backend from fdroid repos cuz its still old version from 2015. And quite obsolete.
Please try using new local wifi backend and local gsm backend together from fdroid repos. And collect additiinal wifi and gsm data with radiobeacon.
My gps with custom gps.conf and local xtra.bin file is giving me gps fix in 1s in places that I visited before. So faster than with fGoogle. If you have some questions ask me via email.
AreYouLoco?
On February 8, 2016 9:35:40 AM GMT+01:00, jw243 notifications@github.com wrote:
I am on version 0.1.11, which I use together with microG 0.2.0 (newest version) on CM 12.1 on a Nexus 7 (2013). I experience the same problem as mvglasgow. My location is always marked as 0°N/0°E in the middle of the ocean. This happens both in online and offline mode. This even doesn't change when I switch on GPS, as openbmap seems to prevent the finding of the correct location. The correct position can only be found when I disable openbmap.
Any suggestions what I can do?
Reply to this email directly or view it on GitHub: https://github.com/wish7code/org.openbmap.unifiedNlpProvider/issues/6#issuecomment-181255113
Recently I fired up SatStat, and to my surprise the OpenBmap location provider claimed that I was in the middle of the ocean, at 0°N/0°E. Closer investigation revealed that for some reason I was using an old wifi catalog (ca. August 2013) which, as far as I remember, had no wifis in the area I was in. Apparently the location provider reports zero latitude and longitude when wifis are in range but none of them are in the catalog – the correct thing to do would probably be not to report a location at all.