@ubportsnews Another 20.04 question (sorry if this has been asked before): According to the Ubuntu package database, package syncevolution is not part of the Focal package repositories any more. What will contact and calendar synchronization be based on in Focal based UT?

New Pure Maps release 1.29.0 contains a patch that applies audio role notification to voice directions. Normal audio, e.g., music, is no more stopped, but damped now.

VW carkits have an infamous bug, that auto-mute Bluetooth audio after music was paused/stopped. When the next voice direction came in, unmuting took some time, cutting-off part of directions. This problem does not happen any more with the new Pure Maps release.

Using Ubuntu Touch as daily driver got a little more comfortable again. Thanks @rinigus and jonnius!

Thanks to @trainailleur, in the mean time, I managed to install UT on the device. FTR, I just had to unlock bootloader via $ fastboot oem unlock before flashing firmware. Radio firmware revision does now match the one from the link in the initial post:

$ adb shell
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems | grep -i rev
    Revision = .4.0.1.c7-00013-M8974AAAAANAZM-1

@Moem said in OTA-13 call for testing:

Unfortunately I can't reproduce this (with OpO and Jabra Drive carkit). Still no dice.

I have opened a new topic about Bluetooth findings with OTA-13 (rc).

With Nexus 7 LTE (deb) and OTA-12 rc (2020-W14), pressing the power button and releasing it quickly to just switch off the screen, activates the power-down menu as if the button had been pressed for a longer time. Then the screen does indeed turn off. Pressing the power button again, turns the screen back on, with the power-down menu still present. To use the device you have first to press the cancel button. This is quite inconvenient when you have the habit of switching off the screen manually to save charge.

The issue is not present with OTA-11 (tested switching back and forth between stable and rc channels).

@rubencarneiro said in New Ubuntu Bootlogos Now available:

You can find them at : https://rubencarneiro.github.io/rubencarneiro.io//Ubuntu-Touch-Device-Bootlogos.markdown/

Nice! Though, I wonder what the main message of the logos is? Is it the hardware vendor or the OS? Given UT is the same on all devices, the hardware vendor shouldn't matter that much.

Which is the reason various Android hardware vendor's marketing demanding a custom UI. Otherwise, people wouldn't notice and eventually don't care. Should we care?

I suggest putting the key information "ubuntu touch" in the center, making it bigger, perhaps splitting it onto two lines. The hardware information can be put at the bottom.

While development on the technical foundations of UT is regularly covered in Q&A (20.04 transition, Qt 5.12 transition, Lomiri development, new Halium ports etc.) can you shed some light on (under the radar) development in user land? There must be some, because UT has not come to an end, yet.

To name the elephant in the room, what about CalDAV/CardDAV support? That seems to be only half-baked, currently. Is there any development on that front? To quote from the UBports site: With Ubuntu Touch they will have nothing to see. Ubuntu Touch user's response: Because there's no way to share. Since working CalDAV/CardDAV synchronization on a smartphone is a basic requirement like telephony and text messaging these days, would it make sense to back sustainable CalDAV/CardDAV development by the foundation similar to OS development?

@h_b While I can sync successfully with an external CalDAV server, I can't with a self-hosted nextcloud instance that has a self-signed certificate. There are other similar reports ... Is your nextcloud instance, by chance, secured with a self-signed certificate?

CalDAV/CardDAV situation was discussed in Ubuntu Touch Q&A 93 (at 3:00 min). Things will probably not improve before 20.04 transition.

@trainailleur Thanks, will do so!

As (for the time being) this is a spare device, is there anything I can tests with UT on OPO with the current (legacy) firmware, that UT QA folks are interested in (like camera)?

I have aquired a used OnePlus One (A0001/64GB). Current system seems to be LineageOS 13.1.2 (build date 2016-08-11, build MHC19Q). Baseband version is DI.3.0.c6.00241-M8974AAAAANAZM-1. I do find on the net some hints that there is some 4.x baseband version, e.g., at https://www.reddit.com/r/LineageOS/comments/8c627g/oneplus_one_baseband_report/ Additionally, LineageOS 16 is available for the device.

My question is, how to proceed to finally have UT on the phone with the latest baseband version? I'm a bit lost among the options:

• First install latest Oxygen OS 2.1.4 then UT?
• First install latest Lineage OS 16 (daily) then UT?
• Install new baseband/firmware manually then UT?
• Install UT as is?

Can anybody shed some light on this? Any pointers?

@ubportsnews Another 20.04 question (sorry if this has been asked before): According to the Ubuntu package database, package syncevolution is not part of the Focal package repositories any more. What will contact and calendar synchronization be based on in Focal based UT?

@flohack said in Halium 7.1 Test Channel:

Oh seems no sensors work at all, not even after reboot. Is this confirmed?

Yeah, confirmed by my post to the OTA-16 RC topic. I did the obvious and restarted the device before posting, but that didn't help. Will next time test if rebooting more than once makes a difference. (Sounds unlikely, though.)

@messayisto said in Halium 7.1 Test Channel:

Automatic Brightness doesn't work on my device.

Automatic brightness didn't work for me, too, after the update. As well as rotation. Since I've already run into the latter problem recently, I've powered the device off and on and automatic rotation and brightness were back. Note, just rebooting the device might not be enough.

Well, even though, changing environmental lighting conditions has an observable effect on screen brightness, sensitivity could indeed be more intense. Don't know if it is worse than on stable channel, since this device is only used occasionally.

@moem Powering the device down and on again brought rotation back. Thanks for the prompt reply!

@moem OK, thanks.

@unisuperbox Rotation doesn't seem to work on OPO with RC/W10. I've checked rotation lock and restarted the device. Unfortunately, I don't know if rotation ever worked before on this device. According to device page rotation should work. Can anybody confirm?

@keneda said in start.ubuntu.com:

For my self learning, how do you see those requests?

Since you're asking explicitly, here's a hack-ish non-Libertine way to watch outgoing (DNS) connections. Note that deb packages use xz compression nowadays that is not supported by UT's tar. So extraction of the binary has to be done on a device with a more recent version of tar.

# Download armhf deb package of tcpdump.  There are newer package versions on the server, but those may not work as easily because of further dependencies.
$ wget http://ports.ubuntu.com/ubuntu-ports/pool/main/t/tcpdump/tcpdump_4.7.4-1ubuntu1_armhf.deb
# Extract deb archive.
$ ar -x tcpdump_4.7.4-1ubuntu1_armhf.deb
# Extract binary.
$ tar -xf data.tar.xz 

Now, move file usr/sbin/tcpdump to the UT device (via adb, ssh, cloud). Then switch to a terminal on the UT device.

# Make the binary executable.
$ chmod +x tcpdump
# Watch all DNS queries on the device.
$ sudo tcpdump -i any port 53

Then wait and see.

(Tested on OPO OTA-16 RC/W09).

There's already a discussion about start.ubuntu.com that didn't turn up in a forum search for me before. According to that it's a connectivity check.

@keneda In a local (LAN-wide) DNS resolver.

I can see occasional outgoing requests to start.ubuntu.com (every ten minutes or so) on a Nexus 5/OTA-15 and OPO/RC with no apps open. Can somebody please shed some light on what's that used for in UT? Opening start.ubuntu.com in desktop browser reveals a Google search box.