@Keneda Just a few 2 cents her:

• Yes for porting we often set the Android build to build a so-called userdebug image. That ensures certain behaivour, but I am unsure if we really need that. So it could be that the FP4 kernel built during our porting build is set to debug since userdebug target is being used.

Someone could explore this by trying to build their own port with instructions from porting group and then see which flag is being used. It would be good to finally address this, since debug kernels are potentially slower than release.

Sorry it took a while. I set it to 7 days, is that enough?

@discord Hi long time passed, did you achieve anything ?

Hello everyone!

The expected release date for Ubuntu Touch OTA-2 for 20.04 is Friday, July 28th 2023.

This forum post is a companion to the OTA-2 Call For Testing (appears here when its live)

Please post any general observations you have while testing the current image in the RC channel, as compared to OTA-1, in this thread. The current release candidate (RC) is 2023-W29 or newer.

Please note that only critical and security fixes will be able to enter OTA-2 as this point, normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

@Moem I am afraid no one so far did develop any middleware or App for UT to let the PineTime connect to it. Its totally feasable, but would need at least 1 or 2 devs getting their hands dirty.

Hi fellow bacon users

After some really tough challenges with recovery, fake cache and a lot of confusion, the Oneplus One finally reaches a testable state in Focal's devel channel. Now we need you!
A lot of features in this list: https://devices.ubuntu-touch.io/device/bacon/release/focal/ still show a question mark and need to be tested.
Note that this is not a daily driver yet, so do not test it on your main device.
Also very important is to only use installer version 0.10.0 with the "Bootstrap" option! do not simply change channels from inside UT.

Let us know in this thread how this worked out for you...

BR Florian

Please reinstall without data wipe, the problem is fixed in the latest OTA revision

Guys this was a bit premature,

while installing 20.04 on OPO works with manual steps, the recovery is still not prepared to allow both 16.04 / 20.04 installs (which we still must support for a time). So currently using the installer for this will result in a softbrick I guess. Be careful not to do this on your production device!

Seems smth was wrong on my side, a second attempt worked then

Humm strange, nothing should have changed but I feel I cannot install the Nexus 6P anymore with the installer, it hangs on the boot logo after recovery hast installed all things...

@messayisto sorry yes the text is from OTA-24

Hello everyone!

The expected release date for Ubuntu Touch OTA-25 is Friday, March 24th 2023. Note that this is the last release of an OTA for xenial!

This forum post is a companion to the OTA-25 Call For Testing

Please post any general observations you have while testing the current image in the RC channel, as compared to OTA-24, in this thread. The current release candidate (RC) is 2023-W11.

If you have any comments on any of the specific issues in the OTA-25 tracker, please post them in the issue thread so they are easier to track. OTA-25 tracker: https://ubports.atlassian.net/browse/YUMI-6

Please note that only critical and security fixes will be able to enter OTA-25 as this point, normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

Finally it is here: TELEports will support proxy servers!

Since this is a bigger feature, bugs could be coming as well - I am looking for tester who want to try this out first.

Please comment below if you are interested, I am preparing the test version tomorrow or so...

Note: It will be possible to enter proxy data before logging in with the phone number, so even people in troubled countries will be able to connect right away

EDIT Please grab the build for your architecture from this CI pipeline: https://gitlab.com/ubports/development/apps/teleports/-/pipelines/756937071 (in the lower part, click on green teleports button, browse into the artifacts folders and find the click :))

@developerbayman OTA updates are delta-based, so if they break your system is then hit-or-miss, if UT changed something that you also changed with apt or by editing it manually it will get overwritten/erased by an OTA delta eventually. But if that happens simply switch channels back or forth, or reinstall with the instsaller to get a full wipe, and you are back in business.

Its really not easy to break a UT install, in contrast to a desktop PC. And thats the beauty of all those restrictions, they keep you afloat as long as possible.

FYI I made this PR https://github.com/Aarontheissueguy/WaydroidHelper/pull/24 to mitigate issues with outdated Wydroid packages in the future. My Pixel 2 issue was simply that I installed Waydroid during a timeframe where it was kinda broken, but to fix it a manual intervention was necessary.

I hope when this PR is merged we will simply tell users to uninstall/reinstall Waydroid and all is fine. And there might be more users out there that have a broken install right now

@emphrath we cannot take packages from Debian instead of Ubuntu. Thats not how distro packaging works

Hello,

can anyone with a Pixel 2 try to get Waydroid running? Its installable on my GFs phone but never starts, just sits on the startup spinner...

Thx!

Some update, we have looked into the ESM repos now, and unfortunately Canonical does not offer them for ARM architecture, which is really sad. So, even though we have a free license for post-LTS updates we cannot use them

@mw4jet Sorry to say but those changes for buttons might be reverted since we faced a ton of regressions lately with upgrade to Bluetooth...

Whole Bluetooth changes will be reverted. This will delay that OTA further, unfortunately, as we need a new RC...