OK, so it looks like I will be keeping the SIM in the Pixel 3a XL which is still on android.

@Ian Can you still call 333 and get through to get a voice call of your balance, I can on my old Meizu pro 5. I can't even get a signal on my Pixel 3a XL.

@Enrico13011978 from a website about 2G 3G switch off in the UK
Vodafone completed its switch-off in early 2024.
EE completed its switch-off in early 2024..
Three expects to switch-off by the end of 2024.
O2 is planning to switch-off in 2025.

But I thought that to get and make calls having a 4G phone was sufficient.

Ironically Three sent a text to say that they have sorted the issue and of course I could not get it on my UBPorts Pixel 3a XL if it was not fixed.
I did get the text on my old Meizu pro 5 because I had the SIM in that one.
My UBPorts Pixel 3a XL is still not getting a signal. When I try and get a carrier in mobile settings it is not able to, it just keeps coming up with none.

Just had an issue with my mobile connection on my Pixel 3a XL. The signal had been a bit flaky the last few days, dropping off intermittently. I had a chat with my supplier Three UK and they concluded that I needed a VoLTE calling feature compatible phone now.
The thing is that I swapped the SIM into my old Meizu pro 5 and it worked fine.
I also have a spare Pixel 3a XL to use as a backup but have not installed UBPorts on it and the sim works fine in Android.

Do you think that it is a hardware issue with the Pixel 3a XL with UBports on it, or something else.
I was thinking of getting a Vodafone UK SIM and testing that to see if it is an issue with the provider, is that worth trying?

Installer done, now on OTA-4. Had some issues and thought I broke it as the UBports Recovery screen disappeared after the first attempt but that might be normal? New UBports Recovery screen installed the next time.

@MrT10001 Thanks, I will try the installer.

Hi, I just upgraded my Google Pixel 3a XL to whatever was available to be upgraded today (I am sure that I was in the stable channel). The UBports Recovery screen came up after rebooting and I selected Reboot but I just got the google screen and could not get any further. The UBports Recovery screen shows Halium 9 and Slot b at the bottom.
I see an option for Factory reset but would rather not do that unless that would be necessary.
I see the device being recognised in Kubuntu when I plug it in.
Should I try the UBports installer?

@arubislander Thanks, I tried my old Microsoft cable and it connected great.
Time to set up Libertine now...

OK, I am thinking about convergence now. I was using a specific usb to hdmi cable on my Nexus 4 and a Microsoft WiFi monitor cable on my Meizu Pro 5.
What options do I have on the Pixel 3a XL?

channel 20.04 stable.
Seems to be working OK.
I don't use the phone much but I can make and receive calls on my pay as you go Three UK sim fine.
One of the reasons for doing this was to be able to hear incoming calls better, it could just be me, or maybe the caller that I could hardly make out, but it seems loud enough in testing.

And I got my custom ringtones and notification audio clips installed without faffing about with copying files which I had to do originally, so that is better now.

NextDayMobiles did deliver the next day.
So I have it and have done the install already.
I had a problem connecting the device before flashing and that was down to not knowing that I had to set the USB preferences to file transfer. :man_shrugging:
I had to use fastboot flashing unlock to unlock the bootloader.
I could not get the online Android flash tool to work at all after I had managed to set the device to developer mode and unlocked the bootloader.
So I just ran the ./flash-all.sh provided with the Android 9 image.
I used the app image of the UBPorts installer.
I had a little trouble getting the UBPorts installer to recognise the device but it worked after closing it and re-opening it.

Looking forwards to using it in earnest.
What's the best next steps?

I am having issues with my trusty old Meizu Pro 5 and decided to get something that supports halium and waydroid so I chose a Google Pixel 3a XL.
I managed to get a good deal on one from Amazon UK with a 20% off offer they have at the moment, to be delivered by NextDayMobiles in the next couple of days (so much for their name ).

I will probably be on the forum a lot more trying to get this one set up so, thanks in advance for the help that I am sure to get here.

@Yuri to transfer files you can use the WifiTransfer app from the OpenStore. You can also set up SSH.

Well done, my MX4 is still stuck on Canonical Ubuntu Touch. I will have to have a go with antix linux.

@andybleaden I ran sudo alsamixer and noted that the headphones were set to mute (MM) also but unmute did not bring the headphone up on the PineTab.
re-"Uart/Headphone switch (next to SC Card slot)"
So, that was what I thought was the SD card write protect switch?
The headphones started working after switching that back upwards.
This trick works on the PinePhone too.
Plugging in the headphones does not mute the speakers though and you have to mute the line out to mute the speakers in alsamixer to do that.

Got a couple of Kingston Canvas Select Plus microSD Card SDCS2/64 GB SP Class 10 to test with.
Worked fine and formatted OK on the PinePhone.
The PineTab booted OK with it in and recognised it but would not format it. I got "There was an error while formatting the device.
I noticed a small switch next to the SD slot so i changed the position - switched it down towards the bottom of the tablet and rebooted. It still booted OK and formatted the device.
Did I just find the SD card write protect switch?

Rotation not working, but I am stuck on landscape.

Bluetooth still not working on PineTab on dev...

The PineTab had UBPorts Ubuntu Touch installed and no updates were available on the stable channel.
The device connected to wifi no trouble.
Morph Browser works OK to access the web - Youtube videos played but the sound was a bit disappointing.
No sound through headphones and Bluetooth headphones not connecting.
Updating to dev now...

Checking my bluetooth headhones on my PinePhone on dev shows that they are working. I will switch to the dev channel. And
I see that the PinePhone is just getting an update on dev too.