UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. mr_growl
    M
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 31
    • Groups 0

    mr_growl

    @mr_growl

    6
    Reputation
    3
    Profile views
    31
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    mr_growl Unfollow Follow

    Best posts made by mr_growl

    • RE: NordVPN on Ubuntu Touch

      I think I might be having a similar issue with my openvpn connect (not to nordvpn). On my nexus 5 the vpn works fine on wifi and cell service. On my nexus 7 and pinphone using the same keys, certs and settings the vpn connects fine and the routes update but I can't get to the internet. Only difference I saw was that on the nexus 5 (the working connection) the first "default via" entry was for my local router and the second was for the vpn's internal address but on the other devices they were switched around.

      The only time I've noticed the nexus 5 not working is if I set up the vpn and the let the phone go to sleep. When I start it back up sometimes I don't have internet access until I turn the vpn connection off and on again.

      I'll play around and see if I can spot what's different between them.

      posted in Support
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux Here's what /proc/cmdline says for lineage 19.1 on Bonito:

      rcupdate.rcu_expedited=1 rootwait ro init=/init androidboot.bootdevice=7c4000.sdhci androidboot.baseband=sdm androidboot.keymaster=1 msm_drm.dsi_display0=dsi_sofef00_sdc_1080p_cmd_display::timing0 androidboot.force_normal_boot=1 androidboot.serialno=99BAX0K5LP androidboot.slot_suffix=_a androidboot.slot_retry_count=0 androidboot.slot_successful=no androidboot.hardware.platform=sdm670 androidboot.hardware=bonito androidboot.revision=MP1.0 androidboot.bootloader=b4s4-0.4-8048689 androidboot.hardware.sku=G020A androidboot.hardware.radio.subtype=2 androidboot.hardware.dsds=0 androidboot.secure_boot=PRODUCTION androidboot.cdt_hwid=0x05032802 androidboot.hardware.majorid=0x03 androidboot.dtb_idx=0 androidboot.dtbo_idx=8 androidboot.bootreason=reboot androidboot.hardware.ddr=4GB,Hynix,LPDDR4X androidboot.ddr_info=Hynix androidboot.ddr_size=4GB androidboot.hardware.emmc=64GB,SKHynix androidboot.cid=00000001 androidboot.boottime=0BLE:530,1BLL:62,1BLE:446,2BLL:126,2BLE:579,SW:10020,KL:1,KD:106,ODT:117,AVB:496,AFTL:0 androidboot.ramdump=disabled androidboot.blockchain=disabled usbcfg.suzyq=disabled androidboot.hardware.pcbcfg=BPPV androidboot.hardware.devcfg=B4VP root=PARTUUID=366e8a1b-1c20-45e6-b794-df754b290cfe androidboot.verifiedbootstate=orange androidboot.aftlstate=8 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system buildvariant=userdebug console=null
      

      Is that what you were looking for?

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux And a lineage 19.1 sargo for good measure ๐Ÿ™‚

      deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system buildvariant=userdebug"
      
      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux Here's the one extracted from the lineage 19.1 signed zip that I used to flash the phone:

      deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system buildvariant=userdebug"
      

      That is lineage 19.1 (android 12.1) on bonito.

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux I tested bulding on fresh installs of ubuntu server 20.04 and 22.04. Have a look at the readme in this repo: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte

      Run the apt commands, checkout the repo and run the other 3 commands and you should end up with the.img files. I'd recommend 24GB of ram. 16 and a good swap file or 8 and a really good swap file. 60GB of disk is plenty for the OS and the builds. On the first successful build I did I only had 8gb of ram and 20gb of swap and it took ages but it built... before that it'd just keep erroring out (if you see an error 137, that's it saying you need more ram/swap).

      That repo links to two other of my repos which I made some changes in to get it building with one command.

      So to recap:

      1. set up a vm/machine with ubuntu server 22.04 or 20.04 with 24GB ram and 60gb disk (all defaults during the install
      2. follow the readme on the repo linked above.

      If you encounter any problems let me know but it should just go. Expect an hour all up to set up and run the build.

      I'll read through the articles you sent through tonight and see what I can make of it.

      Good luck!

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux I've made some progress, I think. I successfully built halium 12 for bonito and I now have the ubports recovery booting. 2025-10-20-19-34-55-804.jpg

      I flashed the system.img from the halium build, then formatted the data partition as ext4 and then sideloaded a droidian rootfs on to it but it just came back to recovery. The end of the log file is filled with messages like:

      ueventd: Cannot get SELinux label on '/dev/block/mmcblk0p29' device: No data available
      

      So I think it's time to start debugging. Will save that for another time.

      I documented the steps for building halium 12 for bonito here:
      Building-halium-12-for-bonito

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      Current state of affairs:

      New Build Method (the one here: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte)

      • Builds successfully
      • boot.img doesn't boot to anything

      What I'd like to research regarding this is:

      • has any other community port used that method to make a successful android 12 port?

      • if so, I'd want to compare their repo to mine and see what I've missed.

      • how are the binary blobs being included in this build method

      Old Build Method (the one from the video and the halium website, steps documented here: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte/-/wikis/Building-halium-12-for-bonito

      • Builds successfully

      • boots into recovery

      • very clear where the vendor blobs need to be added

      For this method I need to figure out:

      • is the fixup-mountpoints script still relevant and if so, why isn't it in the build folder anywhere

      • are there any obvious flaws with using this method over the new one?

      Droidian

      • Documentation is straight forward

      • they provide api 32 (android 12L) rootfs zips that can be side loaded

      • their deployment instructions are more like lineage (which is a good thing)

      What I'd like to find out with them is:

      • has anyone in their community done a successful halium 12 port to any device

      • why do they have a separate sargo rootfs zip?

      • will an api 28 rootfs work with halium 12 (12.1 should be api 32)

      I think my next step is to do a droidian build following their docs and see what happens. I'm presuming that the boot.img produced should also work for ubports.

      Anyways... off to work ๐Ÿ™‚

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux I've been using a pixel 3a with volte for several months on lineage with no problems.

      Android version: 15
      LineageOS version: 22.2-20250607-NIGHTLY-sargo
      Phone Version: Sargo
      Phone Carrier: Amaysim (Optus)
      Country: Australia

      posted in Google Pixel 3a/3a XL
      M
      mr_growl

    Latest posts made by mr_growl

    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @Eric-H Thank you again!

      Here's what dmesg has to say after my last flash attempt:

      [ 9780.171034] usb 1-2: new high-speed USB device number 40 using xhci_hcd
      [ 9781.164612] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
      [ 9781.164633] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [ 9781.164641] usb 1-2: Product: Pixel 3a XL
      [ 9781.164648] usb 1-2: Manufacturer: Google
      [ 9781.164654] usb 1-2: SerialNumber: XXXXXXXXX
      

      I'll wipe it again and try again with your last message in mind later. I completely forgot to check to boot debug documentation, so I'll have a read through that again as well.

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @Eric-H Thank you for the detailed instructions. I very much appreciate it.

      Here's what I did:

      1. boot into android recovery and do factory reset (to remove encryption)
      2. boot into twrp (fastboot boot twrp.img) and go into terminal
      3. unmount /data (/dev/block/mmcblk0p72)
      4. format /data as ext4 (mk2sfs -t ext4 /dev/block/mmcblk0p72)
      5. remount /data (mount /dev/block/mmcblk0p72 /data)
      6. confirm it is now mounted at ext4 (mount)
      7. push renammed rootfs.img to /data (adb push ubuntu.img /data/)
      8. reboot into bootloader from twrp
      9. boot into fastbootd (fastboot reboot fastboot)
      10. flash boot (fastboot flash boot boot.img)
      11. reboot... this takes me straight to the boot loader
      12. flash dtbo (fastboot flash dtbo dtbo.img)
      13. reboot... still goes back to boot loader

      I'm doing the formatting to ext4 bit as I read somewhere that it is required (please let me know if this was a mistake)

      I'm pushing ubuntu.img before flashing boot.img because flashing boot.img gets rid of recovery and fastbootd.

      I'm still feeling like there's a problem with my boot.img, as if I flash the boot.img from my halium build, it actually boots to recovery and fastbootd.

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      Might just go back a step and try getting a halium 9 build working, since I know that should actually work. Then maybe increment from there.

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @Eric-H I tried a build without the systempart section (the droidian porting doc said to remove it) and then tried flashing just the boot.img and rootfs.img in fastbootd mode using these commands:

      fastboot flash boot boot.img
      fastboot flash userdata rootfs.img
      

      Also tried flashing the sytem.img using

      fastboot flash system system.img
      

      But that always fails saying it can't resize the partition.

      If anyone wants to play with the boot.img, it's in the artifacts from my latest build: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte/-/jobs/11808428371

      But it doesn't seem to do anything useful.

      I'll try to get on to telegram (it's not letting me in currently). I'm just guessing on the android stuff at the moment. Trying various combinations of images and commands, re-flashing android 12 inbetween attempts.

      Thanks all for suggestions on things to try. Much appreciated.

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @Eric-H I had wondered if that was the case (about it just using what was already on the phone). Thanks for that info!

      With the stand alone kernel method, I flashed the boot.img but it would not boot into recovery. When i flashed the boot.img from the halium build it did boot the recovery, so I think I've missed something with the stand alone kernel method. I'll have another go at it, keeping in mind what you've said, and see if anything becomes apparent.

      Thanks again!

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      Current state of affairs:

      New Build Method (the one here: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte)

      • Builds successfully
      • boot.img doesn't boot to anything

      What I'd like to research regarding this is:

      • has any other community port used that method to make a successful android 12 port?

      • if so, I'd want to compare their repo to mine and see what I've missed.

      • how are the binary blobs being included in this build method

      Old Build Method (the one from the video and the halium website, steps documented here: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte/-/wikis/Building-halium-12-for-bonito

      • Builds successfully

      • boots into recovery

      • very clear where the vendor blobs need to be added

      For this method I need to figure out:

      • is the fixup-mountpoints script still relevant and if so, why isn't it in the build folder anywhere

      • are there any obvious flaws with using this method over the new one?

      Droidian

      • Documentation is straight forward

      • they provide api 32 (android 12L) rootfs zips that can be side loaded

      • their deployment instructions are more like lineage (which is a good thing)

      What I'd like to find out with them is:

      • has anyone in their community done a successful halium 12 port to any device

      • why do they have a separate sargo rootfs zip?

      • will an api 28 rootfs work with halium 12 (12.1 should be api 32)

      I think my next step is to do a droidian build following their docs and see what happens. I'm presuming that the boot.img produced should also work for ubports.

      Anyways... off to work ๐Ÿ™‚

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      I tried the halium-install script, too, with a ubports rootfs tarball but it stalled while pushing the system.img over adb (stopped at 5% and stayed there).

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux I suspect it's because I skipped the step in the documentation about setting up the fixup-mountpoints script. I could not find that script anywhere so skipped it just to try to get something booting.

      Here's the part I'm talking about:

      Include your device in fixup-mountpoints
      
      Fixup-mountpoints replaces the aliases of block device nodes in /dev/block/by-name with their literal nodes under /dev/block. This prevents issues caused by by-name not being populated by systemd.
      
      First check if the codename of your device is already included in the <BUILDDIR>/halium/hybris-boot/fixup-mountpoints script.
      
      If itโ€™s not already included, you will need to add it. Your device should be running LineageOS or another ROM where you can get root access over ADB.
      
          Find the fstab file for your device. For my Moto G5 Plus, this was fstab.qcom in device/motorola/potter/rootdir/etc
      
          Enable adb root access
      
          Create the skeleton for your device in fixup-mountpoints, right before the *):
      
          "[codename]")
              sed -i \
                  [replacements, one per line]
                  "$@"
              ;;
      
          For every line in fstab where the type is not auto, emmc or swap, run readlink -f [src] on the target device over ADB. [src] is the leftmost colum in fstab.
      
          Write all of our replacements, one for every mountpoint. Hereโ€™s the bones of one:
      
          -e 's [src] [return] ' \
      
      Replace [src] with what you input into readlink and [return] with what it returns. The space after [return] is important. The build fails without it.
      

      I don't have that in the location they mention. I found a fixup-mountpoints script in another project but I don't know that it'll actually be run if I put it in that location as that location doesn't currently exist.

      So that's what I'm investigating currently.

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux I've made some progress, I think. I successfully built halium 12 for bonito and I now have the ubports recovery booting. 2025-10-20-19-34-55-804.jpg

      I flashed the system.img from the halium build, then formatted the data partition as ext4 and then sideloaded a droidian rootfs on to it but it just came back to recovery. The end of the log file is filled with messages like:

      ueventd: Cannot get SELinux label on '/dev/block/mmcblk0p29' device: No data available
      

      So I think it's time to start debugging. Will save that for another time.

      I documented the steps for building halium 12 for bonito here:
      Building-halium-12-for-bonito

      posted in Google Pixel 3a/3a XL
      M
      mr_growl
    • RE: VoLTE Implementation For Google Pixel 3a/3a XL

      @atarilinux Also worth mentioning for your setup... in the Droidian porting guide is mentions:

      this guide assumes that you're going to cross-compile an arm64 Android kernel on an x86_64 (amd64) machine using the Android-supplied precompiled toolchain that's available in the Droidian repositories. It's trivial to disable cross-compiling and compiling using the standard Debian toolchain.
      

      which says to me that you can compile it on your arm64 machine without having to use any x86 stuff.

      posted in Google Pixel 3a/3a XL
      M
      mr_growl