Announcing PiAware 3! (Latest version: 3.8.0)

Nope. Portrait mode stays blank after several minutes, even with zoom in and out.
Landscape paints slowly, but if I zoom, it paints quickly.

Cannot reproduce this on Chrome 76.0.3809.132, Android 8.1.0

I can verify that Chrome 77.0.3865.73 Android does not display the map tiles in portrait mode. only in landscape.
I noticed this a few days ago. Map displays fine in older version of Chrome and desktop.
Opera for Android also works fine.
This happens in both dump1090-fa and tar1090, with all available map layers

1 Like

I have Android 9, Chrome 77.0.3865.73

top shows dump-1090 at 27% CPU.

Same version, working fine for me.
Try clearing the browser cache.

I tried every trick in the book, believe me. Even clearing the cache partition from recovery and wiping all chrome data.
Finally, I disabled chrome, and reverted to the pre-installed version (74.something), and the map showed correctly. As soon as I updated from the play store, the map tiles stopped showing

I cleared Chrome cache from Chrome, and from the Apps panel.
Still no joy, in portrait mode.
Firefox works in portrait mode.

Android 9, Chrome 77.0.3865.73

In landscape mode, the map background is now blank, even if I scroll around.
If I zoom in or out, then it paints.

That’s another reason to stay with Firefox. Besides the Adblockers being blocked on Chrome…

1 Like

Still no joy with today’s chrome update…

PiAware 3.7.2 is now available! Please see the first post in this thread for the release notes. If you run into any problems please let us know.

Fresh installs:
You can use the disk image found here:
http://piaware.flightcdn.com/piaware-sd-card-3.7.2.img.zip

Or if you already have a Pi running Raspbian you can do a package install by following the instructions here:

Upgrade methods:

If you are currently on a PiAware SD card image:

  1. Re-image with 3.7.2 SD Card image (link) - Be sure to set your ā€œfeeder-idā€ either in the piaware-config.txt file or via the command line after re-installing so that you keep your existing My ADS-B statistics
    Or
  2. Upgrade via your My ADS-B stats page (ā€œUpgrade and restart PiAwareā€ Device command in the gear icon menu)

If you are currently on a PiAware package install:

  1. Upgrade via My ADS-B stats page (ā€œUpgrade and restart PiAwareā€ and ā€œUpgrade and restart dump1090ā€ Device commands in the gear icon menu)
    Or
  2. Repeat all of steps 2, 3 , 4, and 5 at PiAware - dump1090 ADS-B integration with FlightAware - FlightAware

One question you may have is ā€œwhy don’t you want TIS-B data from dump978ā€? TIS-B data is known to cause us issues with downstream processing and it doesn’t provide us much more than what we already get from other sources. TIS-B data will still be displayed in SkyAware.

1 Like

Do we have a change log?

Done it via My ADS-B Stats page!

Please see the first post in this thread for the release notes.

1 Like

@obj
Could you elaborate on which data outputs from dump978-fa give TIS-B and which don’t?
Or is it just filtered by piaware and you are communicating it because of the statistics?

I guess the same goes for 1090 MHz TIS-B?

Station #5252
Refused upgrade of piaware on Raspbian Buster :slightly_frowning_face: :astonished:

[2019-09-20 11:04 EDT] *** running command '/usr/lib/piaware/helpers/run-apt-get update' and logging output
[2019-09-20 11:04 EDT] child process 2962 exited with status EXIT 1
[2019-09-20 11:04 EDT] manual update (user-initiated via their flightaware control page) requested by adept server
[2019-09-20 11:04 EDT] run-apt-get(2962): Automatic updates not available for OS raspbian:10 (Raspbian GNU/Linux 10 (buster))

This. There’s no change to what dump978-fa produces or what’s shown in skyaware; the change is that we stopped forwarding 978MHz TIS-B to the FlightAware servers and it’ll no longer show up in FlightAware stats. We’re not using TIS-B downstream any more (for both 978 and 1090) and it made sense to make this change relatively early before there were a lot of established 978 deployments.

(We decided to stop using TIS-B because the data quality isn’t great and it generally duplicates data we get direct from the FAA anyway since it’s from the same source)

It should actually help with the 978 stats I think since TIS-B tended to be much higher volume than the ā€œrealā€ UAT data and would drown it out (and didn’t reflect your actual coverage - just whether you could hear the ground station)

There’s no change to 1090MHz TIS-B at the moment because we don’t want to disrupt the stats for established sites. We’re not using the data but it’s still being uploaded and counted in stats. The long term plan is to stop forwarding 1090 TIS-B too, but the timeline for that isn’t set yet.

2 Likes

There’s no official support for Buster yet, and we don’t have packages built for it - that’ll be in 3.8

pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"


pi@raspberrypi:~ $ apt-cache policy piaware
piaware:
  Installed: 3.7.1
  Candidate: 3.7.2

.

pi@raspberrypi:~ $ wget http://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_3.7.2_all.deb  
pi@raspberrypi:~ $ sudo dpkg -i piaware-repository_3.7.2_all.deb
pi@raspberrypi:~ $ sudo apt-get update
pi@raspberrypi:~ $ sudo apt-get install piaware
pi@raspberrypi:~ $ apt-cache policy piaware   
piaware:                                        
   Installed: 3.7.2                              
   Candidate: 3.7.2
pi@raspberrypi:~ $ sudo apt-get install dump1090-fa

pi@raspberrypi:~ $ apt-cache policy dump1090-fa
dump1090-fa:
  Installed: 3.7.2
  Candidate: 3.7.2

A simple sudo apt-get upgrade would have done the same.

It’s just the piaware upgrade logic refused to work on Buster.

1 Like

So what they’ll do, cry? I think it makes good sense to discard those too.

At the risk of asking an elementary question: how do I upgrade a compiled version? Simply compile the 3.7.2 and install as usual ?