Ubuntu Touch Q&A 170 call for questions

UBportsNews

Ubuntu Touch Q&A 170 will be live this Saturday 26th July, so if you can please join us at the usual time of 19:00 UTC.
Before then though, if you have any questions on or about UBports and Ubuntu Touch please post them below and we will do our best to answer them.

Remember that questions on porting to device **** or its status, and questions on bugs, will not be answered.

atarilinux

A group on the forum is trying to see if we can setup VoLTE for the Google Pixel 3a. An image was found on Github created by @fredldotme . However, we could not find documentation on the Android version used and a general installation process to being testing. This is where we are right now.

From @Futura ,

"I will say after experimenting this morning with LineageOS for the 3a XL flashing 22.2 with the base version of 12.0.0 (SQ1A.220205.002, Feb 2022) was the most stable for me. I am not sure if 19.1 and 22.2 use the same base version of stock android, or if @fredldotme used a different specific version."

Thanks for everything you all do to support Ubuntu Touch and the amazing Pixel 3a port!

janmv

Could you give me some general context regarding 4G (lte) and battery usage?

As a newcomer, I posted a question on the forum because I noted the large standby power consumption of my FP4: it is larger than 2G and 3G, it is larger than comparable devices on Android and it appears to affect other brands as well. I'm not the first one to note; there is even a battery Saver app which explicitly switches off 4G when there is no use for it.

Digging into the code, I found out about a so-called 'fast dormancy' setting, which (at least on FP4) is 'Not Implemented'. My first reaction, as I am willing to contribute to UT, was to see if I could provide an implementation. But the context is complicated and it is confusing to me. I'll try to list (and correct me if I'm wrong):

In the FP4-UT Telegram chat, Flohack mentioned that an implementation already did get proposed (https://github.com/ubports/ofono/pull/38), but it never found its way into the code.
The 'fast dormancy' setting (a simple yes/no) has developed into a more fine-grained setting in Android, but this seems unexplored territory, also because information on modem APIs is limited; not all modems may be able to handle this new version.
In order to work, something called MCE (Mode Control Entity) needs to provide information on the device state. The code is in the libmce-glib-repowerd-stub repository, which does not sound very final
The repositories in which much of the code resides, are not maintained by UBports (but by Sailfish). I suppose these communities are in touch?

I suppose 4G-battery-use is sufficiently serious to pay attention to. So what is the bigger picture here? What is UT working towards to? And if I wish to do more than just an occasional post in the forum and the Telegram channels, what do you suggest me to pick up?

captainfunk

Hi everyone ,
Thanks for a all contributors and for answering questions.
From my understanding, in an encrypted device, the phone is really secure after turning it off and before the first decryption/unlocking (BFU), after the device is first unlocked/decrypted (AFU) it is not as secure even if it is locked again because the encryption keys are stored in RAM. For extra security, would it be possible and hard to implement an option in the encryption settings to make the phone like in BFU every time the phone is locked ? Even if it takes longer to unlock each time of course