Author Topic: Observation made with very poor WiFi.  (Read 2794 times)


  • Full Member
  • ***
  • Posts: 169
Observation made with very poor WiFi.
« on: July 14, 2014, 12:54:52 am »
I have recently been in Cornwall in the far southwest of England. Broadband in Cornwall is always at a legendary glacial speed, at least away from the few places with fibre. The best WiFi performance I could get was 0.13megabit/s down, 0.3 up. Often slower or much slower. This was measured with That app was measuring a ping time of between 0.8 and 1.4 SECONDS! (to a server in Bristol, in a better served part of the UK. The WiFi point I was using used WEP)
I observed that aqua mail and a number of other apps just failed to sync or access servers, quite understandably. Browsers usually worked up to a point, and google play store *always* worked.
I am trying to understand if there are timeouts built into individual apps like aqua mail that would be sensitive to the long ping time or low speed, or just what magic the google play app deploys to use the poorest of connections reliably.
Just curious.

Kostya Vasilyev

  • Hero Member
  • *****
  • Posts: 12740
Re: Observation made with very poor WiFi.
« Reply #1 on: July 14, 2014, 02:11:03 am »
Aqua's timeout on network connections is:

- 30 seconds on establishing connections
- 60 seconds on transmitting data

Same as used in K9 (and they took it from stock Android Email, I presume).

Don't know what exactly you've tried in the Google Play app, but it does cache a lot on the device (images, etc.) -- same as Aqua caches already loaded messages.

Creating debug logs for diagnostics:

The official FAQ:

Лог-файлы для диагностики:

Вопросы и ответы: