@newguy Not sure if that is possible at the moment.

@ubportsfanboy sounds like a very nice idea...

That's pretty nice, @wilfridd! Are you interested to join our QA team? We can definitely use dedicated people like you! You can join our telegram group at t.me/ubports_qa_team. Everyone who's interested to help is welcome, ofc!

We used a similar spreadsheet to test in the past, i uploaded it to nextcloud so everyone can edit it in their browsers, you'll find the link and password in the group. I won't post it in public to avoid vandalism.

At some point in the future it would be awesome to have a tool to organize this more efficiently, if anyone has recommendations, be sure to speak up!

@zx81 it probably is the power button, mine at times only works on the bottom half of switch other times nothing happens for a few seconds. just an aside you say its not the battery. when you connect it to the charger do you see a battery graphic appear at all even for a few seconds. If not it might well be the battery.

Hey there, yes, that is a good idea. We'll evaluate our financial options again and check out if it's possible to start doing this before the foundation is here. Can't promise you a time, but we will definitely eventually have t-shirts!

And so say all of us
Thank You All. 🗣

Amazing information Kugi, thank you! As soon as I go back at work, I "WILL NOT USE IT" to open Ubuntu x-apps on Windows 😜

Very good job indeed.

Merry Christmas!

Matteo

Thanks for your reply, I get the same message as in that bug report:

WebGL is disabled on Android unless the GPU runs in a separate process or reset notification is supported
Disabled Features: webgl

I am happy to hear that all legacy will get xenial too. Big thank you to all of you. Great work...

@tupp

Yes, modified

Interesting article. Thanks for sharing it, @libremax

@wgarcia Thanks, fixed

I also think about switching

@twinkybot The story with HP and the Intel Management Engine? Its a problem of Intel, you can virtually control every server in the business segment remotely, and with smal mistakes in this firmware also exploit it. Why these featuresa re turned on by default, and cannot be turned off? And why do they produce batches for the US government that dont have them turned off? Guess 😉

BR

@Flohack Thanks for your answer
That's what I had heard from Marius before and recently about the difficulty of getting developers to get involved given the lack of technical documentation and as a result of the heavy investment in time before they could start contributing code.
I hope that a solution will be found. I am sorry for not being of any help in this regard.

One french guy made some progress here. See the relevant video and github.

[https://www.youtube.com/watch?v=HYm4RUwwo5Q](link url)

[https://github.com/ubports/docs.ubports.com/pull/30](link url)

On a sidenote, we indeed haven't done our best yet to provide all the information about our needs for UX.
The website is currently going to be refreshed, so we'd ask you to stay tuned for further updates 😃

As you all properly pointed out, one of first goals is to provide consistency. Or, at an higher level, coherence.

At the moment we're approaching a transition from Ubuntu Vivid to Xenial, and we will be tied to a different toolkit (QtQuick Controls 2, shortly QQC2[1]).

Our effort is to port the Suru design to QQC2; in this regard, we're creating a new style for the components. Here's a very early video, the style is based on Vanilla Design[2].

https://www.youtube.com/watch?v=0ahCT7yqr08&feature=youtu.be

With the new toolkit, which offers less control on how components behave, and all the features that convergence brings, including the ability to run apps that hasn't been designed for Ubuntu Touch, we can expect some obstacle in fully implement the current set of specifications.

Our hope is that it could turn in an opportunity to refresh our Suru specifications.

The full documentation for the current Suru design is not available or, in some parts, outdated (mid-2013, when Suru was still using those odd gradients).
The same documentation available on docs.ubuntu.com has never been completed during the last four years.

In the meantime, we have seen the raise of new UX trends, one of the controversial components (the bottom navigation) has been officially adopted by the Material guidelines, and Canonical decided to drop its Ayatana project (i.e. Unity 7) and adopt the GNOME 3 HIG.

What we need is help and guidance through these multiple inputs, in order to fix some of the current issues in usability, and eventually validate the design of new UI components. In a longer term, we might want to support an effort to revisit the current design guidelines.

I saw you've been interested by the recent changes in clock-app.
Feel free to open a new issue, or join existing discussions at: https://github.com/ubports/clock-app/issues

Thank you again!

======

[1] https://doc.qt.io/qt-5/qtquickcontrols2-index.html
[2] https://github.com/ubuntudesign/vanilla-design

When I flushed mine I had no luck with the magic device tool, but in saying that it did work nice and sweet with my E5. I also had no luck with the UBPorts installer. So in the end I gave installing from the server and that worked sweet as a nut. No issues what so ever this way and worked first time. Personally I would only use this method again if I was to do my other two M10''s.

Yes it is a bit old now but for me it still does what I want it to and works great with UBPORTS. Have you had a look on ebay to see if you can get one slightly cheager?