Themes / Apps / Mods SamSprung TooIME - Cover Screen Keyboard (Universal)

Search This thread

EZTYC

Member
Nov 30, 2010
7
1
Hi there!
I recently installed the keyboard app via the play store.
When the keyboard shows up, the keys on the right are distorted/misaligned:

1647311093596.png
 
Last edited by a moderator:
Just happened to be testing some other things and noticed the keyboard was now working with MultiStar and Good Lock

The navigation bar pushes everything to the top of the screen, but it's progress. I'm hoping they update, since they also have the recent app bug (meaning you have to clear the app from recent to launch from the main display after using it on the cover).

I may need to place suggestions vertically due to size limitations. I can't make the keys any shorter, but they can be thinner.
 

Attachments

  • Screenshot_20220322-112658_CoverScreen.png
    Screenshot_20220322-112658_CoverScreen.png
    18.4 KB · Views: 25
Last edited:
There is a weird issue that causes the keyboard to become stretched out that I haven't quite pinpointed. I can't tell if it's from installing it through Android Studio during testing or how it gets launched in general. If this happens to you, it is being worked on. Knowing how it was installed (Google or GitHub), which wallpaper shows up on the main app (cover or main screen), and if a reboot changes anything would be the relevant info for it.
 
The lifetime sales for this app still come in less than a single lifetime license to other launchers, so I have no reason to be worried that anyone is being forced into a purchase they don't actually want.

Anyway...

The handwriting recognition tests are included in all versions. The open space in the bottom of the app settings allows writing and will attempt to read the text after a 2 second delay without input. It struggles, but hopefully there are some settings to be tweaked with the recognition library that will improve it.
 
Last edited:
Additional language support for predictive input is now just a matter of finishing the word lists and setting the key layouts. Unfortunately, handwriting is restricted to English. The limitation comes from Google, which is a bit ironic considering the original implementation they released was a Chinese keyboard. It was Pinyin, though, which I believe is based on using Roman characters to form Chinese words.
 

lodvn

New member
Apr 18, 2022
2
1
Does the Google Play keyboard app work with the current version of UI? I have it enabled but no keyboard shows up on the cover screen of any apps.

Edit: Got it to work after all, only issue I'm having is after I close the keyboard or send my message, the keyboard reopens but its cut off/can only see half of it.
 
Last edited:
Does the Google Play keyboard app work with the current version of UI? I have it enabled but no keyboard shows up on the cover screen of any apps.

Are both accessibility and the keyboard enabled? It seems a lot of people miss accessibility, which is needed to override the restriction on input for the cover screen.

The newest version (1.5.9) also includes a failsafe to combat Samsung's malicious ChimeraPolicyHandler. Once accessibility has been enabled, the keyboard will prompt that it is unavailable if it is attempting to run and was terminated.

Samsung went against Google's API standards and has added their own modified task killer, named ChimeraPolicyHandler, to kill anything Samsung hasn't excluded. This means foreground services and other "normal" methods to provide an ongoing service are subject to being randomly killed off without any explanation. It has also been found to remove items from the "Never sleeping apps" exclusion list.
 
Last edited:
Edit: Got it to work after all, only issue I'm having is after I close the keyboard or send my message, the keyboard reopens but its cut off/can only see half of it.

I keep chasing that one. It seems to come and go for everyone at different times. When it happens, launching the app part of the keyboard fixes it for a while. That's not really much of a solution because it defeats the purpose of working on the cover, though. Hopefully I can get it ironed out shortly. So far, the latest tests have been unable to get that particular issue to reappear.
 
Last edited:
They never appealed to me personally, but the main reason for not attempting that sort of thing so far is the screen size. The accuracy is already a bit low on keys, but adding in gestures without a really, really effective correction / prediction algorithm would be a train wreck. The algorithm being used now is as basic as it gets, since the way the keyboard has to be added is already a lot more than if it were natively supported. It doesn't include any sort of spell check, which would be a necessity.
 
They never appealed to me personally, but the main reason for not attempting that sort of thing so far is the screen size. The accuracy is already a bit low on keys, but adding in gestures without a really, really effective correction / prediction algorithm would be a train wreck. The algorithm being used now is as basic as it gets, since the way the keyboard has to be added is already a lot more than if it were natively supported. It doesn't include any sort of spell check, which would be a necessity.
As I expected
 
@lodvn Has the keyboard stopped stretching beyond thee screen for you on the newest update? I believe I finally tracked down the issue.

For anyone that is interested in the "behind the scenes" junk, the interaction between the cover and main screen is a little buggy. Rather than a straight 0 or 1 for the current screen, it is more like 1111001111011111. What this ends up doing is more or less throwing a random full inner screen resolution into the mix at random intervals when things are idle. The trick is to keep invalidating the layout when it is added to make sure the measurements are the current ones and not a random injection.
 
The next update to hit will be hands down one of the biggest improvements since thee original release. It appears some of the documentation was a bit misleading and the accessibility service was reporting lost connection at incorrect times. This has now been fixed and was a major cause of the keyboard not appearing and other false positive reports that it was unavailable.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    feature_graphic.png



    The one and only true Z Flip cover screen IME

    If blocking keyboards doesn't prevent using one,
    does blocking them really make sense?​


    After releasing the code to enable keyboards as part of SamSprung TooUI, this is a standalone cover screen IME. This project has been developed in the hope of one day being natively supported.




    Setup is relatively easy.

    Enable the permissions
    -> appear over apps to allow it to display
    -> accessibility to toggle it on the fly
    Enable keyboard (do NOT set as default)


    A free version has been released here through GitHub. The GitHub version has been posted exclusively on xda as a thank you to everyone who has been a part of SamSprung since it began. It is basic, but functional. The Google Play version will be updated with additional features and improvements.

    Traditional keyboard functionality has been specifically blocked on the cover screen by a root level configuration.
    This app bypasses current limitations by creating the keyboard around the field instead of fields requesting a cached keyboard instance.


    See the GitHub README for setup and usage information​



    keyboardtypes.png



    If a picture is worth 1000 words, it would take hundreds to match the code being written.


    keyboard.png
    2
    Added sound and vibration options. The sound may not sync perfectly. Still working out a better way to do that.

    I've also decided to make the Google Play release a paid app. It will only cost $1, but I need to start recovering a little of the cost. The version here will still be free. The only real difference will be that the version on Google Play is verified by Google, if that means anything.
    Nice. I'm actually glad you did a paid version of the keyboard given all the work you've done on the whole Samsprung development project. I didn't buy the Play Store version of the keyboard but I made another contribution today towards the Samsprung development project. I think everyone using the Samprung launcher and/or keyboard should at a minimum buy the Play Store version of the keyboard just to contribute in some way towards this project. It's a very small price to pay for something that has made our cover screen much better than what Samsung has done with it. Keep up the good work, twistedumbrella!!
    2
    @lodvn Has the keyboard stopped stretching beyond thee screen for you on the newest update? I believe I finally tracked down the issue.

    For anyone that is interested in the "behind the scenes" junk, the interaction between the cover and main screen is a little buggy. Rather than a straight 0 or 1 for the current screen, it is more like 1111001111011111. What this ends up doing is more or less throwing a random full inner screen resolution into the mix at random intervals when things are idle. The trick is to keep invalidating the layout when it is added to make sure the measurements are the current ones and not a random injection.
    2
    Just happened to be testing some other things and noticed the keyboard was now working with MultiStar and Good Lock

    The navigation bar pushes everything to the top of the screen, but it's progress. I'm hoping they update, since they also have the recent app bug (meaning you have to clear the app from recent to launch from the main display after using it on the cover).

    I may need to place suggestions vertically due to size limitations. I can't make the keys any shorter, but they can be thinner.
    1
    @lodvn Has the keyboard stopped stretching beyond thee screen for you on the newest update? I believe I finally tracked down the issue.
    Yeah it seems to be working good now :)