• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
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.
    • F Offline
      fredldotme @dieharddan
      last edited by 2 Nov 2020, 09:17

      @dieharddan follow this mini guide here: https://mobile.twitter.com/fredldotme/status/1322714885076275201

      D 1 Reply Last reply 2 Nov 2020, 17:36 Reply Quote 1
      • D Offline
        dieharddan @fredldotme
        last edited by 2 Nov 2020, 17:36

        @fredldotme So I was able to install UT and everything I tested so far works flawless!! The only issue I have is I'm still not able to receive text messages; sending texts seems fine. Any ideas?

        F 1 Reply Last reply 2 Nov 2020, 17:57 Reply Quote 0
        • F Offline
          fredldotme @dieharddan
          last edited by fredldotme 11 Feb 2020, 18:03 2 Nov 2020, 17:57

          @dieharddan So I think there's two things we could try: debugging ofono or rolling a separate build for bonito too. I would prefer not having to do this second one but there's, luckily, some other ways I could propose to speed up XL enablement, but maybe I'm too slow, I don't know 😛

          I'm testing this configuration file right now, which I'm in the process of determining whether ofono is doing everything right (it certainly doesn't by default on my sargo) or not.

          Enable adb via Developer Mode, reboot into bootloader, choose recovery, wait for adb devices to properly connect to your device (it could take some time) and run following command:

          wget -O ril_subscription.conf https://gist.githubusercontent.com/fredldotme/f95acc04d8ec7e470955359b570d24e7/raw/d89b29790029e952611599273c40e9b144d63a54/ril_subscription.conf
          adb shell mount /system_root
          adb shell mount /system_root/var/lib/lxc/android/android-rootfs.img /tmp
          adb push ril_subscription.conf /tmp/system/halium/etc/ofono/ril_subscription.conf
          adb reboot
          

          I can't test it with my own phone right now, due to it requiring a reboot and breaking testing daily-driveability of this configuration of ofono, in case of an error you might have to change the values using busybox vi manually, that's how I created the config.

          1 Reply Last reply Reply Quote 0
          • D Offline
            dieharddan
            last edited by 2 Nov 2020, 18:23

            ./adb push ril_subscription.conf /tmp/system/halium/etc/ofono/ril_subscription.conf

            adb: error: failed to copy 'ril_subscription.conf' to '/tmp/system/halium/etc/ofono/ril_subscription.conf': remote write failed: No space left on device
            ril_subscription.conf: 0 files pushed. 1.5 MB/s (10559 bytes in 0.007s)

            F 1 Reply Last reply 2 Nov 2020, 18:27 Reply Quote 0
            • F Offline
              fredldotme @dieharddan
              last edited by fredldotme 11 Feb 2020, 18:48 2 Nov 2020, 18:27

              @dieharddan In that case maybe removing the existing file and pasting it using busybox vi would solve the issue. The ofono config though seemed unhelpful in resolving all issues I keep having, maybe it has to do with different carriers behaving differently now, I certainly receive SMS anyway but sometimes signal drops without indication and stays unresponsive. I don't know why the ofono-ril-dance doesn't work the way it's supposed to work yet so it might be interesting to find out.

              1 Reply Last reply Reply Quote 0
              • D Offline
                dieharddan
                last edited by 2 Nov 2020, 18:37

                You may be right, but I'm willing to try it anyway, though I'm not certain how to use busybox as I am not familiar with that

                F 1 Reply Last reply 2 Nov 2020, 18:52 Reply Quote 0
                • F Offline
                  fredldotme @dieharddan
                  last edited by fredldotme 11 Feb 2020, 22:47 2 Nov 2020, 18:52

                  @dieharddan In case something went wrong with the config you can re-install without wiping using the Installer of course, but what you could do to get some details is (in the running system, ie not the recovery):

                  setprop persist.vendor.radio.adb_log_on 1
                  sudo reboot
                  

                  And after the device is back up:

                  sudo env LD_LIBRARY_PATH=/vendor/lib64:/system/lib64 /system/bin/logcat -b all
                  

                  It hopefully shows what the error in your case is, else you would have to figure out a way to debug on your own.

                  Btw, does your device report itself as bonito or sargo in the recovery adb shell and in system-settings?

                  D 1 Reply Last reply 3 Nov 2020, 02:54 Reply Quote 0
                  • D Offline
                    dieharddan
                    last edited by 3 Nov 2020, 00:35

                    I dont see a model listed in the recovery screen, the system settings say "Google Pixel 3a"

                    F 1 Reply Last reply 3 Nov 2020, 01:18 Reply Quote 0
                    • F Offline
                      fredldotme @dieharddan
                      last edited by 3 Nov 2020, 01:18

                      @dieharddan Hm ok. Regarding recovery: I mean when you go into recovery mode, connect the phone and enter adb shell on your PC, is it saying sargo or bonito?

                      D 1 Reply Last reply 3 Nov 2020, 01:50 Reply Quote 0
                      • D Offline
                        dieharddan @fredldotme
                        last edited by 3 Nov 2020, 01:50

                        @fredldotme ah I see, yes that also says sargo

                        1 Reply Last reply Reply Quote 0
                        • D Offline
                          dieharddan @fredldotme
                          last edited by dieharddan 11 Mar 2020, 04:36 3 Nov 2020, 02:54

                          @fredldotme said in Google Pixel 3a (sargo):

                          @dieharddan In case something went wrong with the config you can re-install without wiping using the Installer of course, but what you could do to get some details is (in the running system, ie not the recovery):

                          setprop persist.vendor.radio.adb_log_on 1
                          sudo reboot
                          

                          And after the device is back up:

                          sudo env LD_LIBRARY_PATH=/vendor/lib64:/system/lib64 /system/bin/logcat -b all
                          

                          It hopefully shows what the error in your case is, else you would have to figure out a way to debug on your own.

                          Btw, does your device report itself as bonito or sargo in the recovery adb shell and in system-settings?

                          Here is the output from those commands, I tried this a couple times and there was ALOT of text, so I only copied some of the bottom after sending a few consecutive texts to myself

                          https://paste.ubuntu.com/p/R5pFcV99VK/

                          1 Reply Last reply Reply Quote 0
                          • D Offline
                            dieharddan
                            last edited by 3 Nov 2020, 14:51

                            So I was playing around with this again this morning and I found that if I toggle airplane mode, I can send and receive sms as normal for about 30 seconds maybe.... after that it quits until I toggle airplane mode again which gives me another 30 sec of working sms

                            F 1 Reply Last reply 3 Nov 2020, 16:15 Reply Quote 0
                            • F Offline
                              fredldotme @dieharddan
                              last edited by fredldotme 11 Mar 2020, 16:48 3 Nov 2020, 16:15

                              @dieharddan I'm starting to assume it is premature powersaving at fault here, I've changed the ril_subscription.conf again for other reasons, including device state management. Will send you the new one to change manually again soon.

                              Edit: check the config here, especially deviceStateTracking and the last two lines: https://termbin.com/k3gb

                              1 Reply Last reply Reply Quote 0
                              • D Offline
                                dieharddan
                                last edited by 3 Nov 2020, 18:43

                                My ril_subscription.conf says:
                                #deviceStateTracking=auto
                                and I do not have the last 2 lines that you have

                                I tried to copy the new file over with the file manager to test but don't have write permission on the ofono folder

                                F 1 Reply Last reply 3 Nov 2020, 21:00 Reply Quote 0
                                • F Offline
                                  fredldotme @dieharddan
                                  last edited by fredldotme 11 Mar 2020, 21:34 3 Nov 2020, 21:00

                                  @dieharddan What could work is the following:

                                  • Reboot into recovery
                                  • run:
                                  adb shell mount /system_root
                                  adb shell mount /system_root/var/lib/lxc/android/android-rootfs.img /tmp
                                  adb shell rm /tmp/system/halium/etc/ofono/ril_subscription.conf
                                  adb shell umount /tmp
                                  adb shell reboot
                                  

                                  In the booted system you can then remount read-write and replace the preset:

                                  wget -O ril_subscription.conf https://termbin.com/k3gb
                                  adb push ril_subscription.conf /home/phablet/ril_subscription.conf
                                  adb shell
                                  

                                  In the shell enter:

                                  sudo mount -o remount,rw /
                                  sudo mv ril_subscription.conf /etc/ofono/ril_subscription.conf
                                  

                                  After that: reboot.

                                  This will be overwritten by updates until confirmed it fixes your issue, then I will merge it. It seems to provide much more stable connectivity on sargo with my provider.

                                  D 2 Replies Last reply 4 Nov 2020, 00:06 Reply Quote 0
                                  • D Offline
                                    dieharddan @fredldotme
                                    last edited by 4 Nov 2020, 00:06

                                    @fredldotme Can you elaberate on the "remount read-write and replace the preset:"
                                    I entered the "wget -O ril_subscription.conf https://termbin.com/k3gb" on the phone terminal which worked, but not the
                                    adb push ril_subscription.conf /home/phablet/ril_subscription.conf

                                    1 Reply Last reply Reply Quote 0
                                    • D Offline
                                      dieharddan
                                      last edited by 4 Nov 2020, 00:23

                                      nevermind i got it to copy over

                                      1 Reply Last reply Reply Quote 0
                                      • D Offline
                                        dieharddan @fredldotme
                                        last edited by 4 Nov 2020, 01:23

                                        @fredldotme Doesn't seem to have made any difference, I still have to toggle airplane mode to get sms to work

                                        F 1 Reply Last reply 4 Nov 2020, 13:19 Reply Quote 0
                                        • F Offline
                                          fredldotme @dieharddan
                                          last edited by 4 Nov 2020, 13:19

                                          @dieharddan I can only suggest experimenting with the config or, if that doesn't fix it, adding fallback behavior to ofono in case receiving SMS fails.

                                          D 1 Reply Last reply 4 Nov 2020, 14:44 Reply Quote 0
                                          • D Offline
                                            dieharddan @fredldotme
                                            last edited by 4 Nov 2020, 14:44

                                            @fredldotme Ok, let me know if you come up with any other ideas; I will pllay around with that file but not being any kind of developer, I probably won't be able to accomplish much lol

                                            F 1 Reply Last reply 4 Nov 2020, 16:40 Reply Quote 0
                                            43 out of 106
                                            • First post
                                              43/106
                                              Last post