Reposted from the HP TP board since I wasn't getting much help there.
So I bought the HP Touchpad Wireless keyboard for my TP and love it. My only problem at this point is that some of the buttons don't work on Android. Obviously the Card button which was meant for WebOS does nothing here, and even though the Play/Pause button works, the skip track prev and next do not. I see that most of the keys are still sending inputs file the KeyEvent program, but are not mapped properly.
I tried changing one of the keyboard files (when googling this it was recommended I change qwerty.kl) to properly map to the input the keyboard was sending, but it didn't appear to have any effect. My suspicion is that perhaps the HP BT keyboard uses something like /system/usr/keylayout/Generic.kl instead of qwerty.kl, but how do I know for sure? There are like a dozen in there. Is there a way I can make a customized one and somehow tell CM9 to point to that layout file when the BT keyboard connects?
Related
Hi all,
In case anyone was wondering, the following Bluetooth keyboards work with the Infuse, running Gingerbread 2.3.3.
General Note: all devices below paired up seamlessly. They were immediately detected, and simply required me to key in a 6 digit passkey (4 digits for the Apple Magic Mouse).
1) Microsoft Bluetooth Mobile Keyboard: in all honesty, this keyboard worked the BEST out of all three that I tried today. As an FYI, F1 triggered Menu, Home triggered Home, and Esc triggered back. Reason why I didn't dig it all to much was the rather 'flimsy' build quality, although I do use the 7000 Entertainment set at home.
2) Logitech Tablet Keyboard for Android (3.0+?): Ignoring the 3.0 spin, and focusing on the fact that it's an HID-compliant BT device, I picked this up to give it a whirl. Niceties include the case that it comes with, which doubles into a stand for your device. Major setback that made me return it: the Menu button didn't work for me! Otherwise, a fantastic setup.
3) The keeper: Motorola Xoom BT Keyboard. Very similar in functionality to the Logitech offering. Started off pretty bummed because the built-in Menu keys on this kb didn't work either. Where the Moto saves itself, though, is that they keep they have a 5th row, atop the rest of the keyboard similar to a standard desktop keyboard (the Logitech trimmed these off and only had 4 rows), and within that 5th row, was an F1 key (which, after trial and error on the MS kb, triggers Menu). All in all, a nice package. Good to know I can rip away at longer emails with this thing, if I ever need to.
4) Apple Magic Mouse: nothing special here - paired easily, works like a mouse.
Quirks: 1
1) When pairing the Moto to a non-Moto device, you need to hold down the keys V, A and R when initiating the pair (don't worry, it's in the manual).
2) When the screen times out while paired to the KB (not the mouse), a cursor mysteriously appears, and is persistent until I disable BT connectivity on the device.
3) If you use a pattern to unlock your device, you might want to switch to a PIN or password, if you'd really like to be able to unlock your device from the keyboard...
4) "End" on the keyboard locks the screen. From my round of testing, all keys can unlocks (pretty neat) as long as you don't have a pattern set (meaning, you unlock with a PIN or password.)
5) The kb stays paired; the mighty mouse, i need to tap on to connect from within Settings each time.
That's about it. Feel free to ask me any questions if you had any, or correct me if you've me off base with any.
Can you give us some amazon links per keyboard so we can check specifications on the keyboard and maybe purchase one. I'm gonna need one that works with both the infuse and the motorola atrix.
Thanks
Sent from my SAMSUNG-SGH-I997R
Any idea if these will work with the stock at&t rom?
Apples Magic Mouse
Are we saying the magic mouse works on the xoom just like a normal mouse would?
Hello.
I'm interested in a Transformer Prime pad, but don't have one (yet…? ), so, please pardon the question… Anyway…
Is the keyboard from the KeyDock also usable (as a keyboard…), if the display isn't docked in?
Oh, and if the keyboard is used, does Android then also display the (in this case) useless on screen keyboard when text is entered? I hope not…
Lastly, I'm interested in the keyboard layout; how many keys does it have? Does it also have a <ctrl> key? It would be awesome, if somebody could please post a picture of the keyboard (or a link to one…).
I'm asking, because I'd like to figure out, how feasible it might be, to use the thing as a SSH client (using e.g. ConnectBot).
Thx,
Alexander
No, no, lots (could you not look at a picture?), yes. Connectbot works okay, but key combos don't always work. ConnnectBot needs to be updated for full support
Thx for the quick response!
I suppose connecting a Bluetooth keyboard to it would work, wouldn't it?
I know, I'm getting Off Topic, but… How about a USB and/or Bluetooth mouse? On YouTube, I found the video "How to Use a Bluetooth Mouse With the Acer Iconia A500", which shows that BT keyboard & mouse work with 3.1 — on the Acer device. How about Asus?
And, if mouse works, is copy/paste in ConnectBot as easy as it is on a "proper" Linux xterm or as in PuTTY?
Thanks again,
Alexander
Azio kb334b
I use a bluetooth keyboard with Connectbot, and yes the stupid on-screen keyboard appears, but pressing the Back softkey (or Esc on the keyboard, in my case,) hides it.
Key combos don't work for me, because Ctrl is not passed into the app, I think that's my S3 being dumb, but the Menu key on the keyboard brings up the menu with copy/paste and other options, so that at least is OK.
I think a mouse would technically work, but most apps are designed for touch-only, so I don't know if they would handle a mouse correctly. And it would probably be an app-by-app question.
So, I'm loving the hell out of my Surface RT (64GB with black Touch cover) except for two things.
1: I use the actual function keys (F1-F12) a lot more than I need a shortcut key for the play/pause button or the Share charm. Due to the placement of the Fn button on the right side of the keyboard, it's difficult to use the keys the way I'm used to. For example, Alt+F4 is now Alt+Fn+Play/Pause, and requires two hands. If anybody can find a way to toggle the default state of the Fn key, I would be super-grateful! Ideally, I'd be able to actually remap he keys like you can on advanced USB keyboards; for example, I need the Home and End keys too, but rarely use F8-F10 so I'd like to remap those.
2: The default direction of the multitouch scroll drives me up a wall (but only if I try to drive down it). It's a pointing device, not a touchscreen, dammit! I expect it to function like a scroll wheel on a mouse, or the side-scroll on older PC touchpads, or the TrackPoint scroll on the Thinkpad, or... you get my point. Yes, I get that Apple did it first; they were dumb then, are still dumb now, and MS was very dumb to copy them. On the other hand, at least Apple lets you change it! If the direction of this scroll can be reversed (preferably without screwing up the scroll wheel of an actual mouse, if I were to connect one), that would be amazing.
I was really hoping that the included drivers would include controls for these things, the way Microsoft's normal mice and keyboards come with highly configurable drivers, or most Laptops come with fairly advanced Synaptics touchpad driver controls. If any of you have contacts at MS on or near the Surface team, tell them that we really want some drivers like those, please!
have you been able to resolve the Fn key issue?
GoodDayToDie said:
So, I'm loving the hell out of my Surface RT (64GB with black Touch cover) except for two things.
1: I use the actual function keys (F1-F12) a lot more than I need a shortcut key for the play/pause button or the Share charm. Due to the placement of the Fn button on the right side of the keyboard, it's difficult to use the keys the way I'm used to. For example, Alt+F4 is now Alt+Fn+Play/Pause, and requires two hands. If anybody can find a way to toggle the default state of the Fn key, I would be super-grateful! Ideally, I'd be able to actually remap he keys like you can on advanced USB keyboards; for example, I need the Home and End keys too, but rarely use F8-F10 so I'd like to remap those.
2: The default direction of the multitouch scroll drives me up a wall (but only if I try to drive down it). It's a pointing device, not a touchscreen, dammit! I expect it to function like a scroll wheel on a mouse, or the side-scroll on older PC touchpads, or the TrackPoint scroll on the Thinkpad, or... you get my point. Yes, I get that Apple did it first; they were dumb then, are still dumb now, and MS was very dumb to copy them. On the other hand, at least Apple lets you change it! If the direction of this scroll can be reversed (preferably without screwing up the scroll wheel of an actual mouse, if I were to connect one), that would be amazing.
I was really hoping that the included drivers would include controls for these things, the way Microsoft's normal mice and keyboards come with highly configurable drivers, or most Laptops come with fairly advanced Synaptics touchpad driver controls. If any of you have contacts at MS on or near the Surface team, tell them that we really want some drivers like those, please!
Click to expand...
Click to collapse
The Fn Key issue is a little bit annoying, anybody have a solution for it?
Hello world,
(I really hope this is the correct section)
I recently bought an Oyama OY661 for use with my Android tablet and was disappointed to find out none of the special keys (shift, ctrl, alt) worked with it. Using a key test app I noticed that while for my fullsize USB keyboard it showed e.g. meta_shift_on|meta_shift_left_on along with 'a' when pressing shift-a, obviously, for the bt keyboard it just showed the letter, while showing the shift code when pressed alone (so I knew the keys themselves were working, just not combining them). Without giving it any second thought I returned it as incompatible and got a Rapoo E6300 instead, as I saw it had all-around great reviews.
I now regret that decision. The keyboard is the same size as the onscreen one, but with all the keys crammed together, it's actually even more uncomfortable go use. The battery is built-in, meaning you have to get a new keyboard when it dies out, and the auto-sleep is too agressive, having to reconnect more often than not when e.g. browsing and reading a forum.
Seeing how I actally preffer writing this post using the onscreen keyboard of my 4" phone than using the E6300, I'll return this one as well today. So my question is: Should I get the OY661 back? I've tried every "confirmed working fix" (disable chrome after uninstalling updates, set everything to 'default' in lang&input, force everything to 'English (US)' in lang&input etc) but none worked for me. But now I'm thinking maybe this can be fixed by modifying the keyboard layout&map files? Or is this a driver/hw specific issue and I'm better off looking for another keyboard? (I'm looking for something cheap to use with a $200 tablet. So a $100 keyboard that works with my computer, tablet & dog will not do, as anything designed primarily for the desktop compromises on the mobility usage and vice-versa - take the multimedia vs Fn keys; plus, I don't have a dog.)
First, just want to say thanks for the development on the Note Pro. CM on this thing is awesome. That said, I still have a couple of lingering issues, hoping someone may have found some work arounds/solutions. Inevitably there will be someone that will reply with "USE THE SEARCH!". For those that do, I will offer you my sincere admiration. Your search foo is only exceeded by your wit. For those that are still willing to read on and assist, know that I've come up empty in my search attempts. Believe me, I'd rather have found a simple search result than to have typed all this up... In any case:
1. Hardware keys and navbar -
CM has a setting for "Enable on-screen navigation bar and disable hardware buttons". Checking this box enables the navbar, but fails to actually disable the capacitive and physical buttons. This causes me some grief when using the tablet in portrait mode. I've tried hacking around in the build.prop and the Generic.kl files, but haven't found that magical combination of new lines/commented out lines. Maybe CM does this differently than other roms? (I've not observed a difference in these files when toggling back and forth in the settings, so there must be something else I'm missing.) Any pointers?
2. Key Mapping -
I have the Logitech Pro Keyboard Case. Seems to work well, for the most part. (I'm typing on it now...) However, not all of the keys work. Example - there are keys on the top left row for "back", "menu" and "task switching". Nothing appears to happen when pressing these now. Again, probably something in a .kl file somewhere, but I'm coming up empty. There doesn't appear to be a Vendor-Specific.kl file, but Generic.kl doesn't seem to cut it either.
3. On-Screen keyboard still displays when using bluetooth keyboard.
Well, that about says it all really. I've tried using both the Google keybard, and SwiftKey. Both continue to show up on-screen, even though I'm typing on the bluetooth keyboard. Swiftkey even tells me that it cannot detect a physcial keyboard. Probably related to the key mapping issue from above, but...
Again, thanks for all the work on this. Having CM saved my tablet from it's date with eBay.
Thanks!
- Bri
1. i thought about it but now i haven't spare time to implement. next week maybe.. but i dont promise
2. and 3. try this programm https://play.google.com/store/apps/details?id=com.apedroid.hwkeyboardhelper
171
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
bribash said:
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
Click to expand...
Click to collapse
Hey, try going with Null Keyboard, enable all your keyboards, and switch between them depending on whether the device is connected or not