Issues with poor signal/timeouts

[annihat]

Hi, I've been enjoying your app (F-Droid v1.2.2) for a while but recently it's failed to obtain any postcodes.

I've read your intro on lshift.net & only one of the 3 postcode lookup addresses you quote has a sensible response, the first gives '404', the 2nd gives api instructions & the 3rd gives a captcha

I hope you'll be interested to fix it :-)

[palfrey]

Where are you physically located? There's a command line test (./gradlew runTest) that still works fine for me using http://postcodes.io/ but that's UK-only.

[annihat]

It's just worked but for the first time in months. It's telling me I'm currently in the SA9 postcode area (it gave a specific postcode) & I think it's correct.

I'm now wondering if there's an issue when there's poor signal? I think I probably use it most in poor signal areas. (Obviously no signal at all isn't going to work & that's fair enough). Can any timeouts be extended dynamically to reflect signal quality? perhaps with an on-screen note to say what's happening?

[palfrey]

Plausibly. There's a bunch of code in https://github.com/palfrey/postcode/blob/master/src/main/java/net/tevp/postcode/PostcodeBackend.java#L219 that has the current settings, and I'd be interested in patches that provide that, but I'm not immediately planning on doing this myself.