Ubuntu Touch 24.04-2.0 call for testing

PhAndersson

Just tried to upgrade the Quintus to 24.04-2.0. As recommended, I switched to the 'release candidate' channel and checked for updates. It downloaded an image identified as "version 15", which I installed. The robot character announced the install and the phone rebooted without issue, but Settings still shows it as 24.04-1.3, still on the RC channel (24.04-1.x/arm64/android9plus/rc), but with no further update waiting.

Have I missed anything?

gpatel-fr

@PhAndersson

then run the following command in Terminal app or via ADB/SSH:

gsettings set io.ubuntu-touch.system-settings.update offer-development-release true

paulcarroty

@PhAndersson to be 100% sure which version/channel is going to be flashed, go to https://system-image.ubports.com/24.04-2.x/ and check the latest manually.

P.S. Battery life isn't good on the 2.x daily, -30% last night.

Ida_

A bug has shown up for me. FP5, 2.0 Beta.

A collegue called me this morning, and didn't get any sign of life from my phone. I had no missed calls on my phone. Confirmed that it was still not working with a different phone number, despite the reception triangle being filled and the L being there. I'm on a VoLTE only network. I was able to receive calls again after a reboot.

PhAndersson

@gpatel-fr said:

@PhAndersson

then run the following command in Terminal app or via ADB/SSH:

Of course -- right under my nose. Sorry for the silly question.

Running 24.04-2.0 beta now.

Thanks much.

PhAndersson

First feedback regarding Morph:

general web surfing works OK (news sites, etc.)
searching through Google works OK
creating bookmarks works OK
viewing the bookmarks: OK
opening link in new tab: OK
showing open tabs and closing some of them: OK

I also tried accessing a personal web application on my local net that uses Apache Basic Authentication method:

Morph shows the login dialog, but it disappears as soon as you tap the username field
navigating to the password field is not obvious
once authentication is complete, the web app interface displays, but only part of it (disclaimer: its home page uses frames and the app was never designed to be accessed from a mobile)
also, it seems it re-prompts for credentials in order to display the 2nd frame, instead of re-using the already provided ones

Something else I know was problematic with Morph on Focal was handling captive portals for WiFi authentication (a rather typical setup in hotels these days). This I couldn't test with 24.04-2.0 beta.

PhAndersson

Bluetooth on the Quintus is still problematic as far as connecting to a laptop is concerned. The behaviour is still the same as the one described here: Noble bluetooth issues.

peat_psuwit

@Keneda said:

@peat_psuwit
Could you give a link for known and for reporting issues on this RC please ?

This issue board shows issues known to affect Ubuntu Touch 24.04-2.0:

https://gitlab.com/groups/ubports/development/-/boards/9687679

Although, we have to admit that not all issues are recorded here; we have been pretty lousy regarding to issue tracking. We hope to improve this in the future.

@gpatel-fr said:

@Vlad-Nirky

I have seen already another post about things being messed up in landscape and staying messed up when back to portrait - something I definitely don't see on my FP5, where the landscape mode is not perfect but when switching back to portrait all is well.

I think I see the difference now: your phone has no notch for the back camera. It's probably the root cause. The MR has been tested for a phone like the FP5, not like your phone.

The problem with notch avoidance being broken after rotations is a known issue and will be fixed in the next Beta/RC.

@rduivenvoorde said:

Non related to this: should a phone work in a car using Bluetooth? It see it connects as a headset, so I can talk/hear. But I does not present a phone or contacts to the car?

The Bluetooth integration with the phone/contacts system is indeed a known issue. We're still working on it, but there are a few moving parts related to this which makes implementing this a bit complicated.

@paulcarroty said:

X00TD works fine.

$ df -h /dev/mmcblk0p13  
Filesystem                     Size  Used Avail Use% Mounted on
/dev/disk/by-partlabel/system  3.9G  3.4G  524M  87% /

Thank you for your report. X00TD (Asus Zenfone Max Pro M1) will receive the next Beta/RC.

PhAndersson

I can also confirm that the RTC issue is still present on the Quintus. Just created the following issue about it: [Bug] Volla Quintus: RTC problem: correct time/date not preserved across power cycles.

uxes

Not sure if already reported issue, but.

After taking the screenshot, the screenshot editor is shown, where I can edit or share the image. However, this window is higher (like z-index) than the volume-control popup, and I assume it’s the same for notifications too. So when I change the volume while I’m on this screenshot editor screen, I can’t see the current volume status.