The RC images have been respun to include the fix for an issue with private browsing in Morph Browser: https://github.com/ubports/morph-browser/issues/237

Please update your devices and continue testing.

This forum post is a companion to the OTA-11 call for testing blog post.

Please post any general observations you have while testing the current image in the rc channel, as compared to OTA-10, in this thread.

If you have any comments on any of the specific issues in the OTA-11 tracker, please post them in the issue thread so they are easier to track.

This is not a place to request more bugs be added to the scope for this release. We'll experience death by a thousand cuts if we allow adding "just one more thing" to the release again. We want to make sure that the bugs labeled as fixed are actually fixed so we can get improvements out to the Stable channel.

No, remounting the system as read-only is not undone after the terminal is closed. It's also more possible to break the system when it is mounted read-write and OTA updates may erase your changes. Overall, I think you'll be very upset with using the system this way.

The best way to install packages from the Ubuntu archives on your device is with Libertine: https://docs.ubports.com/en/latest/userguide/dailyuse/libertine.html

@dtarrant, there's a lot to unpack there. I don't think we'll be able to do it justice as part of an hour show, or even if we dedicated the whole episode to it.

@kugiigi

The A64 cannot handle multiple displays unless you're lucky with the display timings. For the most part we'll have to handle using either the internal or external display.

@jezek

No. Bespoke ARM images can only be installed to their target devices. Similarly to phone images.

UPDATE September 22 11am Pacific:

Inexplicably, a Huawei spokesperson reached out to Android Authority to clarify that Huawei, in fact, has no plans to unlock the Mate 30 Series bootloader, directly contradicting what CEO Richard Yu said in his Q&A with the site.

I'm happy to say that all of the messages in the thread so far will be covered in the News section, with the exception of SimJacker. That is, indeed, an issue that we may never be able to solve. Please consult with your mobile carrier to insist they mitigate the issue by blocking the malicious messages.

@errorcodevortex, we're trying to help the best we can. I'm speaking to you as the development manager of Ubuntu Touch, and I'm here in that capacity. I hope that is "good enough" or close enough to "knowing what I'm talking about" for you. I'm telling you that I have never done what you are trying to do, and I don't think it'll work the way you're trying to make it work. I base that on my knowledge of the system as the manager of development. We haven't done what you're trying to do, so all we can do is try to guide you to find the answers you need.

If our answers aren't what you want and you know you can do what you're trying to do, please do it. Find a way to do it. Prove us wrong, and shove it in our faces with a guide for how to do it. But respectfully though.

You are misunderstanding how Ubuntu Touch and Anbox work. Please, read what others are replying to you and take this on board. We're really trying to help you be successful with Ubuntu Touch... please don't take this as trying to attack you in any way..

When you run adb shell and are presented with phablet@ubuntu-phablet, you have shell access to an Ubuntu system. Not an Android system. The layout of files is very different from Android. Ubuntu Touch is not an Android ROM. It is an Ubuntu system which runs on Android hardware.

Anbox is not a complete install of Android. It is a container which can be used to run some Android apps from the Ubuntu Touch environment. You will not be able to do everything you are able to do in Android within Anbox. If that is all you want, I suggest flashing Lineage and forgetting about this. Ubuntu Touch will not provide you with what you want on your mobile device. It's a waste of your time to try to continue this way.

Anbox will probably not pass SafetyNet ever. For that reason, Magisk will not be useful to you. The use of Magisk is to modify your Android system without actually modifying it, allowing all of the security checks to succeed

I think you might be jumping in on the deep end before knowing how to tread water... Ubuntu Touch does not work the way you expect it to. It will not work the way you expect it to. My suggestion is to poke around the Ubuntu shell first. Check out how things are working, see what's running, see how it boots and runs. Read our software development guides to learn how software is packaged and installed, and maybe the porting guide to learn how the system becomes compatible with Android hardware. Next, check out the code for Anbox. The documentation is a bit sparse, but you'll need to understand its code to know what's really going on. Then, you may have more insight to look into using Magisk.