@dwray85 Are you sure that you flashed the Bonito Android image instead of Sargo? I had a similar issue when installing UT on my Pixel 3A and I mixed up the Android images.

I'm running Focal OTA-2 on a Pixel 3A and experience the issue that UT apps like uNav and Puremaps do not show the current GPS location as soon as I start Waydroid. Inside the waydroid container the GPS signal is still available, as mentioned in my other post.
Stopping the waydroid container does not solve the issue, but a reboot does.
Can this be solved or should i report it as a bug?

@arubislander The fix is accurate. Google maps navigation is providing correct location, when driving on the freeway with no nearby wifi networks.

Does Android inside Waydroid have access to the GPS sensor even when the location detection in UT is set to 'off'?
I noticed Google Maps was able to get a fix, even when I turned off location detection. It was at a highway outside of town, therefore I don't think the fix was a result of Google Location services

I reinstalled Android, the SIM card still did not work properly. I was able to read the correct provider name in the phone settings. I tried different SIM cards from different operators, all had the same issue. I could read the operator correctly, but no cellular connection did not work.
Than GPS also started to show issues, in the first weeks I was able to get and hold a fix. But now the first fix was ok, but after a couple of minutes the GPS stopped working.
I opened the device, because previous owner said it got a new battery. half of the screw were missing. I needed my phone for work and had no time for further investigation.
In the end I bought a new Pixel 3a and am installing UT at the moment.

I just flashed to stock android and the issue persists. I assume a hardware failure

@lduboeuf I changed to devel just before posting this, but it doesn't fix the issue
@arubislander I've tried both rebooting and complete shutdown followed by manually initiated booting, it doesn't fix the issue

I've been using Focal for three weeks. Today, after a reboot, the cellular connection is not established anymore. Instead of displaying my provider name, now it displays 'unknown'. If I remove my sim card, it says 'no sim'
The reason for the reboot was the unability to start Morph, tapping the icon did not result in starting the app. After reboot, Morph works again, but the cellular connection is gone. Rebooting doesn't solve the issue. The SIM card is good, as it still works OK in my Nexus 4.
I noticed some different messages in the ofono logs. What should i do to fix this issue?

Ofono log when SIM unknown is displayed:

May 14 13:12:29 ubuntu-phablet systemd[1]: Starting oFono Mobile telephony stack...
May 14 13:12:29 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: oFono version 1.29
May 14 13:12:29 ubuntu-phablet ofonod[3521]: oFono version 1.29
May 14 13:12:29 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: Initializing RIL binder transport plugin.
May 14 13:12:29 ubuntu-phablet ofonod[3521]: Initializing RIL binder transport plugin.
May 14 13:12:29 ubuntu-phablet systemd[1]: Started oFono Mobile telephony stack.
May 14 13:12:29 ubuntu-phablet ofonod[3521]: parse_devices_reply: found 1st battery device: /org/freedesktop/UPower/devices/battery_battery
May 14 13:12:29 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: parse_devices_reply: found 1st battery device: /org/freedesktop/UPower/dev>
May 14 13:12:29 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: slot1 version 102
May 14 13:12:29 ubuntu-phablet ofonod[3521]: slot1 version 102
May 14 13:12:29 ubuntu-phablet ofonod[3521]: ../../../gobject/gsignal.c:2618: signal 'DisplayPowerStateChange' is invalid for instance '0x55e>
May 14 13:12:29 ubuntu-phablet ofonod[3521]: SIM card OK
May 14 13:12:29 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: SIM card OK
May 14 13:12:29 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: Requested file structure differs from SIM: 6fb7
May 14 13:12:29 ubuntu-phablet ofonod[3521]: Requested file structure differs from SIM: 6fb7
May 14 13:12:51 ubuntu-phablet ofonod[3521]: Power request failed: INTERNAL_ERR
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: Power request failed: INTERNAL_ERR
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: failed to set rat mode
May 14 13:12:51 ubuntu-phablet ofonod[3521]: failed to set rat mode
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: SMS History Probe for modem: 0x55e47502f0
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: Registered interface org.ofono.NetworkTime, path /ril_0
May 14 13:12:51 ubuntu-phablet ofonod[3521]: SMS History Probe for modem: 0x55e47502f0
May 14 13:12:51 ubuntu-phablet ofonod[3521]: Registered interface org.ofono.NetworkTime, path /ril_0
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: data reg changed 0 -> -1 (), attached 0
May 14 13:12:51 ubuntu-phablet ofonod[3521]: data reg changed 0 -> -1 (), attached 0
May 14 13:12:51 ubuntu-phablet ofonod[3521]: nw selection is already auto
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: nw selection is already auto
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: Requested file structure differs from SIM: 6fb7
May 14 13:12:51 ubuntu-phablet ofonod[3521]: Requested file structure differs from SIM: 6fb7
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: Unable to read mailbox identifies from SIM
May 14 13:12:51 ubuntu-phablet ofonod[3521]: Unable to read mailbox identifies from SIM
May 14 13:12:51 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: Setting Cell Broadcast topics failed
May 14 13:12:51 ubuntu-phablet ofonod[3521]: Setting Cell Broadcast topics failed
May 14 13:14:06 ubuntu-phablet ofonod-wrapper[3521]: ofonod[3521]: Power request failed: INTERNAL_ERR
May 14 13:14:06 ubuntu-phablet ofonod[3521]: Power request failed: INTERNAL_ERR

Ofono log last successful cellular connection:

-- Reboot --
May 13 22:11:19 ubuntu-phablet ofonod[1266]: ../../../gobject/gsignal.c:2618: signal 'DisplayPowerStateChange' is invalid for instance '0x5612bf0160' of type 'ComCanonicalUnityScreenProxy'
May 13 22:11:19 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: parse_devices_reply: found 1st battery device: /org/freedesktop/UPower/devices/battery_battery
May 13 22:11:19 ubuntu-phablet ofonod[1266]: parse_devices_reply: found 1st battery device: /org/freedesktop/UPower/devices/battery_battery
May 13 22:11:20 ubuntu-phablet ofonod[1266]: slot1 version 102
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: slot1 version 102
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: SIM card OK
May 13 22:11:20 ubuntu-phablet ofonod[1266]: SIM card OK
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: Requested file structure differs from SIM: 6fb7
May 13 22:11:20 ubuntu-phablet ofonod[1266]: Requested file structure differs from SIM: 6fb7
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: SMS History Probe for modem: 0x5612c1b850
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: Registered interface org.ofono.NetworkTime, path /ril_0
May 13 22:11:20 ubuntu-phablet ofonod[1266]: SMS History Probe for modem: 0x5612c1b850
May 13 22:11:20 ubuntu-phablet ofonod[1266]: Registered interface org.ofono.NetworkTime, path /ril_0
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: data reg changed 0 -> 2 (searching), attached 0
May 13 22:11:20 ubuntu-phablet ofonod[1266]: data reg changed 0 -> 2 (searching), attached 0
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: nw selection is already auto
May 13 22:11:20 ubuntu-phablet ofonod[1266]: nw selection is already auto
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: Requested file structure differs from SIM: 6fb7
May 13 22:11:20 ubuntu-phablet ofonod[1266]: Requested file structure differs from SIM: 6fb7
May 13 22:11:20 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: Unable to read mailbox identifies from SIM
May 13 22:11:20 ubuntu-phablet ofonod[1266]: Unable to read mailbox identifies from SIM
May 13 22:11:21 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: data reg changed 2 -> 0 (unregistered), attached 0
May 13 22:11:21 ubuntu-phablet ofonod[1266]: data reg changed 2 -> 0 (unregistered), attached 0
May 13 22:11:22 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: data reg changed 0 -> 2 (searching), attached 1
May 13 22:11:22 ubuntu-phablet ofonod[1266]: data reg changed 0 -> 2 (searching), attached 1
May 13 22:11:22 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: data reg changed 2 -> 5 (roaming), attached 1
May 13 22:11:22 ubuntu-phablet ofonod[1266]: data reg changed 2 -> 5 (roaming), attached 1
May 13 22:11:22 ubuntu-phablet ofonod-wrapper[1266]: ofonod[1266]: Activating context: 1
May 13 22:11:22 ubuntu-phablet ofonod[1266]: Activating context: 1

I'm running Focal on a Pixel 3a with a bumper cover. The cover makes it difficult to perform edge swipes. This post indicates that it can be solved by adjusting the edge size with UT tweak tool, but the tool is not available for Focal in the OpenStore yet. Is there an option to change the edge size manually?

I have been using this method, Wifi hotspot and Nexus4,
to enable a hotspot on my Nexus 4 with OTA-15 an -16.
However, after upgrading to OTA-17, other devices can connect to my hotspot, but there is no data transfer.
Connected android devices report "connected, no internet" Any thoughts how to fix it?

After reading this article, I was wondering what is or can be done to protect devices running UT from this vulnerability. As far as my knowledge goes, UT uses an android kernel, which uses device specific and mainly closed source hardware drivers. The white paper says that the vulnerability can be mitigated through software or firmware updates, but older devices don't get firmware updates anymore.
My question is whether UT users will stay vulnerable to Kr00K as long as there is no firmware update available or can it be solved through software and is it just a matter of capacity and priority?

Basically the same question applies to Spectre, Meltdown and other bugs where the source is in the hardware.

Is there an alternative available for the Microsoft Authenticator app in Ubuntu Touch Stable?
The Authenticator NG app from the Openstore does not recognize the QR code that is supposed to be used to register the MS Authenticator. If trying to manually set up the account, I have to enter a nine digit activation and a phonefactor URL. I can only control the client side of the connection, my guess is that the server side uses Azure AD.

@tera Thanks, that solved the issue

If I open an SSH session from the terminal app to my Ubuntu server, this process appears to be paused after switching from other apps back to the terminal app. I'm able to resume the SSH session with command fg %1, but after resuming the terminal acts differently. That means commands are echoed after pressing enter, but before executing them and arrow keys result in control characters (^[[A for arrow up, ^[[C for arrow right etc) being printed to the terminal.
This behaviour seems to be more an SSH issue, than an UT issue. Because the same happens if i send SIGSTOP to SSH sessions from laptop to server or laptop to UT.
The display behaviour is similar to this and this issue, but I checked in my case the shell is always bash and $TERM doesn't change before and after the pausing of SSH.
Is it possible to either prevent the SSH session being paused during app switching or to fix the terminal behaviour after resuming the paused session?

It's possible to mount SMB/CIFS shares from the command line.
First you need to install the cifs-utils package, which requires remounting root to make it writeable. Than the network share can be mounted with:

mount -t cifs -o sec=ntlmssp,username=user,password=pass,iocharset=utf8,vers=1.0,rw //servershare ~/'directory to mount to'

I recently reported a bug for a Nexus 4 running OS build number 2018-W48. The same behavior is also present on a Nexus 5 running OS build OTA-5. Should I add this information to the existing report or is it better to file a new report?