@totalsonic I wish information like this was on the main status page for each phone. I purchased a Pixel 3a XL because it has all green check marks. I live in the USA and now have an unusable Ubuntu Touch. I'm uncertain as to whether or not using 2G in 2022 can be called "fully functional", but I'm finding it difficult to contemplate using this phone on a daily basis. Who should be messaged about maybe adding a note or perhaps a red X with VoLTE so that people know that all green check marks DOES NOT mean "fully functional"?
Posts
-
RE: Is there a phone that actually calls (USA networks) with UT?
-
How to install emacs?
I am happy that I can ssh into my phone, but I'm a heavy emacs user, and need that for text files. As an Ubuntu user (longer time linux / unix user), I immediately tried ap-get, however, that will not work due to the read only file system. So, what is the "approved" method of installing standard linux tools?
-
RE: *UPDATED* USA: T-Mobile (and MVNO) settings for a fully functional UT device
@rik Thank you very much for posting this. I just purchased a Pixel 3a for use on T-Mobile, not knowing that it would not work. This answers a lot of questions. Is there a table somewhere that shows which things work on which carriers? Which carriers are fully supported on UbuntuTouch? (meaning I don't have to fall back to 2G for simple phone calls)
-
RE: Problems with gps on google pixel 3a xl
@jite were you able to make progress on this? I'm having the same issue.
-
RE: T-Mobile MMS issues
@triguy did you ever make any progress on this? I have a Pixel 3a XL, and am not able to send or receive MMS messages. If this helps, during one of my attempts I monitored the logs, and found this that might be relevant:
Dec 1 10:13:22 ubuntu-phablet ofonod[1655]: setting up data call
Dec 1 10:13:22 ubuntu-phablet kernel: [ 2070.574575] c1 1655 R0: [ofonod][40005098418] [18:13:22.061772] wlan: [1655:E :HDD] __wlan_hdd_ipv4_changed: 936: Adapter context is invalid 0000000000000000
Dec 1 10:13:22 ubuntu-phablet kernel: [ 2070.580064] c1 1655 binder: 2258 has pending async transaction, but still adding a new transaction to todo list (gbinder bug workaround)
Dec 1 10:13:22 ubuntu-phablet kernel: [ 2070.580113] c1 1655 binder: 2258 has pending async transaction, but still adding a new transaction to todo list (gbinder bug workaround)
Dec 1 10:13:22 ubuntu-phablet kernel: [ 2070.580133] c1 1655 binder: 2258 has pending async transaction, but still adding a new transaction to todo list (gbinder bug workaround)
Dec 1 10:13:22 ubuntu-phablet kernel: [ 2070.580510] c1 1655 binder: 2258 has pending async transaction, but still adding a new transaction to todo list (gbinder bug workaround)
Dec 1 10:13:22 ubuntu-phablet kernel: [ 2070.648242] c7 7037 R0: [ubuntu-upload-m][40006512841] [18:13:22.135439] wlan: [7037:W :HDD] __hdd_ioctl: 7216: unknown ioctl 35591
Dec 1 10:13:22 ubuntu-phablet kernel: [ 2070.648307] c7 7037 R0: [ubuntu-upload-m][40006514147] [18:13:22.135507] wlan: [7037:W :HDD] __hdd_ioctl: 7216: unknown ioctl 35591
...
Then a little later, I found this around the same time the GUI changed to "Failed":
Dec 1 10:14:22 ubuntu-phablet ofonod[1655]: Deactivating context: 2
Dec 1 10:14:22 ubuntu-phablet ofonod[1655]: Clearing active context
Dec 1 10:14:22 ubuntu-phablet kernel: [ 2131.191763] c6 1655 R0: [ofonod][41168948415] [18:14:22.678965] wlan: [1655:E :HDD] __wlan_hdd_ipv4_changed: 936: Adapter context is invalid 0000000000000000
Dec 1 10:14:22 ubuntu-phablet ofonod[1655]: Deactivated data call