Hi @messayisto

VoWifi is usual phone calls but you connect to your carrier via the wifi and internet connection instead of the cell towers around you.
On the other en of the line it can be a cell tower or whatever.

As stated by Marius is a previous Q&A it happened to work out of the box by enabling VoLTE, but it has not been tested too much and could vary depending on the device. I think Marius tested it with the Fairphone5.

As for audio call apps, there is maybe one instance of telegram that is working but I haven't tested it in a while.

Hi @messayisto
Thanks for your interest and suggestion.
Currently the OS development work is being discussed mostly on Telegram:
https://t.me/ubports_devel

@ChromiumOS-Guy I think also that the one shown by Moem is the one that fits Ubuntu Touch's design the best.
For reference:
https://docs.ubports.com/en/latest/humanguide/design-concepts/app-icon-design.html

Hello @messayisto

It might have been a mix-up on my side.
I had a test version for Noble that worked.
I installed the new release and apparently it doesn't open files.

So I guess the fixes were published for Focal and maybe another version will be required for Noble.

Hi @darshpreets

I cannot be sure about your specific device.
But phones are usually only able to be either an access point or a client, but rarely both.

As for Ubuntu Touch being able to handle this case on such compatible hardware, I'm not sure.
That would be something to test.

Hi @Simmonz

Have you reached out to Volla?
They are working with local carriers in Canada to support their devices

Hi @MrT10001
And my answer was also not a snarky one.
One might want to buy it preinstalled with Ubuntu Touch, so Volla will make a donation to the foundation.
Then switch to android if Ubuntu Touch doesn't meet their expectations yet.

@MrT10001 said in Volla Phone Quintus: How to Disable the Security Warning on Volla Quintus after flashing Volla OS?:

why did you buy it with UT to then install Volla OS?

To help contribute to the UBports foundation.
And it's highly appreciated. Thanks @Pandolin

Hi @atarilinux
Thanks for your enthusiasm.

To start, here is the porting documentation because you'll probably need to prepare the development environment to build your own image for the Pixel3a.
https://docs.ubports.com/en/latest/porting/introduction/index.html

@fredldotme might find some time to give you more insights on how to proceed and the exact repository for the pixel3a.
As you see we're not connected all the time, but I try to keep up with the forum as much as I can.

@kristatos said in 20.04 Focal: uNav freezes with GPS enabled:

And for me, that was the case under Xenial.

On Focal it navigation works fine with Pure Maps, I tested it earlier this year.
But since I'm testing Noble, I don't use Focal so much...

Hi @lduboeuf

Not sure what the problem is, there might be several...
I noticed some freezes, but I can overcome them and I managed to have to location updated while walking.
When freeze occurs it's often after making a search or new navigation or this kind of operation.
Edit: to be thorough only uNav freezes.

I don't remember exactly but I think I make my search before asking to locate me.
Basically there is an order that work ; search the location, then start the navigation, then location activation.

I'm using a FP5 on Noble and Pure Maps doesn't work on Noble yet.

Hi @atarilinux

Thanks for this message.
The testing required is technical.
I'm sure @fredldotme can (and is willing to) point you in the right direction to test things out.

Of course to embark on this journey, you'll need to have another daily driver as it will require to be on the devel channel.
Also it'll require to check various logs on the device to investigate the possible bugs and try to find a suitable solution.

It's not development per se IIUC, but more integration, so building the big picture, understanding how different component rely on each other and interact.
And some times when fixing issues or propose MR on those components.

If what I described is difficult to understand, maybe you can try to find people with the required skills around you. But if you understood but are not sure you can do it, I would encourage you to give it a go and see where it lands...

Hi @gdegrez

The Volla Tablet is available with Ubuntu Touch working on it.
I'm currently at the Volla Community days and I will test a couple of apps if I can.

There is a lack of tablets compatible with Ubuntu Touch, but what you're saying about running desktop apps on Ubuntu Touch is changing ; with a keyboard and mouse/touchpad apps available for ARM should run on Ubuntu Touch and with the compatibility with snaps it brings a lot of apps to try out.

Of course we cannot guaranty full compatibility, but it might work...

Also the best way to have something is not just raise an issue in a forum, you can create a real issue (feature request) on Gitlab and sponsor developers or raise founds to get the feature you want.
This is a community, which means the effort is also shared across our community members.
Sitting idle is not being part of a community (and to be clear I don't say that you are, I'm just encouraging everyone to contribute)

@Ian I agree.
100 percent

@Ian
The only way to access the external keyboard layout is from the drop down menu.
What you can find in the settings is the ine for the OSK.

A better UX is being discussed and the current leading idea would be to have the drop down menu available only if an external keyboard is connected.

@developerbayman said in Setup a shared folder between UT and Waydroid:

Does Ubuntu touch have a "autostart” feature?....if it already does not exist that could be a clickable....auto start clickable apps or run scripts.....surly someone did this already?

Not sure what you put behind "autostart feature", but Ubuntu Touch uses systemd to start services at boot time.

@Eric-H said in Device recommendation for VoLTE support:

@wally
Regarding VoLTE on the Pixel 3a, this is a new port under Android 12 that was developed to enable this feature.
However, I am not aware of the current status of this port, nor whether the effort will continue or has been abandoned.

Alfred was clear that he cannot test this out.
So consider it abandoned, but if anyone is willing to push this further, he'll be able to assist, so it's open for contribution.

Hi @AnhVu

You had the correct setting and Vietnamese is very well missing.
They got confused with the settings for external keyboards that support most existing layouts.

The On Screen Keyboard (OSK) needs a bit of work to deisgn the keys ans actual layout of the keys.
You were on the right track with the lomiri-keyboard-<language> list that you shared.

Hi @HarryBass

That's not what OP was asking for.
This setting is for external keyboards, they are looking for the OSK which is more limited in options.

Hi @mschmids

As @Moem said, this is not the best place to talk about this.
But Signal is updating from time to time and the bridge as well ; that would explain the change you noticed.
Xenial is not supported anymore, the app you're using as well, and your device as well so unless you manage to update, similar things will continue happening like we notice with Morph browser.
We try to keep legacy as long as possible, but it depends on people and their personal investment in time.
Sadly you're on your own.