VoLTE Implementation For Google Pixel 3a/3a XL
-
Hi @atarilinux
Thanks for your enthusiasm.To start, here is the porting documentation because you'll probably need to prepare the development environment to build your own image for the Pixel3a.
https://docs.ubports.com/en/latest/porting/introduction/index.html@fredldotme might find some time to give you more insights on how to proceed and the exact repository for the pixel3a.
As you see we're not connected all the time, but I try to keep up with the forum as much as I can. -
Thanks everyone! I will read over the documentation and see what I can find out. I'll be happy to help with testing and trying to learn more. Keep in mind that this will be a ground-up experience for me, but anything I can learn is better than nothing! I'm thinking other people in the US may be interested in this as well. Hopefully, I can find and connect to some community to keep learning and keep this going (as well as improving the pace of possible completion). It's a new field for me, but one I'm deeply curious about. I don't know how far I will get due to other life responsibilites, but I will try my best!
-
K Keneda referenced this topic
-
@atarilinux
I think that Alfred who maintains the port for this device mentioned something about VoLTE needs atleast Halium 10 to work. This port uses Halium 9. -
Thanks for this information! I will take a look at Halium 10. I know @AppLee said something along the lines that testing was needed. I'm not sure if this means that a port was already built on Halium 10 or not. If a port is already available, then that could expedite things. However, I will jot this down in my notes in case a Halium 10 port is not available.
-
Reading up on things, I saw this on the forum too.
"According to recent Q&A's, it has been confirmed that Pixel 3A will get Noble 24.04 but will NOT get VoLTE on Ubuntu Touch, as the kernel should be hardly patched to do so."
Just to put the pieces together, we would need the following:
- Halium 10
- New kernel (as kernal can't be patched, right?)
- VoLTE Script
Also, if I understand correctly, probably best to build against 20.04 instead of 24.04 to not throw too many variables into the mix when troubleshooting. Once everything works for 20.04, then update the port to 24.04 with the needed components.
Is that a fair assessment?
-
@atarilinux said in VoLTE Implementation For Google Pixel 3a/3a XL:
New kernel (as kernal can't be patched, right?)
With Halium ports you can't just use any newer kernel. You need to use the kernel version the corresponding Android the port s based on came with.
The existing kernel can be patched. It might just be a lot of work, depending on how big the difference is between the source of the patched and the target kernel.
-
Good to know! Thanks for this information! I think I remember reading somewhere on this forum that Google patched a kernel to allow VoLTE on the Google Pixel 3a. I might be misremembering though. Regardless, this part would need to be confirmed. So, I think we are looking at a new Halium Port + a patched kernel.
-
@atarilinux I think the patched kernel came with the newer Android version.
-
@atarilinux
I believe it would be better to use the new port based on android 12 / halium 12 instead of the one based on halium 9.
According to source code, VoLTE is already enabled on this new port.
Therefore, you just need to install Android 12 on your phone, build this new port on your desktop/laptop (or gitlab-ci), install it on your phone, and test if it works.https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a
-
Thanks everyone! This is great news! Sounds like all that is needed is testing once this is installed? If so, I'll just need to know what logs to look at and report back any information. Anything I report back will be US specific since that is where I am located.
I'm assuming the instructions on how to perform this setup are in the KB. It shouldn't be anything different than the normal way to install Ubuntu Touch on the Google Pixel 3a, right?
-
@atarilinux
i checked the files in the UBports installer, and it seems that the new port is not (yet ?) supported.
You will need to install the .img files using fastboot/fastbootD.
However, I'm not sure where you can find these .img files or if they even exist. In the worst case, you may need to rebuild them.
I also suggest asking in the Telegram group for the Pixel 3a, as they might have useful insights.
https://t.me/ubports_pixel3a -
@Eric-H You don't have to build them, they are already built: https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo/-/pipelines.
-
@ikoz
true.
The .img files seems a bit outdated.
Not sure the VoLTE/binder qti plugin was stable 8 months ago.
But yes they can be flashed and tested. -
@Eric-H There hasn't been any commit since then, if you want to re-build with a newer rootfs, without doing it on your computer, fork the repository and trigger the pipeline. I don't think it will work, if it did then the developer wouldn't say he gave up on it.
(I don't have the device myself, just explaining the procedure for anyone wanting to test the images.) -
@atarilinux hi mate, i can join you in testing the pixel 3a xl with Halium 12 for the VOLTE if you want. I am in Australia and i have just ordered the phone which should arrive in a few days.please note i am not a programming expert so should be a ground (ish) up experience for me as well.
-
@ikoz @Eric-H
Thanks for the information. I might be missing something here. Is the image ready to be tested? Does anything need to be built? Maybe we are unsure and need to get more information from the developer? Just looking at the next path to take.I have the device and can test but would probably need a step by step on how to get this image on the phone. Currently, it is running Ubuntu Touch. I have a Debian Linux laptop that can be used to assist with anything extra that may be needed in getting the image on the phone.
Secondly, once the image is installed, I would need to know what to look at to provide any error messages that may show up. Again, I appreciate all the help with this!
-
Thanks for the assist! Much appreciated! I have some programming and data experience, but not in this realm. Ubuntu Touch is new to me, but I find it fascinating. I'm currently trying to learn what I can, but I'm sure it will be a long journey. Also, I just want to thank Australia for Bluey. My daughter loves it. Hahaha
-
Hi @atarilinux
It is better to rebuild the images and it is easy.
This can be done is two step.
First step, fork the repository on gilab :- sign in/up to gitlab.com on your desktop
- go to the new port repository : https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo
- click on
forkbutton - click on
fork project(keep the public visibility)
-
Haha bluey is nice isn't it
-
@Eric-H Thanks, will sargo fork work for bonito automatically?
