[4.6.0.11] Video calls in AppSupport are shrunk (not full-screen). Many apps affected

REPRODUCIBILITY: 100% (always)
OSVERSION: 4.6.0.11
HARDWARE: Sony Xperia 10 III - xqbt52 - xqbt52 - 1.0.1.10 - aarch64
UI LANGUAGE: Deutsch (user: de_DE, os: de_DE.utf8)
REGRESSION: yes (since: 4.5.0.24 - n/a)

DESCRIPTION:

Until 4.5.0.26 a video call in Signal would use the whole screen. Since 4.6.0.11, it only uses about 1/2 of the screen and has a black border around it.

[EDIT]: there are several apps with video calling which are affected. Reported so far:

  • Signal
  • Teams
  • WhatApp
  • Facebook
  • Threema
  • Slack

Aditionally, at least one app from another category is affected:

  • komoot

PRECONDITIONS:

STEPS TO REPRODUCE:

  1. Make a video call with Signal (AppSupport)

EXPECTED RESULTS:

I would expect to have the call fullscreen

ACTUAL RESULTS:

The fullscreen-Signal shrinks as soon as I initiate a video call and gets a black border.

MODIFICATIONS:

  • Patchmanager: yes
  • OpenRepos: yes
  • Chum: yes
  • Other: yes: microG installed

ADDITIONAL INFORMATION:

Device Owner User: defaultuser
Home Encryption: enabled

the initial version of this bug report was created using Bugger 0.9.10+git3
1 Like

Also mentioned in [4.6.0.11][AppSupport] Whatsapp "window" gets closed when hitting back sometimes - #5 by Trebis

1 Like

Today this happened to me when I started to navigate with komoot.
As I was sitting on my bike, I somehow turned the phone to landscape mode and back to portrait, and then I had it fullscreen again.

3 Likes

The same issue with Threema messenger. And it seems that the audio routing to the loudspeakers also does not work anymore.

Video Calls with Teams App (Android) are also shrinked to half of the screen width.

So this apparently affects video calls with android apps in general, see for instance this post in Sorry Jolla 4.6 :“Android video messaging in WhatsApp, Facebook etc only occupying a third of the screen,”

So far, this bug is reported for

  • Signal
  • Teams
  • WhatApp
  • Facebook
  • Threema

@jauri.gagarin.II : maybe you can change the title in the bug report (and maybe also the details in the report) to indicate that this bug affects video calls with android apps in general.

It is a clear regression that hopefuly can be fixed by Jolla prior to releasing 4.6 to everyone

In principle you are right, but it seems to affect more apps than “only” video calling, e.g. komoot (at least simetimes).
Do you have an idea for a short but concise title?
[EDIT]: already changed title.

I tried video calls with WhatsApp and Signal on Xperia 10 III (4.6.0.11). Both worked in full-screen mode. Incoming and outgoing video calls.
What is causing the difference? I do not know. I do not have any of the “modifications” but would they do any harm?

This text is a bit unclear: “Video calls with several apps (+other apps) in AppSupport are shrinked”
Does it mean that there must be several other apps open to make the video call problem occur? I think not, so I modified the heading.

Hi,

Im not sure if this is same issue that I encountered but I think it means that app is only size of a postcard. This happen also in Google Sheets app. See my attachment.

Yes, modification of heading was correct:)

1 Like

Yes, this shows the “shrinked” screen. The video screen in a Teams video call looks the same

I tried to compile the reports from several users in several threads and thus came up with the list above. Apparently

  • Teams
  • Threema
  • Signal
  • Facebook
  • WhatsApp

are concerned.

With Teams, the video only “shrinks” when the connection is established. Initially (prior to a response from the called person) the image is full-screen.

Both, landscape and portrait orientation are concerned.

I am also using an Xperia 10 III with Chum, OpenRepos, MicroG, but no Patchmanager

This is how a video call in Teams looks like:

I get this too, both on X10 iii and XA2 Plus, with Whatsapp video calls and Facebook video calls. They were full screen on the 4.5 releases.

1 Like

What do you get from this command?


rpm -qa |grep -E 'alien|apkd|android|appsupport' | sort

My Xperia 10 III says:

alienaudioservice-1.29.0-1.13.1.jolla.aarch64
alienaudioservice-plugin-pulseaudio-1.24.0-1.11.1.jolla.aarch64
alienaudioservice-plugin-sailfish-1.6.0-1.7.1.jolla.aarch64
aliendalvik-1.8.0-1.5.1.jolla.aarch64
aliendalvik-configs-11.0.128-1.25.1.jolla.aarch64
alienkeyboardservice-0.12-1.2.4.jolla.aarch64
apkd-plugin-geo-qtpositioning-1.0.0-1.1.3.jolla.aarch64
apkd-plugin-media-mpris-1.0.0-1.1.1.jolla.aarch64
apkd-plugin-notifications-fdo-ext-1.0.4-1.1.1.jolla.aarch64
apkd-plugin-permissions-sfos-1.2.0-1.3.1.jolla.aarch64
apkd8-11.0.0.69.1-1.22.1.jolla.aarch64
apkd8-android-settings-11.0.0.69.1-1.22.1.jolla.aarch64
apkd8-l10n-all-translations-1.85.1-1.11.1.jolla.noarch
appsupport-config-generator-1.10.10-1.10.1.jolla.aarch64
appsupport-configs-user-11.0.128-1.25.1.jolla.aarch64
appsupport11-system-unprivileged-11.0.0.74.46.1-1.6.1.jolla.aarch64
feature-alien-0.4.2-1.2.3.jolla.aarch64
libalienaudioservice-1.24.1-1.10.1.jolla.aarch64
libapkd-1.10.0-1.5.1.jolla.aarch64
ofono-alien-binder-plugin-0.3.2-1.4.1.jolla.aarch64
usb-moded-connection-sharing-android-connman-config-0.86.0+mer66-1.13.2.jolla.aarch64
[defaultuser@Xperia10III ~]$ rpm -qa | grep -E 'alien|ap
kd|android|appsupport' | sort
alienaudioservice-1.29.0-1.13.1.jolla.aarch64
alienaudioservice-plugin-pulseaudio-1.24.0-1.11.1.jolla.
aarch64
alienaudioservice-plugin-sailfish-1.6.0-1.7.1.jolla.aarc
h64
aliendalvik-1.8.0-1.5.1.jolla.aarch64
aliendalvik-configs-11.0.128-1.25.1.jolla.aarch64
alienkeyboardservice-0.12-1.2.4.jolla.aarch64
apkd-plugin-geo-qtpositioning-1.0.0-1.1.3.jolla.aarch64
apkd-plugin-media-mpris-1.0.0-1.1.1.jolla.aarch64
apkd-plugin-notifications-fdo-ext-1.0.4-1.1.1.jolla.aarc
h64
apkd-plugin-permissions-sfos-1.2.0-1.3.1.jolla.aarch64
apkd8-11.0.0.69.1-1.22.1.jolla.aarch64
apkd8-android-settings-11.0.0.69.1-1.22.1.jolla.aarch64
apkd8-l10n-all-translations-1.85.1-1.11.1.jolla.noarch
appsupport-config-generator-1.10.10-1.10.1.jolla.aarch64
appsupport-configs-user-11.0.128-1.25.1.jolla.aarch64
appsupport11-system-unprivileged-11.0.0.74.46.1-1.5.1.jo
lla.aarch64
feature-alien-0.4.2-1.2.3.jolla.aarch64
libalienaudioservice-1.24.1-1.10.1.jolla.aarch64
libapkd-1.10.0-1.5.1.jolla.aarch64
ofono-alien-binder-plugin-0.3.2-1.4.1.jolla.aarch64

Xperia 10 III on 4.6.0.11:

alienaudioservice-1.29.0-1.13.1.jolla.aarch64
alienaudioservice-plugin-pulseaudio-1.24.0-1.11.1.jolla.aarch64
alienaudioservice-plugin-sailfish-1.6.0-1.7.1.jolla.aarch64
aliendalvik-1.8.0-1.5.1.jolla.aarch64
aliendalvik-configs-11.0.128-1.25.1.jolla.aarch64
alienkeyboardservice-0.12-1.2.4.jolla.aarch64
apkd-plugin-geo-qtpositioning-1.0.0-1.1.3.jolla.aarch64
apkd-plugin-media-mpris-1.0.0-1.1.1.jolla.aarch64
apkd-plugin-notifications-fdo-ext-1.0.4-1.1.1.jolla.aarch64
apkd-plugin-permissions-sfos-1.2.0-1.3.1.jolla.aarch64
apkd8-11.0.0.69.1-1.22.1.jolla.aarch64
apkd8-android-settings-11.0.0.69.1-1.22.1.jolla.aarch64
apkd8-l10n-all-translations-1.85.1-1.11.1.jolla.noarch
appsupport-config-generator-1.10.10-1.10.1.jolla.aarch64
appsupport-configs-user-11.0.128-1.25.1.jolla.aarch64
appsupport11-system-unprivileged-11.0.0.74.46.1-1.5.1.jolla.aarch64
feature-alien-0.4.2-1.2.3.jolla.aarch64
libalienaudioservice-1.24.1-1.10.1.jolla.aarch64
libapkd-1.10.0-1.5.1.jolla.aarch64
ofono-alien-binder-plugin-0.3.2-1.4.1.jolla.aarch64

What I spot at first sight: while you, @jovirkku, have appsupport11-system-unprivileged-11.0.0.74.46.1-1.6.1.jolla.aarch64, @thigg and me have another version: appsupport11-system-unprivileged-11.0.0.74.46.1-1.5.1.jolla.aarch64 (and we both lack the usb-moded-connection-sharing-android-connman-config-0.86.0+mer66-1.13.2.jolla.aarch64, which doesn’t sound like it could have something to do with the problem), but I guess you know better than me what you are looking for :wink:

alienaudioservice-1.29.0-1.13.1.jolla.aarch64
alienaudioservice-plugin-pulseaudio-1.24.0-1.11.1.jolla.aarch64
alienaudioservice-plugin-sailfish-1.6.0-1.7.1.jolla.aarch64
aliendalvik-1.8.0-1.5.1.jolla.aarch64
aliendalvik-configs-11.0.128-1.25.1.jolla.aarch64
alienkeyboardservice-0.12-1.2.4.jolla.aarch64
apkd-plugin-geo-qtpositioning-1.0.0-1.1.3.jolla.aarch64
apkd-plugin-media-mpris-1.0.0-1.1.1.jolla.aarch64
apkd-plugin-notifications-fdo-ext-1.0.4-1.1.1.jolla.aarch64
apkd-plugin-permissions-sfos-1.2.0-1.3.1.jolla.aarch64
apkd8-11.0.0.69.1-1.22.1.jolla.aarch64
apkd8-android-settings-11.0.0.69.1-1.22.1.jolla.aarch64
apkd8-l10n-all-translations-1.85.1-1.11.1.jolla.noarch
appsupport-config-generator-1.10.10-1.10.1.jolla.aarch64
appsupport-configs-user-11.0.128-1.25.1.jolla.aarch64
appsupport11-system-unprivileged-11.0.0.74.46.1-1.5.1.jolla.aarch64
feature-alien-0.4.2-1.2.3.jolla.aarch64
libalienaudioservice-1.24.1-1.10.1.jolla.aarch64
libapkd-1.10.0-1.5.1.jolla.aarch64
ofono-alien-binder-plugin-0.3.2-1.4.1.jolla.aarch64

That package has been rebuilt on my phone as it is running 4.6.0-devel, i.e. not any more 4.6.0.11 exactly but it has small modifications. Those should not be significant. And indeed, I could see the reported issue with the Signal video call today (with the package collection that I reported). After restarting AppSupport the problem disappeared. We are still hunting for the reason.

Thanks for the rpm outputs. The culprit is not there. No need for more of them.

5 Likes

Strangely this issue only occurs for me on Facebook Messenger if I make the call. If a friend calls me first it scales/works correctly :person_shrugging: Haven’t tested this with any other of the listed apps as this is really the only one I use for video calls with any frequency.