Recent content by Brian

  1. Brian

    Version 13 for Windows!

    Thanks for the feedback! I've added tickets now for the following Windows-specific issues: 1. Consumes too much CPU when minimized! (currently we do not handle this at all, so run full tilt, targeting 30 FPS!) 2. Stability issues associated with minimizing and re-opening the window. Did I...
  2. Brian

    Track up default in 13.2.17?

    I've added this to my list for fixing in 13.3. Your selection should persist, as it used to.
  3. Brian

    Black screen

    We apologize for this mishap, I should have set the "Min iOS version" for our v13.0.30 release to "iOS 13+", and then those with these older devices simply would NOT have seen the update. The downside would have been, is that if you ever removed the app or had to do "App Restore (e.g. from...
  4. Brian

    TACs not loading with iFLYEFB?

    I'm duplicating this symptom now on iFly EFB 12.3.3 -- and should have it fixed tonight for tomorrow's beta release. Looks like we might need to do an emergency patch release for all of our users, on 12.2.x
  5. Brian

    Find and fix the long-standing bug with TFR displays

    I also responded in other thread, and have added this thread link into our bug list to be fixed for iFly version 12.3/4.
  6. Brian

    Bug report (fixed!): City search behavior

    BOTH ARE NOW FIXED -- for the first Beta release of 12.3 which due for release within a few weeks.
  7. Brian

    Bug report (fixed!): City search behavior

    Added this to my short list: 1. 3 chars typed should show "Google" on Androd too. 2. Android "Back" button from search results should be same as "Cancel" not "Done/apply". You can expect these to be fixed for 12.3. Thank you for the detailed bug report!
  8. Brian

    IFly EFB 12.2.19 released

    Dynon Patch has been released here, ready for testing/validation: https://iflygps.com/AndroidAPK Install "DynonPatch-iFlyEFB-12.2.23.Android.apk". The main fix here is Auto-Detect was fixed. Without this fix it was partially working, instead of full-failure, which caused more confusion...
  9. Brian

    IFly EFB 12.2.19 released

    Hi Mike, thanks for the detailed bug report. It's possible (likely?) that when we added Avidyne support that we caused Dynon to break, in which case the fix should be easy. It's been several years since we touched Dynon code. This'll float to the top of my todo list, for the coming week...
  10. Brian

    iFLY EFB, ADS-B and XPlane

    Not sure if this is helpful advice, but you could delay starting your ADSB device until 15 secs after iFly EFB starts up -- giving iFly a chance to get weather. From then on, your Wx updates should come THROUGH the ADSB feed. Since devices tend to only be connected to one WiFi router at a...
  11. Brian

    Lost all my maps! What happened?

    Are you using a removal SD Card? In our experience, these weird one-off failures of this nature, can indicate a failing SD Card, which means it can come back. This is only a guess -- I give it ~50% chance of being the root culprit. Additionally, do you have "Menu => Settings => Device Sync"...
  12. Brian

    NMEA Output..

    POLL: iOS vs. Android. If we only did one (or did one first) -- which is more important? Since the work to be done here is mostly about "plumbing" (enabling our software to transmit via the USB port) - for something like this, the code for Android is completely separate (and often very...
  13. Brian

    NMEA Output..

    It's been years since I've given NMEA output any attention, so I'm risking sounding ignorant here. My barely educated (at this point) guess is that an adapter like this might work.. Is RS232 output what we want for hard-wired...
  14. Brian

    NMEA Output..

    @Cobra - answered this pretty well. I'll restate most of what he said, in my own words, in case it's helpful. For something "officially supported" we're obligated to "take support calls" which can be lengthy -- and if the expectation of the customer is "this is supposed to work" - then there...
  15. Brian

    NMEA Output..

    Chiming in here -- thanks to the forum poll, this feature is getting light on our end. Since we *already* have this feature in our code (which resides on the tablets as well) - the only obstacle in our way for implementation is "plumbing". The other obstacle in our way is "business case"...
Back
Top