Models: Samsung Galaxy Note 10.1, GT-N8013 (WiFi) and SCH-I925 (4G LTE) Android version 4.1.2
I've been experiencing problems with the overly aggressive Samsung soft keyboard popping up whenever I touch the screen to select an input field, even though I am using a Bluetooth keyboard, and only intend to use a Bluetooth keyboard with this device.
Constantly having to dismiss the soft keyboard is a major hindrance to filling out complex forms.
In an attempt to work around the problem, I tried installing the Null Keyboard app from Google Play.
This works for a while, however whenever the Bluetooth connection is lost and reestablished, the Samsung soft keyboard, even though not selected as the default, pops up the following message:
Change input Method. To use Bluetooth keyboard, change input method to Samsung QWERTY
The Samsung soft keyboard then resets itself as default input method.
I have tried other workarounds, such as using the Perfect Keyboard app and decreasing its size to the bare minimum, but unfortunately the Samsung keyboard still watches like a hawk and pops up its insipid dialog and resets itself as the default every time a Bluetooth keyboard connection is established...and then proceeds to pop itself up at the first opportunity. This is irresponsible behavior. The Samsung soft keyboard knows the Bluetooth keyboard is there, yet not only can't it just go away when the Bluetooth keyboard is active, it insists on resetting itself as the default input method regardless of which alternative keyboard you may have selected.
Yes, I know I could root it and disable the otherwise undisableable Samsung keyboard, but unfortunately I need to be able to deal with this solution on about two dozen units in field deployment, so I pretty much need to keep things safe and simple. I'm not trying to do anything crazy - just use a Bluetooth keyboard for one of the primary reasons for which they were created - to be able to type without taking up screen real estate with a soft keyboard.
Has anybody found a workaround for this yet?