A shame for suzu there is no noble build yet. I would love to try it out.

@Lakotaubp unless I have missed that, but we can't build apps for noble yet, since we are missing clickable images for 24.04. So they either work or we need to wait for clickable adaption.

@Salah Thanks a lot!

@domubpkm The Volla22's hardware doesn't support taptowake. There is nothing the OS can do about that.

@SalahPlease note, that none of the mentioned features is necessarily related to a new version of the OS upgrading the Ubuntu base. Those can be enabled "every time" - if someone does the work.

***** Ability to delete contact's photo if not required, not deleting the entire contact.

I think Lionel is working on contact backend and some frontend features. So this feature might come soon.

• Contact's photo to be enlarged while receiving a phone call.

Can you please create a feature request describing where you wish this to happen in dialer app?

• Ability to have two separate wallpaper for both Lock Screen and Desktop.

• Separate Media control for keyboard sound (while typing texts) because it is too loud. I do not want to toggle it off. Only reduce the sound a bit.

The first step for those would be to file a feature request. But it needs someone to implement them. I do agree, sound management can (nned to be) certainly be improved.

• The return of Always On Display (AOD) and Tap To Wake the screen.

You can set the screen lock time to "never" or use apps like ActiveScreen to keep the screen on. Is that not sufficient for you?
Tap to wake is already implemented in the OS. It works on devices that support this feature. On some devices it does not work due to hardware limitations. The devices page should list this feature. If your device supports the feature but it doesn't work, maybe the porter needs to do some adaptive work. You may need to get in touch with them.

• Ability to change icons and add new one to icon folder.****

This does likely involve more work. Not sure, but as with all the other features, it needs someone to do it.

This just some quick feedback on your idea.

@Keneda Thanks for the answer. It would have helped to have clear question to start with. And I guess only @mariogrip can really answer this question. But I guess this weeks post is about 24.04. From what he wrote, I would assume there will be another post next week that might target other topics. Maybe Marius can shed some light on what he plans.

@domubpkm I will need to investigate the copy/paste functions of the TextArea. That might conflict with system clipboard. But not today, its Christmas. Have a nice time everone and I hope you can spend some days in peace and with friends+family.

@Keneda To be honest, I don't really understand what your question is. I simply tried to explain that this post/thread is about noble (aka 24.04) development of Ubuntu Touch.

Is this is only about 24.04 or OS (see my signature to have a clue of my wonder ^^ ) ?

Its about a Noble based version of Ubuntu Touch (the OS). As we are currently on a Focal based version and had a Xenial based version before that.

@domubpkm Thanks for the report. Sounds like it may be related to clipboard and/or long press copy/past. Although that may not explain why it cashes when swiping. But its something to look into.

@stanwood Btw. thanks for your logs. The second last line looks familiar to me. The part Main process exited, code=killed, status=11/SEGV might be a trace.

Just got a broken tedit again. But I don't have this message in Logviewer. Interesting, in terminal I get this message too, but from systemd service, not tedit. So filtering seems to be handled different there. I will have to ask other developers maybe if they have an idea.

@domubpkm I never had instabilities too. But since the app is unconfined, I understand that users are reluctant to install it just for some logs.

@stanwood No worries, trust me, I started like that some years ago as UT user. We all learn by doing this kind of testing. I had to actually search a while through Logviewers code to retrieve this command.

First a suggestion in case you don't know yet. You can run just adb shell to open a terminal on the device. Then you can run commands as normal. It doesn't need to be adb shell COMMAND. (I find this more convenient)

The full command writes all the log output into a file called tedit.log. That is done by the last part >> tedit.log It kind of forwards output to a file. To see the output on screen just ommit this part and run only

journalctl --user -u lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service

@stanwood Logs can be pulled via journalctl. To grab the logs for tedit, you can run in terminal

journalctl --user -u lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service >>tedit.log

@messayisto Thanks a lot. Although sadly this doesn't help much. The only error is the "binding loop" one, which I get also without crashes. So not related I assume.

@stanwood and @messayisto very strange. Just to be safe, did you also try a reboot?

Could you please check the apps log and see if there is anything in it? All I see is an error about a binding llp in TextInputPopover. But that is also when not crashing, so likely not related.

Hard to track down if not reproducible. But a very annoying bug...

@domubpkm App cache is handled automatically. I don't think there is anything I can do about the size, except maybe clear cache every time tedit is closed.

@domubpkm Thanks for testing. Yes, clearing the cache did help before too. I assume when I build the app with clickable, this clears the cache as well. No idea why something in the cache can make the app crash though...

@domubpkm Ah, sure. arm64

Btw. Lionel did already create a fix for gitlab. Should be coming soon.

@stanwood No worries. First make sure you get the right artifacts file. Most devices are arm64 (64bit), but some older ones are armhf (32bit). Download that file on your device and extract it in file manager. Then hop into that folder and go builds/aarch64-linux-gnu/app. There you should find a .click file. Click on that, you should be asked to open it with another app. Pick OpenStore there to install it.