3G is turned off on all US carriers. VoLTE (4G) does not work for calls or messaging. You won't be able to receive MMS, only SMS. Your phone should function on 2G. This requires a setting change in Ubuntu Touch where you turn off 4G support. Data should work on 4G, but not calling or MMS. Data will be slow on 2G, but you can make/receive calls with lower quality sound and some delays. You can also receive SMS text. Ubuntu Touch currently does not support VoLTE (4G) or higher for the Google Pixel 3a. Similarly, your carrier may or may not allow your Google Pixel 3a on the network. You will need to check with your carrier. If the carrier accepts your phone, only expect 2G calling and SMS. Calling and SMS may have some delays. 3G service is not available in the US. If you need faster data and are not expecting calls, switch to the 4G setting in Ubuntu Touch. I've tested the Google Pixel 3a in the US with a 5G SIM card.

@Futura If it doesn't work with Lineage OS, I think one of the following is probably happening: The VoLTE patch for the Google Pixel 3a might not be in the Android image. Lineage OS might not be picking it up. Lineage OS supports VoLTE, but not VoLTE roaming. I read somewhere that the VoLTE patch only allows VoLTE roaming on the Google Pixel 3a. The roaming setting might not be turned on in the Lineage OS settings. The carrier doesn't support VoLTE roaming. The carrier dropped support for the Google Pixel 3a. I completely understand on the device switching and focusing on the Fairphone 5. No issues or worries there! I'm also on the market for a new phone as I'm certain this device is on borrowed time. I'm still looking to get a Fairphone 5 if I can. However, any progress made on the Google Pixel 3a would be good I think as it seems a number of users were using this phone in the US. So, until I can get a new phone, I'm going to be seeing what I can do with this one. Enjoy the Fairphone 5! I heard it is great with Ubuntu Touch on it!

@PhAndersson Hello, it happens to me now, and it also happened with previous OTAs, that the phone uses only the earpiece instead of the speaker for ringing, so the ringtone is silent. It was not possible to set it up, but restarting the device helps. I have a feeling that this happens after connecting the speaker via Bluetooth (hands-free in the car).

@arubislander Good thought. Perhaps I should have mentioned that I use Tor (or a public computer) because this site forwards user data to Cloudflare. I believe that live a session won't prevent fingerprinting/canvassing, regarding my accessing this site; and and not help regarding the problem of 'missing files' in the Google bonito file. Any more ideas?

@thedeafenguy From what I know about anti rollback protection, you can downgrade or upgrade without problem if you don't relock bootloader.

@zpeedmaster The easiest way to downgrade the Pixel 3a is to use the Android recovery tool in the chrome browser (not Chromium). Choose factory image PQ3B.190801.002 (the required ROM) from here. Then use the pixel repair tool in Chrome following the onscreen instructions. Check this thread out: Return phone to latest Android 9 (the steps below refer to the Android Flash Tool -- using the flash-all.sh script also works fine but starts with the phone booted into the bootloader) check that 'adb' is not running (otherwise, stop it with 'adb kill-server') turn phone on the usual way redo basic setup, as bootloader unlock returned it to factory default (see above) reconnect to phone using 'adb devices' to get prompt to authorized PC and allow it visit following URL in Chrome (authorise pop-ups in browser): https://flash.android.com/ select device select target build (PQ3B.190801.002) DO NOT select to relock bootloader click Install Build (confirm, accept license) DO NOT interact with device during flashing it reboots to fastboot reselect device in Chrome flash successful -- power cycle device reboot to Android 9, redo initial setup, enable dev. mode, USB debug, connect and allow PC, turn phone off

Ok, that's clear

Hmm. @thebroison are you SURE it's a Pixel 3 and not 3a? You say UT is running normally on this phone?

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

@OtaDr Thank you for sharing the link, however, I do not watch youtube. I appreciate your effort in trying to help me. It simply looks like UT is not an OS designed for my needs.

@uwahl Ok thanks for this information :). It's good to know that the test_gps utility is not reliable. Unfortunatly for me all the apps (Pure Maps, uNav, SensorsStatus, Gps Toolkit) don't give me any fix. I hope someone can bring me a solution

Fairphone 5 with Orange in Spain works well with Volte.

@fredldotme In case anyone still has important videos recorded with Pixel 3A + OTA23 (as I did), kept in case some solution to repair them is found, my script that fixes those videos is here: https://forums.ubports.com/topic/10971/fixing-corrupted-videos-recorded-with-google-pixel-3a-ubports-ota23

Hello I can confirm ( I use airplane mode to redirect calls to another phone number ) After setting the mode the airplane switches after 1 or several rings ( i.e. it does not switch immediately after setting the airplane ... but after some activity )

@Abba Actually Miracast works quite well on the Pixel 3a now. But it is hit or miss if it will work with any particular Smart TV or dongle. If you are looking to buy a dongle, then as mentioned before the Microsoft one is the best bet. Otherwise Sony and Samsung smart TV's also seem to consistently work.

Many thanks to all those who responded, first of all. Based on the initial comment by @wally, I made some further tests yesterday night. Indeed, the car kit has a button/function to import the contacts from the phone, but it fails to import anything. Its message is that maybe I need to authorize the sharing on the phone. I also tried to export all contacts to vCard on the phone (successfully), then to browse to that file in file manager, then shift-left and click on the sharing icon, but that only listed "Messages" and "Dekko" as potential targets. New import attempts from the car kit ended up with the same error message. So I guess that this "sharing" icon is where a "BT File Transfer" app would need to register itself. For the record, this is how I used to send contact info to the car kit from my Nokia N900, using a BT transfer app called "Petrovich'.

@PhAndersson Congrats and welcome!

@OtaDr said in Calendar problem: Calendar problem originally did not sync . So I tried uninstalling and reinstalling Unfortunately, it can no longer be installed. Now tested with OTA-8 Not sure if it is the right group ro ask. But i also had that kind of issue. iirc i had to remove the Account, reboot, recreate one,

@thekosmix The hardware doesn't support. There's DisplayLink but it's a proprietary tech that needs a special adapter and it doesn't work in UT.