Google Pixel 3a (sargo)

fredldotme

@dieharddan I'm surprised about GPS, would have to retest that myself.

Regarding SMS: You would have to, at least, check what happens in the logat radio log and, additionally, enable ofonod debugging.

To follow the radio log (Using SSH, phablet@10.15.19.82) :

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

Try to send yourself an SMS and check whether anything moves in the log and what exactly happens. Also, make sure you remove any private information from the log before sending it to me or posting it here.

dieharddan

@fredldotme I sent the sms at 08-25 03:07:30.243 (near the bottom), but doesn't look like anything happens, as a test i made a call and it does show logs then, also i used my ip address instead of the 10.15.19.82, not sure if that makes any difference..

dieharddan

This post is deleted!

fredldotme

@dieharddan maybe a pastebin service like paste.ubuntu.com would be better for such long logs. Could you please share them there, post the link here and remove the logs you posted already instead?

dieharddan

@fredldotme

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

fredldotme

@dieharddan I remember going back to an older 9.0 based factory image to get rid of the qcril_google_init() Fail. line, maybe it's related to the SMS receive issues.

dieharddan

@fredldotme ill give it a shot and see what happens

dieharddan

@fredldotme Downgraded to the oldest 9.0 and also tried the newest 10.0, no sms on either

Fieldlab

The Pixel 3a does not have a notification led. I have heard the led screen uses such low power when black that you can simulate one.

fredldotme

I'm currently working on the Pixel 3a port again. We're not going to use the GSI for an initial release, we'll require device-specific Halium builds instead for now. This means that for the 3a XL variant someone has to step up and work together with us to support it, as subtle differences make that the better approach.

fredldotme

@dieharddan still rocking the 3a XL? If you want to help us support the device, I have made changes so that the Halium build can start now. We'll soon have Installer support for the 3a, which means there is very little for you to do to support it.

dieharddan

@fredldotme Had to sell it unfortunately, I plan to repurchase later and will contact you when I do

kaiyes

Hi @fredldotme , I know from the ubuntu touch Q&A that sargo is coming and you are looking for users with bonito users.

However, how similar are pixel 3 & pixel 3 XL with the sargo ? Will they work or is it too different ? Currently thinking of getting a bonito as they are available locally but there are more pixel 3/xl available than bonito

fredldotme

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

dieharddan

@fredldotme I found a great deal on another pixel 3a xl which I will receive in a couple days, I would like to assist in getting this supported alongside sargo

dieharddan

@fredldotme I received my device; are you able to share any details on installing ut?

fredldotme

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

dieharddan

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

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)