@Linus67 is it already running Android 11? If not and you are using Windows, the Lenovo Software fix tool is easier...

@projectmoon A GPS Navigator. I was a lot of time searching for a GPS navigator with the functionality I like for me, but I didn't found anyone. So I decided to code my own. I'm reviewing it now for publishing it.

@brenno.almeida said: From apps perspective, there's no way to tweak this behavior. not sure what you are meaning by 'this behavior' and 'tweaking'. What I understand is there would be no way to display a time out notification and detect if the user has pressed the notification before it closes by itself. If this is what you mean, this example shows how it can be done.. Granted, don't know if this can work from an unconfined app. This caveat was not part of the discussion

Hi guys, I'm truying to build Sota4ever_k repository for a Samsung Galaxy S20 FE (r8s, SM-G780F/DS, with Exynos) Is it still usable? Right now, it fails with lot of warning in openssl + make O=/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/KERNEL_OBJ CC=clang -j16 scripts/kconfig/conf -s --syncconfig Kconfig /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/extract-cert.c: In function ‘display_openssl_errors’: /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/extract-cert.c:46:9: warning: ‘ERR_get_error_line’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 46 | while ((e = ERR_get_error_line(&file, &line))) { | ^~~~~ In file included from /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/extract-cert.c:23: /usr/include/openssl/err.h:426:15: note: declared here 426 | unsigned long ERR_get_error_line(const char **file, int *line); ......... lot of warning, and then..... 1 warning generated. /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/drivers/video/fbdev/exynos/panel/sysfs.c:2358:21: warning: unused variable 'panel_data' [-Wunused-variable] struct panel_info *panel_data = &panel->panel_data; ^ 1 warning generated. /home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/drivers/video/fbdev/exynos/dpu30/decon_core.c:1200:38: error: use of undeclared identifier 'prev_state' decon_doze_first_frame_black(decon, prev_state, next_state); ^ 1 error generated. make[6]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:333: drivers/video/fbdev/exynos/dpu30/decon_core.o] Error 1 make[6]: *** Attente des tâches non terminées.... make[5]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:638: drivers/video/fbdev/exynos/dpu30] Error 2 make[4]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:638: drivers/video/fbdev/exynos] Error 2 make[3]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:638: drivers/video/fbdev] Error 2 make[2]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/scripts/Makefile.build:638: drivers/video] Error 2 make[2]: *** Attente des tâches non terminées.... make[1]: *** [/home/vincent/dev/git/UTFamily-Samsung-Exynos9830/workdir/downloads/linux-android-samsung-exynos990/Makefile:1144: drivers] Error 2 make: *** [Makefile:146: sub-make] Error 2 What can I do?

30 days passed and the Xiaomi community app says: "Application quota limit reached, please try again after 05/30 (mm/dd) 00:00 (GMT+8)" I though other people reported this message in MiUnlock app. I guess I have to be granted through the Community app and then do the unlocking job connecting the phone to the PC's MiUnlock app.

@los-tioz cannot confirm the issues on my sony xperia, running 24.04-1.3. Uodate channel is rc, maybe thats the dufference? Camera and Timezone both working as expected.

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