Open Nick768 opened 5 months ago
I'm unable to reproduce this, on my phone the keyboard just doesn't show up (not normal, and not in the broken state). Also, when enabling the Show virtual keyboard setting, the keyboard is displayed normally.
Tested with 1.3 and latest build as of 789b76b790e51fe26e1d8a2c2beb0ebaf5a09a01, on Samsung Galaxy A3 2017, LineageOS 17.1 (Android 10). Either it got fixed since 1.3-beta1 (I don't think so), or it might depend on Android version.
Ok, that's interesting. I try to test it on another tablet running Android 12L... I could also try it with other keyboards. Maybe it has something to do with this special keyboard, because it is connected to the pogo pins of my tablet and deeply integrated in it's software...
That could be a thing. But I remember someone reported there are also problems with hardware keyboard on Windows Subsystem for Android... Maybe it's also some issue in AOSP keyboard forks, then you would see the same problem in e.g. OpenBoard and Indic Keyboard.
Ah, interesting. Yeah, OpenBoard has the same issue. I will try Indic Keyboard as well and the other things I mentioned when I have time for it... I'll report my results back to you
Ok, I tried OpenBoard and Indic Keyboard. Both have this issue, but both do not cover the whole screen. They both show the slightly darker bar at the bottom of the screen. The rest of the screen keeps as it is... Interesting fact: Every AOSP based keyboard I've tested so far sometimes crash if I connect my keyboard and tap in an input field... Now I've to test other tablet and keyboard combos. I wonder if florisboard is also AOSP based, because this keyboard did not have this overlays and bars.
No, FlorisBoard is not AOSP based
I appear to have the same issue on my Galaxy Tab S9 FE running Android 14. The entire screen goes blank until I back out of the keyboard if I have my bluetooth keyboard connected, and it does not happen with the default Samsung keyboard. I also noted it happens with OpenBoard.
I've narrowed it down a little using the debugger. It does not appear to happen sometimes until the device orientation is changed, then happens consistently.
Describe the bug Everytime I tap on an input box HeliBoard is opening without checking if there is a hardware keyboard connected. It shows a white fullscreen overlay on top so that you can't see nothing anymore (see my screenshot). This does also happen with OpenBoard, but not with other keyboards
To Reproduce
Expected behavior HeliBoard shouldn't open when using a hardware keyboard. Nothing should happen at all when you tap on an input box with a hardware keyboard connected
Screenshots
App version Every app version (latest 1.3 beta-1 as well)
Device:
Additional context Can someone test it on other devices? Would be helpful to see, if it is reproduceable on other android devices with hardware keyboards