That certainly looks like the same or related. Can you try de-authorizing and re-authorizing?

Thanks for your help!

Two reports that this is working in 2.21. Not working for you? Let us know!

Initial reports say that release 2.21 has fixed this in at least two cases; keep us posted!

Probably a transient network problem - sorry for the difficulty!

I'd initially made a mistake in the config- should be fixed now!

Moving conversation to our new Bugs forum - viewtopic.php?f=13&t=2465 for this issue.

We're seeing trouble decrypting/using authentication credentials in the Android O developer previews. We've minimized the case to reproduce the issue, and have a potential fix in progress here

We're seeing recurring problems decrypting stored WiGLE credentials on LineageOS with Samsung S4/S5 .
We're working on this issue, but would appreciate any full logfiles showing app initialization. This may be addressed by https://github.com/wiglenet/wigle-wifi- ... g/pull/157

We've got this down to a minimal reproducible case; getting ready to report to Google.
Info to follow. Until this gets resolved, I guess we aren't compatible with Android O.

People seem to be getting locked out of their LineageOS WiWiWa installs. We're on the case. It seems to be related to this bug report Please respond in forums if you have more info or can helps us test some things with Lineage!

Those radial lines are consistent with a common GPS failure we see. if you look at the points, I think you'll find that they have excellent signal and accuracy according to the wifi/GPS, but a timestamp of 1970-01-01 00:00:00.000 - which means that while the GPS is claiming to be accurate, it's actu...

The "download observations" function should work fine for you now (we rewrote it in 2.20) - if you want to know your new/seen stats beforehand, but only if you want to pay the performance penalty vs. just keeping a clean DB!

Cheers,

-ark

I've lined up a 6p to test with - will post the results here Monday!

Cheers,

-ark

hm, ok, so that solves that; we're probably being denied writes once the DB + new commit reaches the FS limits. We'll need to find ways to partition this in the long run. Bright side: if you use the new app version / streaming download to establish a new DB, it won't contain all the old *observation...

Hi! There are a lot of items that can effect this, so I'll try and give a framework for all of it here, and we can drill down on individual items: 1. Locally, you store your observations (you can see dots when you select an individual network) and a "best" location in the network table (we...