Android: chat not resilient on low quality connections

### What I did
I attempted to use chat and files and git features when travelling (Barbados) in areas of spotty reception.

### What happened
Chat and other features entirely didn't work. Repeatedly giving timeout errors. Other chat apps (e.g. Hangouts) worked but were just slower.

### What I expected to happen
Keybase to function similar to other chat apps, and be resilient to poor connection quality. Responding slower but still being able to send small messages, etc.

The report identifies Android chat, files, and git features failing with timeouts on spotty reception, but names no files, tests, or entry points. Start by reproducing the timeout behavior under a low-quality connection and trace the Android chat path; done would require a defined resilience target and verification that small messages and related features continue working more slowly rather than failing.

Written by the indexing model from the issue text.