Tekla force-closes on reboot
Bug #792997 reported by
Jorge Silva
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Tecla Access |
Fix Released
|
Critical
|
Jorge Silva |
Bug Description
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
summary: |
- Tekla force-closes on restart + Tekla force-closes on reboot |
Changed in meadl: | |
importance: | Low → High |
Changed in meadl: | |
importance: | High → Critical |
Changed in meadl: | |
milestone: | 0.5-beta → 0.4.3-alpha |
status: | Confirmed → Fix Committed |
Changed in meadl: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
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.