@68k_dude That's what i thought after the first post also, but then the thread seem to be more about being different. :-)
I think the way it i now goes well with ubports.com, but i think it would be nice to be a little bit more clear in the startup. Maybe adding "by UBports" after/under "Ubuntu Touch" or something like that. And if they would have kept the robot, it would have been more clear as well. :-)
@doniks Thank you for your reply. In every log for desktop application (like application-legacy-container-identifier_firefox_0.0-.log) I have got this:
Fatal server error:
(EE) Failed to connect to Mir: Failed to connect: not accepted by server
@Tobisch No its all done via the PC. Install the magic device tool on the PC and use the terminal. Look up the magic device tool pages on git hub or in your PC browser and all you need comes up.
All other system and app update come straight through to your device.
That pointer to their developer documentation on Oxide is very useful!
If anybody with connections back to Ubuntu can pass the word, the "Updating the Chromium version" text just has "TBD". For the long-term viability of UBports, it would be amazingly helpful if a Ubuntu wizard could fill in some details there!
@Lakota I got mine for the M10 and the E5 later today. Both of them worked all OK, but there was no notification to let me know there was an update. Also the look on the M10 and the E5 is different, but I have the update.
Thanks guys for all your posts and words of help. I have over the last few days, been able to get UBPorts on my M10 (after a lot of trying) and now I have r1 under Settings > About >Build Number. It does take a long time to boot up and sticks on the 'Powered by Ubuntu' screen for around 3 minutes, then I see the U|BPorts logon with the flashing dots.
I must say that I was hoping to have more visual ways to tell that I was on UBPorts though. After the first boot up I checked the Settings, but could not tell if I was in UT or U|BPorts, so I rebooted to check that I had the UBPorts logo on boot. To versify the update had worked correct. We need to make U|BPorts look different, so you can tell the difference.
Initially I emailed Marius from the MDT site. Thankfully he replied and gave me the following link (sudo snap install magic-device-tool --devmode). I removed my previous version of MDT and installed the devmode version. This found my device and started the porting process. However, after it had finished I looked and it had installed the previous (clean) version of Touch.
So I then went on to the devices.ubports.com site and followed the 'Install using system-image server' method. This worked and now I am running UBPorts. This means that I can have Dekko 2, winch I really like.
Thanks again for all your help and thanks to Marius.