Recent content by Cobra

I tried it a long time ago, before AP made a Windows version available. It ran, but it was finicky. I think since then the Android emulator on Windows has been deprecated, so I haven't ever tried again. Once a stable Windows version came along I never tried messing with an emulated Android...

🤷🏻‍♂️

What we really want is a modern UI where you can press-hold, then drag waypoints up and down in the list. And I think that's coming...eventually. But not immediately.

iFly EFB has not been updated on Google Play since June 2025. Adventure Pilot is working on a significant update, but it is still in beta testing and has not been publicly released yet. I can't explain why you saw the button fading behavior, but I don't think "somebody fixed something...

T41. We're real close to Class D EFD and not too much further from Class B HOU, so there's a lot of overflight traffic in the area. Especially for EFD, I could see potential conflict with arrivals from the east descending to 1000' for pattern entry and converging with T41 pattern traffic, so...

What specific devices? What do you mean by "in the last one hour"--has iFly been running continuously for over an hour, and at some point the buttons faded and won't come back? Or do you mean iFly was working fine when you shut it down less than an hour ago, and you just launched iFly again...

I, too, am confused by that. I'm not sure why a field would have a non-standard TPA but not publish it in the Chart Supplement (A/FD). That's what the authoritative source I am supposed to have access to in the plane. I'd never even heard of the "Know Before You Go" website before this post...

iFly was originally built as a moving-map navigation aid. Flight planning support was added later. I am a long-time user of and big cheerleader for iFly, but I will be honest and tell you that I don't find iFly's preflight planning features to be its strongest asset. For what it's worth, I...

I hope they have a knowledgeable user writing up the review. I was annoyed by the recent AOPA review by someone who doesn't even know the difference between "Microsoft" and "Android". It also came across as a newbie who had used it for about an hour comparing it against the comfort they had...

Maybe 15 and a half, if you were an early adopter. iFly 700 came out in Aug of 2010.

The v12 version you are running is the most current production release. Subsequent Windows versions have not yet made it out of beta testing.

The ADSB data stream includes both (uncorrected) pressure altitude and GPS position, which includes altitude. The "Use Pressure Altitude" selection in iFly likely affects which altitude is plucked from the ADSB traffic data and used to display target altitude (or relative altitude).

I'm not really sure which is more accurate. If your Stratux sensor is calibrated well, then if you keep the altimeter settings consistent between your tablets and your pressure altimeter in the panel, then pressure altitude may be the more consistent measurement to use, since that's what ATC...

Any chance one is using pressure altitude, and the other is using GPS altitude? Pressure altitude can differ significantly from GPS altitude for numerous reasons. Check here: Menu > Setup > Units of Measure > Pressure Altitude Support Alternately, could they both be using Pressure Altitude...

Which tablet? Which version of iFly? I don't have a tablet that runs OneUI 8, but I do have a Samsung S24 Ultra phone that does. iFly runs in full screen with no problems on that device.