Physical Keyboard ENTER Key not working

minix4ever

Active member
I'm trying to get rid of the ON SCREEN keyboard in favor of a physical keyboard. All other Android boxes works fine with the Null Keyboard app (including u9h). Null Keyboard get rid of the ON SCREEN keyboard but I'm having issues with the ENTER key on the physical keyboard. Works pretty much everywhere except in the browser address bars. Same problem with Chrome and Firefox. The ENTER key does not work/register as the "->" Send/Enter key that is available on the ON SCREEN Key.
 
I'm trying to get rid of the ON SCREEN keyboard in favor of a physical keyboard. All other Android boxes works fine with the Null Keyboard app (including u9h). Null Keyboard get rid of the ON SCREEN keyboard but I'm having issues with the ENTER key on the physical keyboard. Works pretty much everywhere except in the browser address bars. Same problem with Chrome and Firefox. The ENTER key does not work/register as the "->" Send/Enter key that is available on the ON SCREEN Key.
Settings/More Settings/System/Languages & input/Physical keyboard/ "show virtual keyboard" switch to off and test the enter key again.
 
Physical ENTER key not working in Browser
Settings/More Settings/System/Languages & input/Physical keyboard/ "show virtual keyboard" switch to off and test the enter key again.

THANKS but didn't work. With your tip I no longer need the Null Keyboard App. Any other idea for SEND? The shortcut assist in advanced gave me hope but no combo for "send" :-(

I doubled check again on my U9H, and I don't have this issue.
 
Physical ENTER key not working in Browser


THANKS but didn't work. With your tip I no longer need the Null Keyboard App. Any other idea for SEND? The shortcut assist in advanced gave me hope but no combo for "send" :-(

I doubled check again on my U9H, and I don't have this issue.
What keyboard are you using? This is now down to the .kl file needed for your specific keyboard.
 
What keyboard are you using? This is now down to the .kl file needed for your specific keyboard.
I am using a Logitech K400+ and when I pressed Enter I was getting letter "q" instead. After researching, I fixed the problem by:
file = /vendor/usr/keylayout/Generic.kl
change: key 28 DPAD_CENTER
to: key 28 ENTER
Of course you need System root on in Device preferences to make this change. I used X-plore with the root setting = "Superuser+mount writable" to edit the file.

It was certainly bugging me. As an interim (till I edited the file), I was able to use Fn-Enter. Hope this helps resolve your issue.
 
What keyboard are you using? This is now down to the .kl file needed for your specific keyboard.
I tried with a physical keyboard and Logitech Keyboard with a BT dongle... All same resulte I also cannot ENTER a manual IP in the config.
 
I am using a Logitech K400+ and when I pressed Enter I was getting letter "q" instead. After researching, I fixed the problem by:
file = /vendor/usr/keylayout/Generic.kl
change: key 28 DPAD_CENTER
to: key 28 ENTER
Of course you need System root on in Device preferences to make this change. I used X-plore with the root setting = "Superuser+mount writable" to edit the file.

It was certainly bugging me. As an interim (till I edited the file), I was able to use Fn-Enter. Hope this helps resolve your issue.

Mines do not send Q, ENTER works as expected in many places such as in this window I'm typing the TEXT. But when it doesn't work in single STRING enty such as adress bars or configuration fields in the Minix Settings. This is extremely annoying.
 
I fixed the problem by:
file = /vendor/usr/keylayout/Generic.kl
change: key 28 DPAD_CENTER
to: key 28 ENTER
Of course you need System root on in Device preferences to make this change. I used X-plore with the root setting = "Superuser+mount writable" to edit the file.
You're really not supposed to edit the generic.kl file, as it governs all devices without a specific .kl file. I would recommend making a copy of generic.kl and renaming it Vendor_XXXX_Product_XXXX.kl . Then use an app such as gamepad tester to find out what the vendor and product ID for your peripheral is, it works for keyboards as well! Proceed to changing "XXXX" in the file name to what is appropriate for your peripheral. Then modify the file to your hearts content.
 
You're really not supposed to edit the generic.kl file, as it governs all devices without a specific .kl file. I would recommend making a copy of generic.kl and renaming it Vendor_XXXX_Product_XXXX.kl . Then use an app such as gamepad tester to find out what the vendor and product ID for your peripheral is, it works for keyboards as well! Proceed to changing "XXXX" in the file name to what is appropriate for your peripheral. Then modify the file to your hearts content.
Thanks for the info. Will follow your suggestion to properly resolve my issue. Curious why the /vendor/usr/keylayout/Generic.kl has key 28 = DPAD_CENTER while /system/usr/keylayout//Generic.kl has key 28 = ENTER ??? The one in /vendor has priority over the one in /system. Again, thanks - love the info sharing in this forum.
 
BUG: Physical Keyboards ENTER Key not sending "send/enter" in most single sting text box (such as browser address line, MINIX/Config fields, etc...). But the ENTER key works as a carriage return in most multi-line text boxes.
 
BUG: Physical Keyboards ENTER Key not sending "send/enter" in most single sting text box (such as browser address line, MINIX/Config fields, etc...). But the ENTER key works as a carriage return in most multi-line text boxes.
Can you please install Gboard from the Play Store and see if it is the same for the enter key in single string text.

Could you also confirm you are on firmware V003A.
 
Physical Keyboard ENTER key not sending ENTER/SEND in single line field
Can you please install Gboard from the Play Store and see if it is the same for the enter key in single string text.Could you also confirm you are on firmware V003A.

V003A Confirmed
GBOAD: FAIL (didn't fix)
 
Sounds like your "ENTER" key is mapped to "DPAD_CENTER". Use an app like "Gamepad Tester" to make sure your keyboard is mapped correctly.

Would DPAD_CENTER act as a proper ENTER in multi-line text fields? Because that's what it's doing.

EDIT: Confirmed: ENTER key registers as DPAD_CENTER using another app.
Gamepad Tester is reporting Key 23 which also refers as DPAD_CENTER according to what I found.

EDIT2:
DPAD_CENTER changed to ENTER in Generic.kl and it worked as you guys expected. THANKS
(I know I know... I should of used "vendor specific.kl" but it wasn't listed and I didn't bother to create one from the Generic.kl master) Plus it didn't screw up the operations of the Minix OEM remote.
 
Last edited:
Would DPAD_CENTER act as a proper ENTER in multi-line text fields? Because that's what it's doing.

EDIT: Confirmed: ENTER key registers as DPAD_CENTER using another app.
Gamepad Tester is reporting Key 23 which also refers as DPAD_CENTER according to what I found.
DPAD_CENTER is incorrect. You have to map that key to "ENTER". You can do this with Gamepad Tester or with a plain text editor. You'll need to know which .kl file maps the keyboard you are using.
 
(I know I know... I should of used "vendor specific.kl" but it wasn't listed and I didn't bother to create one from the Generic.kl master)
Concerning the Generic.kl, there's 2 of them. One of them is mapped as expected, the other is not. You could have just copied the one with the "ENTER" mapping to replace the one with "DPAD_CENTER" mapping.
 
I'm having issues with the ENTER key on the physical keyboard. Works pretty much everywhere except in the browser address bars. Same problem with Chrome and Firefox. The ENTER key does not work/register as the "->" Send/Enter key that is available on the ON SCREEN Key.
Physical ENTER key not working in Browser
I doubled check again on my U9H, and I don't have this issue.
What keyboard are you using? This is now down to the .kl file needed for your specific keyboard.
BUG: Physical Keyboards ENTER Key not sending "send/enter" in most single sting text box (such as browser address line, MINIX/Config fields, etc...). But the ENTER key works as a carriage return in most multi-line text boxes.
Added to the bugtracker under peripherals.
DPAD_CENTER changed to ENTER in Generic.kl and it worked as you guys expected. THANKS
(I know I know... I should of used "vendor specific.kl" but it wasn't listed and I didn't bother to create one from the Generic.kl master) Plus it didn't screw up the operations of the Minix OEM remote.
Removed from the bugtracker under peripherals.
 
Moved to own thread but will question Minix on whether this needs to be addressed in the the next update or if there is a specific reason for why the Generic.kl in /vendor/usr/keylayout has key 28 as DPAD_CENTER instead of ENTER.
 
Moved to own thread but will question Minix on whether this needs to be addressed in the the next update or if there is a specific reason for why the Generic.kl in /vendor/usr/keylayout has key 28 as DPAD_CENTER instead of ENTER.

As long as repairing that won't cause the "q" issue for the virtual keyboards and the Enter key not working on the Minix air mice to come back, preferably...
 
Back
Top