Ubuntu Touch 24.04-2.0 call for testing

klh

@Ida_ I just reproduced this by mistake on FP4, I wonder if it has something to do with the Norwegian one because it only happened after I enabled it to check. It also has a bit different symbol layout than English.

Ok I think I can actually pretty consistently reproduce this with the Norwegian layout.

Ida_

@klh Wow! Cool that you tried. For me it seems to happen mostly on first use shortly after a reboot so far, but it did happen one time many hours after the last reboot too.

klh

@Ida_ ok, now I got it - leave it on Norwegian, lock the screen, unlock and type in your passcode - will be broken. issue link

adorsaz

I have installed 24.04-2.0 on my Fairphone 5, it works well, thanks !

I really appreciate the notch adaptation and the new Morph browser.

I've seen in the blog post the home encryption is not anymore an expiremental feature. Could/should I try the data migration with this beta release ?

For the Morph browser, when I visit the swiss train company website https://cff.ch :

the selector of rail station works well now (with morph browser qt 6 beta, the list of proposed rail station missed the white background)
the website seems to make Morph browser freeze or go out of memory, because when tab switching make every page fully reload (this was not happening with the Morph Qt 6 beta app)

PerlMax

Does the 24.04.-2.0 update already include the Mir server update (to 2.x)? If so, I'd be interested to know whether the entire screen is touch-responsive in landscape mode when using uWolf or other XWayland apps. This likely relates to this bug: https://gitlab.com/ubports/development/core/lomiri/-/merge_requests/207

Unfortunately, I can’t test it myself right now because I don’t have a device on hand to install the update on...

messayisto

@phandersson May I ask if Morph is/was working for you on the Volla Quintus in 24.02-2.x?

alagirialagiri

For the supported devices shall we switch to daily channel .I want to know the daily channel for 24.04-2.x is updated and available .Also the devices in the second list is upgraded with sufficiant space to receive 24.04-2.0 beta or daily?

adorsaz

Unfortunately my Fairphone 5 is not able to connect anymore to the phone network.

My provider is "Sunrise" in Switzerland (the product name is "yallo") and it has shutdown last year the 2G and 3G network. There's only 4G and 5G in my region.

It worked this morning when I wrote the above report but now the network status is always something like "Searching" in English ("Recherche" in my french UI).

I tried to use enable/disable airplane mode to force a new session start, but it doesn't work. I tried to reboot it doesn't work too.

On reboot it ask my pin code to unlock the network but after its state is always "Searching".

Here is the journalctl from my latest boot: journalctl_-b0.txt

gpatel-fr

@adorsaz

well, you install new version and it works. You wait half a day and it don't work anymore. It's not possible to exclude the possibility that it's unrelated.

To be sure of it, you could revert to stable to see if it fixes the problem (if you need the method see this post)

peat_psuwit

@haagch said:

Surprised to hear so few questions about this: Will the new morph support lomiri location service? The morph beta from the store does not seem to, but it did appear to support geoclue last time I tried.

The new Morph should have support for lomiri-location-service, but we forgot to include it. ️

We hope to have it fixed in the next Beta/RC.

@pparent said:

It starts but not OSK right?

I see on your logs and on the logs of @equareo that line:
qml: Application requested te be focused but no window for it. What should we do?
So I think your hypothesis might be right! Given that a patch was added in Maliit to "Verify an application has focus before granting it input", it seems possible that the XWayland windows are not detected correctly in Lomiri as giving the focus to the app and therefore block the virtual keyboard. This is only an hypothesis but seems very possible.

Hey, thank you very much for this hint!. We're working on this issue and hope to get this fixed both for 24.04-2.0 and for 24.04-1.x minor releases.

@PerlMax said:

Does the 24.04.-2.0 update already include the Mir server update (to 2.x)? If so, I'd be interested to know whether the entire screen is touch-responsive in landscape mode when using uWolf or other XWayland apps. This likely relates to this bug: https://gitlab.com/ubports/development/core/lomiri/-/merge_requests/207

Unfortunately, no. We hope to be able to do so (at least partially) in 26.04-1.0, but no promise at this time.

@alagirialagiri said:

For the supported devices shall we switch to daily channel .I want to know the daily channel for 24.04-2.x is updated and available .Also the devices in the second list is upgraded with sufficiant space to receive 24.04-2.0 beta or daily?

Not sure if I understand correctly, but:

Supported devices can also switch to Daily channel and receive 24.04-2.x daily images, which will include fixes earlier but has not been tested more widely.
Except for OnePlus Nord N10 5G, OnePlus Nord N100, and Xiaomi devices, we currently don't have timeline on when they'll be able to receive 24.04-2.x. We're still developing solution for those devices.

adorsaz

@gpatel-fr thanks for the revert command, I switched back to 24.04-1.3 stable.

My network was still in the "Searching" state. Full story of my experiments below.

As a summary it seems I faced tow issues: first the operator looks up do not work with network type "2G/3G/4G/5G", second I had to reset the access points to get back network connection.

For the last point, maybe the issue was the "MMS" access point which has been enabled automatically by the message app when I run a "send MMS" test.

If I understand correctly MMS cannot work for me as my network operator do not provides any more neither 2G nor 3G networks and so I should avoid to test them.

I think I'll install 24.04-1.2 next Sunday and report if it works when I do not try to send MMS.

On 24.04-1.3, I opened the Network Settings, the default preference for network types was "2G/3G/4G/5G".

Then I went to to "Provider and access point name", the Provider field value was "None", I opened it and the searching spinner was active less than a second and no operator appeared.

I tried in previous screen to select network type "2G only", look up again for providers, the spinner ran a longer time (like if it was actually searching), but result list was empty.

I switch back to "2G/3G/4G/5G" network type, run a lookup, the spinner ran less a second again and no success.

I tried a last time with "2G/3G/4G" network type as I know my provider provides 4G network, the spinner ran a longer time again and then it succeed with all local operators in the list.

I tried to select the "yallo" and my network state has changed to "Not authorized". Then I went to "Access point name" and used the button to "reset all settings of access point", I enabled/disable airplane mode and finally my phone connected correctly to the network.

To write this last sentence I opened again the Access Point Name list and I see know the "Sunrise Internet" is enabled and the "Sunrise MMS" is disabled. Before I click the reset button, both were enabled.

I think it's possible the "Sunrise MMS" access point was the real issue as my provider disabled 2G and 3G networks and because I think the MMS technology is linked to these older technologies.

Ok, I did a try to send a MMS and it seems the message application automatically enable this access point. Today when I had 24.04-2.0 I tried too to send MMS and so I suspect the connection has been lost a while after I ran this test.

gpatel-fr

@adorsaz said:

I tried a last time with "2G/3G/4G" network type as I know my provider provides 4G network, the spinner ran a longer time again and then it succeed

hmm, I have no real knowledge on this stuff, the only link that seemed vaguely relevant I found in a quick search was this and it says that MMS are handled in a similar way in 2G/3G/4G and are only different for 5G (NR).

At least it seems to have a relationship to your problem of losing the network when sending a MMS while connected to 5G. While protocols are standardized, small details can matter to create problems with some providers.