@DJac said: I update my sony Xperia X with ubuntu touch 24.04-2. But I have a problem with the "bookmarks app". They no longer works. What I see : a blue loading bar ,then a black screen (or white if i m not in dark mod). I found it with blablacar, but after some tests, it seems that include all " bookmarks app" I have also a display problem with morph web browser : nothing is displayed online, but parameters are usable. Others browsers works normaly (merezhyvo & ufirefox) Do anyone else have the problem with the "Boorkmark" apps problem? ( With apps based on webapp-container ). If confirmed it seems to me an important problem. What about apps created manually with Webber?

Thanks, I am going to installiert telegram!

@777X yea i am using localsend now and then, its a nice clean application if it works xD

@projectmoon very true.

@Ida_ That's great news!!

@YamiYukiSenpai I'm not sure what's causing it because I know someone where the root was successfully resized on this device. I have 2 Pro1-X and my 6GB variant is the one that has this issue so far. My other one is still in 24.04-1.3 so haven't tried. All I remember is that I initially flashed this one the old manual way because it wasn't in the installer yet.

@DerekZoZo said: but in a sense of being told that "we don't want you here" 🤯 I am autistic and have a tendency to read to deep into what someone writes online All what I said is that volla is the device manufacturer and porter, and that best support (port related) for those devices is volla. Since you need support, i redirect you to the place I think you'll get the best for your device : volla. I'm not a dev, just here because I love Ubuntu Touch since more than 10 years, and try to help UBPorts and community with my limited knowledge and assets.

@pparent en effet, même problèmes avec les autres signets. Je vais tâcher de signaler ça. Visiblement il y a un pb d affichage avec morph aussi. Cela est sans doute lié. (Merezhyvo fonctionne)

@KoJans said: That worked in a few minutes outside. Glad to hear it!

Thanks for the hint. Yes, both work correctly. The physical volume buttons change the playback volume. The system volume slider (volume indicator) also changes the playback volume. Only QMediaPlayer::setVolume() has no audible effect, although the property itself changes correctly. So it looks like the backend ignores the player's volume while still using the system media volume.

@fischer.poco I noticed in your attempt to "fastboot oem unlock: that you received a message "Flashing Unlock is not allowed". Do you know what model of phone you have? (e.g. within OnePlus NORD N10 5G there are 4 BE2026, BE2028 (T-Mobile), BE2029 and a 4th one (MetroPCS) I can't remember the number). Basically, you need BE2026 or BE2029 to directly unlock the bootloader without OnePlus. If you have BE2028, you have to request the bootloader from OnePlus (which has been mixed, sometimes they give you the unlock token, sometimes they don't).

@Moem Looks promising, It could be just what I need. Thank you!

Yes! I confirm that disabling the Timekeeper service resolves the issue. The clock on the phone was still correct this morning after turning it on in "offline" mode. Which also confirms that RTC is indeed supported natively on the Quintus.

@kristatos maybe doing some more tests. I tried it again with my phone (FP5) setup with 24.04-1.3 stable and succeeded with receiving and sending test files. However I have reproduced some of your problems. Not the obex service not known. This was not happening for me. I have seen the disconnection of Bluetooth happening though. Strangely the Bluetooth page for the device (an Android phone) was displaying the device as connected BUT with no signal, then disconnected very soon after (may seem logical given there was no signal). I removed each phone from the Bluetooth configuration of both phones, tried again and this time the signal was rated 'excellent'. It then stayed connected. Needless to say, for all these tests the phones were sitting on a table very near of each other. It looks as if the state of connection is rated with 'no signal', it's staying so even if the real connection is good. In this case the pairing had been done much before and the phones had both been off or way to distant of each other to talk with Bluetooth. After solving this connection problem, I think another trouble may be that if a transfer is not acknowledged by the receiving end, all following transfers fail. Not sure but it looks like that. This problem was happening with a transfer UT -> Android. If my impression is correct, it may be a problem with the app (the connection problem mentioned before is probably more caused by the system bluetooth stack).

@Persinto since you want to use it as android phone, then any

@sambk Have you had any luck?

@Keneda Will contact Florian tomorrow.

Hi, I find the app really useful, specially due to the daemon. I would really love video call functionallity. Is there any chance it will be added soonish? It's really the only thing keeping me on Waydroid's Whatsapp app at the moment. Thank you so much for working on this, keep it up!

@woodyst Love the concept, and there's definitely a need for more thorough GPS. But yeah, it needs translating. Is there a place to contribute translations? Or maybe you can generate a set of machine translations for the most used languages on UT and then people can update those? Would help people actually be able to use the app. My Spanish is way too rusty for this lol. As for what I can see so far: Does not fit UT's/Lomiri's UX, which isn't necessarily a bad thing, but a more native appearance would look better in my opinion. It's unclear what the account is for. I assume traffic reports, and I assume it's probably explained in the tour I didn't read because I don't know enough Spanish lol. Might be nice, if this is possible (not sure it is) to integrate with system links for directions and stuff, e.g. responding to geo: URIs if you don't already.