1. Cosmin Petrenciuc's Avatar
    I just switched from Microsoft Lumia 950 XL to Samsung Galaxy S9+. After awhile I got accustomed with the new OS way of functioning. The company I work for uses GSuite for collaboration and communication. When I configured my G Suite account on my smartphone, after the workspace has been created, I observed that it disabled both SwiftKey and GBoard keyboards. It left me only with Samsung Keyboard which I do not like.

    I have reached to Samsung Romania support team and they looked at my problem but couldn't figure it out. I have reached our IT administrator and asked him if there is some strange company policy that disables those keyboards. The answer was no.

    Further more, SwiftKey keyboard works perfectly on other colleagues smartphones with Android Oreo and G Suite. This is why I do not think this problem has something to do with the G Suite policies (SwiftKey works in G Suite workspace on Xiaomi and OnePlus smartphones).

    If I remove the workspace from my Galaxy S9+ the SwiftKey works perfectly.

    I'm thinking now that there might be a problem in Google Device Policy app. Maybe the Galaxy S9+ is such a new device that it is not correctly recognized by this app. Or perhaps the combination of Samsung Knox and Google Device Policy is the culprit.

    Does anybody have any ideas? Do you know if I could reach the support team for Google Device Policy app?

    Thank you,
    morbidz likes this.
    03-30-2018 01:25 PM
  2. claykin's Avatar
    ask your IT admin to check policy for non essential apps on Android/mobile.
    03-30-2018 02:06 PM
  3. JHBThree's Avatar
    I just switched from Microsoft Lumia 950 XL to Samsung Galaxy S9+. After awhile I got accustomed with the new OS way of functioning. The company I work for uses GSuite for collaboration and communication. When I configured my G Suite account on my smartphone, after the workspace has been created, I observed that it disabled both SwiftKey and GBoard keyboards. It left me only with Samsung Keyboard which I do not like.

    I have reached to Samsung Romania support team and they looked at my problem but couldn't figure it out. I have reached our IT administrator and asked him if there is some strange company policy that disables those keyboards. The answer was no.

    Further more, SwiftKey keyboard works perfectly on other colleagues smartphones with Android Oreo and G Suite. This is why I do not think this problem has something to do with the G Suite policies (SwiftKey works in G Suite workspace on Xiaomi and OnePlus smartphones).

    If I remove the workspace from my Galaxy S9+ the SwiftKey works perfectly.

    I'm thinking now that there might be a problem in Google Device Policy app. Maybe the Galaxy S9+ is such a new device that it is not correctly recognized by this app. Or perhaps the combination of Samsung Knox and Google Device Policy is the culprit.

    Does anybody have any ideas? Do you know if I could reach the support team for Google Device Policy app?

    Thank you,
    Probably device policy. Theoretically a keyboard app could log keystrokes which is why it's probably blocked. Your IT department would have to fix it on their end.
    Laura Knotek likes this.
    03-31-2018 12:32 AM
  4. cliberti's Avatar
    Only if you set up the work profile. I ran into the same issue. If you do not setup the work profile you can install it
    03-31-2018 03:13 AM
  5. cliberti's Avatar
    And by that I mean setup the device policy just have it combined under your personal profile. If you set a work profile you can’t install a 3rd party keyboard
    Cosmin Petrenciuc likes this.
    03-31-2018 03:16 AM
  6. Cosmin Petrenciuc's Avatar
    And by that I mean setup the device policy just have it combined under your personal profile. If you set a work profile you can’t install a 3rd party keyboard
    Thank you very much. I was a bit against allowing the IT admin to control my entire smartphone. I would have preferred to give access to IT admin only to the workspace.
    But if you say it works if I do not set a workspace I give it a try.
    03-31-2018 05:26 AM
  7. Cosmin Petrenciuc's Avatar
    ask your IT admin to check policy for non essential apps on Android/mobile.
    Thank you. I'll do that.
    03-31-2018 05:27 AM
  8. Cosmin Petrenciuc's Avatar
    Probably device policy. Theoretically a keyboard app could log keystrokes which is why it's probably blocked. Your IT department would have to fix it on their end.
    You would think that's the case but again how come that my colleagues with Xiaomi, Huawei and OnePlus smartphones can use SwiftKey in conjunction with the G Suite account? They do not have specific device policies just for themselves.
    03-31-2018 05:30 AM
  9. Rukbat's Avatar
    Different manufacturers make different modifications to Android, so not all Android phones are running exactly the same firmware.

    Did you try just re-enabling Swiftkey after G Suite was installed?
    03-31-2018 01:21 PM
  10. Cosmin Petrenciuc's Avatar
    Different manufacturers make different modifications to Android, so not all Android phones are running exactly the same firmware.

    Did you try just re-enabling Swiftkey after G Suite was installed?
    Yes, I did that. No success. I even tried to install G Board after I register the Google Suite account. No luck either.

    If it would have been a firmware problem wouldn't that have meant the SwiftKey would not have worked at all on Samsung Galaxy S9+? Without G Suite account SwiftKey works flawlessly.
    03-31-2018 02:07 PM
  11. Cosmin Petrenciuc's Avatar
    And by that I mean setup the device policy just have it combined under your personal profile. If you set a work profile you can’t install a 3rd party keyboard
    I owe you one. It worked if I didn't setup a work profile.
    03-31-2018 02:59 PM
  12. Prestige Group's Avatar
    I owe you one. It worked if I didn't setup a work profile.
    I had this same issue on my Note 8. I added my own email to the google app and installed the admin. I then uninstalled the work profile and went through the process again. There is a step which you can skip rather than install. This is for security and admin controls/funtions. It then added my own domain email to the list of gmail accounts. No more problem disabling the swiftkey app. Now just trying to access that email and download my emails...will see how it goes

    Thank you!

    J
    05-23-2018 09:48 PM
  13. strikeIII's Avatar
    From my understanding is any MDM policies utilize Samsung Knox and once Knox is enabled it blocks some 3rd party keyboards.
    If possible it would need to be a Knox configuration from G Suite Admin to allow it. This is why it works differently in other Android devices because they don't use Knox.
    05-24-2018 06:14 PM
  14. Ellover's Avatar
    And by that I mean setup the device policy just have it combined under your personal profile. If you set a work profile you can’t install a 3rd party keyboard
    This was not true for Samsung 8. Work profile was installed, Swiftkey worked fine. With the S9+, unfortunately Swiftkey is not permitted. I suspect it is Samsung Knox, not Google Device Policy.

    Have others found a workaround? I need my work profile and personal profile on this phone, however the Samsung default keyboard is horrendous. Even simple words like "you" are autocorrected to "ugly" or "tlou"!!
    09-13-2018 12:38 AM

Similar Threads

  1. Blue LED light always on when screen is off on Galaxy S9
    By Dustbury in forum Android 8.0 Oreo
    Replies: 3
    Last Post: 10-26-2018, 11:57 AM
  2. Replies: 2
    Last Post: 03-30-2018, 02:56 PM
  3. why won't my galaxy tablet stop Scanning ?
    By Android Central Question in forum Ask a Question
    Replies: 2
    Last Post: 03-30-2018, 02:44 PM
  4. My phone Samsung Galaxy S7 randomly calls people I don't know.
    By Android Central Question in forum Ask a Question
    Replies: 1
    Last Post: 03-30-2018, 01:29 PM
  5. How does one change the font color of a text bubble on galaxy s7 active
    By Android Central Question in forum Ask a Question
    Replies: 0
    Last Post: 03-30-2018, 01:01 PM
LINK TO POST COPIED TO CLIPBOARD