I have seen a few videos online, mainly with the dell streak, that show how an apple bluetooth keyboard works with android. Pressing F1 when paired with the streak brought up the menu button, will that work on the nexus one too?
I'm assuming the HID support in CM6 would let one work the same way on the nexus one, but is there any way to navigate the phone using the arrow keys on the keyboard? I guess it'd be similar to emulating a d-pad or a trackball.
If the implementation in CM6 can't, are there any apps that can?
i've used it briefly on my n1 + apple bluetooth keyboard. it's very responsive, but i didn't test all the keys. give it a shot. it's pretty cool.
I've played around with my dinovo mini and N1. Both the keyboard and touchpad/mouse work well.
Related
Hi there.
I got Quake3 loaded on the phone, it starts up and I can look around and shoot, but I can't bind anything to the keys for movement.
Has anyone successfully configured it to use any of the buttons on the phone?
Thanks.
I went through the same issue. After reading the requirments it states a physical keyboard is required. Shame too.
Sent from my DROIDX using Tapatalk
Well, the Volume and Camera buttons are probably map-able, since Volume Up is already mapped to fire by default. Probably need to talk to the author.
Check Here http://forum.xda-developers.com/showthread.php?t=745579
I think this is what you're looking for
Someone get the Wiimote to be compatible and I'll send you boatloads of money lol
The developer already has rudimentary on screen joystick support as of yesterday. It is rudimentary, but it works, and it is mostly multitouch capable.
He is currently working on making that better. Also I will be making a quake3 mod that will make the menus be more easily usable on the android port. The current best setup I have used is:
Volumes are forward and back, camera is shoot, screen is aim. I tried mapping jump to touch, but it didn't work.
The port is still very much in early stages, and it sounds like he is hard at work on making it more usable. Hopefully I can help with my mods
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?
I'm loving ics on the hp touchpad but I'm having a lot of problems with the hp Bluetooth keyboard in android. Note it's pairing up just fine but Ihave the forllowing issues.
Not all keys on the keyboard work properly, ie the shift and caps lock don't work. Notice all the missing caps in the this post. Only caps are auto entreated by the spell checker.
The soft or virtual keyboard always pops up for any input and Ihave to close it to get it out for the way.
any help in resolving these issues would be greatly appreciated.
note I'm using classicnerd v2 but I've had the same problems no matter what rom. I've installed.
Thanks
Bob
I AM USING MY HP KEYBOARD RIGHT NOW. caps work SHIFT works....most of the xtra keys on top work...i.e. volume, power button...brightness does not but search and home do work...maybe change your batteries.
The Gametel controller is now available on Amazon.com. I got mine in the mail today. Here's a quick review.
It came with no battery charge, so I had to plug it in to test it out. I was using a USB cable plugged into my computer. At first it only showed a red light to indicate charging, but then a green light came on shortly afterward. This is supposed to indicate that it's on but not paired. I tried pairing with the device using the Gametel software from the market, but it would not work. Turns out you can't use the controller while it's plugged into a computer. As soon as I unplugged it it turned off, and when I turned it back on it paired fine. I tested it again while plugged in and it still wouldn't connect to the phone. No big deal, but it's a minor hassle. It might work fine when plugged into an outlet. It supposedly has a 9 hour battery life, so just keep it charged and this issue should never bother you.
Despite the One X's huge size it fits fine, even with a TPU case. The TPU case has the added benefit of keeping the controller arm from pressing the down volume button. The software has a feature to disable the volume keys because of this potential issue, but it's nice that I didn't need to use it. It says it can provide volume control using the device itself, but I'm not sure how that would work, since all the physical buttons are mapped to SNES buttons for my purposes. You could always slide the phone a little bit to the left and it wouldn't hit the volume key. The phone would be off center, but it wouldn't be too bad.
The controller acts as a virtual keyboard. As part of the software setup it installs an input method in your keyboard settings. As soon as you launch the software it prompts you to change to its input method, which is handy. Then you can launch your favorite emulator and map the keys is uses to the emulator's buttons.
I initially had problems with the default keys that the controller was emitting. I'm used to an SNES button layout, so I will call the buttons X (top), Y (left), B (bottom), A (right). For some crazy reason the A button was emitting the Android "Back" button by default. This was mappable in Snes9x EX, but pressing it still performed the "Back" action which prompted you to quit the game. The B button was emitting the "DPAD Center", which worked, but was an odd choice. It's even stranger because none of the preset key configs in the Gametel software's Advanced Settings have this setup. If this happens to anyone else, just load the Android Gamepad preset and it will work fine. However, it reverses X & Y and A & B from what I'm used to, so I made my own preset named SNES. That way when I configure Snes9x the purpose of the button matches up with the key being emitted.
As for the controller's buttons and D-pad, they are OK. The buttons are great, but the D-pad makes you move diagonally a little too easily. If anyone is familiar with the Xbox 360 D-pad, it's the same sort of problem, but not as bad. Maybe with more time I'll get used to the feel of exactly where to press to avoid moving diagonally. Part of the problem is the D-pad is circular instead of cross-shaped. It's hard for your thumb to feel exactly where the cardinal directions are. This isn't the entire problem, though, because the 360 controller has clearly raised cardinal directions and it still sucks really bad. Thankfully it's not nearly that bad with this D-pad. Pretty much anything is better than on-screen controls.
That actually looks pretty cool.
I don't game enough to need this and touchscreen controls don't bother me enough, but thanks for the review!
As it turns out, the D-pad is really ****ty. This is most noticeable in games with movement in both directions, like Secret of Mana. Zelda wasn't so bad because you move kind of slow and you can adjust your thumb position if you notice yourself moving diagonally by accident. However, in Secret of Mana you fly across the screen, and moving diagonally by accident for a second can really put you off course. In a game like Super Mario World you don't really notice the problem.
I might have to try an iControlPad. I just really liked the Gametel's single-piece design and spring-loaded arm.
Sixaxis controller app and ps3 controller.. All you'll ever need
Sent from my One X using xda app-developers app
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.)