Call for testing: Ubuntu Touch Focal OTA-4

@peat_psuwit Is Xperia X still on the list? There is an upgrade for rc. Its called version 10, about 150 mb, but upgrading lands in recovery saying upgrade failed. Do I have to switch ti devel or do I have to use the installer?

We does intend the Xperia X to be part of this release. However, due to limit resource we didn't test it before hand. We'll take a look at this.

@ATTESA said in Call for testing: Ubuntu Touch Focal OTA-4:

Do you mean the new policikit/pkexec feature for apps with elevated privileges?

If so, any app we can take as example to update the code of our apps?

Thanks for your hard work.

We actually meant whether usual microphone/camera/location prompt appear when you use a new app. Sorry for confusion.

Unfortunately, the work on PolicyKit agent has to be reverted for now, due to regression found in the System Settings app.

arubislander

@peat_psuwit said in Call for testing: Ubuntu Touch Focal OTA-4:

due to regression found in the System Settings app

Might you be able to clarify? The more people know, the more people that are able to answer questions about this if it comes up.

peat_psuwit

@arubislander said in Call for testing: Ubuntu Touch Focal OTA-4:

@peat_psuwit said in Call for testing: Ubuntu Touch Focal OTA-4:

due to regression found in the System Settings app

Might you be able to clarify? The more people know, the more people that are able to answer questions about this if it comes up.

It's a regression in the user experience when a user changes the PIN or passphrase. With the changes, an additional password prompt will show up after pressing OK, asking for a new password while confusingly implying that the old one is needed.

https://gitlab.com/ubports/development/core/lomiri-system-settings-security-privacy/-/issues/7

Sander

I've updated and tested on my Pixel 3A.

Things that work:

The ADB prompt works reliably on both macOS and Ubuntu.
My ringtone is still the same as it was before updating.
Permission requests work.
Changing my PIN works.
Waydroid still works.
Morph seems to be working fine for my everyday browsing. 1080p YouTube videos playback fluently.
Video playback in Teleports and the Media Player works.
Vibrations from app notifications or calls work.
The dark mode switch in the Settings app works great

Things that don't work:

I don't see charging information on my lock screen, even though it is enabled in the Settings app.
In the camera app, I can see the same strip of background that Moem describes.
I encountered a weird bug: when changing the system language from Dutch to English, the system is partly in Dutch and partly in English. After a second reboot, this issue still persists. When changing back to Dutch, the entire system (apart from some untranslated strings) is in Dutch again. I've also tried other languages and there is still a mix-up with Dutch. I've added two screenshots where I've set the system language to English.

photo_2024-01-16 19.18.13.jpeg photo_2024-01-16 19.18.24.jpeg

peat_psuwit

@Sander-Klootwijk said in Call for testing: Ubuntu Touch Focal OTA-4:

Things that don't work:

I don't see charging information on my lock screen, even though it is enabled in the Settings app.

This is weird. Please get the result of command upower -d, executed either via ADB, SSH, or the Terminal app.

In the camera app, I can see the same strip of background that Moem describes.

I can reproduce this, how this seems to be purely cosmetic. Either you or @Moem, please file an issue at https://gitlab.com/ubports/ubuntu-touch so that we don't lose track of it. Since this doesn't seem to break the actual camera usage, it will probably be fixed in the next OTA.

I encountered a weird bug: when changing the system language from Dutch to English, the system is partly in Dutch and partly in English. After a second reboot, this issue still persists. When changing back to Dutch, the entire system (apart from some untranslated strings) is in Dutch again. I've also tried other languages and there is still a mix-up with Dutch. I've added two screenshots where I've set the system language to English.

This is also weird, and I can't reproduce this - although my phone is originally set to English. Could you please get content of file ~/.pam_environment and file /etc/default/locale, and also the output of command locale? Again, this can be done via ADB, SSH, or the Terminal app.

I also have a few questions:

Have this ever happen before with the previous OTA?
Does the reboot seem to happen fully? In other words, does the Google logo appear after reboot? I'm looking into a possibility that the reboot might not actually happen, but instead our shell (Lomiri) crashes create a reboot-looking situation.

Sander

@peat_psuwit said in Call for testing: Ubuntu Touch Focal OTA-4:

This is weird. Please get the result of command upower -d, executed either via ADB, SSH, or the Terminal app.

This is the output, while charging my phone: https://pastebin.ubuntu.com/p/GGQKnC8YKn/

I can reproduce this, how this seems to be purely cosmetic. Either you or @Moem, please file an issue at https://gitlab.com/ubports/ubuntu-touch so that we don't lose track of it. Since this doesn't seem to break the actual camera usage, it will probably be fixed in the next OTA.

I'll file an issue for this.

This is also weird, and I can't reproduce this - although my phone is originally set to English. Could you please get content of file ~/.pam_environment and file /etc/default/locale, and also the output of command locale? Again, this can be done via ADB, SSH, or the Terminal app.

These are the results with the system language set to English (US).

Content of ~/.pam_environment:

LANGUAGE        DEFAULT=nl_NL
LANG        DEFAULT=nl_NL.UTF-8
LC_NUMERIC      DEFAULT=en_US.UTF-8
LC_TIME DEFAULT=en_US.UTF-8
LC_MONETARY     DEFAULT=en_US.UTF-8
LC_PAPER        DEFAULT=en_US.UTF-8
LC_NAME DEFAULT=en_US.UTF-8
LC_ADDRESS      DEFAULT=en_US.UTF-8
LC_TELEPHONE    DEFAULT=en_US.UTF-8
LC_MEASUREMENT  DEFAULT=en_US.UTF-8
LC_IDENTIFICATION       DEFAULT=en_US.UTF-8
PAPERSIZE       DEFAULT=letter

Content of /etc/default/locale:

LANG=en_US.UTF-8

Output of locale:

LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Have this ever happen before with the previous OTA?

I have not changed the system language before. It has been Dutch since I flashed Ubuntu Touch. So I don't know what the behavior would have been on previous OTA's.

Does the reboot seem to happen fully? In other words, does the Google logo appear after reboot? I'm looking into a possibility that the reboot might not actually happen, but instead our shell (Lomiri) crashes create a reboot-looking situation.

After clicking 'Restart Now,' a full reboot occurs. I see the Google logo, and I have to enter my SIM PIN again.

vince.vs

Hello,
I agree with you about the improvements to UT, and about not always saying the same thing, namely that the led notification still doesn't work permanently on OPT5 : https://forums.ubports.com/topic/9592/notification-lights-not-working-topic-8775

As for the comments shared by several users, here's what I've noticed:
@Moem writes:
My first impression is that it seems smoother/faster.
I reply: absolutely true!

Waydroid still works. Incoming messages in Waydroid do vibrate.
I reply : I don't use Waydroid - lineage in practice, but in my case, I have installed it and I notice that MicroG crashes and so use would then be difficult ... ( but that may be beside the point ... )

Starting the camera, I very briefly see a strip of the background at the bottom of the screen which is otherwise black during camera startup.
I reply: I've also noticed this.

Camera works fine.
I reply: yes and no, that is to say that sometimes the recording has no sound, and this happened with ota 2, then it worked with Ota-3, then not always the sound with RC ota-4

Double tap to wake doesn't seem to be working.
I reply:as has been pointed out, it's permanent, so it also works after restarting the device, but .... if I start Waydroid, then stop Waydroid, the double tap to wake is deactivated and you have to set it up again.
@Sander-Klootwijk write :
I encountered a weird bug: when changing the system language from Dutch to English, the system is partly in Dutch and partly in English. After a second reboot, this issue still persists. .....
I reply : same problem for me, in my case in French ...
Sincerly

peat_psuwit

@Sander-Klootwijk said in Call for testing: Ubuntu Touch Focal OTA-4:

@peat_psuwit said in Call for testing: Ubuntu Touch Focal OTA-4:

This is weird. Please get the result of command upower -d, executed either via ADB, SSH, or the Terminal app.

This is the output, while charging my phone: https://pastebin.ubuntu.com/p/GGQKnC8YKn/

Sadly, I can't find any interesting information from this. If you could help, could you please get the output of command gdbus introspect --system --dest org.freedesktop.UPower --object-path /org/freedesktop/UPower/devices/DisplayDevice?

This is also weird, and I can't reproduce this - although my phone is originally set to English. Could you please get content of file ~/.pam_environment and file /etc/default/locale, and also the output of command locale? Again, this can be done via ADB, SSH, or the Terminal app.

These are the results with the system language set to English (US).

<snip>

And for this, please help me get additional information. To avoid getting too much clutter, please follow these steps in this order:

Go to System Settings > Language & Text > Display language, so that you're in the language chooser. Don't choose a language yet.
Over ADB or SSH connection, run the command sudo dbus-monitor --system sender=org.freedesktop.Accounts destination=org.freedesktop.Accounts. The command will output a few lines, and then wait for more.
Choose a language and confirm, so that you're asked to reboot. Command in 2.) will output a lot more. Press Ctrl + C to stop waiting for more output.
You can now reboot the phone. Please send the output from 2.).

@vince-vs said in Call for testing: Ubuntu Touch Focal OTA-4:

@Sander-Klootwijk write :
I encountered a weird bug: when changing the system language from Dutch to English, the system is partly in Dutch and partly in English. After a second reboot, this issue still persists. .....
I reply : same problem for me, in my case in French ...
Sincerly

Could you please also follow the steps from above to collect more information?

lduboeuf

@Sander-Klootwijk write :
I encountered a weird bug: when changing the system language from Dutch to English, the system is partly in Dutch and partly in English. After a second reboot, this issue still persists. .....
I reply : same problem for me, in my case in French ...
Sincerly

Could you provide some contexr: device, have you started on Focal with a clean install, or from 16.04 to 20.04 and maybe came back to 16.04 for some time, did you have used apt install or some random commands that may write to the device ?

domubpkm

Volla. I'm still on OTA-3, not rc. But is it normal to see this when I use a French keyboard ? Bug ? known or corrected in rc test OTA-4 ?

kristatos

@domubpkm I've observed this since I'm on focal. On Xenial it has worked like expected and since focal the keyboard-quickmenu is always "English".

vince.vs

@peat_psuwit
Hello,
Unfortunately, I don't have time to deal with this this week, and I'm a bit reluctant to dig deeper into my only phone that I use every day.
To rectify, on my OPT5, my version is in French, but on the home screen, there is still the information: "No text message received today" (so in English), but the date and time and the rest are in FR.
I should point out that in the system settings, there are several items that are still in English while the main one is in French; I've noticed that it's not only on UT that this sort of thing exists, because on a Linux distribution with, for example, KDE, Gnome, etc, it happens that there are still some indications (by default) in English, while a previous version was mature and well translated...
Have a nice day

vince.vs

@lduboeuf
Hello,
Yes, I first went from 16.04 Xenial to ota-1 20.04 Focal, and following various problems, I reinstalled focal directly with Ubports installer.
Best regards

Sander

@peat_psuwit said in Call for testing: Ubuntu Touch Focal OTA-4:

Sadly, I can't find any interesting information from this. If you could help, could you please get the output of command gdbus introspect --system --dest org.freedesktop.UPower --object-path /org/freedesktop/UPower/devices/DisplayDevice?

Here is the output: https://pastebin.ubuntu.com/p/BnHxXdsPRX/

And for this, please help me get additional information. To avoid getting too much clutter, please follow these steps in this order:

Go to System Settings > Language & Text > Display language, so that you're in the language chooser. Don't choose a language yet.

Over ADB or SSH connection, run the command sudo dbus-monitor --system sender=org.freedesktop.Accounts destination=org.freedesktop.Accounts. The command will output a few lines, and then wait for more.

Choose a language and confirm, so that you're asked to reboot. Command in 2.) will output a lot more. Press Ctrl + C to stop waiting for more output.

You can now reboot the phone. Please send the output from 2.).

I've once again changed the display language from Dutch to English (US). This is the output of the command: https://pastebin.ubuntu.com/p/bsjsPMqRVB/

peat_psuwit

@domubpkm said in Call for testing: Ubuntu Touch Focal OTA-4:

Volla. I'm still on OTA-3, not rc. But is it normal to see this when I use a French keyboard ? Bug ? known or corrected in rc test OTA-4 ?

The keyboard in the quick settings is supposed to mean "physical keyboard", when one is connected via e.g. Bluetooth or USB-OTG cable. If there isn't one connected, the keyboard layout shouldn't show. This is a known issue to us, but for some reason didn't have an issue filed. I've filed one, so that we don't lose track of it: https://gitlab.com/ubports/development/core/packaging/ayatana-indicators/ayatana-indicator-keyboard/-/issues/7

That said, while we appreciate all issue reports, in the future, please refrain from reporting an issue which is known to happen on an earlier OTAs of Ubuntu Touch in a "call for testing" thread of the next OTA. The purpose of the "call for testing" is to catch a regression - an unexpected breakage that happens from changes in this OTA - to avoid shipping them to the end users. For a general issue reporting, please report issue at our issue inbox at https://gitlab.com/ubports/ubuntu-touch. Sorry your inconvenience.

@Sander-Klootwijk said in Call for testing: Ubuntu Touch Focal OTA-4:

@peat_psuwit said in Call for testing: Ubuntu Touch Focal OTA-4:

Sadly, I can't find any interesting information from this. If you could help, could you please get the output of command gdbus introspect --system --dest org.freedesktop.UPower --object-path /org/freedesktop/UPower/devices/DisplayDevice?

Here is the output: https://pastebin.ubuntu.com/p/BnHxXdsPRX/

Thank you for your info. The output seems to indicate that our battery software (UPower) is unable to figure this information from what your device's kernel provide. Unfortunately, debugging this issue further requires more information than we can communicate via this forum post, so please file an issue at your port's issue tracker so that your port's porter can have a look.

And for this, please help me get additional information. To avoid getting too much clutter, please follow these steps in this order:

<snip>

I've once again changed the display language from Dutch to English (US). This is the output of the command: https://pastebin.ubuntu.com/p/bsjsPMqRVB/

Meanwhile, this one reveals some interesting information. And with more information from @vince-vs, I've revealed some more information even if I can't completely reproduce the issue just yet. A quick question: are you also upgrading from Xenial or this is a clean install (or with wipe) of Focal?

That said, with the information we have, it's likely that this could have been the case since OTA-3 or earlier. As such, we will continue our investigation in the issue here: https://gitlab.com/ubports/ubuntu-touch/-/issues/2175

domubpkm

@peat_psuwit Thanks for clarifying the bug as I probably wasn't the only one in the dark.