VoLTE Implementation For Google Pixel 3a/3a XL

atarilinux

Furthermore, Lineage OS has a recent build that should incorporate the retro-fitted super partition changes for the Google Pixel 3a. See below the github page.

https://github.com/orgs/LineageOS/repositories?q=android_device_&type=all&language=&sort=

ikoz

@atarilinux All modern UT devices already work with the super partition. I don't understand what you mean by "implementing" it, the only thing UT has to do is mount them, which is already done.

atarilinux

@ikoz

@fredldotme mentioned having an issue with the retro-fitted super partition for the Google Pixel 3a build on a QA call. He stated that we will need to figure that part out to get it working. When the Google Pixel 3a Android 12-based Ubuntu Touch port was trying to be built, we get the following error messages below, which refernces the partitions. If this has already been worked out on other Ubuntu Touch ports can the fix be applied to this one, or is this a different issue entirely? Any insight is recommended! Thanks!

cp: cannot stat 'partitions/': No such file or directory
System image: Applying update: halium_halium_arm64.tar.xz
cp: cannot stat 'partitions/': No such file or directory
System image: Applying update: device_sargo.tar.xz
System image: Applying update: version.tar.xz
cp: cannot stat 'partitions/*': No such file or directory
losetup: /dev/loop0: detach failed: No such device or address

ikoz

@atarilinux The cp error is normal and happens on all builds, the actual problem is the last one. From my understanding based on an older discussion in the porting telegram group, the retrofitted partition is used for older devices which didn't have the new super partition. However, it shouldn't be impossible to get it working, as others got their device booting, mounting the android partitions is necessary only for getting the android container running.

Anyways, more experienced people are active on the telegram group, so you may want to ask them.

atarilinux

@ikoz

Yes, that is correct. The retro-fitted partition is what the Google Pixel 3a uses. Thanks for helping with reading the error! I'll see what I can find out on this. If you know of anyone who may have some insight, can you let them know this is something we are looking to get resolved?

As we understand it, VoLTE works with a more recent version of Android. We are hoping to make this possible for the Google Pixel 3a on Ubuntu Touch as well. It has been confirmed that other alternative OS's already have VoLTE implemented for the Google Pixel 3a, so I think we have some resources we can potentially pull from if we need to. I'm not entirely sure what is being discussed on Telegram or if people may already be looking this.

mr_growl

@atarilinux No prob. So you know, I've just ordered a Pixel 3a XL for playing around on so if you'd like any specific versions of lineage tested for VoLTE, let me know. I gather that testing with a version based on 12.1 is the one you're most interested in?

atarilinux

@mr_growl

Thanks so much! Yes, that is correct! We are currently looking at Android 12.1 for two reasons:

The unfinished Ubuntu Touch port is based around this version.
This version is supposed to have the VoLTE patch included.

The current struggle seems to be with the retro-fitted super partition, but it seems like this has already been worked out with other Ubuntu Touch ports. If we can get whatever worked for them applied to this port, we may be able to get this working if I understand the recent comments correctly. We may have other issues down the line, but that looks like the first thing we need to address.

atarilinux

Just an added note on trying to troubleshoot the loop error:

Error:
losetup: /dev/loop0: detach failed: No such device or address

Note:
"Loop devices are provided by a kernel module. Therefore, you need special privileges to access them. You also need them to be exposed into your container, or you need to manually create the device files."

I'm not sure if something may have changed between Android 9 and Android 12.1 for this. We would need to investigate this error in addition to the retro-fitted super partition issue.

Eric H

@atarilinux
I see same errors (cp and losesetup) in other ports.
For example:

here's an example of flashing devel images on a device with a super partition :
https://gitlab.com/EricHeintzmann/ubuntu-touch/xiaomi-surya/-/wikis/fastboot-flash

About fastbootd :
https://source.android.com/docs/core/architecture/bootloader/fastbootd

atarilinux

@Eric-H

Thanks! I do see these same errors from the logs of the other device ports you sent me...so maybe that isn't the problem mentioned in the QA call? Also, thanks for the fastbootd link!

Quick question... for any of these devices you sent, are we looking at a retro-fitted partition? The reason why I ask is that I'm trying to match some of this up to the issue presented on the QA call. That way we can see if this part can be resolved.

Eric H

@atarilinux
AFAIK, these devices use a super partition, but not a retro-fitted one.
But, I don't think the build system is aware of the partition type.