some shifted top row keys produce nothing (in SDL/Debian Noroot)

[GoogleCodeExporter]

What steps will reproduce the problem?

1. In Debian Noroot (and perhaps other things built with libsdl?) open a text 
editor and try to enter: @, # or + by shift and the appropriate top row key
2.
3.

What is the expected behavior? What do you see instead?

I would expect to see @, # or + produced. In fact I see no input at all.
Note that the other symbols on the top row do work in Debian Noroot; and using 
your debug apk in Android proper, pressing shift-2 for @ produces this output:
0: onKeyUp, key=AT, code=77, meta=, flags=, scan=0, device=1

What version of Hacker's Keyboard are you using, for example "1.37"? (See
"Debug" section at the bottom of the app's Settings menu.)

1.37.1419

On what phone or tablet?

Samsung Galaxy Note 10.1 2014, Android 4.3

If applicable, does this affect the 4-row or 5-row layout, or both? Which
language(s)?

5-row layout, US english

Please provide any additional information below.

input connection com.cuntubuntu type=NULL

Original issue reported on code.google.com by harris.g...@gmail.com on 1 Oct 2014 at 7:08

[GoogleCodeExporter]

This sounds like a bug in the target application where it trying to handle raw 
keyboard input but not implementing it right. The keyboard sends a KEYCODE_AT 
event which is valid since Android API level 1:

http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_AT

My guess is that the application is making assumptions about a physical 
keyboard layout and failing to find a key mapping when it tries to convert this 
to an internal key event, for example a US QWERTY keyboard doesn't have an '@' 
key as a hardware key. But this should be fixed in the application.

Original comment by klausw@google.com on 6 Apr 2015 at 10:18

• Changed state: NeedInfo