UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    VoLTE Implementation For Google Pixel 3a/3a XL

    Scheduled Pinned Locked Moved Google Pixel 3a/3a XL
    volte
    131 Posts 14 Posters 17.6k Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • M Offline
        mr_growl @atarilinux
        last edited by

        @atarilinux I haven't done much with gitlab but have experience with github runners. I'll try to get something going this weekend. I gather the error in your last build is due to not running as the root user. Maybe try putting a "sudo" in front of the apt commands in .gitlab-ci.yml ?

        A 1 Reply Last reply Reply Quote 0
        • Eric HE Offline
          Eric H @atarilinux
          last edited by

          @atarilinux
          unsure but maybe systempart=/dev/mapper/system is missing in cmdline

          from porting Telgram Group :

          system.img and rootfs.img are the same thing from a fastboot POV. your userdata should be freshly formatted as ext4, but yes that's what the bottom of the doc also explains, which one you need and how to flash it depends on if you included e.g. systempart=/dev/mapper/system on cmdline for devices with super partition

          also unsure about other fields

          • Ubuntu Touch for Xiaomi POCO X3 NFC Telegram group
          • Ubuntu Touch installation guide for Xiaomi POCO X3 NFC / X3
          A 1 Reply Last reply Reply Quote 0
          • Eric HE Offline
            Eric H @atarilinux
            last edited by

            @atarilinux
            it seem this this file should be updated too :
            https://gitlab.com/atarilinux/ubports-ubuntu-touch-google-sargo-volte/-/blob/main/.gitlab-ci.yml

            • Ubuntu Touch for Xiaomi POCO X3 NFC Telegram group
            • Ubuntu Touch installation guide for Xiaomi POCO X3 NFC / X3
            A 1 Reply Last reply Reply Quote 1
            • A Offline
              atarilinux @mr_growl
              last edited by atarilinux

              @mr_growl

              That's what I'm thinking too. When I looked at it again today, it looked like permission was denied because it wasn't running as sudo. I was using the runner on my local machine. I noticed it didn't prompt me for my password which was interesting. So, yes, we probably need to add sudo to the file.

              1 Reply Last reply Reply Quote 0
              • A Offline
                atarilinux @Eric H
                last edited by

                @Eric-H

                Thanks for the info! Just to verify, should work for a retro-fitted partition too, right? I'll check this out in the file and see if I can find anything else that may need to be added.

                Eric HE 1 Reply Last reply Reply Quote 0
                • A Offline
                  atarilinux @Eric H
                  last edited by

                  @Eric-H

                  Thanks! I was looking at that one when I was messing with the runner. Good to know we are on the right track with thinking something was going on with that part!

                  1 Reply Last reply Reply Quote 0
                  • Eric HE Offline
                    Eric H @atarilinux
                    last edited by

                    @atarilinux
                    https://lucaweiss.eu/post/2023-03-30-retrofit-dynamic-partition/

                    • Ubuntu Touch for Xiaomi POCO X3 NFC Telegram group
                    • Ubuntu Touch installation guide for Xiaomi POCO X3 NFC / X3
                    A 1 Reply Last reply Reply Quote 1
                    • A Offline
                      atarilinux @Eric H
                      last edited by

                      @Eric-H

                      Thanks! This is a great post! Very helpful!

                      1 Reply Last reply Reply Quote 0
                      • A Offline
                        atarilinux
                        last edited by

                        I added Sudo to the Apt statements in .gitlab-ci.yml. I also added systempart=/dev/mapper/system to the deviceinfo file.

                        For this part,
                        https://lucaweiss.eu/post/2023-03-30-retrofit-dynamic-partition/

                        I'm trying to figure out where to add this on github. The code on github is referencing a number of other githubs by "clone." I'm trying to untangle it to get a since of what happens when and where. I want to make sure I'm not missing anything.

                        1 Reply Last reply Reply Quote 0
                        • J Offline
                          JayH @atarilinux
                          last edited by

                          @atarilinux said in VoLTE Implementation For Google Pixel 3a/3a XL:

                          @Eric-H

                          What you have stated above is correct to the best of my knowledge. Here is the other part from the QA call:

                          *Source Material - Not Image
                          *Information on image build process, but not how to install it
                          *Built on top of latest Android 12.1 version for the Google Pixel 3a, but build not completed

                          So....it looks like we need to:

                          1. Finish the build (This part is the least specific. Finish what? This is the main issue due to it not being specific. Maybe it is only the retro-fitted partition issue? A lot of data may need to be checked to see what is complete. Here is the bottleneck in completing development.)
                            ...snip...

                          I think this, at the very least, is what you're running into. For one thing, the LLVMgold library isn't referenced correctly by the build system. I was able to correct that but my make skills are simplistic and old and rusty. Am currently looking at a problem with the device tree.

                          A 1 Reply Last reply Reply Quote 0
                          • A Offline
                            atarilinux @JayH
                            last edited by

                            @JayH

                            Yes, that is where I am stuck. I need to know what exactly is missing to complete the build. It's my first port, and I'm new to this. The port does reference other code via clone statements, so I have to look at that too. There are no comments that I am finding that tells me what does what. It will take me a while to figure out what each thing does and what goes where and when. I'm comparing other ports and reading some documentation, but it will be slow going on my own unfortunately.

                            1 Reply Last reply Reply Quote 0
                            • M Offline
                              mr_growl
                              last edited by

                              Don't suppose anyone has the vendor blobs for android 12.1/lineage 19.1 extracted already? I'm trying a build myself and it's at the point where it wants them but I've been struggling a bit to extract them from the payload image I have. Checked the muppet but they don't have 19.1 .

                              A J 2 Replies Last reply Reply Quote 0
                              • A Offline
                                atarilinux @mr_growl
                                last edited by

                                @mr_growl

                                Sounds like a good idea! Keep us posted how the build goes and if you need anything! I did find this online during my research. Would this help?

                                https://github.com/propgsp/Android-Tools

                                1 Reply Last reply Reply Quote 0
                                • J Offline
                                  JayH @mr_growl
                                  last edited by

                                  @mr_growl I would think since the vendor blobs are device specific that they wouldn't change from OS-to-OS ??

                                  M 1 Reply Last reply Reply Quote 0
                                  • M Offline
                                    mr_growl @JayH
                                    last edited by

                                    @JayH I was presuming they'd be specific to the kernel they were built for. But I'm new to that πŸ™‚

                                    @atarilinux Thanks for the link. I'll give those a try next time I'm working at it (been too busy lately)

                                    A 1 Reply Last reply Reply Quote 0
                                    • A Offline
                                      atarilinux @mr_growl
                                      last edited by

                                      @mr_growl

                                      I completely understand. It has been hectic this way too. I hope I can get some more time to look at this soon! I hope what I sent can be of some use.

                                      1 Reply Last reply Reply Quote 0
                                      • A Offline
                                        atarilinux
                                        last edited by

                                        @JayH @mr_growl

                                        I also found this UBPorts video from 6 years ago. It shows how to build a port. Some things probably have changed a bit since then, but it should assist in providing a visual for the Porting Documentation.

                                        https://m.youtube.com/watch?v=nShXVDXM50A

                                        1 Reply Last reply Reply Quote 2
                                        • M Offline
                                          mr_growl
                                          last edited by mr_growl

                                          I had a go with doing a build this weekend and it seems to have built something (I have a boot.img, rootfs.img and system.img).

                                          So now trying to sort out the phone to get it ready to try flashing. I checked my /data partition and it is mounted from dm-4 and is not ext4 (instructions say /data should not be encrypted and should be ext4). So just trying to sort that out. Any advice on setting up the partitions in preparation to flash would be appreciated πŸ™‚

                                          arubislanderA 1 Reply Last reply Reply Quote 0
                                          • arubislanderA Offline
                                            arubislander @mr_growl
                                            last edited by

                                            @mr_growl As I understand it, just that /data should be ext4. There is no need for repartitioning if the correct stock ROM was installed beforehand.

                                            πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                                            Happily running Ubuntu Touch
                                            JingPad (24.04-1.x daily)
                                            OnePlus Nord N10 5G (24.04-2.x daily)
                                            PinePhone OG (20.04)
                                            Meizu Pro 5 (16.04 DEV)
                                            Google Pixel 3a

                                            M 1 Reply Last reply Reply Quote 0
                                            • M Offline
                                              mr_growl @arubislander
                                              last edited by

                                              @arubislander Thanks! I flashed android 12.1 to it, so I'll just try reformatting that partition as ext4.

                                              1 Reply Last reply Reply Quote 0
                                              • First post
                                                Last post