Hi, after latest update wifi and bluetooth don't work. Ive even tried usb tethering as client and it doesn't work either.

@padraic For a next time, to verifiy the device, you must enable developper mode in system settings / System information. Connect the usb. Accept the connection on the phone. adb devices must show you your phone.

@kugiigi Yes, I've noticed that too reading around forums. This is why I'm looking into open source+hardware solutions like Modos (https://www.crowdsupply.com/modos-tech/modos-paper-monitor) and others, although most don't support touch yet. Honestly, considering you're getting a 75Hz refresh rate monitor that's actually e-ink in 2025, the prices don't look that bad, although do correct me if I'm wrong. There are even ways to add touchscreen support to any monitor, but that's a whole different story, and won't be worth getting into until UT develops touch monitor support.

@nparafe That device's kernel is too old for using cgroupv2 and eBPF to mediate device access, it's advised in the port to set the kernel cmdline systemd.unified_cgroup_hierarchy=0 and recompile the kernel image. Please tell your device maintainer about this.

said in http://repo2.ubports.com/dists/focal/InRelease blocked when there's football on the tv: I have filed a complaint to the internet provider via the OCU. I guess they'll day it's not their fault. I got an «answer». Please note that I'm being blocked (and everyone that connects from a Spanish network) to several websites because, literally «security reasons». «Security reasons» means that a football business is blocking random IPs because they think they are pirating their signal. Also, the «security reasons» are intermittent as you can see in the logs of OONI. The more it goes, the more IPs that are being blocked (it seems). My next step is going to the European Síndic de Greuges (that I don't know how it's called in English)

@fredldotme Nice, though I just logged in to say that I can't test it anytime around. I've lost the phone. It's been a few days so I have no hope getting it back by a chance. I've been thinking in the meantime and decided I'll rather not buy another one anytime soon. I'm still interested in using Ubuntu touch but there are points to address before I'd be happy with it, so I might try to help solving them in VM (or just wait if eventually these got solved...). For now I've set price alerts in my favorite shops, hoping to catch next nice discount

@Eric-H thanks a lot

@GerhardF A smile works fine!

It seems Droidian have their own modified version of Firefox with some UI adaptation: https://github.com/droidian/firefox-esr-mobile-config

said in What are a few straightforward ways to write notes in Ubuntu Touch and be able to get them on the Internet/WWW on my Debian PC?: emacs While all packages should work just fine inside of Libertine, the main issue is making the desktop tools usable on the phone. Libertine Tweak Tool was good for resizing text on the app to a comfortably readable font on a phone screen, only thing missing now is modifier keys on the software keyboard, and a way to force the keyboard to appear inside of emacs for me: this is because the 'touch-to-click' compatibility system isn't always the most reliable, and a program like emacs is of course macro-heavy. My biggest way around the Desktop / Mobile syncing problem actually comes down to avoiding it as much as possible, by having my phone do (almost) everything, as syncing takes time while HDMI output to an external display is instant

@Sentinel said in No GPS access from inside Waydroid: maybe the MIUI version I flashed might have impacted Waydroid's reliability or other things? Yes — this can significantly affect UT. The MIUI image version to use is specified in the installation guide under "2. Check the correct version of MIUI", and it looks like you used the correct one. I can't explain the unusual bugs you've reported. Did you remount the system as read-write and make any changes? Did you use apt (update/upgrade/install)? I'm fine with starting a new discussion thread.

@wally Yes, I was adjusting the edges in UI tweaks. However as I stated in other thread I never liked swype OS navigation. Expanding the subject, I also don't like touch OS navigation. Touch screens register the touch "without my consent", i.e. when I just grab the phone. That's wrong, but it's been like that since the beginning of all mobile OSes. I'd love to see an option to enable touch-and-confirm input where you touch and have to swype a bit immediately to make the original touch point registered as touch, otherwise it's meaningless

Hy all, In update 224 it is fixed. Glad i din't rush things... Ernst-Jan

@d4f0 @messayisto thanks for your replies, I'm beginning to think that there is nothing wrong neither in force-adb nor in systemd (!) and the problems comes from the device tree of the FP5, that is, the kernel configuration. Changing force-adb could be an easy work around but mostly wrong. I'll try to explore the FP5 kernel code to see if I can find the problem all by myself (enthusiasm level: ) Edit: created this gitlab issue to make the problem more visible.

I will control the condition of test : -the stat of the phone of the friend who send me the messages. and if it works in differents direction. but not this week I will come back for that.

@projectmoon Thanks, you're completely right. It works now.

@enki said in top 3 app wish list for Ubuntu 24.04: Conversation for xmpp chat audio/video client There is an experimental port of Kaidan being developed: https://gitlab.com/alaskalinuxuser/kaidan_0_6_0

@gpatel-fr I see, thank you for clarifying.

@Vlad-Nirky Thanks, I did not see the double entry.