Best posts made by ThePossessor

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.

I have 3 questions:

• I learned that the beefy arm64 server you need for development is sponsored by a company. Does this mean that your second patreon goal has no assignment? Wouldn't it be helpful to correct the second goal and maybe also to be more explicit about third one?
• The old Ubuntu Touch services seem to die one by one. Some time ago it was weather app. Are you guys looking into this? I mean proactive measures could bhave been helpful or at least finding out in time what services risk dying next and maybe get in touch with the right persons in time would be a not so bad idea.
• I like the convergence idea and I like to hear that actually some people seem to have positive experience with it. Is there any reason why you still need to drop to shell and install from server X in order to get hold of it? I am not saying that I cannot do that. I am saying I do not want to be forced to do that. Why the heck not put it in openstore?

• I totally agree about freedom of software and freedom from getting tracked everywhere I go.
• related to freedom is security. This is a major point if I want to use it as my everyday phone.
• Equally important I think is that a stable base is needed. What I mean is that it is not enough to be able to say "we have bluetooth" or "we have miracast" . I mean if it is there, it should also really be working and be compatible to thirdparty devices. Lets not get trapped but featurism . And all this does not only apply to BT and eathercast.
• Anbox will certainly make transition easier for all people coming from Android. (including me)

Personally right now things beyond this are already a bonus at the moment. In my case things that I miss are:

• vpn support for cisco (vpnc) based vpns
• great would be an integrated SIP client
• convergence could become interesting but right now other missing things are more painful und thus they seem more important.

Before I start shooting out questions, please let me put this in context. I am a day one ubuntu phone fan and supporter. I really find it great that you guys (same as me) still believe in the idea. I think this can still become great. But that doesnt keep me from having questions.

• About the ubports webpage.... It does not seem to be updated since quite a few weeks. Voted devices and information about donations for supporting a specific port have note changed for quite some time. This is not exactly encouraging more donations or help. How comes this is not updated for so much time?
• In my opinion a port to a *current" platform like the op3 would be helpful to convince people about the advantages of ubuntu phone. When is this planned to become reality? It seems to make very little progress since quite some time...
• to follow up on op3 ... does it include a port to op3t? It is not clearly stated anywhere.
• I have been supporting ubuntu phone since the beginning, but astonishingly they have not been fixing basic features up to today when canonical has given up. I am talking e.g. about bluetooth car headset support that has not worked with any of my ubuntu phone devices. What is planned on your side in this? In my opinion it is a no go for many people if such basic functions are not working. Especially if you consider that in many counties car headsets are required to be allowed to use the phone while driving.
• what will happen with convergence? will canonical continue to push their snaps idea? What about ubports devices, will they do so (too)?
• finally about miracast. Even though I have multiple different ubuntu devices and tried with multiple different miracast dongles and TV sets, I did not manage to find a working combination. How comes? Is this expected to change? (soon?)

@hudson
Hi, I can understand that you miss the today scope. The aggregation feature was really nice to have a few goodies for daily use. Unfortunately there is not enough of us in the community for this to be considered to matter somehow.
A while ago there was a discussion about scopes or not. Not enough people voted to continue support for aggregation scopes in some form. The reasons you hear range from "nobody wants to maintain them" to "their implementation is not nice" .
The short is that scopes do not matter at all to the core team and nobody else from the community has picked up the problem to get it solved. So unless you can maintain them yourself or you know someone who can, you will have to accept that they are gone. R.I.P.

It is the day of the month. It will advance by one each day.

Sadly all you say is true. But for some reason not many people seem to care. At least people don't take the effort to say that they want to keep Today scope alive. I want the weather info back, I want the list of holidays and all other goodies it provides back.

Does really nobody care? Tell the guys at ubports that it matters.

I don't want to be left with a text console only phone in a year from now. Not that I don't like text consoles - I use them for work every day. But is it too much luxury to expect a few everyday use goodies on my phone?

I made some further tests by rebooting at different points of basic setup process.
This way I found out that booting is not working anymore after timezone setup.
I then first removed timezone settings with adb shell in the first boot. After this I was able to reboot successfully multiple times.
I then configured a different timezone. After this I could still reboot fine.
To crosscheck I configured the timezone I usually choose. The problem was back,

"Europe/Berlin" works but "Europe/Luxembourg" does not.

Just weird.

Wow guys - this seems to have gone a bit out of control.

Sometimes stating the obvious IS necessary. Bluetooth still has a lot of issues. To keep silence about it will not get it fixed. And yes it affects many people. Not all of us know about the technical reasons or even not all know that due to these reasons the state of Bluetooth support may differ among UT devices.

So OK it cannot get fixed in 10 minutes. Is there a plan or do we rely on the community to spontaneously fix it? How about someone would take the lead here?

In my understanding this all started with a simple request for information. Nothing more.