I'm replying to myself here to stay within the confines of this topic - but I've been beating my head against the wall on this one...

Basically, my ongoing issue with convergence on the Meizu Pro 5 (on 16.04/devel) is the "fuzzy" resolution using aethercast - and I know that it's purely down to the resolution being set in aethercast/src/ac/basesourcemediamanager.cpp to 720p and not 1080p.

I scavenged an old laptop today, installed Ubuntu on it (I'm an Arch Linux user by default) and was trying to cross-compile a UBports xenial version of aethercast to upgrade the output resolution to 1080, as per this patch:

https://launchpadlibrarian.net/267505693/p1.diff

However, try as I might, I can't past these errors during cross-compiling:

Get:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease [247 kB]
Err:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

I've tried importing those keys - goodness me, I have - but to no avail.

So, in a big shout out to @mardy (who is maintaining ubports/aethercast), is there any chance that you might be able to add these three lines to the code and recompile in the near future? The patch worked wonderfully on 15.04 and I briefly (before moving to 16.04/devel) had a crystal clear 1920x1080 UT desktop on my external monitor.

Or is there an excellent reason that the 1080 isn't included by default? It seems a little odd, as almost all external monitors are at least 1920x1080 now - as I mentioned before, I had to trawl through our department's old IT storeroom to find a ten-year old monitor with a native 720p resolution - which is seemingly the only way to have crystal clear resolution using aethercast in 16.04/devel!

I really appreciate that @mardy does so much for the community already - and I know that there's likely so many more important issues to deal with - but it seems a simple change to the code and would make for a wonderful early Christmas present.

Or a late Thanksgiving one for any North Americans on the site 🙂

Ah! Thanks for the wonderfully prompt reply @advocatux and others - always some small comfort to know that you're not alone in these situations.

I just assumed that the issue was because @mariogrip and any other Norwegian developers involved had pushed the update through in a hurry so as to get out and celebrate a glorious Constitution Day, that one day a year where the sun absolutely has to shine in Bergen - by law 🙂

And on that note, I wouldn't expect anything to happen on the Norwegian side for a couple of days now 😉