member of the board, developer of the installer
Hey porters,
we have just landed an overhaul of our devices page and would like to encourage you all to list your devices there more early to make upcoming ports easier to discover. Adding new entries can now be done by creating a merge request with a markdown file that contains a YAML metadata block.
We invite you all to help us complete and refine the entries, because the community probably knows best about all the different ports 
Cheers,
Jan
Here's the official GitHub Statement and a blog post from Nadella.
I wouldn't make this so much about feelings. Let's face it: Microsoft is not evil. But Microsoft isn't necessarily good, either. Microsoft is just a very big company doing what they think is best for their business, and that doesn't always mean it's what's best for everyone else. And yes, they're dabbling with some open-source stuff, but only where it's required or at least very difficult to justify not to have it open. Microsoft wants to stay in control. They already lost the windows-server market to the "foss revolution", so they understood that they have to join the winning team if they want to stay on top. That alone doesn't make them evil. In fact, most companies work that way (even GitHub always has, that's why the GitHub server is proprietary), but they could still change. So let's give them credit for embracing foss where they are and encourage them to abandon their proprietary projects and selfish business techniques. They're saying they aren't the enemy, let's believe them that. But that doesn't automatically make them our friends.
What's worrying to me about this potential acquisition is that it will concentrate too much power with one entity, and that can't be good. This is a development that has been going on for a while now, the FOSS community made the mistake to place too much trust in GitHub for a long time.
GitLab is different that way. It's still a for-profit company behind it, but the client is open-source. You can even host it yourself, and even though real federation is not there yet, it's a lot more likely to come.
The biggest problem GitLab has at the moment is that it's a lot smaller than GitHub. GitHub has 27 million users and 49 million repositories, [GitLab only has 100.000 users/groups (even though that number seems to be pretty old). When we moved UBports from Launchpad to GitHub a little more than a year ago, we discussed GitLab as an option as well, but dismissed it because of lack of adoption. Since then, Gnome has proven that it's possible to move a big open source project to GitLab, and it worked for them.
All in all, i have to say i'm in favor of moving, but i would not rush things. The migration itself is pretty straightforward thanks to great tools, but there's a lot of stuff around it that needs to be modified. Most work will probably be updating the documentation and workflows. Worth it, but no need to rush it. We could make some preparations now, really analyze what to look out for, and make the move after OTA-4.
And for the lack of users, build it and he will come i guess 
Hey Alan,
thanks for the writeup, that is a great explanation, especially for our non-technical users.
I can confirm that the switch to xenial is on the horizon. After the release of OTA-3 (which still uses vivid), it's full steam ahead with xenial work. To quote what Marius' famous words: "We want to walk up the stairs, not jump up the stairs," so i don't know what mir version the initial stable release of ubuntu touch on xenial will use, but i've seen the Wayland tests already working on some phones, so who knows... In the long run, Ubuntu Touch will ideally just use the latest stable version of Mir, we should not allow for another big backlock like the current one to accumulate. I'll restrain myself from using the stairs quote again.
It's great to see support from Canonical(-employees) here, thanks a lot Alan! I hope it will be a fruitful collaboration, without your continued work on Mir our already big task would be a lot more difficult. I'm sure you will also profit from us as an active downstream project that uses Mir.
Cheers,
Jan
"Explicit is better than Implicit" is a great principle for programming language design, but a user-friendly user-interface plays by different rules. In UX design, actions should be intuitive, and what could be more intuitive than tapping the background to get to the background?
If you think there needs to be a text or icon to hint for this action as well, ok, maybe. But it should be way more subtle than in the mockup. For me, the Application spread is one of the most distinctive and beautiful features of Unity 8, we can't f*** (mess) this one up.
A go-to-desktop-app in the spread... I don't know. Being able to just tap the background feels way more practical to me. Either the go-to-desktop-app would always be in the end of the spread, which would cost you time, or it would be somewhere in the list making it more difficult to find an application you want to switch to. Why add another UI element, if there's already a perfectly good option we can go with that doesn't bloat the UI nor reduce ease of use of the existing usecases?
On the topic of what is home, might i add:
Don't kill the desktop: A manifesto
In my opinion, Unity 8 should become a proper desktop environment, and that includes being able to put stuff on your desktop. Doesn't have to be applications (unless the user wants to, then let them do it), but it would also be incredibly useful for short-lived files. For example, i'm very often travelling by train in Germany, and since we don't have a ticketing app for Ubuntu Touch, i always put the ticket-pdf on my phone and open it in document viewer. That's something i would put on my desktop. Yes, i know, Gnome removed that feature a while back. But for many people that is a standard feature of Desktop Environments and it would be foolish to dismiss it as a legacy usecase. For me, it is clear. The desktop is my 127.0.0.1. And i'd love an easy way to get there.
I'm with @Flohack on this one. We should only have the real essentials as core apps preinstalled. In my opinion these are:
@WLBI It's not set in stone how soon this will be available, but we will support Anbox (Native Andorid app compatibility), so you will be able to run DB Navigator and clever-tanken if you can get your hands on the apks. Anbox already works(-ish) on Ubuntu Touch and it might even (as soon as it's stable, but not in our first release) be pre-installed.
Hey all, just wanted to give you a heads up that UBports Installer 0.5.6-beta is now in prerelease stage and it includes some stuff i know some of you have been waiting for. If your port needs to flash files that we can't re-host or download automatically, you can use the new manual_download step to have the user download something for the installer to work with afterwards. If your fastboot flash needs some of the new-fangled cli flags like --disable-verity or --disable-verification, the new flags array on the files object has got you covered. Use caution with these, don't be lazy
You can find more information on the release page. Also see the call for testing.
Let me know if we need anything else to make your port work with the installer, or if you have any other thoughts how i could make your lives as porters more enjoyable.
Cheers, and happy hacking!
If you want to chat about Ubuntu Touch and its related projects, you've come to the right place!
Here are some tips to help you get the most of this forum:
You're familiar with the process by now: UBports Installer 0.6.0-beta is in prerelease stage and needs your attention. The good news: The Installer now features a GUI for automatic reporting, to OPEN-CUTS, making automatic reporting even easier!
You can find all packages along with an extensive changelog on the release page.Take it for a spin with your favorite device and push that button to let us know how it went. Thank you for your help!
Hey everybody, sorry about the late reply. I just had a report of a successful fix for this on Telegram. The user who had the exact same problem was coming from CyanogenMod 11, while our HAL-container for the Oneplus One is based on CyanogenMod 12. What you can do is flash the firmware of CyanogenMod 12. Download this zip file, extract it and open a terminal in the folder containing the files. Then, reboot your phone to fastboot/bootloader mode and connect your device with a usb cable. Run the following commands to flash the firmware:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Making a mistake at this stage can brick your device, so please make sure no of the commands return an error. Last but not least, reboot the device.
Why does it have to be one or the other, when we can do both? The other selling points of Ubuntu Touch don't magically go away just because it can also run android apps.
Having Android app compatibility helps lower the entry bar for many users. I'm not talking about the general public and people without any interest in Linux and free software, i'm talking about Linux users that still need (not because they want to use them, because they have to) certain apps, like WhatsApp, Snapchat, etc. Even some UBports team member even carry an iPhone or Android phone additionally to their Ubuntu Touch device with them in order to use these (not pointing fingers here). That is ridiculous, and if we can avoid that, why wouldn't we? Sure, you can dislike these apps, but if you need WhatsApp for your work, what are you going to do about it?
Another thing that is disregarded in my opinion is the open nature of this project. A (imho) unique selling point of Ubuntu Touch is the fact, that it let's you use your phone like a real computer. I'm not talking about attaching a screen, mouse and keyboard here, i'm talking about the open nature of the OS. You should be allowed to run whatever weird-ass piece of software you find, just like on the Linux desktop. And Anbox already works on the Linux desktop (in fact, it already works more or less on the phone as well), so artificially breaking compatibility would seem really weird to me. If i want to run something on my phone, who the f*ck are you to tell me not to do so?
The argument that Android compatibility would discourage developers from creating native apps for Ubuntu Touch is only valid up to a certain point. Big for-profit companies don't care about Ubuntu Touch, the market is way too small for that. There won't be a native Whatsapp client, there won't be a Netfilx app, that's just how it is. Again, you can go all Stallman about it and say that you don't want to use these services anyways (and you are probably right), but until there are alternatives, it is kind of necessary for many people.
What's also disregarded in the discussion about the unavailability of Google Mobile Services is how many apps work perfectly fine without them. 2300+ free and open source apps from f-droid change the math a lot. Also, many of the Apps from Google Play are available as Apk downloads, and can be used without Google Mobile Services.
Last but not least, i want to remind you a) how hard it is to develop Apps for Ubuntu Touch at the moment (ask @DanChapman, he will sing you a song about it) and b) how much work it is to maintain the SDK. UBports only has a very small and busy team, so having Android compatibility just takes the pressure of for now. It is by far not an ideal solution, but it could help a lot of people using Ubuntu Touch as a daily driver, and that's what we're aiming at after all. We don't want (and we won't) make Ubuntu Touch just another Android rom, we have unique advantages that won't go away. We will still have native apps. But having Android compatibility is the right decision for now.
Here we go again: Hopefully the last release in the series of major backend-refactoring efforts. This one implements a new specification for the installer's config files, which allowed us to re-design the engine that translates configs into runnable steps from the ground up and correct some mistakes of the past. We're now at 56% unit test coverage on the installer itself (with all of our internal libraries sitting at 100%), and we are now unblocked from getting the installer to 100 % as well. Before we can do that, however, we need to do a full pre-release user testing session with all devices. This will hopefully be the last time we have to do it this diligently, so let's make it count!
@poVoq Sure, i'm open to including any and all operating systems! I opened an issue about it a while back, happy to hear your input on weather pmbootstrap should be wrapped or re-implemented: https://github.com/ubports/ubports-installer/issues/1396
Another UBports Installer pre-release is ready for testing:
This one was all about re-factoring the installer's own source code. not many new features, but massive changes to improve stability and maintainability. Let's do thorough QA to make sure I did not mess anything up ^^
Sorry for the quick iterations, here's yet another one:
Due to time constraints, we had to squeeze another minor thing in.
This maintenance release improves some error handling and improves the process of re-connecting to devices if the cable is unreliable.
Alright, we found some issues that should hopefully be resolved in 0.7.2-beta. If anyone wants to test, you know what to do.
@tigerpro A fix for your heimdall issue has been prepared in the library and will be included in 0.7.3-beta, if everything goes according to plan. Sorry for the delay there.
@tigerpro Thanks for the log, that should be fixable. Will report back when i know more.
nor can i figure out how to bring up opencuts mid-install
either by clicking report a bug in the top right corner or by selecting it from the global menu
This one doesn't include as many exciting features, but lands a major refactoring effort of our core background library promise-android-tools. The library is responsible for adb, fastboot, and heimdall - the communication with the device. We touched almost every function in the library, so meticulous testing is needed. See the changelog for more information.
Please download a package of your choosing from the release page and take it for a spin on your favorite device. Use the built-in reporting feature to let us know how it went. You can find out what combinations are still missing on UBports OPEN-CUTS.
Thank you for your help!
@herbi can you clarify, did this issue surface after using the installer or after starting an over-the-air upgrade from the system settings? In any case, you should be able to restore your device by using the installer, as long as there is no hardware issue.