OpenADSB 4+

Binning flight radar

Because of this app. The only thing I don’t like is it doesn’t seem to show airports/departure-arrival boards the way fl24 does. Do t know if that’s something I’m doing wrong or if it’s a feature that could be added. Really quick app, can only compare to fl24, sorry lol but it is the superior app here. Shows some aircraft that fl24 does not, but fl24 also shows the flight path from take off airport to destination. Something else that could be added possibly. Loving it, well done and keep up the hard work ❤️

Good app with minor issues with selected altitudes.

This is a very good app. But lately I’m finding that most of the ‘selected altitudes’ are wrong. I see aircraft cruising at FL340 which have a selected altitude set to FL70, even though they won’t be descending for quite a few hours yet. When I consult plane Finder, I find that their selected altitudes are correct and do fit in with what should be the case. Not sure what’s going on here.

Developer Response ,

Thanks for the feedback and bug report.

The ground vehicles appear as a result of the FAA’s ADSE-X, in which traditional radar is used to detect and track non ADS-B tracks. Since they are not ADS-B, they do not have a unique 24-bit address (hex code). ADSE-X assigns them a random address which appears in OpenADSB as a hex code prefixed by a tilde (~). One way to not show these ground vehicles is to set the ICAO Hex Code filter to “!~*”. !=not, *=wildcard, thus it will only show tracks with a hex code that doesn’t start with ~.

To show only callsigns that starts with EXS, set the callsign filter to “EXS*”. This will only show tracks with a callsign that starts with EXS.

The transition altitude slider issue is indeed and bug and will be fixed soon. Thanks for catching this.

For ADS-B Exchange’s VRS setting, its removal from OpenADSB was intentional. Until earlier this year, ADSBx was running VRS. ADSBx has since switched to tar1090 due to VRS’ ability to scale and its considerable expense to operate. Those that have used ADSBx VRS will have noticed how much faster tar1090 is. The reason why you see VRS briefly appear on a new install is that the VRS menu option is only removed after the app is run for the first time.

Another difference between VRS and ADSBx tar1090 is bulk history fetching. The VRS protocol supports fetching all aircrafts’ history in one network request, whereas for tar1090 this isn’t possible (tar1090 requires a request per aircraft). This explains why the History button is hidden for ADSBx tar1090. Note that ADSBx’s tar1090 history goes back much further than with VRS. Sometimes the history trail is so long that it clutters up the display in which case there’s an All vs Recent history toggle button in the upper-right.

As always, feedback and bug reports are appreciated. I found your emails in the spam folder and my apologies not replying sooner.

Needs tweaking!

Yes it’s a good app, however, it would be so much better if ALL airline tracks displayed their call signs and flight number and route information as other apps do that use the same data sources, the info is there, it just needs to be displayed.

Developer Response ,

OpenADSB connects to any VRS, dump1090, ModeSMixer2 and Radarcape server. By default it uses ADS-B Exchange. Most likely you're seeing missing data from ADS-B Exchange. Feel free to contact me (Settings – Feedback) so that I can help troubleshoot.