Comment 1 for bug 792997

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.