@rik I remember Group MMS working a lot worse for a lot of people so I guess some progress has been made in that department then!

@jackharness said in Pixel 3a XL experience: Network support is very hit-or-miss out here unless you go with Verizon, and I honestly couldn't be bothered with the switch. Keeping a number while switching plans is a hassle, and keeping my number is important to me. I'll definitely keep my eye out for VoLTE support, though. Yes, unfortunately several parts of the US are only covered decently by Verizon. VoLTE support would be a big win. As noted, Droidian may be worth trying, but you won't have the UT / Lomiri goodness there yet.

@rhl120 said in what model number do I need for flashing on a pixel 3a and how does it differ from a pinephone: Hi, I am very new to ubuntu touch and flashing roms on my phone in general and I would like to know what model number I should buy of the pixel 3a to flash ubuntu touch on it. Please read https://devices.ubuntu-touch.io/device/sargo/ carefully! Also watch out for carrier locked phones! In some countries it's still a thing it seems... Other than the trivial differences between it and the PinePhone (like the specs, the kernel and the boot process), how does the pinephone and Google pxiel 3a differ when it comes to using ubuntu touch (do they both have the same functionality (at least theoretically)? can I install the same programs on both? etc) It's like you would run Android on both of them : The same stuff runs on them but at a different speed! Good luck with the flashing stuff!

@fredldotme Again with the latest android version the Bonito bootloader was even lower on the phone (B4s4-0.1)and the sargo image would not recognize it.. Finally hopeing that the 0.1 version was Android-9, flashed the 190801 sargo image and it worked. From there it was my speed; just push the buttons. Best phone OS in the world. Thank you all for developing it and for taking the time to help.

@lsitongia Could you check, please, and tell me first 8 digits (TAC) of your IMEI? And do you have IMEIs from your previous phones that you were able to return back? It would be interesting to compare them.

@lsitongia Google Fi uses T-mobile. Red Pocket has all networks. GSMA is AT&T, GSMT is T-mobile. So different network. Strange that you had success with Wi-Fi on. Most were succeeding with it off. But gives us something to explore further.

@keneda I used that screen for a full year now, was working a couple hour ago, moved from dirty unicorn to the recommended version, was stll working on stock 9.0, flash ubuntu, don't work on the first screen to select the language. The screen's cracked again, yes, but it worked for a solid 2 months like that fine and the hairline cannot expend anymore.

Here's what I do: I've prepared a gprs file on my Linux box. First I turn off Cellular data in the UI, then I adb push it to the phone, then adb shell to the phone, then sudo cp the gprs file to /var/lib/ofono/###########/gprs. When I turn Cellular data back on, the gprs file on the phone is immediately overwritten with the original one, that I get when I Reset All APN Settings in the UI. Where are those settings coming from? From the cell provider (Google Fi)? Some other file on the phone? So, I can't use the UI to set the APN I want and I can't hand code it in the gprs file. What's it gonna take?

@rik It's surprising, but if I use your MMS APN settings with my Google Fi SIM (which gets set to T-mobile values after installing the SIM), then I can send MMS but cannot receive. I do have wifi off and have rebooted.

@rocket2nfinity thank you for the info.

@lsitongia I'll add that while MTP should be on from first uTouch start on your device, screen must be active, phone unlocked, in order to mount it on a computer. And only five folders can be accessed this way, documents, downloads, music, pictures and videos, for security reasons.

@lsitongia said in Miscellaneous Questions: I'd like to ask a number of questions here in one thread. If you think it's better that I create a separate thread, tell me, and I'll do that. I don't have a Pixel 3a, so I can not answers questions about that device, but I can answer general questions. Do you know when UT running on Ubuntu 20.04 will be released? Where can I keep track of progress on that? There is no set date for the rebase to 20.04 - it will be released after everything is made to be functional and it has gone through an initial test period. My guess is sometimes towards the middle of 2022, although it is possible it could come sooner. You can keep up with the progress at https://gitlab.com/groups/ubports/-/epics/10 or via the Q&A's that are posted to YouTube every other week at https://www.youtube.com/c/UBports Do you know when there will be full Nextcloud integration? I see the client on UT on my phones only has a toggle for Calendar. On Mobian on my Pinephone, all of the usual services are there, including Calendar, Contacts, Documents and Files. I wonder if the Mobian/Phosh/Gnome software would help with UT. How do I track progress on Nextcloud integration and the Online Accounts interface? You can get file syncing and automatic backups working in UT with NextCloud by using the UBsync app - https://open-store.io/app/ubsync A nice file browser app for your NextCloud server is GhostCloud - https://open-store.io/app/me.fredl.ghostcloud Calendar sync works great - but Contacts sync support still needs to be fixed. What I do in the meantime is every time I update it, I export my Contacts list (via the Contacts app Settings "Export all contacts" option) and then save the vcf file to a folder I've shared with my NextCloud server via UBsync. Does GSConnect/KDEConnect work between a Ubuntu laptop and the P3a running UT? No it does not, someone would need to code support for UT for those apps. I see the "What Works" page says NFC works! I know it can be used for touchless payment on the Big Two phones. What is it used for in UT? Currently UT OS support for NFC has been enabled, but so far there have been no apps which take advantage of this made yet. Best regards, Steve Berson

@lsitongia, as far as I understand, "Type C" only defines physical shape of a USB port. Inside it could be USB 2.0 or USB 3 or USB 3 + DisplayPort alt mode. Most mid-range phones only have plain USB 2.0/3.0 , and so video output is not supported. Do you know, is that because it's the lower-cost version of the phone? I think it definitely helps to reduce manufacturing costs. In case of Pixel devices the absence of physical video out ports also help advertising chromecast devices, I believe . Considering all the things I wouldn't count on support for video output over USB Type-C port on a phone by default, unless it is explicitly advertised in device specs.

Hi @justinz There is a simple enough procedure on google website. I don't have the link right now, but pixel devices are great on that regard. Ask if you want me to dig out the link for you.

Could this have something to do with the problem we're seeing? https://github.com/ubports/ubuntu-touch/issues/1837 If so, it's not obvious to me there is a solution. @UniSuperBox posted "Funny enough, you can get another shell into the device in this state. Running sudo reboot there causes the Pixel 3a to boot into the selected mode, but the Volla Phone does not." but I don't know how to use this information to complete the install. BTW: I tried using UBports 0.8.8 ... but I ran into the same problem.

My thanks comes in the form of monthly payments to these devs. Since I have no skills to contribute XD Also, to AsteroidOS team. Hope they haven't given up.

@stanwood thanks mate. I used your link and had a play. The only thing I can't seem to do is remove useless duplicates from the ubuntu touch app drawer. I disabled the useless duplicate apps within the settings app in the waydroid instance however it doesn't remove them from the ubuntu touch drawer... sigh

@thousandtopics Indeed, as I described above, WayDroid is built to be far more usable than Anbox, but is still in a very pre-alpha development stage. To remove completely old Anbox, Go in the terminal and type: anbox-tool disable sudo rm -rf ~/anbox-data/ ~/.local/share/applications/anbox/ Reboot the device. Then, there are desktop files named anbox* at ~/.local/share/applications which you can delete the apps on the drawer. Delete them all. So then you can install WayDroid as explained in my previous post.