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/
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/
-
@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
-
@peat_psuwit Thanks for clarifying the bug as I probably wasn't the only one in the dark.
-
Hello everybody,
I use an Xperia X Suzu, which was running fine with UT 20.04 (2023-W44), i.e. Release-Channel. I switched to Development-Channel, downloaded, and pressed "Install". Which ended in a message "Installation failed. Please reboot." Which I did, resulting in a system start. Surprisingly the "System"-section shows, that UT 20.04 (r852) is the current OS, under details the device image is shown as 20240111-31815. It seems that the update was done, despite the error message.
As far as I can see, all apps work, in particular the Morph browser. Camera, ADB and change of PIN works, too, as well as WLAN and BT. Currently I do not use phone calls in this device, so no testing in that respect.
I returned to the release-channel, installed the previous version, which worked and showed the earlier entries under system information. Then I started the update a second time with the a.m. result.
Hope this helps. Thanks for your ongoing work!
Stefan -
Update: the new RC has been pushed, with regression fixes for apps that embed web browser and for Xperia X. Please have another go at RC. Thank you.
-
@peat_psuwit said in Call for testing: Ubuntu Touch Focal OTA-4:
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.
I will do that!
A quick question: are you also upgrading from Xenial or this is a clean install (or with wipe) of Focal?
This is a clean install, with wipe, of Focal. If I remember correctly I did switch between stable, developer and RC channels since I used the installer, but it has not been updated directly from Xenial.
-
Thanks for this. I got the update. I still have the WiFi bug that I have been experiencing in my Xperia X with the OTA-3. Here's the link for reference. What happens here is that when I connect to WiFi, I would immediately get the prompt connected while the WiFi icon won't be fully coloured white. It would just show the 3 dots in it. After around 2 minutes, it would ask me to enter the password again. It has been like this since OTA-3 but I choose not to go back to Xenial because of the night-and-day performance. It would be nice to get some workaround to this. I didn't have this bug when I forced OTA-2 on mine, even though it wasn't supported yet at that time. Cheers.
-
First batch of tests on a OnePlus 6T. (I will test some of the other issues identified in this thread later)
The ability to use ADB with the phone (we've added restored prompt system).
Yes, that works. Pops up "Allow USB Debugging?" as advertised.
If your ringtone settings are still effective across updates.
Yes, same as before.
Whether the permission request works for a new app
Prompts for permission on a new app that wants access to restricted parts of the system (e.g. Battery Saver app), but not for new apps that don't (e.g. Guess Words)
If you can still change your PIN and/or passphrase in the System Settings:
Changing Passcode (PIN) works fine. Passphrase not tested.
Browse your everyday websites with Morph
Browser: Seems fine.
For Waydroid users, see if Waydroid still works for you.
Seems OK.
-
@lduboeuf How is it set? I can't find it in System Settings
-
@ancientsounds said in Call for testing: Ubuntu Touch Focal OTA-4:
@lduboeuf How is it set? I can't find it in System Settings
Talking about the DT2W ? If it is not visible under "Gesture", then your device does not support DT2W
-
@lduboeuf OK thank you. It's a OnePlus 6T, and I can't see such a setting under Gestures, so presumably this phone does [EDIT: not] support it
-
@peat_psuwit
More tests on OnePlus 6T:lock screen now shows the estimated time to charge your phone:
No, it doesn't. Toggled the checkbox in setting, but that makes no difference
Theme switching now built-in
"Enable dark mode" in system settings works without having to reboot.
For developers: connecting your phone to new a computer now asks for confirmation
Yes, that works
bug fixes:
messaging-app · start in landscape: compose bar not shown
https://gitlab.com/ubports/development/core/messaging-app/-/issues/340This is fine on OP6T (but perhaps it was not a bug before?)
-
@Sander-Klootwijk said in Call for testing: Ubuntu Touch Focal OTA-4:
- 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 tried to reproduce this by switching to French. Some of the text remains in English even though a lot of it has changed to French. E.g.
"No text messages sent today" on the splash screen circle,
In system settings, "Flight Mode", "Rotation Lock", "Background & Appearance", and "Reset" are in English (the rest in French). Some of the app names remain in English although others are in French. (Perhaps this is down to the individual app's coding) -
@ancientsounds
The issue that is being reported here is not when switching from English to another language. This could simply be due to untranslated strings.The issue mentioned is when switching from another language back to English, where some strings remain translated to the non-English language.
-
@arubislander Ah, I see. In that case, I can report that switching back to English from French did not give rise to that problem on the OP6T
-
Redmi Note 7
Things that work :
- ringtone settings are still effective
- the permission request works for a new app
- Browse your everyday websites with Morph Browser
Things that don't work :
- send/receive mms
- video recorder
- flash light
- sometimes swipe from right don't work
-
@dioginfo said in Call for testing: Ubuntu Touch Focal OTA-4:
Things that don't work :
- send/receive mms
- video recorder
- flash light
- sometimes swipe from right don't work
May I know whether these issues happen on the earlier OTAs as well, or are something which break when switching to the RC channel?
-
@peat_psuwit
Hello,
For flash light @dioginfo is he talking about the photo flash or the notification led ?
If it's for the notification led, I've already explained the problem several times:
and so it only works once after dev. or rc or stable update. After a second reboot of the device ( OnePlus5T ) it doesn't work anymore.For video recorder: on my OPT5, sometimes the recording has no sound.
Interface translations not complete, home screen and settings ...If it's not possible to solve this in ota-4, it would be a plus for the next ota ... ( if we show a UT to someone, it will be more convincing )
Thanks -
@lduboeuf Small point of detail: it is not possible to import a personalized ringtone for a contact if the name of a personal file is written in several separate words. With just one word, the mechanism works well. Thanks for the feature.
-
@peat_psuwit
MMS reception was OK before switching to RC, as well as flash light and swipe from the right, I also have the issue with mixed language@vince-vs
I am talking about the photo flash
