Comment 5 for bug 1585534

This happens also to me.
I had filed a bug, but marked it as a duplicate of this one since this one has high priority.;)

For me the problem is that the aethercast is choosing the resolution 1280x720p30 instead of the 1920x1080p30.

But the screen is still at 1920x1080 so the aethercast is doing a downscale of the desktop transmitted to the dongle and the dongle is doing an upscale of the shrinked desktop so we get this problem.
I have attached the log.
The problem is at line 125 when InitOptimalVideoFormat is deciding to go with 1280x720p30 even if it is clear that the device is supporting 1920x1080p30 (line 76).

Even more digging.
This seams so simple.
The log shows clear at line 2422 that the aethercast itself ONLY supports 1280x720 resolution.

Why is that?

The basesourcemediamanager.cpp:70 states that this is the "best" resolution.

I disagree, since most miracast dongles will work with 1920x1080p30 natively.
We are producing a very ugly image on screen.

Still, can add the resolution that I want?

What is the easiest way to compile a new binary for meizu pro5?