Hi There, The CNTL key is not existed in Android 2.x series. You'll have to dig into the OS keymap, like what you mentioned, to open these to the underlined applications.
My app, 9420 Tablet keyboard (and 9420 Thai Keyboard), handls the key inputs from the HW keyboard as well beside the on-screen one. It emulates Cntl-A, Cntl-X/C/V and even overrides the sticky behavier of the SHIFT key to non-sticky. On the 9420 Thai Keyboard, it also suppots multi-tap and long-press from the HW keyboard (just to mention to show how far the customization can be done without rooting the phone) It is on the market, you can check it out, maybe it serves your purposes more or less. Frankly speaking, 9420 Thai/Tablet Keyboard is designed to be able to re-map the HW keys to any Android keyCode as long as the HW keyboard is sending out the key inputs. Best Regards, Solutikn 9420 www.solution9420.com On Mar 18, 7:30 pm, Никита Траторов <nikita.win...@gmail.com> wrote: > <https://lh3.googleusercontent.com/-junDMI1xOCI/T2XUzN_5f5I/AAAAAAAAAq...> > *Good day to all developers!* > > I have a Bluetooth (BT) Hardware keyboard RAPOO E6300, working on my SGSII > with Android 2.3.5. > > It is working fine, but some special keys is not mapped as expected or may > not work at all, like Ctrl in Putty. > For example, "VolumeUp/VolumeDown" keys is working, but "Mute" key is don't. > > *With help of dev.android.com I get keymap:* > > D:\android-sdks\platform-tools>adb shell getevent -p > add device 1: /dev/input/event9 > name: "Broadcom Bluetooth HID" > events: > SYN (0000): 0000 0001 0004 0014 > KEY (0001): 0001 0002 0003 0004 0005 0006 0007 0008 > 0009 000a 000b 000c 000d 000e 000f 0010 > 0011 0012 0013 0014 0015 0016 0017 0018 > 0019 001a 001b 001c 001d 001e 001f 0020 > 0021 0022 0023 0024 0025 0026 0027 0028 > 0029 002a 002b 002c 002d 002e 002f 0030 > 0031 0032 0033 0034 0035 0036 0037 0038 > 0039 003a 003b 003c 003d 003e 003f 0040 > 0041 0042 0043 0044 0045 0046 0047 0048 > 0049 004a 004b 004c 004d 004e 004f 0050 > 0051 0052 0053 0055 0056 0057 0058 0059 > 005a 005b 005c 005d 005e 005f 0060 0061 > 0062 0063 0064 0066 0067 0068 0069 006a > 006b 006c 006d 006e 006f 0071 0072 0073 > 0074 0075 0077 0079 007a 007b 007c 007d > 007e 007f 0080 0081 0082 0083 0084 0085 > 0086 0087 0088 0089 008a 008c 008e 0096 > 0098 009e 009f 00a1 00a3 00a4 00a5 00a6 > 00ac 00ad 00b0 00b1 00b2 00b3 00b4 00b7 > 00b8 00b9 00ba 00bb 00bc 00bd 00be 00bf > 00c0 00c1 00c2 00d9 00f0 > MSC (0004): 0004 > > I think, that half of solution of this problem is to develop new keylayout > file and put it to */system/usr/keychars*. > And the othe half of solution is to develop android service app, that will > cover othe virtual keys, like changing tracks of media/radio player etc. > And this service must start or will enabled new functions only when > keyboard is connected with device. > > Who can help me with advice? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
