fix(android): Convert Keyman app layout to use ConstraintLayout for handling edge-to-edge 🪟

[darcywong00]

Follows #14395 for #14248

This uses Android Studio's tool to convert the top level layout from RelativeLayout to ConstraintLayout.
Layout also updated with constraints to specify the order and boundaries. This way, the edge-to-edge doesn't cover up the top and bottom portions of the app.

Also incorporates @chrisvire's suggestions from the KAB team along with AlphaTiles/AlphaTiles#160 to BaseActivity

Note: BaseActivity.setupStatusBarColors() only works on Android API M (27) through Upsidedown Cake (34)

Screenshots

Phone Android API 34 in portrait and landscape orientations. Landscape orientation width to tweak separately (Now fixed)

Keyman app	System Keyboard

TODO's on separate PRs:

• Tweak landscape keyboard width
• Update other activities in the Keyman app and engine
• Update FirstVoices and Sample apps
• Handle OSK on API 36

User Testing

(edit) Changing groups from API 28 to API 34
Setup - Install the PR build of Keyman for Android on an Android device/emulator of the specified API

GROUP_PHONE_API_34: Use Android API 34 on a phone device/emulator
GROUP_TABLET_API_34: Use Android API 34 on a tablet device/emulator

• TEST_INAPP - Verifies in-app keyboard layout is fine

1. Install Keyman for Android on the specified Android API level for the device/emulator
2. Launch the app in the default Portrait orientation and dismiss the Get Started menu
3. Observe the Keyman app and verify:
   • Keyman menu bar is not covered by the top status bar
   • in-app keyboard is not covered by the bottom navigation bar
   • keyboard buttons and suggestion bar function as expected
4. Rotate the app to landscape orientation (unlock orientation lock if necessary) and wait for the app to refresh
5. Observe the Keyman app and verify:
   • Keyman menu bar is not covered by the top status bar
   • in-app keyboard is not covered by the camera notch or navigation bar
   • keyboard buttons and suggestion bar function as expected

• TEST_SYSTEM_KEYBOARD - Verifies the system keyboard is not obscured

1. Install Keyman for Android on the specified Android API level for the device/emulator
2. Launch the app in the default Portrait orientation use the Get Started menu to enable Keyman as the default system keyboard
3. Launch Chrome app and select text area
4. With Keyman as the system keyboard, verify:
   • system keyboard is not obscured by the bottom navigation bar
   • keyboard buttons and suggestion bar function as expected
5. Rotate the device to landscape orientation (unlock orientation lock if necessary) and wait for the keyboard to refresh
6. With Keyman as the system keyboard, verify
   • system keyboard is not obscured by the camera notch or navigation bar
   • keyboard buttons and suggestion bar function as expected
     .

[keymanapp-test-bot]

User Test Results

Test specification and instructions

• ✅ GROUP_PHONE_API_34: Use Android API 34 on a phone device/emulator

  2 tests PASSED

  • ✅ TEST_INAPP (PASSED) (notes)
  • ✅ TEST_SYSTEM_KEYBOARD (PASSED) (notes)

• ⬜ GROUP_PHONE_API_36: Use Android API 36 on a phone device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation"

  • ⬜ TEST_INAPP (OPEN): retest
  • ⬜ TEST_SYSTEM_KEYBOARD (OPEN): retest

• ✅ GROUP_TABLET_API_34: Use Android API 34 on a tablet device/emulator

  2 tests PASSED

  • ✅ TEST_INAPP (PASSED) (notes)
  • ✅ TEST_SYSTEM_KEYBOARD (PASSED) (notes)

• 🟥 GROUP_TABLET_API_36: Use Android API 36 on a tablet device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation"

  • ✅ TEST_INAPP (PASSED) (notes)
  • 🟥 TEST_SYSTEM_KEYBOARD (FAILED) (notes)

Results Template

# Test Results

### GROUP_PHONE_API_36: Use Android API 36 on a phone device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation"

* **TEST_INAPP (OPEN):** notes
* **TEST_SYSTEM_KEYBOARD (OPEN):** notes

Retesting Template

Test-bot: retest GROUP_TABLET_API_36 TEST_SYSTEM_KEYBOARD

Test Artifacts

• Android
  • Keyman for Android apk
  • FirstVoices for Android 16.0 apk
  • FirstVoices Keyboards for Android apk
  • KeyboardHarness apk
  • Keyman for Android 16.0 apk
  • KMSample1 apk
  • KMSample2 apk

[MattGyverLee]

@darcywong00 The App Builders have the same API35 problem. I see that your fix is in the Keyman Android app and not the Keyman engine. Does the proposed fix extend to a SystemKeyboard when the app is closed and make it show above the toolbar as well?

[darcywong00]

I'm still trying to work on the fix (this is in progress :( )

[MattGyverLee]

Well it seems that you and @AaronHemphill are SIL's experts on this issue (we just discovered it today). App builders was hoping to release AB 13 soon and this API35 issue may be a blocker. It seems to affect all of the apps' bottom elements, but blocking the bottom bar of a keyboard is the worst case.

PR ready to re-review.
Note: only the main app is updated (in-app keyboard and system keyboard).

[MattGyverLee]

Richard has completed his inset work for the app builders, including fixing these margins.
https://github.com/sillsdev/app-builders/issues/1925

[darcywong00]

@dinakaranr - maybe a polyfill missing on older Android device. I'll change the tests to use API 34 instead.
Test-bot: retest

[dinakaranr]

Test Results

I retested this PR in the "Keyman-19.0.89-alpha-test-14396" build on Android 9, API_34 and API_36 for Mobile and Tablet. Here I am sharing my observation.

GROUP_PHONE_API_34: Use Android API 34 on a phone device/emulator

• TEST_INAPP (Passed):

1. Install Keyman-19.0.89-alpha-test-14396 for Android on the Android 9 API_34 for the device/emulator.
2. Launch the app in the default Portrait orientation and dismiss the Get Started menu
3. Observe the Keyman app and verify:
   • Keyman menu bar is not covered by the top status bar on the horizontal bar. It works well.
   • in-app keyboard is not covered by the bottom navigation bar. It works well.
   • keyboard buttons and suggestion bar function are not work as expected. because keyboard does not appear.
4. Rotate the app to landscape orientation (unlock orientation lock if necessary) and wait for the app to refresh
5. Observe the Keyman app and verify:
   • Keyman menu bar is not covered by the top status bar. It works well.
   • in-app keyboard is not covered by the camera notch. It works well.
   • keyboard buttons and suggestion bar function works as expected.

• TEST_SYSTEM_KEYBOARD (Passed):

1. Install Keyman-19.0.89-alpha-test-14396 for Android on the Android 9 API_34 for the device/emulator.
2. Launch the app in the default Portrait orientation use the Get Started menu to enable Keyman as the default system keyboard
3. Launch Chrome app and select text area(online editor webpage)
4. With Keyman as the system keyboard, verify:
   • system keyboard is not obscured by the bottom navigation bar
   • keyboard buttons and suggestion bar function are not work as expected. because keyboard does not appear.
5. Rotate the device to landscape orientation (unlock orientation lock if necessary) and wait for the keyboard to refresh
6. With Keyman as the system keyboard, verify
   • system keyboard is obscured by the camera notch or navigation bar
   • keyboard buttons and suggestion bar function are not work as expected. because keyboard does not appear.
     Please refer to the screenshot below

GROUP_PHONE_API_36: Use Android API 36 on a phone device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation"

• TEST_INAPP (Passed):

1. Install Keyman-19.0.89-alpha-test-14396 for Android on the Pixel 8 API_36 for the device/emulator.
2. Launch the app in the default Portrait orientation and dismiss the Get Started menu
3. Observe the Keyman app and verify:
   • Keyman menu bar is not covered by the top status bar on the horizontal bar. It works well.
   • in-app keyboard is not covered by the bottom navigation bar. It works well.
4. Rotate the app to landscape orientation (unlock orientation lock if necessary) and wait for the app to refresh
5. Observe the Keyman app and verify:
   • Keyman menu bar is not covered by the top status bar. It works well.
   • in-app keyboard is not covered by the camera notch. It works well.
   • keyboard buttons and suggestion bar function works expected.

• TEST_SYSTEM_KEYBOARD (failed):

1. Install Keyman-19.0.89-alpha-test-14396 for Android on the Pixel 8 API_36 for the device/emulator.
2. Launch the app in the default Portrait orientation use the Get Started menu to enable Keyman as the default system keyboard
3. Launch Chrome app and select text area(online editor webpage)
4. With Keyman as the system keyboard, verify:
   • system keyboard is not obscured by the bottom navigation bar. It works well.
   • keyboard buttons and suggestion bar function works as expected.
5. Rotate the device to landscape orientation (unlock orientation lock if necessary) and wait for the keyboard to refresh
6. With Keyman as the system keyboard, verify
   • system keyboard is not obscured by the camera notch or navigation bar. It works well.
   • keyboard buttons and suggestion bar function are not work as expected. because keyboard does not appear.
     Please refer to the screenshot below

GROUP_TABLET_API_34: Use Android API 34 on a tablet device/emulator

• TEST_INAPP (passed):

1. Install Keyman-19.0.89-alpha-test-14396 for Android on the Android 9 Tablet API_34 for the device/emulator.
2. Launch the app in the default Portrait orientation and dismiss the Get Started menu
3. Observe the Keyman app and verify:
   - Keyman menu bar is not covered by the top status bar on the horizontal bar. It works well.
   - in-app keyboard is not covered by the bottom navigation bar. It works well.
   - keyboard buttons and suggestion bar function works as expected.
4. Rotate the app to landscape orientation (unlock orientation lock if necessary) and wait for the app to refresh
5. Observe the Keyman app and verify:
   - Keyman menu bar is not covered by the top status bar. It works well.
   - in-app keyboard is not covered by the camera notch. It works well.
   - keyboard buttons and suggestion bar function works as expected.

• TEST_SYSTEM_KEYBOARD (passed):

1. Install Keyman-19.0.89-alpha-test-14396 for Android on the Android 9 Tablet API_34 for the device/emulator.
2. Launch the app in the default Portrait orientation use the Get Started menu to enable Keyman as the default system keyboard
3. Launch Chrome app and select text area(online editor webpage)
4. With Keyman as the system keyboard, verify:
   - system keyboard is not obscured by the bottom navigation bar. It works well.
   - keyboard buttons and suggestion bar function as expected. It works well.
5. Rotate the device to landscape orientation (unlock orientation lock if necessary) and wait for the keyboard to refresh
6. With Keyman as the system keyboard, verify
   - system keyboard is not obscured by the camera notch or navigation bar. It works well.
   - keyboard buttons and suggestion bar function as expected.
   Please refer to the screenshot below

GROUP_TABLET_API_36: Use Android API 36 on a tablet device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation"

• TEST_INAPP (Passed):

1. Install Keyman-19.0.89-alpha-test-14396 for Android on the Pixel 8 tablet API_36 for the device/emulator.
2. Launch the app in the default Portrait orientation and dismiss the Get Started menu
3. Observe the Keyman app and verify:
   - Keyman menu bar is not covered by the top status bar on the horizontal bar. It works well.
   - in-app keyboard is not covered by the bottom navigation bar. It works well.
   - keyboard buttons and suggestion bar function as expected. It works well
4. Rotate the app to landscape orientation (unlock orientation lock if necessary) and wait for the app to refresh
5. Observe the Keyman app and verify:
   - Keyman menu bar is not covered by the top status bar. It works well.
   - in-app keyboard is not covered by the camera notch. It works well.
   - keyboard buttons and suggestion bar function works expected.

• TEST_SYSTEM_KEYBOARD (failed):

1. Install Keyman-19.0.89-alpha-test-14396 for Android on the Pixel 8 API_36 for the device/emulator.
2. Launch the app in the default Portrait orientation use the Get Started menu to enable Keyman as the default system keyboard
3. Launch Chrome app and select text area(online editor webpage)
4. With Keyman as the system keyboard, verify:
   - system keyboard is not obscured by the bottom navigation bar. It works well.
   - keyboard buttons and suggestion bar function as expected.
5. Rotate the device to landscape orientation (unlock orientation lock if necessary) and wait for the keyboard to refresh
6. With Keyman as the system keyboard, verify
   - system keyboard is not obscured by the camera notch or navigation bar. It works well.
   - keyboard buttons and suggestion bar function are not work as expected. because keyboard does not appear.
   Please refer to the screenshot below

[darcywong00]

Ah, there may be some interaction on the Android 36 emulator while a physical keyboard is plugged in.
Will update user test setup steps for the following:

device Settings --> Keyboard --> On-screen keyboard --> click Gboard --> physical keyboard --> Show on-screen keyboard needs to be "on"

[darcywong00]

Setup steps for API 36 updated.
Test-bot: retest GROUP_PHONE_API_36
Test-bot: retest GROUP_TABLET_API_36

[darcywong00]

I still can't get the OSK to show on API 36. Will move those tests and address on a follow-on PR

Copying those test steps here:

For GROUP_PHONE_API_36 and GROUP_TABLET_API_36, additional steps if running on emulator:
device Settings --> Keyboard --> On-screen keyboard --> click Gboard -->  physical keyboard --> Show on-screen keyboard needs to be "on". This way, the on-screen keyboard appears in the emulator.

GROUP_PHONE_API_36: Use Android API 36 on a phone device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation"

GROUP_TABLET_API_36: Use Android API 36 on a tablet device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation"

And clearing the tests that got moved:

Test-bot: retest GROUP_PHONE_API_36 TEST_SYSTEM_KEYBOARD, GROUP_TABLET_API_36 TEST_SYSTEM_KEYBOARD

[AaronHemphill]

Hi all, I'm no expert on this issue, but I thought I had resolved edge to edge layout issues for Alpha Tiles, but then the Play Store started complaining about apps that were being published, so I spent the day yesterday working with ChatGPT to rewrite the entire ActivityLayouts.java file and then testing it on several devices. I think we're all set now, but we'll see what feedback the Play Store review gives and what feedback (hopefully none!) we get from teams receiving the updated version of the Alpha Tiles app. Here's the before and after of ActivityLayouts.java: https://github.com/AlphaTiles/AlphaTiles/pull/237/files#diff-ffa9782556981f30f50417410a12d591b1659c2b19873327147a9330bbc1982e Aaron

…

On Tue, Aug 12, 2025 at 2:41 AM Darcy Wong ***@***.***> wrote: *darcywong00* left a comment (keymanapp/keyman#14396) <#14396 (comment)> I still can't get the OSK to show on API 36. Will move those tests and address on a follow-on PR Copying those test steps here: For GROUP_PHONE_API_36 and GROUP_TABLET_API_36, additional steps if running on emulator: device Settings --> Keyboard --> On-screen keyboard --> click Gboard --> physical keyboard --> Show on-screen keyboard needs to be "on". This way, the on-screen keyboard appears in the emulator. GROUP_PHONE_API_36: Use Android API 36 on a phone device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation" GROUP_TABLET_API_36: Use Android API 36 on a tablet device/emulator. Also change device to use 3-button navigation. Go to Device settings --> Display & Touch --> Navigation mode --> change from "Gesture navigation" to "3-button navigation" — Reply to this email directly, view it on GitHub <#14396 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARCHYOVHHYNAAWSHFRUVF4L3NGSEVAVCNFSM6AAAAACCHNQF6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZYGMZTCNRUGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mcdurdin]

I still can't get the OSK to show on API 36. Will move those tests and address on a follow-on PR

It'd be better to get it fixed fully here, I think. I don't want to see the build on master not working on API 36 devices...

[keyman-server]

Changes in this pull request will be available for download in Keyman version 19.0.101-alpha