But Tim, your forum, and indeed various others are full of complaints about this problem, so you are in a position to talk to both Garmin and Apple to push for a fix. This is frankly daft, and if not fixed soon, I will dump Skydemon and go back to my trusty 296.

Just spoken to Garmin UK. Very helpful, acknowledged the problems, which he claims is very widespread with many other products relying on Bluetooth connectivity. IOS 10/10.1/10.1.1 actually has a problem which
prevents Bluetooth from maintaining connectivity - it is very much an Apple problem as we suspected. He tells me Apple are working on a fix, which will be issued via IOS10.02 in the near future.

Chequeredflag, Garmin acknowledged the problem was between their device and iOS on the very first page on this thread.

Hi Tim. I think we all understand it's an Apple problem, and it's considerable impact on your excellent SkyDemon service It was only yesterday, having spoken to Garmin Aviation Department, that someone took the bother to talk me through the problems, and actually confirm IOS 10.02 is being developed by Apple to finally fix the problem. Other than that, no information was forthcoming. Looking forward to Skydemon service resuming normally sometime soon!

It's a good point that you make, Chequeredflag.........I've yet to see anything that suggests that Skydemon have actually done anything to improve this situation.

I wonder if we will get a reduction in subscription fees for the period that SD cannot be relied upon?

Seriously, Tim.......please give some indication that you do have at least some slight concern about this problem and stop just shrugging your shoulders and saying "nothing to do with me".

I think this thread has run its course. Blaming SkyDemon for problems that arise from your own hardware configuration is not on, and is a poor choice of where to direct your frustration. Much as we would love to mount a crusade on behalf of our affected users, we actually have a full schedule of work to do on SkyDemon.

If anyone else comes across this thread, the issue has been confirmed to be a bluetooth one between Apple and Garmin devices.