You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when the:keyboard is visible, the bottom row is not clickable, as it is coveted by the android UI input area with the arrow toward the bottom, which is there to exit from the keyboard enter mode.
Is it possible to shift the kb up by the correct amount of pixels?
in the image below I made the kb huge, to be able to access the bottom keys
As a workaround, after messing with the android settings for about an hour i found a setting under gesture navigation to hide the navigation bar. This made the down arrow and keyboard select buttons not show up on top of this otherwise awesome keyboard. (moto edge android 15).
Edit:
Systemnavigation
Navigationstasten automatisch deaktivieren
Codeblock auswählen
Und dann Code Board immer aktivieren ...
I found it (don't know English words I am a noob)
Would be easier for beginners to have a shorter way to solve this problem maybe an intern link to this setting? Or another soution ?
This may be the same as issue #137. I have a fix that might work for you in this fork. The release files including a built APK are here, if anyone is feeling reckless enough to use them!
This works in the emulator using the standard system images in versions 14 (which isn't broken anyway), 15 (which is especially broken) and 16+ (which have layout problems in the config activity but not the actual keyboard).
If someone can tell me whether this works correctly on an actual phone that's having a problem that would be great.
@12kittens I'm sorry to hear that. I have some questions, after which I will probably still be completely in the dark anyway!
Which version of Android are you running?
Is the problem exactly the same with the forked version of Codeboard and the original, or do they have slightly different layout problems in some orientations?
Was it working fine for you before a recent system update, then not working afterward?
Does using the fork make a difference to the Codeboard settings activity layout?
I hope you don't feel pressure to respond -- like I said, I'll probably still be confused regardless, and I'm not likely to respond in the next few days anyway.
P.S. I actually went to bed a week ago thinking I had already posted this message. Whoops.
If anyone is feeling adventurous I was able to resolve this on my Google Pixel 6 by replacing the following two functions in KeyboardLayoutView.java
@OverrideprotectedvoidonMeasure(intwidthMeasureSpec, intheightMeasureSpec) {
DisplayMetricsmetrics = getContext().getResources().getDisplayMetrics();
intavailableHeight = metrics.heightPixels;
intavailableWidth = metrics.widthPixels;
floatkeyboardSize = availableHeight > availableWidth
? uiTheme.portraitSize
: uiTheme.landscapeSize;
// Create a bottom gap (48dp is standard for navigation bars). // Adjust the '48' higher or lower depending on how much space you want.intbottomGapPx = (int) (48 * metrics.density);
// Add the gap to the keyboard's total heightsetMeasuredDimension(availableWidth, (int)(availableHeight * keyboardSize) + bottomGapPx);
}
@OverrideprotectedvoidonLayout(booleanchanged, intl, intt, intr, intb) {
DisplayMetricsmetrics = getContext().getResources().getDisplayMetrics();
intbottomGapPx = (int) (48 * metrics.density);
finalintcount = getChildCount();
for (inti = 0; i < count; i++) {
finalViewchild = getChildAt(i);
// Subtract the gap from the layout bottom bound to push the keys upwardchild.layout(l, t, r, b - bottomGapPx);
}
}
Note that this is not a perfect solution because it hardcodes the gap so it might be annoying for devices where the keyboard is functioning properly. I hope this helps someone.
Activity
proidit commentedon Dec 9, 2025
same problem
brentpkennedy commentedon Dec 19, 2025
As a workaround, after messing with the android settings for about an hour i found a setting under gesture navigation to hide the navigation bar. This made the down arrow and keyboard select buttons not show up on top of this otherwise awesome keyboard. (moto edge android 15).
Lunabatzn commentedon Feb 28, 2026
Same but the setting not found at Xiaomi 13T pro
Edit:
Systemnavigation
Navigationstasten automatisch deaktivieren
Codeblock auswählen
Und dann Code Board immer aktivieren ...
I found it (don't know English words I am a noob)
Would be easier for beginners to have a shorter way to solve this problem maybe an intern link to this setting? Or another soution ?
Rachid90 commentedon May 4, 2026
Same problem. Pixel 7.
larrychips commentedon Jun 13, 2026
This may be the same as issue #137. I have a fix that might work for you in this fork. The release files including a built APK are here, if anyone is feeling reckless enough to use them!
This works in the emulator using the standard system images in versions 14 (which isn't broken anyway), 15 (which is especially broken) and 16+ (which have layout problems in the config activity but not the actual keyboard).
If someone can tell me whether this works correctly on an actual phone that's having a problem that would be great.
12kittens commentedon Aug 29, 2026
Got a similar problem in Xiaomi Poco C85. @larrychips fork didn't solve the issue for my device

ChemicalRascal commentedon Sep 5, 2026
Larry's fork fixed this for the Boox Note 5, which runs Android 15, though I think it's a pretty thoroughly customized version.
larrychips commentedon Sep 10, 2026
@12kittens I'm sorry to hear that. I have some questions, after which I will probably still be completely in the dark anyway!
I hope you don't feel pressure to respond -- like I said, I'll probably still be confused regardless, and I'm not likely to respond in the next few days anyway.
P.S. I actually went to bed a week ago thinking I had already posted this message. Whoops.
saltchicken commentedon Oct 13, 2026
If anyone is feeling adventurous I was able to resolve this on my Google Pixel 6 by replacing the following two functions in KeyboardLayoutView.java
Note that this is not a perfect solution because it hardcodes the gap so it might be annoying for devices where the keyboard is functioning properly. I hope this helps someone.