SOTI Pulse Logo

Gboard missing after migration Android 13 on ZEBRA

NL
Nicolas Le Bihan
systemeu

Hello,

Following a migration from Android 11 to Android 13 on ZEBRA model TC21 terminals, some have lost the virtual keyboard. The virtual keyboard is no longer available from any application (Chrome, system, ...).

Setting-Keyboard
During my first production runs, 5/63 terminals had this problem.
When I view the list of applications from the mobicontrol device file, I see that my failed terminals have two versions of the Gboard app:

  • “com.google.android.inputmethod.latin” which is in the ‘uninstalled’ state
  • “com.android.inputmethod.latin”, which is in the ‘installed’ state.

Terminals that are not failed only display

  • “com.google.android.inputmethod.latin” in the “installed” state. 

AppGboard-Android13-KO-AND-OK
I have tried unsuccessfully to re-enable / re-install this bundel “com.google.android.inputmethod.latin” by several different methods (Mobicontrol / Mx).

My device use

  • Agent Mobicontrol : 2024.0.2.1131
  • OEM version : 13-30-12.00-TG-U04-STD-HEL-04

Any ideas? 

inputmethod.latin Android13 keyboard gboard android 13
a year ago
Android
ANSWERS
WT
Warren T
a year ago

Hi Nicolas

We found ourselves when we moved on to a newer Android OS that they were stricter on applications that weren't whitelisted being unavailable and would effectively hide themselves from within the system.

Do you use any lockdown or application run controls?

In order for us to unhide those apps, we had to whitelist them in application run controls, one was also Gboard. When we did this and restarted the agent on the affected devices and restarted the device, Gboard re-appeared amongst other apps. It even got to a stage where because we use System Webview/Chrome Webview we ran into issues with devices where our lockdowns would crash frequently requiring our intervention until they were both whitelisted because as soon as the device would check in during its update period Soti would think the apps weren't available and the menu would effectively crash. 

I'm sure others with more knowledge on the subject might provide further insight but the above certainly helped our problems on the matter.

RS
Rafael Schäfer
a year ago

Depending on your enrollment method you should consider adding follwoing to the JSON (Zero-Touch-Enrollment):

android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED: true;

Default is false which means disabling several apps which could hit gboard maybe (but to be honest never seen that yet as we don't use this option yet).

Otherwise check following script:

enable_system_app com.google.android.inputmethod.latin
N
NSMOD@soti.net
11 months ago

Hi Nicholas, 

I hope the suggestions provided by Rafael and Warren have helped you answer your query. Please inform us if you require further assistance. 

Additionally, if any response has helped address your inquiry, we kindly request you to mark it as "is solution" so that others may also benefit from this information.

Thank you, Rafael and Warren for your valuable suggestions.

Thank you for choosing SOTI.

 

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net

MS
Mark Schweikle
10 months ago

This is not solved. 

Sendnig these scripts do not resolve the issue that OP described.

enable_system_app com.android.inputmethod.latin
enable_system_app com.google.android.inputmethod.latin

Also, application whitelist is not an option for AE  as far as I can see, only Blacklist. Looking forward to further recommendations.

Similar Discussions