@PiotrBujakowski Original Poster I guess.

Hi @Plarde Thanks for your contribution. And you're right, it's important to discuss such matter. I don't know how involved you already are in the system development. I'll make the assumption that you're more an app developer from the argument you made. So I don't want to go too deep as this is a topic that I don't master. One argument that can be made against it is that it will make the system image grow even larger when it's already too large for some devices. So the current situation is that such library/framework have to be packaged within the click. I guess the clickable template with already included SDL is a very good idea and should help developers wishing to use SDL tremendously as not many people are familiar with clicks and it can be cumbersome to build a simple app... I'll let other people prove me wrong or go deeper in the explanations. Kindly yours.

@readyblue Hello. If this application is indeed an apk for Android, have you tried extracting it (via apkextractor for example) from the Android phone, transferring the apk to the UBT phone and installing it in waydroid? I've recovered a few apks from my old phone this way. Some work, some don't.

@peat_psuwit Hello. As Alfred said in the last Q&A, clickable continues to evolve. After a clickable update-images, how should clickable.yaml and manifest.json be for compiling (and installing) applications on a phone with the latest Noble nigthly build? Is this still relevant? ‘For now, you'll need to get a nightly build of Clickable. After that, specify ubuntu-touch-next-internal as the framework inside clickable.yaml and specify policy_version of the AppArmor profile to 9999. You may also have to make sure your manifest.json specifies @CLICK_FRAMEWORK@ in the framework field so that the correct version is filled in automatically by Clickable (sadly a similar mechanism doesn't exist yet for AppArmor policy - see this issue). When building, you'll have to specify --accept-review-errors for now, as click-reviewer-tools has not been updated.’

Ubuntu Touch 20.04 OTA-8 is released. Thank you everyone involved in testing. https://ubports.com/blog/ubports-news-1/post/ubuntu-touch-ota-8-focal-release-3953

Since this needs to be implemented in Mir, this feature will have to wait once we move to Mir 2.x and fortunately Marius already have it working so there's progress Someone just needs to be willing and skilled to implement it

@AppLee said in New contact backend story: Hi @lduboeuf Thanks for your work. Do you need help? If I can be of any help, please PM me. I rely heavily on my calendar on the phone to sync well with my Nextcloud account. Of course welcome. The issue we are facing is related to an update in signond afaik. So out of my skills Mike is looking at this normally. After that being fixed, testings on contact sync will be ready. But local contact is already there with the new backend already test able. I'm currently working on error feedbacks for user ( re prompt for password, and UI notification on failure with contact sync ). A missing part is also for address book via Bluetooth. Epic: https://gitlab.com/groups/ubports/development/core/-/epics/19

@ricardo65 With the latest daily build, it works with my Redmi Note 9 Pro (Orange provider) For me it's the Lomiri message app that can't send a new SMS. (receive is OK) while SMS sending works in command line with ofono.

@Lakotaubp It also got the error a few weeks ago then I just tried it again and it worked. Anyway, let's see if there's any news about it

@mariogrip said in This week in development (week 52 2024): I'd like to start posting weekly development updates here on the forums - this is a bit of an experiment, so please let me know if you find these updates useful and what could be improved. I think it's a great idea, and I think starting a fresh weekly thread would improve things. If once a week is too much, consider a slower pace that's easier to stick to.

@peat_psuwit I overlayed touch.pa for two reasons: to make bluetooth calls work more reliable. So this one maybe get fixed by the MR. to make wired headphones work. For this it was needed to explicitly add the rate=48000 parameter to the load-module command: https://gitlab.com/ubports/porting/community-ports/android10/fairphone/fairphone_fp3/-/blame/halium-10.0-focal/overlay/system/etc/pulse/touch.pa?ref_type=heads#L55

Just wanted to say thank you! OTA-7 arrived tonight on my Redmi Note 9S and I applied it successfully. All seems perfectly fine. So thank you for continuous hard work!

@arubislander said in The Cell Broadcast story: Does anyone know however if the audio settings should be overriden in an emergency broadcast and that the alarm sound should always be audible? I don't know if it should, but that would make sense. And if it should not, it would make sense to give the choice to user in settings anyway.

@kugiigi Thanks for asking! I know the Arrow and Touch Area of the Keyboard exsits. But I would need tap, ctrl, alt, ... more or less the keyboard modifier keys