Posts made by fredldotme

@dsimmons @dieharddan No, I'm not seeing those issues on my phone (T-Mobile/Magenta, Austria). What I've noticed is a different issue where ofono (UT-side) and rild (Android-side) don't communicate with each other anymore because rild runs out of IPC memory. Hard to fix since it's the proprietary blob acting up.

Your problem, it could be either differences in operators, but also there are specific models with different modem settings. In the case it's the modem settings, could you please post the output of getprop ro.boot.hardware.sku? Mine is G020F.

We have one known US citizen getting his compatible device soon, so at least we can verify and potentially fix those issues.

What I would propose for now, since it's your daily driver, is to revert to Android until we have a solution. Those issues are harder to fix than expected because most developers/porters who get into contact with ofono live in Europe. We will surely ping you in the thread as soon as we have something for ya.

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

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

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

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

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

@Duhjoker the Pixel 3a is now officially in the installer, should be easy to get going now! Make sure to downgrade your phone as per instructions first.

@Duhjoker it's not officially in the installer yet. What you can do instead is follow this mini guide right here to force the installer: https://mobile.twitter.com/fredldotme/status/1322714885076275201

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

@Pingu it would be better to make a bug report on the UBports Installer GitHub page instead.

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

@kaiyes The Pixel 3/3XL would need a new port, that I can't help much with. So it would be better to get a sargo (or bonito if you want to help).

In other news, I haven't been able to reproduce the SMS problem as of late, so that should be fixed on sargo.

@bennypr0fane forget the Ubuntu actions, they don't help us right now.

So since you have the recovery already on your phone, try a flash without the bootstrap option again. The phone should reboot to recovery again and the UBports installer should start pushing the files onto the device. If you lose connection during the push operation I would like to know the contents of some directories, using adb shell:

adb shell ls -lah /cache
adb shell ls -lah /cache/recovery
adb shell ls -lah /data
adb shell ls -lah /system