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

    Google Pixel 3a (sargo)

    Scheduled Pinned Locked Moved Google Pixel 3a/3a XL
    106 Posts 17 Posters 44.7k Views 6 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.
      • E Offline
        Etn
        last edited by

        Hi, im new here hello to everyone, i just flashed on my sargo from the UB installer beta 0.7.2 on windows, and im happy to say that everything is working well for now, no problem with sms sync and cellular data at the moment, the only thing is that mms not working but maybe its my apn settings.
        iam happy to try it very good works thanks.

        E 1 Reply Last reply Reply Quote 0
        • E Offline
          Etn @Etn
          last edited by

          @Etn i can confirm now that mms work send and receive

          1 Reply Last reply Reply Quote 0
          • fredldotmeF Offline
            fredldotme @Louie
            last edited by fredldotme

            @Louie Could you please try the following:

            • Download https://drive.google.com/file/d/1T_00cBUyWrB3V-QLFxWPbmguYQ-gEdOn/view?usp=sharing
            • Copy the file to the Downloads folder on your phone
            • Open a terminal with adb shell
            • Run:
            sudo mount -o remount,rw /
            sudo cp /home/phablet/Downloads/libgbinder.so.1.0.47 /usr/lib/libgbinder.so.1.0.37
            sudo reboot
            

            Also interesting for you, please try to replicate the change here:
            https://gitlab.com/ubports/core/rootfs-builder-debos/-/merge_requests/18/diffs

            In case you don't know how to do this:

            sudo mount -o remount,rw /
            sudo nano /etc/init/ofono.override
            

            Remove the provision, from the file and save (Ctrl+o and enter, then Ctrl+x to exit) and sudo reboot for good measure.

            Please make sure to try the combinations separately, if any of the changes fixes it it would be interesting to know which combination it was, so please remember that and let me know! 🙂

            L 1 Reply Last reply Reply Quote 0
            • N Offline
              Nathan123
              last edited by

              Is it hard to get UT on a Pixel 3a? I think I tried to root it, and it was having issues. I'm fairly tech savvy...just not in this area of Android and Linux.

              fredldotmeF 1 Reply Last reply Reply Quote 0
              • fredldotmeF Offline
                fredldotme @Nathan123
                last edited by

                @Nathan123 rooting is not required but you need to unlock the bootloader. Follow this guide to unlock it: https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-3a-0198625/

                After that follow the guide, including reverting to the last Android 9.0 factory image and installing via the UBports Installer.

                N 2 Replies Last reply Reply Quote 0
                • L Offline
                  Louie @fredldotme
                  last edited by

                  @fredldotme Thanks for your kind help :smiling_face_with_sunglasses: . I tried both options in different order without success. However, when turning airplane mode on messages come through after around 40 seconds. Then when turning airplane mode off message can be received for a few seconds. Please let me know if there's anything else I can try...

                  fredldotmeF 1 Reply Last reply Reply Quote 0
                  • N Offline
                    Nathan123 @fredldotme
                    last edited by

                    @fredldotme Oh ok. I didn't go back to 9.0. I'm currently on android 11. Will do that.

                    Here's the errors I'm seeing.

                    Screenshot_20201118-025657.png Screenshot_20201118-025709.png Screenshot_20201118-025746.png

                    fredldotmeF 1 Reply Last reply Reply Quote 0
                    • N Offline
                      Nathan123 @fredldotme
                      last edited by

                      @fredldotme I really want to root. Don't I need it to have "complete control" over the phone?

                      1 Reply Last reply Reply Quote 0
                      • fredldotmeF Offline
                        fredldotme @Nathan123
                        last edited by

                        @Nathan123 I'm sorry but this is not a support forum for Magisk and rooting. Installing Magisk is not a prerequisite so please follow the instructions on how to install UT.

                        1 Reply Last reply Reply Quote 0
                        • fredldotmeF Offline
                          fredldotme @Louie
                          last edited by

                          @Louie What you could do too is make ofono run in debug mode and figure out what is hanging here, or send me the log in private (it will contain dialed numbers and such):

                          Connect to the phone via adb shell, then run

                          sudo mount -o remount,rw /
                          sudo nano /etc/init/ofono.override
                          

                          And append -n -d to ofonod's launch flags.
                          After a reboot you can obtain the log file from /var/log/upstart/ofono.log.

                          dieharddanD 1 Reply Last reply Reply Quote 0
                          • D Offline
                            dsimmons
                            last edited by

                            @fredldotme Just wanted to say, thank you! I have been dying to move away from Android/iOS, and was looking for the perfect device to do it on. I just got my hands on a Pixel 3a, and didn't even set up Android as I was so excited to try Ubuntu Touch. I'd like to mention, installation through the UBports Installer was an absolute breeze.

                            Thus far, the experience is awesome! I look forward to seeing Ubuntu Touch grow, and I'm sure as I get my hands dirty I'll be revisiting this page many times.

                            1 Reply Last reply Reply Quote 1
                            • dieharddanD Offline
                              dieharddan @fredldotme
                              last edited by

                              @fredldotme I would like to try this, but im not quite sure what it means to append -n -d to ofonod's launch flags, could you elaborate?

                              1 Reply Last reply Reply Quote 0
                              • D Offline
                                dsimmons
                                last edited by

                                @dieharddan I am trying this as we speak. What he means is if you edit the ofono.override, you'll see a line:
                                exec ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

                                Asking to add -n -d as flags for when ofonod executes.

                                dieharddanD 1 Reply Last reply Reply Quote 0
                                • dieharddanD Offline
                                  dieharddan @dsimmons
                                  last edited by

                                  @dsimmons Ok, thanks, I did edit the file as such: exec ofonod -P - n - d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

                                  But i didn't see the log in the upstart folder, so I figured i did it wrong

                                  1 Reply Last reply Reply Quote 0
                                  • D Offline
                                    dsimmons
                                    last edited by

                                    @dieharddan I think the order matters here. Not familiar with ofonod, but it looks like the help page suggests that the -P is for noplugin, followed by a list of plugins not to use. So reading through here, provision,udev... and the others need to follow -P directly. I'd edit it to reflect this instead:

                                    exec ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap - n - d

                                    I was able to get the log... now I'm trying to get it off my Pixel 😆

                                    dieharddanD 1 Reply Last reply Reply Quote 0
                                    • dieharddanD Offline
                                      dieharddan @dsimmons
                                      last edited by

                                      @dsimmons lol nice, i will give this a try thanks again

                                      1 Reply Last reply Reply Quote 0
                                      • D Offline
                                        dsimmons
                                        last edited by

                                        hah, yeah I am having a rough time of it. Default SSH config isn't working, trying to sort that so I can use SCP, if I try to email the file or copy over from the /home/phablet/ folders, it seems to think the files empty, even though when I look at it in nano it's not.

                                        1 Reply Last reply Reply Quote 0
                                        • D Offline
                                          dsimmons
                                          last edited by

                                          @fredldotme hey, I was able to get the ofono.log (I also have the SMS issue, but airplane mode on/off doesn't resolve)

                                          I'm not sure about pastebining this whole thing, is there anything in particular you're looking for, or a section I can parse out? It looks like there is a lot of identifying information, and I don't want to just slap it all in a public pastebin.

                                          1 Reply Last reply Reply Quote 0
                                          • D Offline
                                            dsimmons
                                            last edited by dsimmons

                                            @dieharddan / @fredldotme looks like I may have found something interesting, I think short enough to drop here:

                                            ofonod[2048]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_list() 6 cell(s):
                                            ofonod[2048]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=1,mcc=311,mnc=480,ci=78151704,pci=166,tac=1280,strength=18,rsrp=107,rsrq=11
                                            ofonod[2048]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,pci=172,strength=12,rsrp=107,rsrq=10
                                            ofonod[2048]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,pci=166,strength=13,rsrp=107,rsrq=11
                                            ofonod[2048]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,pci=172,strength=13,rsrp=111,rsrq=16
                                            ofonod[2048]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,pci=167,strength=13,rsrp=114,rsrq=15
                                            ofonod[2048]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,pci=200,strength=13,rsrp=116,rsrq=19
                                            ofonod[2048]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_cells_changed_cb()
                                            2020-11-19 20:55:18 slot1< [00000146] RESPONSE_ACK
                                            2020-11-19 20:55:18 slot1< 0000: 20 03 00 00 46 01 00 00 ...F...
                                            2020-11-19 20:55:22 [gbinder-radio] WARNING: /dev/hwbinder:slot1 died
                                            2020-11-19 20:55:22 [grilio-binder] ERROR: slot1 radio died

                                            It looks like right after ACK, the radio hardware binder up and fails. Possibly related to the issue? Maybe driver failure?

                                            fredldotmeF 1 Reply Last reply Reply Quote 0
                                            • fredldotmeF Offline
                                              fredldotme @dsimmons
                                              last edited by fredldotme

                                              @dsimmons that's interesting, thanks for finding that! I have built updated versions of some components and would like to see if they work for your use case:

                                              • Download: https://drive.google.com/file/d/1HIZkTBRqypqeFz-p-AfDoqogFo7ukYsa/view?usp=sharing
                                              • Download: https://drive.google.com/file/d/1G-WQNpbNLTsmaptDw4HaFC1GcwXfq9VO/view?usp=sharing
                                              • Copy the two files to your phone's Downloads folder
                                              • Run an adb shell and enter:
                                              sudo mount -o remount,rw /
                                              sudo cp ~/Downloads/libgbinder-radio.so.1.0.11 /usr/lib/libgbinder-radio.so.1.0.8
                                              sudo cp ~/Downloads/libgbinder.so.1.0.47 /usr/lib/libgbinder.so.1.0.37
                                              sudo reboot
                                              

                                              It's certainly interesting that the rilmodem would just disappear from binder, so I'm eager to find out if that somewhat fixes your issue.

                                              EDIT: Also, could you please verify with dmesg -w | grep -i binder in a separate terminal window if there are binder transaction failures coming up when your issue appears?

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