Steps to reproduce:
2 devices (Android and Android)
or
Android and Windows 10
Android smartphone:
1)make a video call
you can see the your face
2)Rotate the smartphone
The other person (B) can see Person A in landscape (horizontal) mode (other device)
3)Now if you - Person A - start to share your screen Person B can see the screen in landscape (horizontal) mode [Windows 10: Here crashjami-client-qt#536 (closed)]
BUT
If you make a video call and share your screen immediately and rotate the screen, Person B only sees the screen horizontal BUT in portrait mode! [same issue using Jami,Windows 10]
Example:
Device B can have Windows AND Android OS
Auto rotate works if I start call horizontally!
Edited
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
Elyschanged title from Switch Between Portrait and Landscape Orientation does not work to Switch Between Portrait and Landscape Orientation does not work if you share your screen immediately
changed title from Switch Between Portrait and Landscape Orientation does not work to Switch Between Portrait and Landscape Orientation does not work if you share your screen immediately
using newest beta: as mentioned switch Between Portrait and Landscape Orientation does not work AND you get video lag (during the switch; Android: hardware acceleration OFF AND ON)
We have an ongoing work to refactor the renderer in client-qt (Windows/Linux/Macos). This should fix the crash on Windows. We will update when it's merged. You can follow the patches here https://review.jami.net/q/topic:qvideosink.
For the rotation mismatch, there is a patch that was merged on December 2021, that fixed a similar rotation issue (see commit c74375b3f8e2466e79b359f814f5f158d2eb7527 in Daemon). I don't know if you had the chance to test with this patch? If it's still there, we would have another issue then.
Yes, version 202112221635 includes this patch. So, it seems it's another issue (possibly related).
As I mentioned, on our side, we will wait for the client-qt refactoring and redo the tests.
We will update when ready.