So the OSK theme landed a few OTAs back. Awesome right?!
And now I'm back with my OSK works....finally!....specifically with the advanced text functionalities in the OSK.
I've prototyped and demoed this almost half a year ago but now I want to make it "PR-ready".
So once I get satisfied, I will propose this officially.

List of changes and additional features

• Added audio and haptic feedback to the word ribbon (auto suggest bar)
• Temporary fix for the issue where cursor mover isn't working correctly in QtWebEngine text fields such as in the Morph Browser (some trade-offs to fix this temporarily)
• Horizontal movement in the cursor mover will now move vertically once the start/end of line is reached. I'm not sure how this really affects the experience but it was definitely implemented like that before for a reason. (a trade-off for the issue above)
• A new way to trigger the cursor mover mode (bottom swipe). This is available anywhere in the OSK so regardless of the layout or type, you can now trigger it. Press and hold in the space bar is still available.
• Implemented text manipulation features which are available in a top bar that shows up when in cursor mover mode.
  • Copy
  • Cut
  • Paste
  • Select All
  • Undo
  • Redo
• Implemented text selection mode (no timeout, needs manually exiting)
  • While in cursor mover mode, double tap/click to enter selection mode. You can also immediately select texts by double tapping then swiping immediately without lifting your finger.
  • Word Selection: Double tap while in cursor mover mode without swiping [Disabled for now to fix QtWebEngine issue]
• Added floating buttons in cursor mover mode
  • Move cursor to the start/end of line or document
  • They can also be used in conjunction with the selection mode!
  • Done button: Used to end selection mode and/or cursor mover mode
• Changed timeout of cursor mover mode to 5 seconds (experimental)

Know Issues:

• The new toolbar buttons and floating buttons sometimes retain their previous color when changing OSK theme.
  FIXED: Just needed to bind the colors

• Using the Start of line/document button from the floating buttons while in selection mode doesn't select texts. I'm not really sure why.
  FIXED: Stupid mistake by me....it worked in my first branch and just had a mistake with this new branch

• The bottom swipe trigger might be difficult to trigger in landscape mode especially for devices with protrusion on the sides/bezels especially those with cases.

Please feel free to try it out from the git branch linked below. You'd need to use crossbuilder to compile it and deploy to your device via ADB.
https://github.com/kugiigi/keyboard-component/tree/xenial_-_textfunctions

NOTE: BEWARE EDGE CHANNEL USERS. This won't work on edge because there's a separate branch for it which I don't have a modified fork yet. If there's plenty of interested then I might consider

Suggestions and feedback will also be greatly appreciated especially on the design

Hello Everyone,

I'm starting this thread because I wanted to share my ideas about improving the OSK in UT.
Back in the Canonical days, I suggested to use the space key for controlling the text cursor.
It was a real joy when I learned that Canonical did implemented it which we can now enjoy with UBports.
And I want continue with that idea and improve or extend its functionality.

At the moment, I have two prototypes.

1. [Swipe to trigger cursor mover]
   Instead of the current "Press and Hold" gesture to trigger the cursor mover, I made it to work with just a horizontal swipe in the space key. For me, this gesture is more natural while typing unlike the current one which will some kind of disrupt your flow by long pressing before swiping. There's a catch though because there's more chance of accidental trigger especially for those who tend to drag fingers while typing. My experience so far is good though and did an accidental trigger just once.
   Demo Video

2. [Swipe to switch OSK language]
   This one adds a functionality to change OSK language via swipe in the space key. Some people needs multiple OSK layout/language enabled and it could be a bit hassle to switch between them especially if you have more than 2...remember emoji? yeah that counts I personally don't have this problem so I can''t attest if this one would be really helpful. And also, at the moment, emoji kinda breaks it because it has a very different layout which doesn't have the space key. I'm also planning to propose a new layout for emoji
   Demo Video

Now I don't have a concrete plan yet on how I will propose these. I'm thinking of adding a Gesture section in the settings app so users can customize the gestures and which functionality they want for them. For example, you can set "PressAndHold" for Cursor Mover then "Horizontal Swipe" for Language switch. But that could be too much settings? can't say yet.

EXPAND IT FURTHER!
Currently, I have another idea to expand this idea further and I'm trying to do a quick hack for it.
The idea is to also use the "cursor mover" feature for text selections/manipulations. My initial thought is to use double click/tap (without releasing) to start the text selection. I would also like to put Copy, paste, select all buttons above the OSK. I want to see and use it first in action before thinking of the best way to implement these gestures. Unfortunately, I can't even do the first step yet which is to enable text selection from the OSK and it seems like I have to modify the C++ part of maliit and recompile which I am not familiar enough.

Any thoughts, opinion, violent reaction, help maybe?

FUN FACT: When I got the idea of the "Space key cursor mover", it was a "Eureka" moment for me and I thought I was the first one in the world to come up with that idea. Then days after that, I saw the exact same functionality on my friend's LG G3. At least it was my original idea and it just happened someone got it first LOL

Some screenshots

Cursor mover mode

Selection Mode

I won't mention anyone specifically but I'm very thankful to this whole community!
It's been great to be a part of this

@Lakotaubp There will indeed be a huge wave of new users once PinePhone is generally released.
But I think many of those people expects a traditional linux OS and many will complain about UBports being "limited" and might go to other OS.
But in any case, this will be big for UT and I'm pretty we'll still get legit happy new users

And I'm about to be brave with a heart and buy a PinePhone

@PINE64 That sounds really promising. I might get one just to do some mobile OS-hopping

This is a known issue on the Pinephone which affects apps that use secondary windows. As a workaround, install UT Tweak Tool and switch to windowed mode

I'm honestly not satisfied yet. The behavior of horizontal swipes might be erratic with one hand.
And I really want to add a better trigger than just the current "press and hold" the space bar.
Hopefully, I can work on it very soon so it'll be included in OTA-11.

Enjoy everyone! and don't be hesitant to nitpick so we can improve

Here's a quick overview of my experiments with bottom gestures in the OSK.
I'm still undecided with the horizontal bar at the bottom to be honest
Everything's experimental here..take note
What do you think?

https://youtu.be/Qh_CkiM4nyQ

Some progress for the themes support hurray!

Here are the repositories I've uploaded which so far works quite well except the settings-app which I was not able to build myself but I've only changed QML and those worked fine when I tested directly on my phone
Keyboard component
Settings app

My initial plan was just create a dark mode for the OSK but since the foundation for the colors is already there so I experimented with different themes and these are the ones I've come up.
(I don't know how to shrink the photos here :P)

Ambiance (Default)

Suru Dark

Suru Black

Just White

Just Black

Just Grey

Bordered White

Bordered Black

Bordered Grey

Colored ones are also possible but I did not include any in the repo but here's a sample

I don't know if this will be accepted but if yes, @CiberSheep I would like get the opinion of the design team and you can check the colors.
They're just in json files in the repo and can be easily modified

And BTW, this completely removed the border images and replaced with rectangles with borders

@odo Xperia X also has some issues with the camera although they've been mostly fixed recently. At the moment, main issues are the lack of zoom and camera stops to work once you used flashlight from the indicator at least once. A reboot is needed to fix it. I never had an OPO so I can't compare the performance but Xperia X works great overall.
As for FM radio, this has never worked on UT. I think the challenge here is that they are implemented per OEM and of course, they are proprietary.

I've seen this issue before but I never experienced this on my 2 Nexus 5.
I guess it'll only show up once in a blue moon

@lakotaubp I would think switching channel on the device itself would be a better test since that's how it'll be deployed to most
I don't have an OPO though i'm waiting for something similar for Nexus 5. Just a suggestion

@cliffcoggin It is for managing external drives like SD card and flash drives. It
s not in the OpenStore installed apps list because it's probably a deb and not a click app similar to other preinstalled apps like Morph.

Previous versions can be requested from Brian. GSI ports are still not officially supported right?

But I'm thinking, this may have happened because clickable now defaults to building with Qt5.12 and perhaps apps that don't explicitly use the new framework will still be offered to <=OTA-15 devices.

@markatrafik Which device do you have? It's working on my Nexus 5.

@tomrausner I'm not sure but it's usually pressing Volume Up + Power button for some time while it's off.

@tomrausner Can you confirm if you are on devel channel? Your issue sounds very similar to recent issue on devel. Try going to fastboot mode and connect to your PC and try to reflash. If you setup SSH, you can try to connect to it and update via apt.

This has been discussed on the telegram group and someone suggested a workaround while the issue still exists.

vlladdrakk on telegram:
So I took a look at that code, though I don't know c++ well, but it looks like it is a case sensitivity issue. The detected name is "pine64 pinephone (1.2)" but the name in pinephone.yaml is "Pine64 PinePhone (1.2)" I edited /etc/deviceinfo/devices/pinephone.yaml to match the case of the detected name and device info is now showing the correct device information. It is odd since the detected name is purposely lowercased here: https://gitlab.com/ubports/core/deviceinfo/-/blob/main/src/config.cpp#L65 and that change was from a long time ago, so I'm not sure why it is causing a problem now and not before. Someone else may already be fixing the problem

Do you know which channel you are on?
or maybe try reflashing with a different channel.