Also daily driving the N10 on 24.04.1 daily channel. It works great for me, but there is one issue regarding if you are on WiFi and receive an MMS, your MMS may stop working. But I don't use WiFi very much, so it was not a big deal for me.

I bought the 2028 variant, and I had to hack the settings.xml, I wrote a little blog post about it, but you are probably smart enough to do it without my input. Still, if you want to see the step by step and the pitfall I ran into, here it is:

https://alaskalinuxuser3.ddns.net/Ubuntu Touch works on AT&Ts whitelist.html

Also, if you purchase refurbished models from Amazon, that seems to be confirmed to work with OnePlus to get the unlock token.

I think you actually want the 24.04.1x daily channel. My N10 5G only has volte on daily, not stable or rc.

Uhmm.... I'll be honest, I don't know how to take your last few posts. I'm not sure what you are trying to tell me.

@developerbayman

That's great!
Do you mind if I tinker on it a bit? Then I can upload my copy (like on gitlab) so you can see the changes? Mainly working on adding content hub so the end user can pick roms that they have stored on their phone.

With that said, yours comes with alot of roms built in, but aren't there license issues with distributing those roms? For the one I was tinkering on, I dropped all the roms and put in several open source home brew roms, like D Pad Hero I & II, which are GPLv3.

I don't want to hijack your project though. Just thought I'd help out with this one, because it is interesting to me. Whatever you release is completely up to you.

@developerbayman
There is some neat stuff in your repos.
A question, the NES emulator, which nesjs did it come from, there are dozens online with that name.

I maintain a few of the other emulator clicks on the open store, like the sega master gear emulator and helped with qvbam, so I was interested in this implementation of nesjs, it is different from the other ones I have seen.

It really needs a way to be able to hook up with content hub so the user can choose a rom to load. I was playing around with that in this click, but was wondering where the original source was from.

Thanks for posting the stats! Looks like 2025 was a great year for UT! Here's looking forward to another great year in 2026!

Good news! I had some free time this morning and looked at these issues. I think I fixed them all, but would like you to test them:

https://gitlab.com/alaskalinuxuser/kaidan_0_6_0/-/jobs/12427701531/artifacts/raw/bin/ubuntu-touch/im.kaidan.kaidan_0.6.0_arm64.click

In landscape mode the list of contacts scrolls and you can select ones from the bottom.

In landscape or portrait mode, the search bar is now wider and usable.

The keyboard height is now figured mathmatically, so it should scale for everyone and work/look proper.

If you have time and can test this out, that would be great! Working good for me on Noble 1.1, with FP4, but would love to hear feedback from you all. Thanks for helping me make this better by pointing out issues that needed addressed!

Excellent! Thanks both of you for testing.

As for the keyboard and spacing, I am not a very good programmer, but unfortunately, anchoring the message field to the keyboard did not work properly, perhaps because it was written in QT creator for use on KDE environments, I added lomiri components and the code I saw in other apps for anchoring, but it doesn't follow the standard rules for anchoring to the keyboard like I have seen in other apps (by my trying their code in the Kaidan app). For better or worse, I went with the "wasted space" because I think on smaller screen phones this wasted space is less, and I wanted to make sure that it was not covered by the keyboard when it was displayed.

But, I'd happily accept any input if someone could try some other keyboard code that would work.

As for landscape mode, you are right, it does scroll the list of contacts, but springs back making it hard to choose contacts that are at the bottom of the list. I'll look at that for sure.

For all looking to send messages with pictures or files (audio files are good too), you can send any file if your server/account supports it. For instance, jabber.sdf.org does not support sending files, but ubuntu-jabber.net and conversations.im both do, and the icon to open folder/document doesn't appear in the compose message bar unless you have an account/server that supports it.

Ah, yes, the search field is wayyyyy to small!

Thanks for some great feedback! I'll take a look at this, perhaps early next week.

Hey all, as you know I went through (with lots of help) and updated tons of apps from Xenial to Focal, and then moved most of those on to Noble.

One of the apps that I really wanted to update was Kaidan, the xmpp messaging click. It was too big of a project for me when I started, and maybe still is now, but I have a fully working click now, and was wondering if some folks would like to test it.

https://gitlab.com/alaskalinuxuser/kaidan_0_6_0/-/jobs/12352075616/artifacts/raw/bin/ubuntu-touch/im.kaidan.kaidan_0.6.0_arm64.click

This app is built for Focal, but I have been using it on Noble daily. Need focal testers and noble testers. The original app stopped at Kaidan 0.4.2, and I have upgraded it to Kaidan 0.6.0, which is the last version to support QT5.12.

All functions work for me, I added content hub, some lomiri things, and got some great keyboard help as well. I hope to start work now on a Noble version with the higher QT and Kaidan with Omemo, because Kaidan 0.6.0 does not support Omemo encryption.

Hope to do a thourough test for a week, please pm/dm me or respond here. Screenshots or logs welcome. Please scrub private information if desired.

And it was suggested that I move this conversation to the open-store group.
Sorry for posting it in the wrong place. So no worries if you don't address this during the stream.

After some discussion on the telegram chat, an idea was to disable manual upload of appps, and only allow gitlab CI to update apps, ensuring source code is what is built.

We could still have a few select users with manual upload permission, for 'reviewed' apps.

Just a thought.

How do we verify the apps on the open-store match the source code listed?

For example, a developer makes a chess app, says it is a chess app, links source code to a chess app, but then uploads a prebuilt click which could actually be a link 'rickrolling' people.

The only way to verify app integrity currently is to rebuild the app personally and make sure it matches.

I ask, coming from an F-Droid background. In the F-Droid store (FOSS android apps), you submit links to the build source, and a build recipe, then F-Droid has an automated server that builds the app for release, making sure the uploaded app is in fact built from the source.

Is there any system in place to verify the integrity of the open-store apps? Or do they get scanned somehow?
Do we plan in the future to implement a build system to ensure that the apps are safe?

Thanks for all you do!

@stanwood I do not know about the update channels. Sorry, I'm not very knowledgeable. Interesting about the VoLTE, glad to hear that UT got it worked out, on a per phone basis. I hope that they work it out on the FLX1 soon.

But, for those wondering, my JLAB Bluetooth headphones connect and work great! If there is anything else folks are wondering about testing, let me know, I can try it out (unless it is a specific Bluetooth item, as I don't own every Bluetooth device...).

Initial impressions are great!

There were two updates as soon as I booted, the camera app was one, and you do need it for it to work properly, so I installed it, and then the camera had issues with video recording, but the app suggested I restart the phone, which fixed it.

So, initial testing, the camera took pictures front facing, rear facing, and took video with sound. There is a slight delay when you select record for the video recording, it hangs almost long enough for you to think it froze, then it starts recording and updating the viewer screen. Same pause when you stop recording video, it looks like it hangs for a few seconds, then is fine.

Sound worked, the screen was good and responsive, touch worked, all the usual stuff just worked! WiFi was good.

I turned it off, put in my sim card, booted up, picked up my carrier right away. Data worked. I could not make a phone call, but that is not UT's fault. My carrier still uses 3g towers, and the FLX1 does not support my local 3g tower bands. So that is not Ubuntu Touch's fault.

Now I just have to check on how UT handles SIP calls, as I use that. But yeah, seems to be working great overall!

Installation instructions:

From Jason: (https://t.me/ubports_porting/217354)
[In reply to alaskalinuxuser]
Yes pretty painless, but I found a workaround as it wasn't working as intended>

1. In Branchy select> Bootman gui> ubports
2. Let it download and install
3. Wait for Successful...
4. Click OK
5. In Bootman
6. Name> Ubuntu Touch 2nd Local Partition
7. Size:> 20.00 GiB
8. Select Download Icon
9. Select 2nd option> Ubuntu Touch
10. Reboot
11. In Boot Manager> Select Rootfs
12. After start
13. Bootman
14. Select Download icon to install the software
15. Wait for> Successfully installed Ubuntu Touch!
16. Reboot
17. Select 2nd option> Ubuntu Touch 2nd Local Partition
18. Setup Ubuntu Touch

Rewriting the instructions to fill in the blanks for people like me who have no idea what we are doing....

1. on the FLX1, open the terminal (or ssh to it from your computer)
2. sudo apt update && sudo apt upgrade -y
3. sudo apt install furios-app-branchy (This installs the branchy app on the phone screen.)
4. In the branchy app, type bootman in the search to save you from scrolling. Select> Bootman gui> ubports
5. Click apply, and let it download and install
6. Wait for Successful...
7. Click OK
8. open the terminal (or ssh to it from your computer)
9. sudo apt install furios-app-bootman (This installs the bootman app on the phone screen.)
10. Open bootman app and click the + icon to add a boot option.
11. Suggested settings:
    -Name> Ubuntu Touch 2nd Local Partition
    -Size:> 20.00 GiB
    -You can choose where to install it, internal or external, I chose internal.
    -Select Download Icon
12. It will say the download is qued. Now you need to reboot the phone, it will not install until you reboot.
13. You will see the new boot manager, choose rootfs for now.
14. When you log into your normal FLX1 furios, open the bootman app.
15. Select the download button next to the Ubuntu Touch 2nd Local Partition. It will give you a drop down, select Ubuntu Touch (the alternative is another Furios).
16. It will show a pop up with a progress bar as it downloads the 3.5GB file. Wait for it to complete.
17. Now it will start installing that file, and then will prompt you several times for your Furios pin/password because it is running various commands as sudo. Enter your password/pin and let it complete. Eventually, it will say it was sucessful.
18. Reboot the phone.
19. On the bootman screen, select the Ubuntu Touch boot partition.
20. Setup and enjoy Ubuntu Touch!

@wally Good point, just tried the installer, and you are correct, it is not listed as a device, even for choosing manually. The latest blog post from Furiphone said that dual boot of UT was now working, so I thought it was streamlined already. I am talking with "Jason" on Telegram currently who is walking me through it. I used to use UT years ago, but had to switch for other reasons. But if it will work now, that would be super!

I have a FLX1, I will try this out....

@nontrivial said in Ubuntu Touch Mainline Generic amd64 Issue:

Download latest ubuntu-touch-mainline-generic-amd64.img.xz file from https://ci.ubports.com/job/rootfs/job/rootfs-generic-amd64/
Uncompress it with unxz
Convert to VirtualBox VDI disk image: VBoxManage convertdd disk.img disk.vdi

The boot process appears to hang on "Starting virtual private network daemon".

By the way, I know this is a thread from four years ago, but if you web search running UBports image in VirtualBox, it leads here, so I thought I would update it to help the next person save some time...

After you run the convert line:
$ VBoxManage convertfromraw /home/alaskalinuxuser/snap/utqemu/common/ubuntu-touch-mainline-generic-amd64.img ./ubports.vdi --format vdi

And you try to launch it in VirtualBox, you will still hang at Starting virtual private network daemon, but the real issue is the graphic card settings, as @hacker1024 pointed out, but didn't offer the solution. What worked for me was:

Display settings in VB:
Video Memory 32 MB
Graphics Controller VMSVGA
Enable 3D acceleration
RDS and Recording (don't matter, but I use) disabled.

Setting the RAM to 1536MB and using the converted VDI drive seems to work great for me. Hopefully that helps the next person....