@Salah you can access anything in your home folder (- or $HOME). UT does not restrict that.

@Il-Dorato said in Can't connect to WPA3 Wi-Fi networks, only WPA2 ...:

I can't figure out how to copy and paste the password into the terminal.

Long press in the terminal window and a menu should pop up, allowing you to paste text from the clipboard.

@uxes This could be an issue on devices with a smaller recovery partition, yes.

@Lakotaubp I can confirm this bybwritignthis message on my UT device in a web app!!

@Lakotaubp ADB works on my Pixel 3a too, You just have to make sure Developer Mode is toggled on. You might need to toggle it off then on again to get it to show up (no need to reboot in between).

@kristatos That the fix was merged does not necessarily mean it has already made it into the latest build. Best to wait for a few releases, or an official announcement before reporting it as still not working.

@Lakotaubp Today I installed 24.04 on my Pixel 3a. I unticked both check-boxes and went for it (so no wipe, and no install via boot-loader). So far a great experience. Most apps work (only SturmReader doesn't, so far) and the OSK shows up everywhere it is expected to, except in Morph.

So I would say it is possible to upgrade in place.

EDIT: I also installed it on my JingPad following the same procedure. With the same positive results.

@vince-vs said in OP5T removed from device list 20.04...:

because after all, isn't One of the reasons for UT to run on more phones, to avoid obsolescence and enable a more sustainable world?

That has never been one of the stated goals of this project, no. It has been among the top reasons quite a few users have adopted it, though.

@newguy Indeed, as you have noticed, the path may differ from device to device, not only between halium devices and mainline devices.

@Lakotaubp not even Morph? Then your device might be stuck on an older build.

@Lakotaubp most apps don't yet work as they need to be recompiled for 24.04

@paulcarroty Great work!

Maybe you could explicitly mention in the description that it will not work on all devices, along with the link to the readme which is already there. Some users don't make the effort to read before posting reviews...

@paulcarroty Are you on Matrix?

If so you can request a manual review to @bhdouglass:matrix.org.

Include a link to your repo in the message, including instructions on how to build the app.

@paulcarroty I see..

I will ask if there are alternative ways and get back at you.

@paulcarroty said in Resurrection of Indicator Upower:

The app has been submitted to the Open Store and should be reviewed by the Ubports maintainers (it seems):

Have you asked for manual review in the Open Store telegram group?

@Kristoffer_Umea said in Ubuntu Touch Q&A 155 Call for Questions:

@arubislander True, but UT can install Android apps due to Waydroid so I fail to see what's going to break.

For one, not all Android apps work on Waydroid. And it is not often possible to know beforehand which will and which won't work.

Waydroid is a layer if I'm not mistaken.

Not exactly, Waydroid is a container, in this it is different to WINE on the desktop. WINE is a translation layer for system calls. Waydroid is actual Lineage OS running in a container.

For your use case, this would mean having it running in the background constantly, which currently would drain your battery very quickly.

Of course you are the only person who can decide if these tradeoffs are worth it.

@Kristoffer_Umea If this is an app your health and life depends on, best to only run in on an OS that is officially supported by the app.

@blendermen You seem to be following the porting documentation. Have you also seen mentioned the Telegram group for support with Porting Questions? There are more eyeballs there to pick up and notice your questions.

@MrT10001 When you say upgrades, you mean on the PC side, right? So then re-installing the OS would not help.

@vince.vs. Could you boot up a live version of Ubuntu and see if your device is recognized in that? If so, then you know it has nothing to do with the OTA, but with an update on OpenSuse.

To avoid having this conversation on parallel threads, I will lock this one, as the OTA is live and if users experience issues they feel are due to this, opening a new thread about it is best.