[Bug] Keyboard issue on Android mobile devices

[RealPlurr]

Describe the Bug Keyboard doesn't work correctly (or at all) on android phone (redmi 8). Wont type in chat or and wont type in username field.

Steps to Reproduce Start launcher, click keyboard button try to type and see it works broken or dont work at all.

Additional Information Browser google and chrome. Latest version available from google play market. Phone redmi 8 using google keyboard and android version 10, MIUI 12.5.3 (stable version)

[colbster937]

idk if it will work i was the one who added the keyboard button and i only have iOS so i only tested it there

[RealPlurr]

Like keyboard opens but with it also whole game moves down, and secondly it wont even type so idk. ChatGPT says that it technically muss work but it doesn't.

[colbster937]

moves the game down? if its moving the game out of the way for the keyboard then thats probably built into the os/browser.

[RealPlurr]

Yeah but it also makes like idk white gap between keyboard and game it can be also bug of this js feature idk but anyways it isnt such critical bug the most critical that it wont type at all

[colbster937]

But the keyboard opens right?

[RealPlurr]

It opens keyboard but it wont type leme attach photos

[RealPlurr]

[RealPlurr]

Also new bug button goes off screen before it wasn't happening and I typed "Bello" and it didn't wrote as you see

[FlamedDogo99]

I have several ideas I can try, but support is limited since we currently don’t have any android devices to test with. Several ideas:

• [x] Test if changing input opacity from 0 changes anything
• [x] Add type="text" to input element Also, this may be an issue with the Chrome browser on android (see https://github.com/nosir/cleave.js/issues/147)

[colbster937]

I mean we could test in android studio just running a browser

[RealPlurr]

Okay, I hope y'all will be able to fix it. By the way you can emulate android using BlueStackX or smth

[RealPlurr]

I mean we could test in android studio just running a browser

Also good option

[FlamedDogo99]

I just quickly added both ideas, holler if it makes a difference. Edit: I don’t think this will make a difference. The Eagler application is looking for a key event where key, keyCode and which are defined. It may be that your custom keyboard simply isn’t dispatching the correct events, and I’m not really sure how to work around that. If I could directly inject code into the Eagler client during runtime I could easily fix this, but until then I’m not sure. I’ll keep looking into this, and hopefully someone else with more experience with android can weigh in.

[RealPlurr]

Leme test it rq

[RealPlurr]

Now buttons are a bit out of their places

And Now I can't close keyboard using button it keeps appearing after closing it using < or button

[RealPlurr]

Oh wait forgot to rotate phone my bad leme test it rotated

[colbster937]

and the button doesn't close it it only opens it

[FlamedDogo99]

I need to do some more research on this. I’ll get back to you.

[RealPlurr]

Ok so. It still bugged and buttons are out of screen. Secondly its impossible now to close keyboard beacuse it loops opens. Thirdly it wont type like it was. White gaps became smaller but still exist

[RealPlurr]

and the button doesn't close it it only opens it

Then we need add for mobile android devices close button beacuse it loop opens it

[colbster937]

Well by what i have tested its impossible to close the keyboard with js so idk

[RealPlurr]

Then uh need unloop it somehow, anyways but it still wont type its also critical bug now there is 2 critical bugs

[colbster937]

okay...

[RealPlurr]

I think now its kinda chrome issue fully..

[colbster937]

let me test it on chrome on ios and see if i get the same issues

[colbster937]

no i dont get the issue but its probably because apple makes google use webkit on ios chrome but on android im guessing it uses chromium?

[RealPlurr]

Yeah it definitely uses Chromium ig. Anyways it still happens probably even android bug idk. The fact keyboard is hella buggy is fact

[colbster937]

try using another browser that has another engine like firefox and see if it happens there

[RealPlurr]

Same issue

[colbster937]

hmmmmm

[RealPlurr]

No clue it muss be fixed somehow... there is a lot more android users than iOS users so yeah

[colbster937]

yea

[FlamedDogo99]

Alright I have a solution but it will take me some time to fix regardless. 1) Looping open keyboard

• [x] This flaw appears to have been here since the button was added. I’ll have to keep track of the keyboard state and toggle between open and closed, which is fairly easy to implement. Its now fixed in 2.4 2) Android key presses It appears that we can’t trust android to dispatch the proper key events. Eagler needs key, keyCode, and which. My current idea is to completely eliminate android’s keyboard events. Instead, we read changes to the hidden keyboard input and dispatch the event programmatically ourselves. Here’s the general outline of what needs to change
• [x] override key event completely to include an extra don’t ignore flag.
• [x] Update all script key events to include the don’t ignore flag
• This allows us to disregard any keyboard inputs
• [x] add an event listener to the keyboard input that has an onchange event listener.
• [x] When the event listener fires, we read the new value from the input, pass it through to our normal keyEvent function, and then clear the input
• We also need to allow there to be a character within the input so we can detect the delete key press through the length of the input decreasing.

This would eliminate the need for constantly implementing changes to jump through each devices requirements for reading the key events, and feels fairly straightforward to implement.

I’ll start working on this tomorrow unless someone else wants to take a stab at it.

[colbster937]

Yeah I would have made the keyboard button do that and track the state but it just worked for me when clicking the done button on the top of the keyboard it would be fine so that's why I didn't

[PlurrYT-Kolama]

android doesn't have such button

[colbster937]

i fixed the looping check my pull request

[colbster937]

oh and completely off topic but i've found by using shadow client i can get at least 30 fps so i think thats the next thing to try to make it automatically optimize the settings

[colbster937]

well good for you i was just saying from my personal experience

[FlamedDogo99]

Y’all keep it on topic in the issues. I can open up discussions if you really want to do that

[colbster937]

okay sorry but can you?

[RealPlurr]

Anyways lets move to issue. Any progress on fix?

[colbster937]

no not really

[colbster937]

(for me)

[FlamedDogo99]

Actually, I could use all of your help. If anyone has an android device, could they go to https://w3c.github.io/uievents/tools/key-event-viewer.html and type “e”, and post a screenshot of the result here? I’m close to a solution but I want to make sure it will work.

[colbster937]

i dont have an android device but here's it in bluestacks

[RealPlurr]

[PlurrYT-Kolama]

any updates?

[FlamedDogo99]

Oh wow, that’s not good. Most of your UIEvents are undefined, and that makes this extremely hard to work with. This is what it ideally should be closer to: There’s a really bloated solution I could implement, but it’s making me question if I should even put in the effort. This might be something that we wait for Android to fix, because there’s no reason for it not to support keyCode, which, or key. From https://github.com/substance/substance/issues/982:

I read some of the comments in that long thread.. installing hacker's keyboard will fix the issue (sends correct key codes) with the typing and the save button getting triggered properly.

https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en

So it appears to be an issue dealing with the returned key codes.

Y’all might have to fix things on your end

[PlurrYT-Kolama]

uh then its android issue

[PlurrYT-Kolama]

we kinda cant do anything about that so kinda this project is broken for android