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

@martinm Please do not post the same question in two places ( https://forums.ubports.com/topic/6570/waydroid-installation/6 ) it only confuses things for people trying to answer. Waydroid has it's own website http://www.waydro.id/ and Telegram group https://t.me/WayDroid you could try asking there.

@nero355 im not certain on the protocols, do you know how i can check that

@lakotaubp I guess so. When I press 1 on the phone, it doesn't auto dial. When I hit 1 then the phone icon, it looks like it's dialing then fails. When I call RedPocket using my phone number, it says the VM hasn't been set up yet and doesn't allow me to access my VM. Not sure how to fix this.

@rik yes, I know. This was fixed among other issues by the wonderful work Alfred, the maintainer, is doing with this device. Autobrightness works but with some quirks. Other quirks are related to calls, for instance the loud speaker call works but the interlocutor can't hear me because of the noise in the background (I opened a bug report on Github). Cheers. Matteo

@dieharddan @kmsgli just noting that SMS in and out now 100% reliable. MMS takes some fiddling with APN to clear out, can't have multiple APNs with the same name (one for internet, one for MMS). But after getting it set, should work in and out for MMS photos when WIFI OFF. WIFI ON is still a problem beyond the P3a. https://forums.ubports.com/topic/6039/bounty-for-pixel-3a-halium-9-stability/18?_=1630188659271

@azraelpwnz note that SMS is now 100% reliable in and out. MMS photos work in and out with wifi OFF. Wifi ON is a problem, but broader than the P3a. https://forums.ubports.com/topic/6039/bounty-for-pixel-3a-halium-9-stability/18?_=1630188659271

@aircooled note that MMS photos in and out are now reliable with wifi OFF. With wifi ON it is a problem, but broader than the P3a. Thanks to @fredldotme for the fixes: https://forums.ubports.com/topic/6039/bounty-for-pixel-3a-halium-9-stability/18?_=1630188659271

@standupmobile @damiam note that APN settings sticking via the GUI are indeed a problem: you can manually install updated ofono and ofono-scripts packages that help address that. Even then it takes a bit of fiddling to clear out, but note that after that MMS is reliable for photos in and out when wifi is OFF. Wifi ON still is a problem, but broader than the P3a. SMS is now 100% reliable thanks to fixes from @fredldotme https://forums.ubports.com/topic/6039/bounty-for-pixel-3a-halium-9-stability/18?_=1630188659271

@mw4jet @Nutmeg great news, SMS is now 100% reliable. Here is a link to the post @fredldotme made noting the fixes: https://forums.ubports.com/topic/6039/bounty-for-pixel-3a-halium-9-stability/18?_=1630188659271 In short, "IMS" services needed to be disabled on the phone so that carriers don't start sending SMS over "IMS" and keep sending them the "old school way" which works. MMS photos also working reliably when wifi is OFF. With wifi on, it is not, but it is a known problem broader than the Pixel 3a. MMS group messages have trouble coming IN, but can be SENT (again only with wifi off).

@CJLes72 GOOD news! Incoming SMS is now reliable on the P3a in the US / Canada (due to disabling "IMS" on the phone so the carriers don't convert sending SMS over IMS and keep sending it the "old school way" which works). This is quite reliable now. Also, MMS photos in and out work reliably with wifi turned OFF: with wifi ON they do not work right, but it is broader than the P3a. Here is the link to the post where @fredldotme references these fixes: https://forums.ubports.com/topic/6039/bounty-for-pixel-3a-halium-9-stability/18?_=1630188659271

@liamfj17 it did have that bug at one point - system update should have taken care of it I guess

@keneda Thank you