We tried everything but eventually we did wipe the device and re-enrolled, which resolved the issue.
What was bizarre was that even after we removed the kiosk, the device did not have access to a samsung keyboard. In the input settings on the device the only options available were for Google or Samsung Voice input, no keyboard option. After wiping and re-enrolling the default is now Samsung Keyboard.
Thanks all for your suggestions!
------------------------------
JOSEPH ADETORO
------------------------------
Original Message:
Sent: Mon January 11, 2021 11:09 PM
From: mohanraj muthusamy
Subject: COSU Kiosk
Hi Joseph,
Try whitelisting the following app id's
com.samsung.android.honeyboard
com.sec.android.inputmethod
you can find the installed app id on the mobile using this play store app (https://play.google.com/store/apps/details?id=sk.styk.martin.apkanalyzer).using this app can find that device keyboard app id.
------------------------------
mohanraj
Original Message:
Sent: Mon January 11, 2021 07:36 PM
From: JOSEPH ADETORO
Subject: COSU Kiosk
No they do not have any of those settings disabled
------------------------------
JOSEPH ADETORO
Original Message:
Sent: Mon January 11, 2021 02:42 PM
From: Matt Shaver
Subject: COSU Kiosk
The keyboard shouldn't have to be whitelisted separately. It's an interesting glitch though - do they happen to have any of the following policy features enabled? Can they try disabling them to see if the keyboard appears?
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
Original Message:
Sent: Mon January 11, 2021 02:23 PM
From: JOSEPH ADETORO
Subject: COSU Kiosk
That app ID worked for allowing the dialer app. However the customer says she is still unable to access the keyboard in any other app including text messaging.
I've opened a case on the keyboard. Thanks Matt!
------------------------------
JOSEPH ADETORO
Original Message:
Sent: Mon January 11, 2021 12:52 PM
From: Matt Shaver
Subject: COSU Kiosk
Can you ask the client to whitelist the com.android.phone app ID as well, and if that does not resolve, could you open a case at ibm.com/mysupport. If it doesn't work, we'll need to gather some sensitive info to continue troubleshooting.
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
Original Message:
Sent: Mon January 11, 2021 12:35 PM
From: JOSEPH ADETORO
Subject: COSU Kiosk
Hi Matt,
The dialer is a kiosk launcher setting that we enabled in the policy
These are the app IDs we have manually whitelisted:
| |
| |
| |
com.google.android.apps.maps |
| |
com.samsung.android.incallui |
| |
com.samsung.android.messaging |
| |
com.google.android.webview |
| |
com.samsung.android.dialer |
|
The device is a Samsung Galaxy Note20 on Android 11
The admin is unable to type anything because the keyboard doesn't come up. When she tries to input anything she gets an "Autofil" prompt
I believe the dialer and keyboard issues are related
------------------------------
JOSEPH ADETORO
Original Message:
Sent: Mon January 11, 2021 12:04 PM
From: Matt Shaver
Subject: COSU Kiosk
Hi Joe - what's the app ID they whitelisted in the policy - is it com.android.phone? When they state that it's not allowing access - does the app appear at all or is it there but fails to launch or crashes? Any on screen errors?
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
Original Message:
Sent: Fri January 08, 2021 09:20 AM
From: JOSEPH ADETORO
Subject: COSU Kiosk
I have a customer using the Android Enterprise COSU kiosk on a Samsung device. For some reason the kiosk doesn't allow her to access the dialer app. It appears the dialer app also controls the keyboard so as a result she is also unable to type. We already have the dialer app whitelisted in the kiosk policy and we also tried whitelisting the app ID com.samsung.android.incallui but still not working
Any help would be appreciated.
Joe
------------------------------
JOSEPH ADETORO
IBM Security MaaS360 @ AT&T
------------------------------