View Single Post
thp's Avatar
Posts: 1,391 | Thanked: 4,272 times | Joined on Sep 2007 @ Vienna, Austria
#298
Originally Posted by onion_cfe View Post
I also noted a few times that when the timeouts were allowing me to make no progress, the only way to recover was to reconnect the wireless. Does the above and this not perhaps point to this being my problem?
Sounds like, yes. Maybe try another Wifi Access Point and see if this problem persists?

This timeout was the second timeout of the session at 56% after one at around 30% which I wasn't capturing. The throughput was much higher during this one, reported at 300KiB/s plus (my service is best in the early morning).
One possibility is to try and toggle the download rate limit on/off and see if this helps. Try it with different settings.

Tapping Download again led to no movement. Cycling offline and online again causing the wireless to reconnect and then tapping Download led to the file resuming at good speed.
This really sounds like some problem with the wireless, then.

This now gets more confusing. it didn't time out again, but it decided it was finished at 97%. I checked the show and it was definitely missing the end.
This is where the tcpdump output and the Range: headers come into play. Do they match with the "real" size of the file? Normally, gPodder uses the headers provided by the server to determine when it should stop downloading.