GPS data not available to apps after iOS 8.3 update

In reply to Hansvg

Thank you for your post. I'm not sure whether you are suggesting that I update my GLO via Bluetooth? I was on the 'phone to Garmin yesterday concerning the loss of service following the IOS8.3 update, and at the same time we discussed my problem with updating my GLO software. I had already downloaded the WebUpdater software (as you suggested) and connected my GLO to my PC (via the USB cable), but whilst it charged the GLO without a problem there was no other communication between my PC and my GLO. Garmin walked me through checking my PC Device Manager to no effect and declared that they could not help me any further, although they did offer to update my software if I sent my GLO to their Southampton office. It is the same on my Windows 7 PC and my Windows 8 laptop. Given that a software update would not solve my iPad communication problem, there seemed little point in taking this any further, although should a future software update provide significant benefits I still have the option of asking Garmin to update my device. Unless, that it, you have a fix that neither Garmin nor I have yet found ...............?

Not ALL Bluetooth GPS are affected.

I use a Bad Elf Pro+ which is still working fine. It's just the earlier versions that are caught in this mess. I flew on Thursday on a GA ferry flight and my Pro+ and iPad Mini3 on 8.3 using SkyDemon worked flawlessly.

Your IPAD mini probability has an internal GPS (cell phone capable) and more likely runs using it, instead of your external one.

LL.

<Edited By Host>

You're wrong on this one.

The Bad Elf pro PLUS is not affected by the iOS 8.3 bug.

Those who own them are the lucky ones

As for me, I think Apple takes so long because they haven't figured out the problem yet without scrapping something else in the iOS.

Try a (very) short USB cable. Works for me on various equipment.

Longer cables tend to charge the device (not only Glo but also Cactus flash trigger), whereas only short USB cables recognise the device for FW upload.

Nope. Definitely works with the external one. Very easy to check by switching on flight mode and then enabling just Bluetooth. Not exactly Phd level computer science 😉

However it does throw up a bit of a point that why is it the newer BT GPS units still work and the older types don't. Surely it's still the same GPS data, or is it down to the type of BT 'service' they use?

Pilots do not use internal phone GPS's, because we know that they are crappy and unreliable (or at least not accurate enough for aviation).

I have been doing just that for years. I'm using an iPad mini and the internal GPS. The GPS locks on in about 30 seconds and works perfectly throughout my entire flight. Accurate to within about 10 feet. Zero issues. Zero problems.

I appreciate your frustrations with this bug. I would be surprised if Apple corrects this "rapidly". If you cannot live with a 3 or 4 month delay, an Android device may be your answer.

No, 2.70 on Garmin Glo doesn't fix anything.

Let's all understand this is *not* a Garmin, Dual, Bad Elf, etc., issue. These devices successfully communicated by BT with our iPads and stopped working when Apple changed something in 8.3 The BT devices worked with a multitude of Apps for years - And now they don't.

I expect Apple will eventually restore this functionality and hopefully soon. But, Apple better realise that they have a real Quality Assurance problem. BT is one thing but the WiFi issue affects everyone. And Apple had better realise it is tarnishing its reputation and doing harm to a previously extremely successful business. Apple had over the years built up a cult like following bit, cults come and go often with great speed.

You need to tell Apple. We can do nothing for you.

Feedback

Pete

Apple had over the years built up a cult like following bit, cults come and go often with great speed.

I have been an Apple customer since 1979. Mostly I love them, but sometimes, 😠😕😢.

I have seen this many times with iOS in many different products. An update, BREAKS SOMETHING. A simple solution would be an EASY method to go back to the previous version. That way, people using iOS 8.3 could go back to 8.2 until the bug gets fixed.

So, why doesn't Apple do this? The reason is largely because they want to move forward, and it puts pressure on all parties to make the fix. But it would be nice to give the customer an option.

http://bad-elf.com/blogs/bad-elf/18013536-alert-compatibility-issue-with-apple-i os-8-3-and-external-gps-receivership

What I understand is that it is not "broken".

Bluetooth has different variations on their protocol.

Apple decided to implement the latest version with iOS 8.3

This already had been adapted by some GPS producers, hence the fact that some latest models do work or a FW update solves the issue.

Although I would like to have seen backwards compatibility, I do not think the blame is solely on Apple.

If the GPS communicates with the latest protocol it works.

All Apple had to do was flag the change to its users *before* making the change. At least I wouldn't have spent hours trying to figure out what had happened To something that was working very well. It seems to me that nobody was aware of the change or its implications for safe aerial navigation. Not the GPS device makers nor the App producers and certainly not the Apple Customers. I was taught in Marketing at University that, in markets, the Golden Rule is the paramount guide. The Golden Rule? He who has the gold (the customer) Rukes. Apparently, the Golden Ruke does not apply to Apple and they prefer the Old English Law epithet "Caveat Emptor".

Like my teachers used to write on my School Reports "with more effort, could have done better". Apple, more and effort required.

IF I hotspot my WiFi only iPad Mini to my iPhone via WiFi, will the iPad Mini be able to source GPS data from the iPhone's GPS receiver?