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
    138 Posts 14 Posters 18.2k 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.
      • 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 Online
              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
                • A Offline
                  atarilinux
                  last edited by

                  @mr_growl

                  That's great news! Keep us posted how everything goes! Fingers crossed everything works correctly!

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

                    Did first attempt at flashing. This is on pixel 3a XL:

                    1. flash last stock firmware (android 12.1)
                    2. install twrp
                    3. boot into twrp and open terminal
                    4. umount /dev/block/dm-4 (which was mounted to /data and /sdcard)
                    5. mke2fs -t ext4 /dev/block/dm-4
                    6. mount /dev/block/dm-4 /data
                    7. mount /dev/block/dm-4/sdcard
                    8. boot into bootloader
                    9. flasboot flash boot boot.img
                    10. attempt to reboot into recovery

                    At this point the device wouldn't boot into recovery. So I'm flashing twrp back on to it.

                    Any thoughts?

                    Here's the repo I'm using: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte
                    I'm building in a ubuntu server 20.04 vm. I modified the deviceinfo from atarilinux's version slightly which got it building properly for me.

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

                      While I was re-flashing twrp a thought occurred. With TWRP on the pixel 3a (compared to the nexus 5 and 4 which I used to use) I have to boot it using "fastboot boot twrp.img" and then use the "flash current twrp" option (taken from the lineage install instructions)... on the older phones it was "fastboot flash recovery twrp.img". Which makes me think this twrp might be writing to the same place as boot.img when I do the "fastboot flash boot boot.img". Any thoughts on that?

                      1 Reply Last reply Reply Quote 0
                      • ikozI Offline
                        ikoz @mr_growl
                        last edited by ikoz

                        @mr_growl Why don't you formtat through the built it in option in TWRP or even better via fastboot: fastboot format:ext4 userdata? (the partition name may differ)

                        Also, when the block device shows up as dm-something it is encrypted.

                        May the source be with you

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

                          @ikoz Thanks! I'll give that a go (I'm still new to a lot of this).

                          I was thinking it was encrypted. Seems to me that encryption is on by default in android 12 / lineage 19.1 and there isn't an option to disable it in the interface. Not sure what to do from this point.

                          ikozI 1 Reply Last reply Reply Quote 0
                          • ikozI Offline
                            ikoz @mr_growl
                            last edited by

                            @mr_growl If you disable requiring password to login (just swipe to unlock), it will also disable encryption.

                            But just running the fastboot command will work (if it throws any error, it likely means your fastboot build is broken and you'll have to use the official one from Google).

                            May the source be with you

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

                              @mr_growl

                              I might be off here, but did you use fastbootd? The Google Pixel 3a has retrofitted dynamic partitons in Android 12.1.

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

                              Info on Retrofitted Dynamic Partitions:
                              https://lucaweiss.eu/post/2023-03-30-retrofit-dynamic-partition/

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