@mihael if you mean by 'address the issue' actually create an issue for each of the apps you want changed as you like, I'd say with a high degree of probability that your issues will be closed or ignored. If you meab 'create a MR', then it could be discussed but likely rejected for the same reason. Notifications are meant to be temporary. If they become an UI, the notifications will almost inevitably be longer, or even become permanent. So they will stack. If can become a hot mess and even hinder the phone notifications for incoming calls. This could be adressed by making the feature optional but you'll see that it implies some maintenance work for the project owner, even if the MR is fully complete and functional.

@Linus67 Yeah. I think the priority is to improve the app drawer and add features there. That's kind of the "home" in UT. I don't think there's immediate need to do drastic change to have an actual home. The desktop is also empty but I don't think it should also be a priority. Maybe on the desktop use case but not on mobile.

@RJDan said: @tunnel rush I would like to run the 'community favourite app' awards again later this year but there are a few things that could have been a bit improved. One issue was that we didnt have a nice award. It would be good to gather something meaningful to provide as a reward to the developers. I was thinking to organise a fund raiser of sorts but I dont know what works best in this type of crowd. What types of fund raising has worked in the past? From what I’ve seen over the years, small voluntary donations usually work better than complicated fundraising schemes. People are far more willing to throw in a few dollars when the process is simple and transparent. Even a modest prize pool plus a custom digital badge/trophy can mean a lot to indie developers.

@MrT10001 I did one more restore and flashed Ubuntu Touch 20.04 and it worked! Didn't have to do the long list of things here. Thanks for your help! I guess sometimes it just works.

@hunter_tor To get the 3T working with UT, it is Xenial only (16.04), you have to ensure the data partition is EXT4. Use the installer version 0.10.0. Download this version of TWRP and boot it from fastboot - use the command: fastboot boot (location of your TWRP file) Once in TWRP format date to EXT4, then wipe SYSTEM, CACHE and the others . Reboot to the bootloader and do the same again, but it is not necessary to wipe the system etc, just format the DATA again to EXT4. Reboot to the bootloader and fire up the UT installer and connect the device and manually select it from the drop down box. Leave the "wipe data" box unticked and follow the instructions on the installer. Let it do it's thing. Once it is at the screen in your image, leave the device, it can take up to 15 minutes to install. The OP3 and 3T are very similar, TWRP for 3 and 3T is the same. Ensure you are on OxygenOS (9.0.6) before starting the UT install. The two main points of a failed install I have found for the device is using the latest UT installer, use 0.10.0 instead and the incorrect formatting of the data partition to EXT4. Also as @moem pointed out, the OP3T is old and Xenial is now unsupported... (It still works though).

@skipperkeith said: Salut, je viens d'installer UT 24.04 sur une lenovo m10, l'open store fonctionne parfaitement mais je ne parviens pas à faire fonctionner waydroid, y êtesvous parvenus ? Salut, Tu utilises waydroidhelper : https://open-store.io/app/waydroidhelper.aaronhafer ?

Hi @Thomasb98, There is a documentation: https://docs.ubports.com/en/latest/porting/introduction/ Hope it helps... It seems feasible because this device is supported by lineageos and kernel source code is available: https://wiki.lineageos.org/devices/PL2/ Do you have the version with 4 GB of RAM or the one with 3 GB?

@arubislander said: this is probably the left-overs of some app that shared status info to the greeter infographic Possibly the Lock Message app?

@hlbkv said: Failed to write reboot parameter file: Permission denied yes that's also a side-effect of installing Ubuntu Touch for my phone. I can work around it by running adb shell then sudo reboot bootloader

@thomasf Check this topic.

Thanks @tusch001 this was very helpful and worked on the stable Focal channel with Snapz0r installed. I would recommend one change: the sed command should read- sudo snap run libinput.list-devices | sed -n '/himax-stylus/,+20p' instead of: sudo snap run libinput.list-devices | sed -n '/himax-stylus,+20p' A few practical questions for you or anyone else: What kind of daily battery life are you seeing for the stylus, over how many hours of use? Do we know if it's compatible with other UT devices? In Libertine, is there a convenient way to anchor the stylus' nib to things like scroll bars? I've been trying to scroll up/down on VS Code but it's quite cumbersome and feels like I have to press it multiple times then do a small flick to get it to scroll by a little bit every time. Kind of much like using my finger (it's just that the nib is so much more small and thus more of a precision instrument compared to anyone's finger!). Unfortunately I need to figure out how to get my Volla Keyboard accessory working again and thus I don't have access to its touchpad and a mouse cursor (I've been using a bluetooth keyboard instead), so this would be a great workaround for the time being if it's possible. On an OS level: Hopefully someone can formally implement this into an OTA upgrade for the tablet on Noble and potentially even a maintenance release on Focal? The code changes look straightforward if they're just about changing the udev rules and such. I have been working on contributing to app development on and off but as a) the tablet is a bit of a daily driver for me and I like to keep it on the stable channel and b) contributing to OS patches is something I'm not really familiar or comfortable with, it would be excellent to see this happen if someone else can help out.

@sm-xcx Hey xcx, how far are we with this project? what is still requirered to finish this project?

Hello all, It has been decided to postpone the new contact backend to 26.04.x to avoid slowing down the overall roadmap. We will try to move also at that time to the new calendar backend.. 2 major internal changes in a row. I keep you informed.

@Linus67 Thanks very much. Will try it out…