Tekla force-closes on reboot

[Jorge Silva]

Android 2.2.1 Froyo on Milestone

When any of the alternative input methods are selected (fullscreen switch, connect to Tekla Shield or Always show keyboard) restarting the handset always results in one or two force-closes before Tekla actually starts properly

[Jorge Silva (jorge-silva)]

The source of the problem seems to be a null pointer exception caused by trying to force-open the keyboard before it has been created. A potential solution is to delay the call to show the keyboard until well after the boot completed intent is received. Will experiment with adding a delayed call that opens/configures the keyboard a few seconds after the phone has finished booting.

[Jorge Silva (jorge-silva)]

After additional testing, the issue still appears sporadically. The problem is a related to trying to act on the soft input method (e.g. draw highlights) before the OS creates it and shows it on the screen (returning a null pointer exception). Another alternative using a splash screen that requests the keyboard to be shown, will be explored. This will require adding the ability to receive BOOT_COMPLETED events from the OS.