@CyBerT For Multiboot Check out this link: https://wiki.postmarketos.org/wiki/OnePlus_6_(oneplus-enchilada)/Multi_Booting_and_Custom_Partitioning#Dual_booting_pmos_with_other_uefi_based_os_(like_openbsd_,_netbsd_,_freebsd,windows,etc)_via_Renegade_Project

@Sander I hadn't tried that! THANKS

@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer): OK, first batch of results: 'obexd' is started by default on Xenial and runs with the same command-line parameters the same two OBEX-related packages are installed, but of course their version differ (5.53 for bluez-obexd, 1.7.1 for libopenobex2) the files provided by the 'bluez-obexd' package are the same, except for the dbus-org.bluez.obex.service unit file that is missing on Xenial the output of busctl list | grep bluez is quite close to what it is on Focal, except that the corresponding 'systemd' unit file is not shown the output of busctl list | grep obex shows something in lieu of a unit file ('session-c1.scope' -- what is it?), but still doesn't advertise any name for the service (see below) further digging reveals that although 'systemd' is already present on the system, it is not used for user-related processes (i.e. no systemd --user process) -- 'obexd' has been started by upstart --user (based on its PPID) Maybe the problem on Focal stems from a lack of integration between the OBEX daemon and systemd --user (which could also explain why the service doesn't start although enabled)? For what it's worth, here is the output of busctl list | grep obex on Xenial: :1.59 4084 obexd phablet :1.59 session-c1.scope c1 - Yes indeed, Xenial relies on upstart instead of systemd. Maybe something is missing there. This discussion could interest core team. @peat_psuwit do you have an idea ?

@k.nacke Thanks a lot for your efforts and time. Looking for an update. What's ironic is that, the fron camera in UT is far more better than even the stock rom. Its only the back cam that is cloudy. Really appreciate it, enjoying its so far.

On lenovo tab, I m not sure... but I m curious of your feed back. have you some details about the processor ?

About the state of Frameworks and Game Engines: Unity: There is a Demo App in the store that prints FPS. Godot: There is also a kind of benchmark-like Demo App. Bacon2D: works, but is unmaintained for 8 years now. I believe that anything based on SDL or WebGL (or Qt) should do. Providing SDL3 with better system integration is in the works. Clickable provides a Godot app template, but this is for UT 20.04 currently. 24.04 support probably comes after beforementioned SDL3 (+SDL2 via compat layer) support is finished.

@kristatos said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed: @pparent Sure, I can complement your bug report. But do you have the same experience? Press power button Backlight powers up No image is coming up Yes I've seen it a few times as you describe, but most of the times I had a freeze with still image while using the phone and using the interface. In that later case the phone stays still in the last image, and pressing the power button does not have any effect. So I guess what you describe can be the same bug except that it happens while the phone is suspended, so when you press the power button it remains frozen on a black screen.

@UBportsNews ubfortunately still doesn't support gps, does it?

@rocket2nfinity said in Oneplus n10 24.04-2.x follow up: ..if it does, it should be persistent, since halium upgrades only happen every now and then. Search XDA for unlocking network locked devices ah ah , if ever this device get an halium 12 upgrade !!! as volte is working with 9 , i doudt it will . Thanks , i put a lot of time trying xda solutions already . i'll see ,if i put some more .

@gpatel-fr said in Why does UT not have assisted GPS?: We currently do not expect to continue our operations beyond the year 2025 Yes, Positon is intended as a temporary offering. Please note that I do not recommend using Positon, BeaconDB, or even Geoclue 2 — I am only testing them

Hello I've managed to send a file using Bluetooth. First to get bluetooth running again, I've reset the device. After this, bluetooth service worked again normally. As advised by @gpatel-fr, I've installed bt-obex using crackle. crackle install bluez-tools I've then opened 3 Terminal tabs to run these tasks in parallel: Terminal 1 # To find the Android phone receiving the file bluetoothctl scan on # Find and copy the MAC address of the Android bluetooth adapter to paste it in terminal 3 Terminal 2 # Start the obexd tool /usr/libexec/bluetooth/obexd Terminal 3 # Make sure that the Android bluetooth device is discoverable # Send the file with bt-obex bt-obex -p [MAC address of the Android bluetooth adapter] /tmp/test-bluetooth.txt On the Android device, make sure that you accept receiving the file from the Ubuntu Touch device and check that the content is sucessfully received.

@viko As has been said, dtbo.img is generally not needed. If the port doesn't boot, the issue is more like due to other reasons. Feel free to check the porting docs I linked you in Telegram.

@maahymot Not that I know of, but I also do not own the Mi A1.

@Talkless sorry to hear that and that the debugging was such a painful process. Let me know if you have ideas for improvements or decide to get back to this issue.

@Merlu Did you downgrade to Android 10 before proceeding with the ubports-installer? Did you check "wipe user-data" and "bootstrap" on installation options in ubports installer?

@bhdouglass One thing that I'm missing in the new site compared to the old one, as a developer, is to be able to have an overview of the stats of all your apps as once.

@Merlu said in Flashing firmware takes an eternity: stuck at the step "flashing firmware" since hours. I take it that 'hours' means literally more than 120 minutes. If it is the case, I'd say that it's abnormally long, yes. It could maybe mean that the download from Internet crashed (network glitch), or that after a successful download the transfer via USB crashed. IMO the #1 probable culprit for this last problem could be a low quality USB cable. In both cases you'd probably expect a good error message, but the installer is not that polished to have faultless (!) error reporting. @Merlu said in Flashing firmware takes an eternity: Is there a risk to brick my phone if i interrupt the process? Possibly but if you are stuck since 3 hours, I don't think there is much else you can do. Normally the low-level firmware, that allows for the phone to be flashed, is not touched by the process, so even if the phone don't start after that, you can try again to flash it, possibly with a better quality USB cable. That's exactly what happened to me when I installed UT.

Alpha 2! https://git.agnos.is/projectmoon/indra/releases/tag/v0.0.2 Next alpha release, focused on dealing with reported bugs and adding features required for MVP user experience. No work was done on Bluetooth connection stability in this release. A database wipe is required for this release! Delete the database by doing rm ~/.local/share/indra.projectmoon/indra.db on your phone, or by deleting indra.db using the file manager. Changelog Store and utilize last heard from nodes. Update Direct Conversation (Direct Messages in the main list) when a node's long or short name changes. Allow deletion of errored or unsent messages. Allow resend of errored or unsent messages. Color messages gray if they've been unsent for a long time (only on channel view load). Alter message sending logic to first queue the message for sending, then send it, then delete the queued message. Theoretically helps with Bluetooth instability. Add ability to search the node list. Separate nodes into online and offline (not heard for at least 24 hours). Catch errors relating to specific messages and mark the message as errored. Render non-public encrypted channels as "group chats."

@nwoo66 In English, please.