Nicholas Killewald

Oooo, hold on, I may have a theory. I didn't realize that Android 6.0's Doze feature messes with repeating alarms (like what I use to schedule the stock price checks)....

Hm, wait. This might get a bit worse than I thought. Turns out the method I thought would help in-code still won't get a network connection if the device is...

Okay... with a bunch of testing data, at least, I was able to get the most recent version (just published to the Play Store) to trigger the Known Location notification...

Okay, that sounds reasonable. In code, if there's a problem fetching the day's stock (isn't posted yet, network failure, etc), it'll snooze for a half hour before trying again. If...

Hm... Well, what you're describing IS the intended behavior, as far as I coded it. It'll only trigger one notification per day (potentially a second one for the globalhash), and...

Well, it took me way too long to get back to this one, but I finally did! Now there's an option in place to have it notify once per Known...

If Geohash Droid exists on F-Droid, I don't have control over it, as I haven't put it there, so I'm afraid I can't edit that myself. However, the actual wiki...

Hmm... I think I can do something with that. For the most part, that is; the main reason I have it starting at 0,0 is because that's just the default...

Update: Everything should be using JSON now, and all looks right as per the MediaWiki API docs, but neither the Geohashing wiki nor my private test wiki are cooperating with...

Well, the issue with the key is pretty straightforward: Geohash Droid's a really old app, and that was the initial key I generated for it way back when. I've been...