[Ring] Gnome-Client/Android Message Sending Timing

[Nathan Royce]

I've been doing some testing. I normally have my client devices use my
server as the bootstrap.

It was good to see the the speed of messages from linux to android
taking maybe a second or two.
However, messages from android to linux were taking 1 MINUTE (at times
longer, but extremely rare for a message to go quick)... ouch.

I thought I'd play with bootstraps to see what difference it would make...
Both devices strapped to local server: linux->android fast; linux<-android slow
Both devices strapped to bootstrap.ring.cx: fast both ways
Linux strapped local, android strapped to bootstrap.ring.cx: both still fast
Linux strapped to bootstrap.ring.cx, android strapped to local:
linux->android fast; linux<-android (10sec, ***2m30s but not displayed
in client, 1m)

***That message that arrived but never was displayed should be
significant (so too should the timing).
Watching dring, I was looking for the "Found peer device" + "Text
message received" sequence (happens for every message), I saw the
message DID arrive to linux but gnome client never displayed that
particular message. The following message that took 1 minute had the
same dring sequence and did display.

Android, linux-x86, linux-arm(server) are all up to date. everything
is from git except for android (1.0 - 20171129) and opendht (1.5)