Force stop on all version 0.3.x

[Nick MItchell]

Hi, I installed Tekla versions 0.3.1, 0.3.2 & 0.3.3 on Motorola Defy Android 2.1 (eclair).
Install successful.
On selecting Tekla as the input method all versions Force Stop.
Presently unable to test & assess Tekla for use by some of our patients.

Is there any debugging I can do or am I missing something?

Regards

Nick

[Jorge Silva (jorge-silva)]

Could you describe in a bit more detail what you are doing to select Tekla as the input method? I would also suggest to uninstall all versions, restart the phone and then try installing again going from lower to higher versions (not the other way around). Hope this helps!

[Nick MItchell (nicholas-mitchell)]

Hi Jorge,
thanks for the prompt response.

After installing I selected Tekla as the input method by
1) selecting search (fixed magnifier icon)
2) long pressing the text/search input field
3) saying ok to input method window
4) selecting Tekla as the input method.

I also tried selecting Tekla from the Settings/Keyboard & Language options.

Installed all 0.3.x versions of Tekla. Got Force Close on each one.
First cleared all previous Tekla installs.
Turned phone off.
Turned phone on.
Installed Tekla version to be tested.
Turned phone off.
Turned phone on.
Selected Tekla as input method as decribed above.
Force closed. Several times before being able to revert to multitouch keyboard.
Tried selecting via settings, Force Closed.
Repeat for each version tested.

Installed 0.2.x
Timed out with Force Closed when attempting to select Tekla options.
No response when Tekla selected as input method.
No Force Closed messages.
Uninstalled 0.2.x

Installed 0.1.x.
It Works!

Thanks

Nick

[Jorge Silva (jorge-silva)]

This must be very annoying. I did a bit of searching and found a similar issue with another input method (http://www.dexilog.com/smartkeyboard/forum/viewtopic.php?f=2&t=1121), so it may be a specific incompatibility with this particular handset. Unfortunately though, without the handset, this is practically impossible for us to debug. However, if you feel up for it, we can guide you through the debugging process (e.g., via Skype). Depending on how comfortable you are hacking around the code, it may take a few sessions to set you up and identify the issue. So, are you up for some hacking and debugging with remote assistance? If so, just email me directly (https://launchpad.net/%7Ejorge-silva/+contactuser) and we can go from there.

cheers!

[Jorge Silva (jorge-silva)]

A couple of new versions have been released. Nick, could you confirm whether the issue still exists? the newest version is 0.4.2 alpha.