Samsung Galaxy S phone crashes after disconnecting shield

Bug #800028 reported by William Li
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tecla Access
Fix Released
High
Jorge Silva

Bug Description

Phone is Samsung Galaxy S (Captivate from AT&T)
When I disconnect the Shield and switch back to my regular keyboard (Swype), things seem to be working fine. However, the Tekla app is still running, and it seems to lock up my phone. A few hours ago, the Tekla just gave up after a little while and closed; right now, though, it seems that I may have locked up my phone more seriously, requiring a hard battery-out reset.

I noticed that the Tekla app is still running by seeing it in my "Task Killer" list in a program called ZDBox, which allows closing of specific apps.

Revision history for this message
Jorge Silva (jorge-silva) wrote :

Michele wrote: "I left the shield paired while working away I was not using it and had selected the swype keyboard but the icon was still in the lef corner and the green light was on. If I hit the switch it activated the screen but not the scanning as had not selected that as an input method. After an hour and a bit my phone vibrated to let me know the tekla app had crashed and I needed to close it. It remained paired and the icon still remained on the screen. So I selected tekla as an input and it started to scan. The green light was still shining BUT the switch no longer worked ...it looked paired. When I accessed the tekla keyboard settings it would not respond.

I could not get it to pair to the shield, which actually was green as if paired. When i tried to connect to the shield it said that there are no shields in range. I then turned off blue tooth and then it was finally not green but red but the tekla icon was still on the screen even though it was not selected or operational. So according to my phone it was connected to the shield even with bluetooth off.I was finally able to activate the switch by turning on blue tooth and searching again for the shield."

Revision history for this message
Jorge Silva (jorge-silva) wrote :

Switching keyboards was not part of the Tekla release testing procedure. This case has now been added and should be solved in the next release:
http://wiki.scyp.idrc.ocad.ca/w/Tekla/App_Release_Testing

Changed in meadl:
status: New → Fix Released
milestone: none → 0.4.4-alpha
assignee: nobody → Jorge Silva (jorge-silva)
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.