Thanks @trainailleur it should therefore work for OnePlus One/bacon and confirmed as reported on the original how to post: https://forums.ubports.com/topic/1012/one-method-to-encrypt-home-phablet/5

@kugiigi I've only just got used to how things work now in OTA 8. I believe it would be almost impossible to judge from a textual description whether an alternative approach would be better or worse. There are so many use cases that it would take weeks to properly evaluate an actual implementation.

i found this quite by mistake this morning when i took a pic and the camera didnt freeze...then i proceeded to take 15 pictures in quick succession. Great work folks!

@AlainW94 Well the API currently misses not the whole notifications but to give the led more colors and more blinking patterns.

@advocatux Thanks. Confirms that no image builds for vegetahd since 27.02.
I wonder why though. Looks like only Nexus 5, FP2 and OPO has builds since that date.

@Nick-T hi, first you need a GitHub account, of course 😉 . For OTA-8 related issues, you can introduce your feedback at https://github.com/orgs/ubports/projects/8.

For general UT issues, the place to file a bug report is https://github.com/ubports/ubuntu-touch/issues

What do you mean by "I had to switch to English language [...]"? The OTA updates should work no matter the language you're using. For example, I have my devices set to Spanish and I don't have any trouble updating.

@chaseadam All the current info is here https://forums.ubports.com/topic/1676/development-testers-for-anbox/155

@michaljenicek13 All the info you need should be in this thread https://forums.ubports.com/topic/1676/development-testers-for-anbox

@guy Please do not post the same question in two places at the same time. It will not get answered any quicker. I have deleted this one and left the other.

Hey @chrisc, the issue you opened has been closed. Can you check to ensure it is working correctly?

some updates are not be visible on Github i see. Would like to help test while on devel channel

Note that upgrading to 5.12 also means even more work on 18.04 on top of the work needed on 16.04, since it likely also breaks compatibility for Qt/KDE apps and libraries there, necessitating we provide rebuilds of the packages broken by the upgrade. With 5.9, we only really need to do this on 16.04 (though the install on x86 is still broken there anyway).

We also have no idea what parts of our own stuff (UITK, etc…) might be broken by 5.12. If it is significant, upgrading Qt could turn into another quite lengthy project, and one that brings numerous new bugs along with it.

Alarm clock now seems to work (3 days in a row). Looks like existing alarms were ignored after an ota-update. This should not happen, it makes the device unreliable for daily use.
The indicator on the lock screen still does not show the alarm, maybe because it is a repeating alarm. I think that should be fixed too.
I will change the bug report in this way, thanks for testing to find the problem.

As we near the OTA-6 release, I would like to gather what I believe are the most important points from this post:

Everyone wants "release faster", without a doubt. "Release faster" depends on having enough confidence that software being released to stable is well-tested, which we do not have. Some things which would translate into more release confidence include: Automated tests on all system components Integration tests between system components Automated full-device testing, such as Canonical's fabled "Frankenstein device lab" Formalized manual testing by users who can confirm stability Even with full release confidence (but especially without), an automatic release model requires the ability to roll back to a previous version of apps and the full system image Aside: I want to experiment with one of the new atomic release models like OSTree which allows agnostic packaging formats to be installed on top. From my quick foray, I see: Benefits: Automatic and manual rollbacks, automatic diffing, and switchable roots Drawbacks that make this a long-term or impossible idea for our existing devices Probably requires newer kernel versions than 3.4 or 3.10 We don't have enough engineering power to concoct a solution which would allow converting a system-image system to OSTree in-flight, so we'd probably require users to manually switch.

I think that bringing up the edge channel as a place to do a large migrations out-of-band with the normal release cadence is going to have a huge impact on how quickly we can release in the future. Previously, @mariogrip's work on bringing us to upstream Libhybris would have had to wait until after OTA-6 lands, and then it would have delayed OTA-7 until we had proper confidence in it. With edge, we can have people help us test these huge changes with the ability to roll back and without disrupting current users.

To respond to my earlier hindsight: OTA-6 was not (yet 😛 ) taken away by TDS. We did not hit the original deadline set, but we will still be within our 6-8 week cycle when it releases. This includes our testing and release admin stage, which we are currently in. All of this while I'm not sweating bullets from pushing a release on ourselves before we're sure we're ready.

We have ended up in "Gotta release slower" in this cycle without a doubt. I hope to make the improvements we've identified here so "gotta release fast" can become a reality. I also hope to be able to take our release management up so that we hit 2-4 weeks development, 2 weeks testing. This means we'll get faster releases, but we still won't hit fast releases. 😛

Important note for anyone interested in contributing to... basically anything I've said here: I'll be holding an OTA-7 development meeting at the start of the cycle where we'll discuss how we want to improve during the OTA-7 cycle and taking bugs from the tracker for the release. Only assigned tickets will be added to this milestone, so if you have a pet bug that you want fixed now is the time to get involved to help fix it! Subscribe to this GitLab issue for more information as the day draws nearer.

You're not that horrible, @unisuperbox. 😉

@dobey said in Language packs as click packages: call to arms!:

@mardy Are we discussing language packs as clicks, or a more general solution to "what apps are installed by default" when flashing a phone? Because those seem like two separate things, and we should not use one of them as a reason to do another thing (or to not do some other different thing instead), I think.

I'm not using one as a reason to do the other, but rather I'm explaining how I imagine this evolving into, to convince you that we can get a nice user experience even with selectable language packs.

I also disagree with the idea of anecdotal argumentation of well, it's a waste in the rootfs for me, so why should it be there for others. I think it would be best to not go down this route. There are plenty of things in the rootfs which are meaningless for me too.

And what I'm suggesting is that, if those things could easily be installed as clicks, and if doing so would save a considerable amount of space, then it's something we might want to try out. It's a question on whether it's worth the effort.
I did start with language packs because I thought that it would be an easy pick, since they are data-only. And so far it looks like it's something easily doable.

[...]

Maybe having langpacks is something we will need to do in the future. But I think right now, we should not rush into this as a solution to the problems we have, as there are plenty of larger concerns at the moment. And if we rush into it, we will be stuck for a long time, even if we discover some other solutions to whatever problem this is meant to solve, instead.

I'm not requesting that people spend their time on this. If @bhdouglass told me that he has no time to review the changes I'll eventually submit to the Open Store, then I certainly wouldn't force him, but it looks like he likes the idea as well.
And I'll try not to rush: I do want to see a good implementation of this (especially because, as I said, I plan to apply a similar scheme for navigation data, later on).

Could I spend my time in a better way? Probably, but I'm doing this as a hobby in my spare time, so I tend to work on those things that interest me first 🙂

I tried to find a pattern to reproduce this issue. But there is none. The best way is to restart the phone, open the browser + uapp-explorer+youtube-app. Load something and begin switching. Mostly it works in the actual RC channel well, then something starts hanging which makes the browser restart and reload the startpage.
Same thing happens with browser+N5-camera that crashes. Email i didnt test since dekko2 has problems.
I also saw with systemsettings., but not often.
Could be an out of memory issue, but i could not trigger it...