@kugiigi closed source apps are currently allowed in the Open Store, as long as they are confined.

Of course it is now evident that apps accessing the network should be under more scrutiny. Too bad that is most apps nowadays.

@Moem Thanks for the translation. 👍

Hello jEzEk,

There are both technical and societal reasons as to why we have decided to not accept new features into the Xenial line of update anymore, even the ones which is developed against Xenial and is near ready.

First, the technical reason: due to a large number of changes involve in making all Ubuntu Touch components works with the new version of Ubuntu, compound with desire to realize the rename in this release, we've decided early on to have a separated branch of code for almost every component we have. Unfortunately, this resulted in a largely separated development between Xenial and Focal, and while one is busy making a component runs on Focal, another proceeds to add new features onto the existing codebase on Xenial. And because we didn't realize this problem early enough, this means now we have quite a backlog to visit. Also, since the code diverged a lot since we start the branches for Focal, sometimes it's not straight forward to port changes to Focal. So, limiting the amount of changes that enters Xenial directly reduces the amount of work needed to make Ubuntu Touch based on Focal a reality.

Now, the societal reason: as mentioned by many people above, we're a small group of people and unfortunately can't do everything at once. In addition to adding the amount of changes we need to carry to Focal, time spent reviewing changes for Xenial is time not spent developing or reviewing changes for Focal. Given that Xenial has been out of support for over a year at this point, it has become our priority to provide our users with the up-to-date base for the security of our users, and that means we need to reduce as much work as possible.

In addition, many people might consider Focal complete when it reaches feature parity to Xenial. However, if more changes keeps being added to Xenial, it becomes harder to realize that objective. Having to chase a moving target is not fun, and personally I already have that feeling when I realized that the contact backend changes will land in OTA-24. Fortunately that didn't happen in the end, but even for smaller features it can easily be unexpectedly hard to bring to Focal.

So, please accept my apology that we cannot accept more changes into Xenial line of update anymore. We want to have an up-to-date and secure operating system, and we cannot have that with an out-of-date base.

On the side of device support, the primary limiting factor at the moment is due to the inevitable change of the init system from Upstart to Systemd. Systemd uses a number of modern features of Linux kernel, and as such requires a (moderately) modern Linux kernel. The version of systemd requires Linux >= 3.13, however the recent version raised that a bit.

It's possible to backport certain changes into an older kernel to make systemd runs, but it's a tedious manual task that has to be done per kernel tree [1]. A rule of thumb is that if the device launches with Android 9 it should be fine, but for older devices one must check the Linux kernel version.

[1] For example, I've done such job on FP2, which allows me to run an old image of Plasma Mobile which uses systemd.

Just for clarification what happens on the next OTA re contacts:

Software has been exchanged to replace the old contacts backend with a newer one The old user data remains in your device A new Db is created, and a migrator runs one time to move all contacts into the new Db (thats the current blocker, the migrator wont start on all devices due to a very difficult datetime issue in the recovery mode) A flag file is created to not migrate more than once Google contacts sync is disabled for now

Thats all. No contacts can be lost. In case anything goes really wrong the old database is there, and with another small emergency OTA we can help all users to re-migrate it for example. So we got most of scenarios covered.

I disagree to keep this pending until everything with sync is fixed. This means we cannot release another OTA, or any update to users. This means 16.04 is dead in the water (which it is already kinda) and we come closer to a cutoff date where everything must first work in 20.04 - imagine all of what we have queued now, approx 35 items, if one of them breaks in 20.04 which is very likely, we can again not release.

Also there is no point of saying that this is ok, simply put all hands on 20.04: It still does not have a release date, and most of all a lot of devices might not get upgraded if we cannot motivate the porters to do the necessary changes.

We need to be able to push 1, 2 or even 3 more OTAs before 20.04

@jezek
Not sure in fact if it can be used with 16.04 you're right.

Here is the link to the Github repository of the PDK (Platform Development Kit):
https://github.com/ubports/ubports-pdk

@nero355
I'm french and didn't know what PF means.
We don't use those cards in France lol.

That said, happy new year everyone, with or without PF 😬🍾

@jezek If the information is any help I used 0.9 MB in six hours (= 3.6 MB per day) on a completely idle Nexus 5 today.

@jezek I have FP2 on Stable channel (so 5.1). I took the charger out yesterday evening to test, it's now a bit over 50%. Wifi was on. I didn't use it much, mostly looking at time occasionally and a bit of web browsing, but not much (maybe couple of minutes total).

Two weekends ago I managed to drain the battery in an hour or so I think, but I was constantly using the camera, so that's prob expected.

So yes, I'd say it's over 24h battery lifetime (assuming "normal" usage).

I've tried to uninstall the app, then deleted all files under ~/.cache/com.ubuntu.reminders, ~/.config/com.ubuntu.reminders and ~/.local/share/com.ubuntu.reminders directories. Then installed app again, configured Evernote account, synced and... the app crashed. Only the titles of 4 notes (out of many) got downloaded, with no text inside. Maybe it's something faulty inside the notes. Have to investigate logs. Will report if found something.

@capsia Thanks, that's good for me!

@applee Hear! Hear! 🙂

@lduboeuf yep, that text_0.txt seems familiar ^^

If someone has an idea for a test, that could identify (narrow down, rule out, ...) the culprit, I'm all ears and in testing mood.

@dobey said in Compass in Device Checklist:

@jezek said in Compass in Device Checklist:
Abstraction on what level are you talking about?

In qtubuntu-sensors.

Thank you for reminding me. I forgot, there is already an issue opened on this.

@dobey said in Indicator pull down regression on new Unity8 (rc/ver. 64):

For the second question, it would be in the unity8 repo, and in the Panel.qml iirc.

Panel.qml is the correct spot. I've poked around with the old unity, and it should just be a matter of properly defining sizes and anchors.

edit:
I see where the indicator is defined but am too much of a newbie to know what's wrong.

line 350: https://github.com/ubports/unity8/blob/xenial/qml/Panel/Panel.qml

@Luksus Wow, that worked. You are a savior. Thank you.