yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze General] SquidgyB:
As far as I understand (from another post somwhere on the forum) it's not technically a bug...

It's a requirement of Windows mobile that the SIP is deployed whenever text is entered into a field. Seems rather daft when you have a hardware keyboard on your phone though...

I've had that registry tweak above work for me, the same tweak is implemented in Advanced Config 3.3 as well. There's another fix that *should* work throughout Windows Mobile, for text fields.

It's called nullkb, and installs an option into the SIP menu that gives you a null keyboard option, and any attempt to bring up the SIP brings up nothing. I installed it, and it appeared to work, but after a reset, it defaulted back to the normal keybaord, so you have to select the null keyboard everytime you reset the device.

I'd love to find a way to simply disable auto deployment of the SIP in ALL circumstances. NullKB forces you to go into the SIP menu and select another keyboard should you want to use symbols, for example. The registry fix only seems to (sometimes) work for opera.

I just want the SIP to stay hidden until I want it, and a single click on the keyboard icon should bring the selected keyboard up.

I have no idea how to go around getting this working, I'm more of an end user than a developer...

e: there's also this reg key HKEY_CURRENT_USER\ControlPanel\Sip\AllowChange=1

Change that to 0 and it disables the SIP entirely. I'm thinking this fix and judicious use of PQzII (once I figure out how the hell to set it up...) to set up hardware keys for lots of symbols (where the hell is "\" on the keyboard? On a WM phone I would've thought a \ key would be mandatory...) might be the way forward, though it's a fair amount of work to get everything set up.
[Touch Pro, Fuze General] prochobo:
That doesn't work, at least not on my CDMA Touch Pro.
[Touch Pro, Fuze General] prochobo:
Doesn't work on my CDMA Touch Pro :( That regedit makes the keyboard appear on screen all the time, with no way to minimize it.
[Touch Pro, Fuze General] Brendo:
it is a bug in opera...

it is well documented as one

you can see if you disable autodeploy of keybaord (use advanced config) and youll see it still appears in opera. the only work around is to download nullkb and select it as your input while using opera
[Touch Pro, Fuze General] SquidgyB:
I had the problem with nullkb that it wouldn't stay as the default SIP after a soft reset. Loading PQzII and setting a link to PQzII in the startup folder fixed this, as within PQzII you can select which SIP should be displayed in portrait *and* landscape individually.

This still means a couple of clicks to get a keyboard up in landscape for entering symbols, but if in portrait the SIP will display normally.

I still can't get the "\" to work properly through PQzII though... it displays odd characters whenever I enter it into any of the PQzII configuration options. I suspect \ is used extensively in the code or something, and this messes up what's going on inside PQzII.
[Introductions] Leif-Eric:
Hey All,

I got here because I joined the dead Pixel 3 club.....

But I think I might stay for more info in other topics, glad I found this site !
[Lenovo P11] lllllllllllllllll:
If it's lower than the original version, it won't lock again

View attachment 5535421

It's already dirty, so it can't be locked back in.

Lock it up and downgrade it with a QFIL.

That's the screen

Unlock and QFIL downgrade

If you re-lock, you'll get a screen

If the same zui13 version is lower than the original version, it won't lock

Only the original version will be locked again.

I just wanted to see how zui13 looked and come down again, but it's a catastrophe.

Personally, I liked zui12 better,

I was forced to stay in zui13.

I hope it's a good post for those of you who are still in zui12.
[Lenovo P11] Drethis:
Oof, thanks for letting us know.
[Lenovo P11] russy23:
Found this out..a round trip to China was needed
[Lenovo P11] salzzz:
I've re-upgraded to 13.0.430. However, relocking still result in the same device is corrupt message.

How do you go back to the original version (13.0.430, I assume) from zui 12?
[General Questions and Answers] qalasan:
Hello are Huawei Y max and Honor 8X Max same models? Does Honor 8X Max screen fits on Huawei Y max ??
[Samsung Galaxy S5 Neo Questions & Answers] cthulhu1987:
I dug up an old S5 Neo from the chaos of my room, and I forgot the lock screen PIN. How do I unlock the phone without a hard reset or expensive software?

Edit: I tried to flash TWRP via Odin in fastboot, but that got me the error message "custom recovery blocked by frp lock"
[Samsung Galaxy Z Flip 3] twistedumbrella:
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.

GitHub - SamSprung/SamSprung-TooIME: The one and only Z Flip cover screen keyboard

The one and only Z Flip cover screen keyboard. Contribute to SamSprung/SamSprung-TooIME development by creating an account on GitHub.

github.com

SamSprung TooIME (Keyboard) - Apps on Google Play

The one and only Z Flip cover screen keyboard

play.google.com

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​

Home

The one and only Z Flip cover screen keyboard. Contribute to SamSprung/SamSprung-TooIME development by creating an account on GitHub.

github.com

View attachment 5539415

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

View attachment 5556727​
[Samsung Galaxy Z Flip 3] rogerandgina06:
It somehow not working for me.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Sorry for the delay. In pulling the keyboard out of the main app, it's still trying to end the service when the device goes idle. Since there is no longer a master service to restart it, it only runs once.

Fix should be up in a couple minutes.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Should stay alive now.

Being completely honest, the keyboard works about 100 times better separate from the launcher. The two biggest issues, one of which was restoring the default when not in use, are much easier to manage when all the other parts don't get in the way.

Now that it's a separate project, we can also start doing adjustable size and themes and all the other proper keyboard stuff that couldn't really fit before.
[Samsung Galaxy Z Flip 3] twistedumbrella:
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 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 will continue to receive cosmetic updates and new features.
[Samsung Galaxy Z Flip 3] crawls69:
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!!
[Samsung Galaxy Z Flip 3] twistedumbrella:
Thanks @crawls69! You've always been a great supporter and it really means a lot.
[Samsung Galaxy Z Flip 3] rogerandgina06:
@twistedumbrella Is this a keyboard for the cover screen? If so, I can't get it to work....
[Samsung Galaxy Z Flip 3] twistedumbrella:
The logcat button can collect a log of any crashes. If it isn't a crash, it may have to do with the type of entry box you're trying to use it on. What have you tried?
[Samsung Galaxy Z Flip 3] rogerandgina06:
Responding to text messages from the native message app.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Alright. I'll run some tests and see if I can reproduce the issue.

Is it just not appearing at all? As in not even a flicker.
[Samsung Galaxy Z Flip 3] twistedumbrella:
I rearranged some things to avoid the keyboard getting cancelled out by other views. Hopefully that will resolve the issue.
[Samsung Galaxy Z Flip 3] rogerandgina06:
Not showing up at all.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Is that still the case? I was able to get it to stop appearing in a couple tests and patched those issues. I haven't been able to get it to not appear since, but that doesn't rule out the possibility of a situation I missed.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Admittedly, it is much MUCH easier to simply include the keyboard in the app using it, especially with accessibility.

Rather than catching the call to enable the keyboard, an InputConnection can be generated from the field itself. Some may not care about passing all of your views through the app, but I treat everyone else's data like I would my own. Grabbing the field and modifying it within the app seems like a huge risk for privacy concerns.

The alternative would be to create an invisible entry box and write to it. This would generate the required InputConnection and avoid directly traversing the screen, but has a large performance cost.

The final version is to temporarily take the default keyboard role. This gives the keyboard the default InputConnection and allows typing directly into an entry box, much the same way a conventional IME would do it. There is one part that hasn't been implemented yet to make this ideal, but where's the fun in copying code and not doing any work?
[Samsung Galaxy Z Flip 3] rogerandgina06:
Still not showing up on the cover screen. The picture shows it showing up in my notification panel.
[Samsung Galaxy Z Flip 3] twistedumbrella:
@Landrea made a good point. This needs a preview.

Not the prettiest in the world, but now it has one.
[Samsung Galaxy Z Flip 3] Landrea:
My point was I couldn't see what I was writing. Now the keyboard has the preview. Not the best one, but still, good job @twistedumbrella . Keep working on this project, it really has value!
[Samsung Galaxy Z Flip 3] twistedumbrella:
It's super ugly right now, but I'm working on getting it somewhat bearable.
[Samsung Galaxy Z Flip 3] crawls69:
twistedumbrella,

It may be super ugly to you but it's drop dead gorgeous to me. LOL

I was willing to accept the fact that I would never have the same experience on the Z Flip 3 cover screen that I did on my RAZR 5G cover display. But you keep getting us closer to it. I no longer miss the functionality of the RAZR 5G cover display (except for the fact that it's larger). That said, is there any way you can do an update that causes the cover screen to physically expand to perhaps 2.7 inches or so? LOL. You already accomplished what was apparently impossible for Samsung to do. Who knows??

As much as I use the cover screen, I was actually gonna get rid of the Z Flip 3 and go back to the RAZR 5G after Android 12 cause the widget version of Samsprung to stop working. I'm glad I didn't. I would be kicking myself right now.

I'm usually not one to throw shade but given what all has been accomplished with the Samsprung launcher and keyboard, Samsung should be really ashamed of themselves. I'm sure they have an army of resources at their disposal that could have easily gotten this done (they have a market capitalization in excess of $400 billion). They should offer you a licensing deal!!
[Samsung Galaxy Z Flip 3] twistedumbrella:
They are quietly watching.

Speaking of Samsung, has anyone with root tried disabling the block on keyboards? I have to go find the post, but there's an xml file that is nothing more than a true / false for native support.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Should be in /data/system/display_settings.xml (but may also be in a vendor folder or overlay)

<display-settings>

<config identifier="1" />

<display

... blah blah ...

shouldShowIme="true" />

</display-settings>

Display support | Android Open Source Project

source.android.com
[Samsung Galaxy Z Flip 3] Landrea:
First screenshot
[Samsung Galaxy Z Flip 3] twistedumbrella:
I think I found a somewhat reliable way to restore the default keyboard. We'll see how it works...
[Samsung Galaxy Z Flip 3] Landrea:
I'm struggling with the keyboard. It just doesn't show up if I open it 2-3 times in a row (eg. texting in telegram or even search app in the drawer)...

And it takes a reboot to work again... any help? thx
[Samsung Galaxy Z Flip 3] twistedumbrella:
That's what is being worked on now.
[Samsung Galaxy Z Flip 3] twistedumbrella:
I'm pretty sure I just spent the last two hour rewriting this thing 20 different ways to realize I was using the wrong flag...

Yeah, so that was a fun waste of time. Should work now, though.
[Samsung Galaxy Z Flip 3] Landrea:
the keyboard in fact appears right... BUT... text doesn't appear on the app when you tap "DONE" :(
[Samsung Galaxy Z Flip 3] twistedumbrella:
I think that's fixed or at least mostly fixed. It may still bottom out in the right scenario.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Here's a quick and dirty overview of the how and why:

Samsung has disabled cover keyboards. This means the calls to view generation methods in the input class aren't attached to the window.

To get an input connection, you need to be either the default keyboard or the only keyboard of the specific type that the view is requesting. The Samsung keyboard is definitely requesting standard entry boxes, so that's a loss.

The alternative would be attaching to each input view. That can't be done without first retrieving that view. Not being the app making the view or using accessibility to grab them, there is no view reference until the keyboard is already connected.

The keyboard itself cannot take focus or the input view focus (aka the thing that makes it possible to type into it) is lost.

Not taking focus means the view gets dismissed when anything else grabs focus from the current window. This is where it can get lost after the first use.

A view can only be assigned to one parent and it must be removed before attaching it again. This means that connecting the keyboard means first disconnecting it. This is the other place where it can get lost.

The choice is to do things in a way that there is a token for the input view, which either means sticking to internal views or doing a whole lot of accessibility stuff that starts getting uncomfortable, or play an elaborate game of shifting focus and recreating views.

Considering one of the big concerns is not abusing accessibility and the input views are almost always in another app, it's musical chairs.

Edit: not to be mistaken for an excuse. If I didn't think I could make it work, we wouldn't be here.
[Samsung Galaxy Z Flip 3] twistedumbrella:
I don't know how it happened, but Google Play has today's build.
[Samsung Galaxy Z Flip 3] twistedumbrella:
It looks a lot more like a keyboard than it did, anyway.
[Samsung Galaxy Z Flip 3] Landrea:
I can't make it happen :( I turned on every authorization... but still
[Samsung Galaxy Z Flip 3] twistedumbrella:
I can't seem to see the log you attached in the post here, in the TooUI thread post, or in your GitHub comment. I wonder why it isn't showing up.
[Samsung Galaxy Z Flip 3] Landrea:
my bad! here's the log... thanks!
[Samsung Galaxy Z Flip 3] twistedumbrella:
The only error, per se, is that the update check breaks. That shouldn't crash the entire thing, though. I'm still looking into why it might not want to appear. The most i've been able to break it on my end is hiding the keyboard and then clicking the same box with the cursor flashing. I could fix it by clicking off and back on the box, though.
[Samsung Galaxy Z Flip 3] Landrea:
Thanks for looking into it, unfortunately I really seem unable to make the keyboard show. It used to work until a couple of days ago, even if not perfect, but now it just doesn't appear.

Tell me if something comes to your mind
[Samsung Galaxy Z Flip 3] twistedumbrella:
I have some suspicion it may be my own navigation overlay doing it. I know at one point I ran into some issues with one cancelling the other out. Usually that results in the text not reaching the intended target, though. It didn't prevent it from appearing at all. It's a touchy game.
[Samsung Galaxy Z Flip 3] Landrea:
Tried new version, still no luck.

I attach a new logcat, if can be useful I can tell you that tapping on input bar, one option shows, "autofill".

I tried several times to uninstall toolui and the keyboard to make it reset...
[Samsung Galaxy Z Flip 3] Landrea:
Because I'm desperate, I tried the old version of ToolUI from 20 days ago, with built in keyboard. It works.

So it seems I have an issue with the Ime keyboard app.

Tell me what I can do to help you help me. I really appreciate your work. Thanks
[Samsung Galaxy Z Flip 3] Landrea:
I found out that the last working version on my phone is #d232aa0.

The next one in my archive, bb93439, doesn't show up.

Idk if you can recall the changelog and might understand my issue... Thanks
[Samsung Galaxy Z Flip 3] twistedumbrella:
The changes since then were mostly for updating and themes for the Google Play version. I guess the only thing to really do is keep pushing forward and hope whatever happened gets resolved.
[Samsung Galaxy Z Flip 3] Landrea:
okay, I agree with you and trust you.

Please make new versions so I can try them out... thank youuuuu
[Samsung Galaxy Z Flip 3] Landrea:
This is good... The fact it appears is good. Thanks.

It keeps changing the default keyboard to Ime, so I have to switch every time I unfold the phone and need to type something...
[Samsung Galaxy Z Flip 3] twistedumbrella:
It's about time I get this thing sorted. Looking into why it appears fine when launching the first app, but seems to disappear on the second.
[Samsung Galaxy Z Flip 3] twistedumbrella:
There has been huge progress getting the keyboard to appear reliably. Unfortunately, at the cost of not switching back to the original default reliably at all.
[Samsung Galaxy Z Flip 3] Landrea:
Keep us updated. You're doing a really good job. Doing a fresh install right now.
[Samsung Galaxy Z Flip 3] twistedumbrella:
I probably should have settled for leaving the keyboard in the launcher, but what fun is that?
[Samsung Galaxy Z Flip 3] twistedumbrella:
Had to work out getting the thing to appear reliably so all the work getting it to handle persisting would hold. I think I found a balance.

Turns out i've been handling display changes "wrong" for the way they were being tracked. I was treating it like the launcher that only watches when active. Since it watches to return the default, that was also killing it off when it became active.
[Samsung Galaxy Z Flip 3] twistedumbrella:
I dare say the keyboard seems stable now. I've been able to use it, switch apps, use it again, come back later, and use it again without losing it.
[Samsung Galaxy Z Flip 3] Landrea:
I still lose it when unflipped and flip it again
[Samsung Galaxy Z Flip 3] twistedumbrella:
The old launcher will still shut down the current keyboard.

Every version so far has worked on my end, but I have always been able to create a scenario that broke it. The assumption being that anyone having issues likely was in one of those scenarios. I can't break it now.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Trying to go about this differently. The issue is that the keyboard can't detect it's needed unless it's the default. Setting the keyboard as default should only happen when using the cover. Every version of handling both wants to fight.
[Samsung Galaxy Z Flip 3] twistedumbrella:
After what feels like a month's worth of folding and unfolding, I think I found the reason things didn't work the same for everyone. Looks like the lock screen Bixby hoopla threw a wrench in the works.

Not that adding my own fingerprint bypass fixed it, it just revealed the issue. The good news being that now it's being fixed. I should have something in the next... soon.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Once I can get the size to remain consistent, I should be able to push all the recent changes. It's still not completely perfect, but it is considerably more responsive.
[Samsung Galaxy Z Flip 3] twistedumbrella:
@chopped0815 Disable the accessibility option for the keyboard and enable it again. Something you ran on the cover killed the service and prevented it from restarting. Further reports exclusively for the keyboard in the other thread will not be redirected.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Rumor is the newest release seems to be stable, so it should be safe to finally work on new stuff. It's ugly with the limitations, but there is significant progress.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Edit: Removed due to nature of implementation
[Samsung Galaxy Z Flip 3] twistedumbrella:
I won't get into too much detail because it's not a feature of the GitHub build, but T9 prediction uses a fairly extensive word list and returns results in an order based on the number of characters provided. If no results are found, it returns the characters entered. Hitting space or done with an entry will automatically return the closest match. Clicking on a suggestion will select it, but will not add a space. Future builds will try to match the previous characters given before spitting out the raw characters.
[Samsung Galaxy Z Flip 3] twistedumbrella:
Seems a bunch of stuff was slipping through the cracks on the GitHub builds. Got that all sorted out, so it may look like an entirely different keyboard in the next version. It's better. I promise.

Fixed sticky and modifier keys to reflect status

The default theme is actually the default theme (not placeholders)

The shadows are aligned properly

Shift is reflected in the key text

Spacing is better to avoid unintentional taps

Colors on the keys don't bleed beyond the key

A bunch of T9 improvements
[Samsung Galaxy Z Flip 3] EZTYC:
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:
[Samsung Galaxy Z Flip 3] twistedumbrella:
The text size has been adjusted for above average font size settings. Max will still look off, but that is the cost of max. All of Android looks off at that size
[Samsung Galaxy Z Flip 3] twistedumbrella:
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.
[Samsung Galaxy Z Flip 3] twistedumbrella:
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.