Thanks for the details Alan. As I don't have an android device with a data plan I'll have to give Glidetrack a try, but I like the simplicity approach you've gone with. I'll forward your link to our club. We have a number of people running Android phones that would probably use this.

Morgan




On Thursday, January 29, 2015 at 3:25:54 PM UTC-8, kiwiindenver wrote:
On Thursday, January 29, 2015 at 4:02:46 PM UTC-7, Morgan wrote:
Does IGCDroid (or Glidetrack for that matter) buffer status messages and send them when it has a data connection?

I haven't flown with Glidetrack yet, but often when I take a picture I will see No Service on the phone. So I may weave in and out of service on a flight. I'm just curious if the reported track is like a SPOT in that a missed message is gone forever or if the reportings are backfilled once a data connection is available.

Thanks,

Morgan



On Thursday, January 29, 2015 at 1:24:10 PM UTC-8, Daniel Dyck wrote:
Thanks a bunch! I will definitely make good use of this!

Yes, both programs buffer data. They use very similar algorithms internally.

When cell coverage is good, GPS positions are buffered and blocks of data are sent to the GlidePort.aero server approx every 1 minute.

In areas of bad coverage data continues to be buffered and the send attempts slow down to not drain the phone battery trying to contact non existant cell towers. All the data is sent when you regain coverage.

The end result is you can get sending delays which depend upon cell coverage but you always get full detailed position data sent to the server.

There is also some delay in getting server data out to your web browsers.

What I typically saw watching my tester's fly was 5m delays. The delay stretched to 30mins at time.

Alan