Keyboard disappearing

For some reason, if I'm typing pretty fast the keyboard will disappear (all my swipe gestures are off), and when I bring the keyboard back up it doesn't show the letters I type.

Hi
since I installed Handcent (today) it already happened once to me... does it happen in another app ?

Hm, I don't think it happens in any other apps, but I don't type as much in other apps so I'm not sure.

On the Motorola Droid I also get the same problem. The only way I could make it work again is by switching to another keyboard like the default keyboard and then switching back to Smart Keyboard Pro. It'll fix the problem but it gets pretty annoying to have to do that every time it happens.

This happened to me earlier using the Touchdown email program. I wasn't expecting it, and ended up erroneously hitting the "Send" button when the keyboard disappeared and I sent my incomplete email.

This is very annoying (especially because it never happens to me...), I will add some logs in the next version, that you will be able to send to me with Log Collector app

avatar5d wrote:... ended up erroneously hitting the "Send" button when the keyboard disappeared and I sent my incomplete email.

The keyboard just disappeared on me again but this time it sent what I had typed by itself. I might have to switch to the default until this is fixed because the disappearing keyboard is starting to happen too often and with it erroneously sending is too much.

Can you send my the phone logs by mail (android@cdeguet.net) with the Log Collector app when you see this problem happens ?

Thanks

Sounds good. Anything to help get the bugs out and help you concentrate on your to-do list.

By the way I think this should be fixed in 1.2.4, but anyway tell me if it happens again

I still see this happening with 1.3.0. The following is a snip from the logs, which contains the same output every time I experience this bug. Dunno if this will help or not.

02-11 18:58:40.219 W/InputManagerService( 74): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@44c6aaa8
02-11 18:58:41.799 D/dalvikvm(31475): GC freed 3796 objects / 248088 bytes in 153ms
02-11 18:58:43.759 D/dalvikvm(32186): GC freed 11230 objects / 794656 bytes in 60ms
02-11 18:58:44.039 D/dalvikvm(32186): GC freed 3946 objects / 449592 bytes in 250ms
02-11 18:58:44.439 D/dalvikvm(32186): GC freed 7104 objects / 742104 bytes in 81ms
02-11 18:58:44.579 W/IInputConnectionWrapper( 74): showStatusIcon on inactive InputConnection
02-11 18:58:44.589 I/ActivityManager( 74): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher2/.Launcher }
02-11 18:58:44.849 W/InputManagerService( 74): Ignoring hideSoftInput of: com.android.internal.view.IInputMethodClient$Stub$Proxy@44d76df8
02-11 18:58:44.859 V/RenderScript_jni( 132): surfaceCreated
02-11 18:58:44.859 V/RenderScript_jni( 132): surfaceChanged
02-11 18:58:44.869 V/RenderScript( 132): setSurface 480 762 0x63ee58

No !!!!!!!
Can you send me the whole logs ?
But at least the other bug (when too much text is entered) is fixed, right ?

Full log sent!

And no, I have not seen the keyboard get stuck since yesterday's fix.

Thanks.
Unfortunately I removed the debug logs which would have been useful to understand why the keyboard is hidden... I will re-add them in the next version (it will be an option)

OK, so I added some logs in 1.3.1, I hope this will be enough to understand the problem.
Can you enable the new option "debug logs" in the advanced settings ? Then you can send my the logs (with Log Collector) if it happens again, and the exact time it happened would help me (as there will be many logs)

Thanks !