@Simmonz
I had the same problem.
I have export the pc keepassxc password to a csv
Install keepass from openstore.
Import the csv and it works, both on Focal and Noble.

@sap
Very good question.
Perhaps our hosts could answer this with a small concrete example by publishing a “Hello UT world” application for Noble.

@messayisto
It works very well

@nogoogle
Bad news...
Maybe you'll have to return to Android and test to be sure the hardware has no issue.

@nogoogle
Hello.
Were you using the correct version of Android before installing UT?
Have you tried installing Waydroid and then the satStat app on it?
Just to make sure the problem is with the software or the hardware?

Thanks a lot.
The installation went without a hitch.
The camera works much better than in 20.04.
voLTE is still fully functional on my Redmi Note 9 Pro in Belgium with Orange.
There's still the known problem that prevents Bluetooth pairing with the car.
As for the rest, I'm happy to adopt it, the OS is superb!

@Futura
Have you tried restarting the wifi router or changing the network?
I've had my phone not connect to wifi in the past and that was the problem.

Another test I did tonight.
The GPS on UT was disabled 60 km from here.
Waydroid satStat shows the correct position.
I launched GPS Toolkit on UT.
I enabled the GPS.
It found the correct position in less than two seconds.
Perhaps it depends on the device.
Mine is Redmi Note 9 Pro running Focal

Next try, during the dog walk, i have kept UT GPS off (UNav can't determine the location) and follow my postion on the satStat map. It has been precisely updated.
So waydroid can use the phone GPS even if UT says it's off.
Is UT GPS switch off only a logical switch that prevents app to use it?
This could explain a part of battery consumption.
Is the satStat app in waydroid access hardware directly and use it as if it was on Android?

@wgarcia
No... All unchecked.
And, more strange, in UT GPS is off and in waydroid in two seconds it locates me at the right place.
In UT, uNav says waiting for GPS and GPS toolkit says noFix.
Really confusing.
Any chance that satStat could access directly to hardware???

Sorry for my belgian cow english...

@wgarcia
Maybe the wifi is only the path to access datas (satellite ephemeris), so it could work through the bridge.
My tests seem to show a significant improvement in connection time.
But it's hard to be certain (there could be persistence or caches).

@wgarcia
Thanks again.
Interresting too.
I guess the first time aGPS uses WIFI or mobile data to get informations from internet.

1. Traditional (standalone) GPS:
   A GPS receiver (such as in a smartphone) picks up signals from at least four satellites to triangulate its position. This can take anywhere from a few seconds to a few minutes, especially during a cold start, because it must:

Download the ephemeris (the exact position of each satellite)

Estimate its approximate position

2. With aGPS:
   aGPS improves this process by downloading this data via the network, instead of waiting for it to arrive slowly from the satellites.

It can use:

The cellular network (GSM antennas)

An Internet connection (Wi-Fi, mobile data)

aGPS provides:

The approximate position of the phone (via the antenna)

The exact time

Satellite ephemeris via dedicated servers

@wgarcia
Thank you very much for the test.
Sorry for going off-topic.
Interesting...
I can't explain this difference between the hosted system (Waydroid) and my host system (UT).
In my french system i have this menu.

@wgarcia
If you are using waydroid, could you make this test. (as you report very long time to fix gps postion)
Disable GPS (and move somewhere else).
Launch waydroid.
Run (after install) satStat.Settings reload AGPS.
Enable GPS.
Look at the connection time in waydroid and in UT.

@wally
If the device is running Android 10, no need to downgrade it.
Maybe, you could push it to the last Android 10 version (Miui 12)
You'll have to unlock bootloader in any way.
You can follow this doc:
https://forums.ubports.com/topic/9957/installation-guide-redmi-note-9s

@RJDan
For KeePassXC
Icon appears after Lomiri restart.
The app is launched without any problem but, on my Redmi Note 9 Pro, the screen is really to small to be usable. ( I don't know if the screen size can be modified )
The snap don't seems to have access to the /home/phablet/Documents where i put the kdbx file.

@UBportsNews
Hello.
Still happy thanks to Ubuntu Touch.
I've done a few snap tests.
For KeePassXC, I couldn't get it to work:
keepassxc
ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
qt.qpa.plugin: Could not find the Qt platform plugin "ubuntumirclient" in ""
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
The Wayland connection broke. Did the Wayland compositor die?

I just wanted to highlight an interesting post, I think, from the forum that suggests listing applications that work well under UT:
https://forums.ubports.com/topic/11143/snaps-tested

A huge thank you to all those who contribute to the life of UT!!!!

@josh
Otherwise, it make sense on the first UT install to check the three checkboxes (wipe, partionning and bootstrap)

Hello all.

To test snap possibilities,
I installed the latest Focal development build on my phone.
I then installed SnapzOr and launched the application.
Finally, I installed keepassxc with the command
sudo snap install keepassxc
Had keepassxc 2.7.9 from Jonathan White (keepassxreboot) installed
When I run keepassxc, I get the following error
[phablet @ ubuntu-phablet - 22:45:44 ] ~

keepassxc
ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
qt.qpa.plugin: Could not find the Qt platform plugin "ubuntumirclient" in ""
library "eglSubDriverAndroid.so" not found
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
The Wayland connection broke. Did the Wayland compositor die?

Is there something missing or the snap is incompatible?