@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.

@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 Hey, thank you for your hardwork, I tested the latest artifact and here's my experience with what I tested: wifi works, usb works. Libertine works, I installed vlc but failed to go any further because "I'll have difficultly explaining this" you can't click all that you see but you can click some of it, it's like the input layer is misaligned with what's actually visible. Waydroid works well, not much to point out about it. Just like how others pointed out, the back camera is foggy but the front one works perfectly. Missing characters, sometimes black vertical lines. Offline charging doesn't work, the device gets stuck at the battery booting screen.

Thanks so much for this! One less webber webapp needed.

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."