Wow! Latest ubports newsletter has a hint that VoLTE and 5G may be coming to FP5:

"...by way of a sort of happy accident 5g should be available first, and has been tested on FP5 and 4..."

Looking good!

Thanks, I've signed up! Now just have to be patient for any news on FP5

@CatWithUT good find ! And where do I sign up to these newsletters?

I'm very eager to hear further news on this too!

@beyolf Thanks, looking forward to it!

Hi!

Long time user of Ubuntu Touch and UBPorts. Firstly, thanks so much for all of your efforts; it's incredible what you've been able to accomplish.

Now to the questions - my existing pixel3a is sadly showing signs of dying and I'm looking into getting a newer device. There were rumours Marius was eyeing off a Fairphone 5 - is there any news on that front? I should read posts better - this probably skirts too close to a question on a device being ported, sorry!

Also, sorry to sound like a broken record as I know this comes up frequently, but what's the latest on VoLTE, and dare I say it, 5G?

Thanks heaps!

Hi,

This will become a problem in Australia soon too (and might already be an issue for some carriers here). The largest provider here, Telstra, is planning to switch off their 3G network in June 2024.

I'm not sure what the status is of a crowdfunding effort, but I would also donate, at least a small amount for VoLTE support.

Merry Christmas / Happy holidays!

Hi,

Thanks all for the comments and suggestions they were a great help.

I've only just ended up moving to Focal on my Pixel 3a, about 30 minutes ago.

Please don't take any of the the following as a criticism - I am happy on UBPorts and it's on my daily driver, but in case it helps anyone considering the upgrade this was my experience:

• Selecting the 20.04 Stable channel somehow went wrong, and it downloaded and installed 16.04 Development (!?) without me realising until it had installed
• Attempting to select the 20.04 Stable channel was an issue - it seemed to switch randomly to other channels (!?). Eventually it "stuck" on the 20.04 Stable, and I could see that the Ubports update it was downloading was labelled as 'Update 3' or 'Version 3' or some such which gave me some hope.
• Install of 20.04 worked, and it rebooted into 20.04 fine. Had to re-select language and location. It also began the introductory tutorial again.
• Noticed the UI scaling had changed and become larger (more on this later)
• Keyboard theme had reset, UI theme had reset to the standard white theme (more on this later)
• Essential applications still appear to open and work, for me these are:
  • Axolotl
  • Quickddit
  • Google Mail
  • Authenticator NG
  • Messaging/Phone (actually untested, because it's late here, but they open)
• Camera app has started working again - this had failed in 16.04 for me. I knew this was software related and not hardware as the 'Tagger' app would work with the camera.
• OpenStore is misbehaving - it doesn't appear to update applications properly, and they disappear from the app drawer after I try, but after a reboot the updated applications re-appear and also seem to have updated okay. OpenStore continues to misbehave.
• Two terminal apps show up. One was non-functional. It was easy to uninstall the old one through OpenStore.
• Investigating scaling / theme change... and I need UT Tweak Tool which isn't available in OpenStore for Focal!
  • Existing UT Tweak Tool install doesn't work (not surprised at all about that, but thought it worth pointing out for others)

Now I realise why domubpkm in an earlier comment wanted UT Tweak Tool available for Focal. I installed UT Tweak Tool ages ago on Xenial and forgot about it. Turns out I must have had the scaling turned down and a custom dark theme installed and just didn't remember. Now I'll have to live with the larger UI elements and white theme in Focal. I'll live

All in all, pretty good - I have the essentials and can work around the odd behaviours. I might consider re-installing OpenStore as per it's about page, but wasn't sure if there are potential downsides.

Hi,

I am still running Xenial on my pixel3a.

I am thinking of upgrading to Focal, however this is my daily driver so I've been a bit cautious.

First I just want to make sure that the stability is fairly good on Focal and there's no degradation in network connectivity as I obviously need the device to function at least as good as it does now.

Next, I use some apps that don't have Focal versions such as quickddit. Will these continue to work after upgrading?

Cheers

Hi,

I've tried multiple times installing/re-installing waydroid on a pixel3a.
I've used the waydroid helper & I've used the command line method from this thread:
https://forums.ubports.com/topic/6764/anbox-halium-or-waydroid-no-support-for-ut/11

Both had the same issues.

The issues I'm hitting:

First I have issues with the 'waydroid session start'. Logs show that it fails on the lxc-network setup as it says device waydroid0 does not exist.

I tracked down the creation of this bridge device into this script:
/usr/lib/waydroid/data/scripts/waydroid-net.sh

I've found that the waydroid0 device is being created, but dnsmasq won't see it for some reason.
I changed the line in the 'start' function to remove the '--interface' parameter to dnsmasq as a workaround and it seemed to at least get past the network issue.

             --except-interface=lo --interface=${LXC_BRIDGE} \

to:

             --except-interface=lo \

However, even after doing that, and re-starting the waydroid container and sesion I then get the following error:

root@ubuntu-phablet:~# waydroid container start
[21:49:33] NOTE: The failed command's output is above the ^^^ line in the log file: /var/lib/waydroid/waydroid.log
[21:49:33] ERROR: Command failed: % umount /var/lib/waydroid/rootfs/vendor/lib/egl
[21:49:33] See also: <https://github.com/waydroid>
Run 'waydroid log' for details.

waydroid log shows:

root@ubuntu-phablet:~# waydroid log
(011333) [21:49:33] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(011333) [21:49:33] NOTE: The failed command's output is above the ^^^ line in the log file: /var/lib/waydroid/waydroid.log
(011333) [21:49:33] ERROR: Command failed: % umount /var/lib/waydroid/rootfs/vendor/lib/egl
(011333) [21:49:33] See also: <https://github.com/waydroid>
(011313) [21:49:33] % umount /var/lib/waydroid/rootfs/vendor
(011333) [21:49:33] Traceback (most recent call last):
  File "/usr/lib/waydroid/tools/__init__.py", line 69, in main
    actions.container_manager.start(args)
  File "/usr/lib/waydroid/tools/actions/container_manager.py", line 132, in start
    helpers.images.mount_rootfs(args, cfg["waydroid"]["images_path"])
  File "/usr/lib/waydroid/tools/helpers/images.py", line 91, in mount_rootfs
    tools.config.defaults["rootfs"], umount=True)
  File "/usr/lib/waydroid/tools/helpers/mount.py", line 118, in mount
    umount_all(args, destination)
  File "/usr/lib/waydroid/tools/helpers/mount.py", line 106, in umount_all
    tools.helpers.run.user(args, ["umount", mountpoint])
  File "/usr/lib/waydroid/tools/helpers/run.py", line 59, in user
    output_return, check, sudo)
  File "/usr/lib/waydroid/tools/helpers/run_core.py", line 343, in core
    check_return_code(args, code, log_message)
  File "/usr/lib/waydroid/tools/helpers/run_core.py", line 219, in check_return_code
    raise RuntimeError("Command failed: " + log_message)
RuntimeError: Command failed: % umount /var/lib/waydroid/rootfs/vendor/lib/egl

(011313) [21:49:33] % umount /var/lib/waydroid/rootfs/odm_extra
(011313) [21:49:33] % umount /var/lib/waydroid/rootfs
(011313) [21:49:33] % mount /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(011313) [21:49:33] % mount -o remount,ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(011313) [21:49:33] % mount /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(011313) [21:49:33] % mount -o remount,ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(011313) [21:49:33] % mount -o bind /vendor/lib/egl /var/lib/waydroid/rootfs/vendor/lib/egl
(011313) [21:49:33] % mount -o bind /vendor/lib64/egl /var/lib/waydroid/rootfs/vendor/lib64/egl
(011313) [21:49:33] % mount -o bind /vendor/odm /var/lib/waydroid/rootfs/odm_extra
(011313) [21:49:33] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(011313) [21:49:34] % start cgroup-lite
start: Job is already running: cgroup-lite
(011313) [21:49:34] % umount -l /sys/fs/cgroup/schedtune
umount: /sys/fs/cgroup/schedtune: mountpoint not found
(011313) [21:49:34] % stop nfcd
stop: Unknown instance: 
(011313) [21:49:34] % chmod 777 -R /dev/ashmem
(011313) [21:49:34] % chmod 777 -R /dev/dri
(011313) [21:49:34] % chmod 777 -R /dev/ion
(011313) [21:49:34] % chmod 777 -R /dev/video
(011313) [21:49:34] % chmod 777 -R /dev/video3
(011313) [21:49:34] % chmod 777 -R /dev/video2
(011313) [21:49:34] % chmod 777 -R /dev/video1
(011313) [21:49:34] % chmod 777 -R /dev/video33
(011313) [21:49:34] % chmod 777 -R /dev/video32
(011313) [21:49:34] % chmod 777 -R /dev/video0
(011313) [21:49:34] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(011313) [21:49:34] New background process: pid=11516, output=background
lxc-start: utils.c: safe_mount: 1653 Not a directory - Failed to mount /dev/video onto /usr/lib/aarch64-linux-gnu/lxc/dev/video
lxc-start: utils.c: open_without_symlink: 1584 Too many levels of symbolic links - vibrator in /usr/lib/aarch64-linux-gnu/lxc/sys/class/leds/vibrator was a symbolic link!
(011313) [21:49:34] Save session config: /var/lib/waydroid/session.cfg
(011313) [21:49:34] Failed to add service waydroidhardware: -1
(011338) [21:49:34] Failed to start Clipboard manager service, check logs
(011338) [21:49:34] Failed to add service waydroidusermonitor: -1
(011607) [21:49:39] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(011607) [21:49:39] *** output passed to waydroid stdout, not to this log ***

edit: the hosts /dev/video contains two devices:

root@ubuntu-phablet:~# ls -l /dev/video
total 0
lrwxrwxrwx 1 root root 10 May 27  1971 venus_dec -> ../video32
lrwxrwxrwx 1 root root 10 May 27  1971 venus_enc -> ../video33

Any help would be appreciated.

Thanks

Hi,

I've been a long time Ubuntu Touch user, having moved to the platform back when the (official Canonical) Meizu MX4 came out.

My old phone has finally started to have battery issues, and my wife wanted an upgrade from her Xperia X. She's now moved on to another device and I decided to see how well the Xperia X port worked.

I'm blown away.

It's working great, albeit with some (very minor) issues. So firstly I wanted to say thank you for your hard work on this. It's very much appreciated.

I thought I'd mention the issues I have in case it helps:

1. Camera occasionally fails (black screen for rear camera) and won't work until a reboot.
2. On first reboot when rear camera works again, it only partially displays an image. Top half of image is solid green, although the bottom half displays fine. At some point this fixes itself - I haven't figured out why yet.
3. Rebooting is a bit odd - when I try to reboot first time after running the device for a while, it just restarts Lomiri rather than restarting the whole device. If I then select reboot again, it reboots properly.
4. UBPorts OTA updates are a bit strange - when doing an update, it seems to go OK, but will always take me to the UBPorts Recovery on reboot giving the impression something went wrong with the update. If I then just select to reboot the device, it all works fine.

I also have a question. On installing (via the UBports installer) I had the option of selecting the 'fredldotme' channel or the 'edge' channel. I selected 'fredldotme' as I was aware this was the handle of the person who ported it to suzu in the first place. Was this the best option? Also, I've noticed I must be on a bleeding dev channel as I get very frequent OTAs (just installed '409', and '410' is already available).

I want to use this device as a daily driver, so I'd like to understand how these releases are made and whether it's fairly safe for me to be applying these often? Will suzu ever be available in a stable channel? Also, is there a changelog for these OTAs? I noticed '409' was hundreds of MB, whereas '410' just came through in only ~1MB so I figure these are deltas and wonder just how much changed in '409'?

Sorry for all the questions