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.

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

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

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

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!

@Moem Thanks again!

I noticed some missing translations when pulling from indicator menu:

1. Pulling «Network» icon, label «Cellular data» is not translated.
2. Pulling «System» icon, label «Report a bug» is not translated.

Tested with Nexus 5, OnePlus One and various languages.

@mihael According to the Arch Linux wiki, when a Device connects, then disconnects after a few moments it might be due a device already being paired (from within a different operating system). A fix is to remove the device and re-pair. The Arch Linux wiki shows how to do that on the command-line via the bluetoothctl command.

@dobey OK, thanks for the clarification!

@Moem Thanks again!

@Moem said in Q: notifications (non-LED):

For sure!

Thank you!

If you want to buy new, the Pinetime is a simple and cheap, but very usable option.

Do you know what that „Disclaimer: sealed device“ refer to? Water-proof? Tamper-proof?

@Moem said in Q: notifications (non-LED):

All I can say to that is that in my highly personal experience, I miss a great deal fewer notifications when I do wear a smart watch than when I don't.

Do you have – for the brave ones – any pointers to learn about compatibility of smart watches and UT phones?

@Moem said in Q: notifications (non-LED):

@padu said in Q: notifications (non-LED):

does Ubuntu Touch support this obscure feature of on-display visual feedback about missed calls, SMS etc. that you can notice without having to touch the phone?

I don't know how that exists at all. How can you show something on the screen without the screen being on?

Advances in low-power screen technology, which gives hardware manufacturers the option to spare that LED. But as I said, I've never really followed such news and am now a bit lost about the actual notification situation.

I mean, I cannot believe, people are happy permanently touching buttons to check for notifications, huh?

That's what my smart watches are for. To let me know about notifications, and even let me read them, without me having to touch my phone.

Adding yet another piece of hardware to the stack gives an opportunity for funny blame games. If I missed a notification, was it the watch's fault or the phone's? Certainly not a peace of mind enabler.

Nexus 5 user here, who has been ignorant of hot stuff in mobile hardware for the last few years. Now, about to buying a new phone, I'm unsure what kind of notifications Ubuntu Touch offers.

• LED notification (which is currently non-working on Focal devices, AFAIK).

• I do recall that (some) phones once introduced a mode of displaying permanent information (such as notifications) on the screen without the usual screen-on-battery-drain. Yet, I don't seem to be able to even google that feature. So, does Ubuntu Touch support this obscure feature of on-display visual feedback about missed calls, SMS etc. that you can notice without having to touch the phone? And what devices do? I'm only interested in knowing that some notification is waiting to be handled. Less in permanent display of (part of) the actual notification message.

Sorry for being so vague about a feature I cannot name or describe. I mean, I cannot believe, people are happy permanently touching buttons to check for notifications, huh? Does this question make any sense?

@lakotaubp said in Dekko 2 incoming email:

Though the app is not in the OS directly so each email account used in Dekko 2 would need password plus another verification for Google to except it, if I have that right of course.

Can't say if you're right, because I don't actually have a gmail account myself. I haven't been aware of big G enforcing 2FA now. Though, I've seen gmail support pages explaining how to turn off "2-step-verification".

What triggered my response was the fact that I've seen old, EOS phones having to be finally retired when mail providers tightened their list of accepted ciphers. 20.04 based UT will certainly stretch the live span of some phones (if not for gmail users).

@emphrath said in Dekko 2 incoming email:

@lakotaubp concerning gmail, they made clear they would drop support for "less secure apps" from may 30 and onwards. Dekko and gmail are a thing of the past.

I've never touched any 20.04 branch for UT, but from Gmail's view, doesn't the "less secure apps" refer to the 16.04 base (selection of supported ciphers etc.)? Shouldn't Dekko on 20.04 appear to Gmail just as an average mail app?

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