If I got this right, it is planned (in long term) to remove scopes. (at least in their current form)

In many cases scopes are nothing more than an always available app. The added value of such scopes is minimal.

However aggregate scopes (like today or nearby) are special and they are a distinctive feature of ubuntu touch.

warning: begin of wild thoughts
Maybe it would even make sense to generalize the aggregate feature so that the user can aggregate information in his own logic. What I mean is wouldn't it be nice to be able to create additional aggregate pages with all information sources that fit in this category for you. Some people would stick with "today" and "nearby", others would group everything in a new "everything" aggregate or else split it up in many different aggregates.
end of wild thoughts

Anyway - what is planned about aggregate scopes?
In my opinion it would be a capital mistake to loose them with no replacement at hand.

@malditobastardo Nobody is expecting a huge effort from them for this right now.

What I am talking about is letting them know that it does have some importance. The current plans seem to be letting Today scope just fade away with no plan B. And to me this does not seem an attractive way.

The guys do a good job. Just I don't always get the priorities. I want to be able to use it as a main phone again. I do not need to set a background picture on scopes for that. But I do need a lot of the stuff from today scope. Weather is one of them.

In order of decreasing importance:

• stability and bug fixes in general.
• bluetooth in general and in particular improve car kit support. I only know one working combination and it's sound quality is a nightmare.
• re-add more of the missing canonical core functionality in particular some missing parts of today and nearby scopes (dayinfo (!!), holidays, where I am, etc) I understand that in long term scopes may not continue to exist the way they are now, but for now many facilities from the aggregate scopes are something that I miss in everyday use. They can be deactivated by default. But I believe the user should have the choice to switch them on if he wants to.
• aethercast support. You don't always have a cable at hand and more and more TV sets support miracast natively. Why not use it when it is so close?

Keep up the good work!

Just in case you guys missed it here , there is an interesting article that @3T_Ed pointed me to.

The article is quite long and not everything may be of interest, possibly also some facts might not be 100% reliable, but the article gives a good overview of what all went wrong. Judge for yourself.

Thanks again @3T_Ed .

Hi - I would like to add a few question to those that @tomoqv has:

1. I would like to propose a more detailed way to present what is working in xenial or not. Right now it is essentially guessing and trying on all the different devices and versions. What I mean is something like a table or matrix showing different functions as rows and the devices as columns. One row could be for flawless booting. In the Nexus 5 column (from my experience this works 8 out of 10 times) this could be "8/10" . A different row could be Miracast "0/10" . Then also Bluetooth Headsets, WiFi, Hotspot or Printer could be other rows with per device scores. It is a pain in a...rm to have no overview on status and possible progresses.
2. Another thing I would find useful is creating a simple way to install Beta or even if this is what the user wants Alpha releases of things like the new webbrowser, anbox or other "experiments" . A good way could be by creating a "Beta channel" for this in openstore. This channel could then be enabled if users feel adventurous. The main point is not every user wants to mess around with terminal for this - even if he is easily able to.
3. It has been so long that @mariogrip is teasing everyone with a "kindof" working port to Oneplus3 . How about making this (and maybe others) available for install by ubports-installer? (You could then also add it to the table mentioned under 1. point)

Please don't get me wrong. I am a supporter. I see immense potential. But when you want support, it is usually better be able to provide visible progress steps. And sometimes this means working on goals one after the other (and reach single goals faster) rather than working on all of them simultaneously and none of them gets completed. (I over emphasized this in order to make the point clearer.)

Hi all. As stupid of a question as this may seem... Is anyone aware of a working combination of a bluetooth carkit and a 16.04 UT device? Both phone calls and music streaming via bluetooth are of interest to me.

So far none of the combinations I tried were anything better than horrible.

I can't really imagine that no working combination exists.

I didn't find a working combination within all combinations of 4 carkits and 3 UT devices. But I cant really pretend to try them all.

After unsuccessfully trying multiple times, I not only wiped all partitions, but also formatted Data Partition in the first step. This seems to have made the difference.

@vince1171 Ubuntu-touch is successfully installed on my Oneplus3. Cheers

I am curious: what happened to librem 5 UBports port?

While quite some months ago we saw quick progress, at some point for some reason it was more or less "wiped" from UBports site. What's the story behind this?

Purism recently claimed that hardware will be shipped "late November 2020". Will there still be a port available?

Congratulations for the release of 16.04 stable channel! Good work!

Now that this primary goal is reached, what will be upcoming priorities?

A few suggestions that come to my mind in decreasing importance

• browser next
• bluetooth car kits compatibility
• miracast TV set compatibility (maybe including support on additional existing UT devices)
• Halium support and halium device ports (we do need UT on a premium device like OP3!)
• convergence
• a replacement for aggregate scopes. (maybe something like widgets?)

I was trying to find information on how to set up a halium device to see the progress on ubports halium port. There is quite a few documentation on how to build halium in general and a general description on how to do a port. This is nice that we have it, but do we really all have to go through the same hassle of compile and figuring out the details of how to put it on our device?

The question really is: are some of these halium ports advanced enough to integrate them in a separate tree in the ubports installer? (I don't care if it is called edge or just halium)

Of course we have to be aware that this might mean installing alpha or even pre-alpha. But I am pretty sure many would like to able to give these versions a try on a currently unsupported new halium device.

@rubencarneiro from what I found on the internet the OP3 and OP3T logo format might not be identical. It seems that OP3T uses a slightly modified format that is the same as OP5. However I was not able to verify this.

@rubencarneiro I extracted the images present in the OP3(T) "recovery.zip" with a tool I found on xda forum. The logo in the zip file is the same as the default one. It does not contain the nice UT design you made.

Maybe only the link that you provided is wrong? When I think about it... "recovery.zip" really indicates what it does. It recovers original images.

@rubencarneiro it tells me I am not allowed to do this if I directly try flashing it with fastboot.

The confusing part is that I can use twrp to replace the boot logo with other alternate logo archives. When I then try again with the supplied file from here, it just reverts to stock oneplus android logo. It seems like that zip just contains the original oneplus android logo.

@thilov I followed your instructions with the same result. The bootlogo is not replaced.

I used twrp-3.4.0-0-oneplus3 however my phone is a oneplus 3 only.

Also it is important to say that twrp gives an error while installing the zip:

I am out of further ideas.

@thilov Thanks for your reply. Do I need to use a specific version of twrp? What steps made it work for you? Do you use a 3T or a plain Oneplus 3?

A really nice set of bootlogos!

I successfully put one on a Meizu MX4 and a Nexus5. No Problems encountered.

I then tried Oneplus3. Instructions are confusing. Why boot to fastboot and then to recovery? And how do I use recovery to flash this zip file? Somehow I didn't figure out how to proceed to make it work. I even tried with twrp. Does someone have a more complete description of what to do? Can I use the normal ubuntu recovery at all to flash it?

Help would be appreciated.

@arubislander Thanks for clarifying things about this. Actually the main interest I saw in the article was to have some insight to many misunderstandings and miscommunications that happened in this collaboration and how this is still somehow hindering things now. Until this article I was not aware of some of those things.
And yes - unfortunately one always needs to be careful when people state things as facts.

@AppLee this can indeed be useful for extra paranoid use cases. I guess it should however not be enabled by default. Network security is not always happy about new unknown MAC addresses in the private Wifi.

@Giiba Thanks for the info. Good to know it is already in the focus.

Just in case you guys missed it here , there is an interesting article that @3T_Ed pointed me to.

The article is quite long and not everything may be of interest, possibly also some facts might not be 100% reliable, but the article gives a good overview of what all went wrong. Judge for yourself.

Thanks again @3T_Ed .