Increase network timeouts/ allow to manually configure for really long timeouts.

[dreirund]

Idea

Increase the network timeouts (and make it user configurable to allow for really long timeouts).

On a 64kbps mobile data connection "OpenStop" often does show timeouts instead of downloading the data. (Internet connectivity works, since the background map partially downloads.)

StreetComplete does not have this issue; it happily waits for the whole batch to finish.

Bug Relation

No response

Implementation

• Increase default timeout to 20 seconds
• add option in (advanced) settings to change it, and allow for up to two minutes (sometimes the mobile connection is bad and really has long round trip times once the data line is loaded. I experience that regularly when I am on 64kbps; data reliably flows but packets take several tens of seconds to go out/ arrive back).

Additional Info

Screenshots:

---

---

---

Regards!

[Robbendebiene]

Hi and thanks for the detailed report.

We don't really like the idea of having a separate setting for this as we want to keep the app as simple as possible (even if it would be a hidden advanced setting).
But we totally agree that we need to find better default values for the timeouts or perhaps implement clever heuristics that define the timeouts. For now we are going to increase them as we experienced this problem ourselves. However after some quick testing 20 seconds won't be enough so we are probably increasing them to about 2 minutes or so.

One problem is that we are using pixel tiles (in contrast to StreetComplete) and at the moment we cannot really move away from them. The raw OSM data requests are "blocked" (have to share their traffic) with the pixel tile requests wherefore it takes longer to complete them.

[7h30n3]

We did some network tweaks in #317. By implementing a tile cache (in best case sceanrio no tile download necessary) and an increased timeout, we hope that mitigates the issue.