This week in development (week 52 2024)

danfro

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

mariogrip

@Keneda if it's fp5 you're referring too, yes this is pretty much daily driver ready on focal already, for noble it does require more work on the os itself, but the device port is ready. But I wouldn't use noble as your daily driver yet.

mariogrip

@uxes sadly yes it's slightly bigger, this is something we need to figure out, ether by slimming the image down or resize partitions on the fly. LTO has been enabled on nobile, this makes the binaries smaller at the same time, so the increase comes from more code

mariogrip

@tigerpro yes, should be mostly just plug and play, see https://forums.ubports.com/topic/10675/status-update-on-the-next-noble-based-ubuntu-touch-release-december-2024 for the changes that may be needed on pulse config.

Lakotaubp

@mariogrip I take it that the best advice is to start with a clean freshly wiped device for accurate testing.

Keneda

@danfro
My question is to know if that new "week dev thread" is about only noble (24.04), or whole OS subjects (fonctionnalities for instance), or any dev subjects related to UT (like new devices from core team).

kugiigi

@Lakotaubp I think a device full of data would also be a good testing since most people will the upgrade that way but considering the early stage of the development, data migration might not have been the focus or tackled yet so I guess a clean install would be ideal for the testers.

Lakotaubp

@kugiigi In that case not a lot works. Updated straight from 20.04 devel. Tried a few core apps all crashed including calls. have moved back to 20.04. Apps tried included system settings, weather, dialler.
Edit: on a FP4

danfro

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

Salah

As we are waiting for 24.04 to be debuted soon. Certain thoughts came to mind which I would like to see them in this upcoming OS such as:

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

Contact's photo to be enlarged while receiving a phone call.
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 return of Always On Display (AOD) and Tap To Wake the screen.
Ability to change icons and add new one to icon folder.****

Having all of the aforementioned points would be great for UT OS to be a perfect OS.

danfro

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

domubpkm

@danfro said in This week in development (week 52 2024):

Tap To Wake the screen

Tap to wake up the screen is not for all smartphones (not for the volla 22 in my case). The usefulness of being able to wake up the screen is certain to avoid wear and tear on the power key. What I like about android is that it is possible to wake up the screen using the volume key if this function is enabled. It would be nice to have this feature with UT too i think.

uxes

@mariogrip thank you, now it seems that latest build is okay,
version-66.json 2024-12-25 12:45
it just seems there is some keyboard no-vibrations issue in system settings, while morph is not opening keyboard at all

Salah

@domubpkm It was working on my device Google Pixel 3a XL while using 16.04 version.

Salah

@danfro Thanks for your thorough reply. As you said if someone can work on these features to be enabled it might be a good idea.

I have filed an issue regarding contact's photo.

Merry Chris-mass and Happy New Year.

Thumbs Up

danfro

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

danfro

@Salah Thanks a lot!

AppLee

Hi @Salah

That's not the goal of this thread.
And you already know that the forum is not an issue tracker.

The focus is currently on rebasing Ubuntu Touch on Noble.
When that's done, developers can then focus on new features but it won't happen in weeks, so be patient.
You already created the feature requests or bug reports, so job done, now it's wait and see or even better if one can: doing it...

Season's greetings :wrapped_gift:

Salah

@AppLee Sure, I know it is not issue tracker thread, let's say a Christmas wishing list or a gift for these features to be enabled. :beaming_face_with_smiling_eyes:

Merry Christmas and Happy New Year

uxes

a) setting up password crashes, but password is set
b) even when setting numeric pin, when unlocking it asks offers me qwertz keyboard not numeric input
terminal is not opening
adb shell is not working for me

$ adb shell

daemon not running; starting now at tcp:5037

daemon started successfully
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

one big plus, fingerprint unlock works