This week in development (week 52 2024)
-
@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.
-
@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 -
@domubpkm It was working on my device Google Pixel 3a XL while using 16.04 version.
-
@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
" Our Business, Is Life Itself,, '
-
@domubpkm The Volla22's hardware doesn't support taptowake. There is nothing the OS can do about that.
-
@Salah Thanks a lot!
-
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
-
@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.
Merry Christmas and Happy New Year
-
- 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
-
@kugiigi Tried again today with no change on FP4 devel. Install works fine but no apps start. As the FP4 is my dd not going to wipe it to try further just yet.
-
@Lakotaubp most apps don't yet work as they need to be recompiled for 24.04
-
@arubislander Yes but I know calls do as Marius has called Jeroen on a FP4 and on mine no apps at all start not one.
-
@Lakotaubp not even Morph? Then your device might be stuck on an older build.
-
@arubislander Probably needs fresh wipe and repartitioning from 20.04 rather than just installing 24.04 straight which as the FP4 is my DD I am not going to do just yet.
As soon as all the core apps work then I will give it a try. -
@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.
-
@mariogrip said in This week in development (week 52 2024):
I'm pleased to report that the latest daily build should have all hardware features working, including GPS, calling, sound, fingerprint reader, NFC, and more. We've also fixed several indicator bugs, making the 24.04 base system quite usable.
Currently, we're missing 24.04 built clicks, which is why some core apps aren't starting yet. While most of them build and run fine, we're waiting for some clickable changes to enable compilation. There are also some pending tasks related to accounts and push services, plus likely a few bugs to address.
As Marius says calls etc should work. I was just testing what would work on a straight move from 20 to 24.04. Which is not a lot without wipe so far.
-
For those who have tested, does morph work well with all sites ?
-
On my device, Morph and the WebView in core apps works, but the keyboard doesn't show up when taping the search textfield.
-
@ikoz I hear a keyboard fix is on the way in the next build or so.
