GPS data not available to apps after iOS 8.3 update

I'm using a Wi-Fi only iPad with remote GPS connected via bluetooth (Bad Elf GPS Pro). Following update to 8.3, the GPS position data from the Bad Elf receiver is not available to other apps on the iPad that require it (in particular, Seattle Avionics FlyQ efb). Bad Elf bluetooth connection is good, and the GPS position data is displayed on the iPad using the Bad Elf accessory app, but it appears to not be available to the FlyQ app. Spent hours with tech support and other paths trying to fix this problem, including reloading iOS 8.3 update and applications, and even bought a new Bad Elf GPS receiver. I think this is a fairly common hardware/software combination (Wi-Fi only iPad, Bad Elf GPS, FlyQ app) for private aircraft pilots, so would expect others to be seeing the same problem (unless they were smarter than I was, and delayed updating their OS). Have others experienced this problem or found a solution? Quite frustrating, as navigation is the primary use for my iPad.

iPad (4th gen) Wi-Fi, iOS 8.3

Posted on Apr 12, 2015 5:31 PM

Reply
249 replies

Apr 25, 2015 2:12 PM in response to louisfromvaudreuil-dorion

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?

Apr 25, 2015 2:34 PM in response to firemediclex

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.

Apr 25, 2015 6:44 PM in response to Pierre J.

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.

Apr 25, 2015 8:09 PM in response to PilotDon

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.

Apr 25, 2015 11:44 PM in response to firemediclex

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.

Apr 26, 2015 3:22 AM in response to Hansvg

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.

Apr 26, 2015 8:22 AM in response to Fricotin123

I too had same problem on my Garmin Glo, with iPad running Skydemon, when I updated to 8.3. I went to Garmin website and downloaded their WebUpdater, and got the latest software update for the Glo from there. Connect your Glo and let PC find the driver before you run the updater. I had a couple of goes to get the Bluetooth to reconnect, and now all seems back to normal. Found out about this from pprune - best source of info on aviation related matters imho.

Apr 26, 2015 11:49 AM in response to Mark72658

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 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 ...............?

Apr 26, 2015 11:54 AM in response to AeroSteve

If only my PC would "see" my GLO I could try a software update. My lead is only about 30 cm long and neither my PC nor my laptop see it. So, despite downloading the Webupdater software I remain firmly stuck in the mud awaiting an Apple fix. I have also tried 2 other leads. So I guess that it's off to the Flightstore website to order a Bad Elf Pro Plus 2300 then!

Apr 26, 2015 11:57 AM in response to AeroSteve

Aerosteve,

All I can say, it works for me. I have negative experience with long USB cables. The shorter the better (pref 30cm=12 inch).

Also some other equipment seemed to have contact (charging etc) but did not update until I used short usb cables. Just my experience, your mileage may vary.

The update to 2.70 seems to have done the job, with me and others.

Apr 26, 2015 12:12 PM in response to Hansvg

I've done some tests with the Garmin Glo with its latest 2.70 firmware update.

The GPS works perfectly well on my iPhone 5c and my iPad mini 3.

I tried it also on an old iPad 2 of mine without success.


The logical conclusion is the compatibility depends on how recent the iDevice is.

I am also lead to believe the solution to this whole mess depends on Bluetooth GPS manufacturers updating their firmwares (Bad Elf, Dual), not Apple patching their iOS.

Apr 27, 2015 9:32 AM in response to ChazMills

YYou are correct. I downgraded to 8.2 the other day and it did fix the issue...However, I kept finding erroneous files under storage under "manage storage" in settings afterwards. These files have no graphical icon and are listed as "documents and data". If I delete them, they always reappear. I don't have these in any other iOS. This link appears to be a quasi-jailbreak. For security reasons, I wiped the iPad and reinstalled 8.3. From Apple. If someone else wants to jailbreak, go for it. It's just not my cup of tea.

Apr 27, 2015 9:50 AM in response to firemediclex

I have not experienced that error, or any others, since reverting to 8.2 about 10 days ago. But if you are uncomfortable with the effect, don't do it. For me, I like the effect of de-bricking my XGPS170.


There has been been some discussion, which has some credibility, that the fault is with hardware makes not bringing their firmware up to developer standards. Pointing fingers is a time-honored tradition in the hardware/software game. Eventually the smoke will clear. Meantime Apple is honoring the Great Sphynix strategy of transparency first pioneered by Microsoft.


I will enjoy how this plays out while having an XPGS170 that talks to my IPad Air and FlyQ. I wonder if there has been much chatter about this at sun 'n fun?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

GPS data not available to apps after iOS 8.3 update

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.