Can't always correctly rotate the camera

Oxide has been using QScreen::nativeOrientation for a while now instead of QScreen::primaryOrientation. Still, we never get Inverted orientations so this bug still exists.

The problem is there's no way in those Qt APIs to specify that the QWindow is rotated relative to the QScreen. Qt API assumes that QWindow axes are always perfectly aligned with the QScreen they're in. You can only express that the *contents* of a QWindow are rotated relative to the QScreen.

Unity8 rotates window surfaces on the display. eg: a fullscreen landscape application window in a 500x1000 pixels phone screen will be 1000x500.

Meaning that applications rotated by unity8 never really know they're rotated as they don't have to bother rotating their contents. qtubuntu does some gymnastics in order to produce QScreen values that make the application think it's always matching its QSCreen and thus no content rotation is needed (eg: SDK's OrientationHelper will never think a rotation is needed).

If you really need to know where your window is on the display and how device is oriented, you will need to look elsewhere. Current Qt APIs are not able to provide that.

And the hack in qtubuntu made to appease code that rotates UI according to Screen.angleBetween(Screen.primaryOrientation, Screen.orientation) (like OrientationHelper) also doesn't work well on desktop (bug 1542395)

Looks like this issue makes the video image appear upside-down in both portrait and landscape orientation for websites using WebRTC (e.g. https://appear.in/test-drive).

Note that the image orientation used to work correctly for landscape phone orientation before OTA-11. This issue blocks the Appear.in app from working, see https://github.com/bittner/appear-in/issues/1

On BQ phone or tablet, using either oxide-1.15 or oxide-1.16, I get 2 or 3
orientations correct, out of 4.

On a krillin, ie Aquaris 4.5, I have a correct camera view in either:
portrait, landscape (rotating anti-clockwise) or inverted portrait, but not
in inverted landscape where I see myself upside down.

This is what ths bug is about.

But a phone is different than a tablet, in that inverted portrait does not
result in a shell rotation.

On a cooler, ie M10 tablet, I have 2 orientations correct: landscape (with
the camera on top), inverted portrait (ie, with the power and volume
buttons looking downward). The other 2 result in the camera view being
upside-down.

On Wed, Aug 10, 2016 at 10:30 PM, Peter Bittner <email address hidden>
wrote:

> Looks like this issue makes the video image appear upside-down in both
> portrait and landscape orientation for websites using WebRTC (e.g.
> https://appear.in/test-drive).
>
> Note that the image orientation used to work correctly for landscape
> phone orientation before OTA-11. This issue blocks the Appear.in app
> from working, see https://github.com/bittner/appear-in/issues/1
>
> ** Bug watch added: github.com/bittner/appear-in/issues #1
> https://github.com/bittner/appear-in/issues/1
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1535820
>
> Title:
> Can't always correctly rotate the camera
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/oxide/+bug/1535820/+subscriptions
>

Sorry to say so, but on bq Aquaris E5 "Ubuntu Edition" your own image is always upside-down in both the Appear.in app (i.e. displayed by the webapp-container) and the phone's Web browser, for both portrait and landscape. Try https://appear.in/ubuntu-phone yourself on the phone, or install the Appear.in app [1] and see.

[1] https://uappexplorer.com/app/appear-in.peter-bittner

As noted before, the orientation used to be correct in the Web browser (before the camera+mike access implementation was introduced) for both orientations until OTA-10 (inclusive), and correct at least for landscape starting with OTA-11.

Is there any hope this is going to be fixed any time before Christmas?

Let me reinforce that this issue is not specific to Appear.in (i.e. no "JavaScript parameter problem"). Other sites have the same problem, and the regular desktop browsers display the image correctly.

Test drive:
- https://talky.io/ubuntu-phone
- https://appear.in/ubuntu-phone
- https://webrtc.github.io/samples/src/content/devices/input-output/

@peter sorry it did not land, track in lp:1605365

Status changed to 'Confirmed' because the bug affects multiple users.