Google Pixel 3a (sargo)

fredldotme

@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.

dieharddan

./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)

fredldotme

@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.

dieharddan

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

fredldotme

@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?

dieharddan

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

fredldotme

@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?

dieharddan

@fredldotme ah I see, yes that also says sargo

dieharddan

@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/

dieharddan

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

fredldotme

@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

dieharddan

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

fredldotme

@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.

dieharddan

@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

dieharddan

nevermind i got it to copy over

dieharddan

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

fredldotme

@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.

dieharddan

@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

fredldotme

@dieharddan What you might also want to try is the two properties ro.ril.power_collapse & ro.ril.disable.power.collapse, these might change the behavior of the power savings mode.

Reboot into recovery
Connect phone to PC
Open an adb shell with adb shell
Enter the following commands:

mount /system_root
mount /system_root/var/lib/lxc/android/android-rootfs.img /tmp
busybox vi /tmp/system/etc/init/on-post-fs.rc

In vi enter edit mode by pressing 'i' on your keyboard once
Paste the following content at the end:

on init
    setprop ro.ril.power_collapse 0
    setprop ro.ril.disable.power.collapse 1

Save and exit by pressing ESC + entering :wq
Run umount /tmp
Reboot

dieharddan

@fredldotme No change Is there something I can capture via log while i toggle airplane mode and send texts