So I installed Quake 3 with no problems. It runs smoothly with A2.
Trouble appears, when I connect bluetooth mouse and keyboard. First of all Apple Magic Mouse simply does not do anything with the phone whatsoever, even though it pairs and connects(this has nothing to do with Q3). When I connect Magic Trackpad the cursor appears and works fine. However, when I run Q3 the cursor is stil there! And when I move the cursor the aim does not move. The only way to aim is to hold the left button and then move, which is lame.
So I have to questions:
1. Why magic trackpad works and magic mouse does not? (non q3 question)
2. How to make the mouse move the aim without having the left button pressed ?
For the second one, you probably need to turn mouselook on. In the Q3 console it is probably mouse_look 1 or something like that
Related
I have the classic controller hooked up to my G2 and am trying to use it to play Quake 3. While I've been able to remap all the buttons to get a decent FPS experience, the problem is that Quake, of course, has left/right turn as keyboard buttons by default, so even with the thumbstick left/right options on the CC being programmed to them, they are too slow to really use and make the game borderline impossible to play. There is the mouselook/freelook option, but that doesn't seem to want to work with the thumbstick on the controller--only with the phone itself. The movement and looking up/down works fine, but I need to make the right thumbstick into mouselook if I want to ever play Q3 again, and I don't know how. Do you guys have any ideas?
-Rocky
Did you try raising the sensitivity? If not link me to the controller you have and I'll buy it and see what I can implement into quake3droid.
I guess I should clarify, I meant the "Kwaak3" port specifically (which I installed as per random googled instructions); I haven't tried "quake3droid" itself. But I assume it's a general limitation of anything based off of Quake 3 (unless quake3droid changes it somehow) that being able to turn left and right is either keyboard-based or requires mouselook, and my problem is getting the program to recognize moving the thumbstick around as a mouse (it didn't work as "Joystick" when I enabled that, unless I was seriously confusing things), so if I set turn left/right as the keys associated with left/right on the CC, then it's godawfully slow to turn and mouse sensitivity has no impact. It seemed like less of a problem looking up and down than turning, but that may just be due to the fact that that I was fighting a bot in a mostly horizontal level so it was much less essential to look up/down than to be able to turn quickly to shoot him.
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?
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
I setup Daggerfall with mouse set to physical and have tried both relative and absolute and in game mouse look turned on, the problem is that i can only turn about 90 degree from left to right. When the android cursor hits the edge of the screen i can no longer turn. Any suggestions on how to fix this would be much appreciated.
you are not alone...
Babalonis said:
I setup Daggerfall with mouse set to physical and have tried both relative and absolute and in game mouse look turned on, the problem is that i can only turn about 90 degree from left to right. When the android cursor hits the edge of the screen i can no longer turn. Any suggestions on how to fix this would be much appreciated.
Click to expand...
Click to collapse
I have the same issue with my nexus7 and I think that most other devices will have it too... Obviously, this problem isn't specific just for daggerfall - since the android mouse pointer won't leave the screen, you can't turn in any 3D game (or scroll in strategy games... etc.).
To my knowledge, there is no way to disable android mouse pointer and I have read that google forbids apps to disable it too. I use a simple workaround which is to set the mouse pointer speed in android settings to minimum - than the mouse in dosbox moves a lot faster that the android mouse.
It won't solve the problem completely, but it makes the games playable - you still need to be careful not to hit the edge of the screen with android mouse pointer, but you can turn about 720 degrees in one direction before that happends (than you just move the cursor back to the center of the screen and continue playing...)
Unfortunately, I think that the only way to get rid of the android mouse pointer completely is to flash a custom rom which doesn't have mouse support built in at all (but of course than you couldn't use the mouse anymore - except for gaming in dosbox...)
it is ok
karyk said:
I have the same issue with my nexus7 and I think that most other devices will have it too... Obviously, this problem isn't specific just for daggerfall - since the android mouse pointer won't leave the screen, you can't turn in any 3D game (or scroll in strategy games... etc.).
To my knowledge, there is no way to disable android mouse pointer and I have read that google forbids apps to disable it too. I use a simple workaround which is to set the mouse pointer speed in android settings to minimum - than the mouse in dosbox moves a lot faster that the android mouse.
It won't solve the problem completely, but it makes the games playable - you still need to be careful not to hit the edge of the screen with android mouse pointer, but you can turn about 720 degrees in one direction before that happends (than you just move the cursor back to the center of the screen and continue playing...)
Unfortunately, I think that the only way to get rid of the android mouse pointer completely is to flash a custom rom which doesn't have mouse support built in at all (but of course than you couldn't use the mouse anymore - except for gaming in dosbox...)
Click to expand...
Click to collapse
You are correct in that the Android OS does not expose any API's to disable the Android mouse pointer. This becomes a problem in some games, because the Android mouse pointer will not go past the screen edges, thus disabling scrolling when you are using an external mouse (ie. bluetooth mouse or touchpad on the TF101).
There are four possible work-arounds built into dosbox turbo:
1. Screen Scaling Reduction + Absolute Mouse Mode (w/Hardware mouse):
In the settings menu, try reducing the screen scaling to less than 100% (ie. 90 or 95%). This will leave a small black border around the screen. When dosbox Turbo detects that the Android Mouse pointer has entered this black border, it should then emulate the mouse at the 'edge' of the screen. This special work-around will only work in "absolute" mouse mode, as there is no easy way to emulate such behavior in relative mode.
2. Analog GamePad mouse Emulation (w/Hardware Gamepad)
In DosBox Turbo 2.1.7+ analog sticks on gamepads are automapped to mouse and joystick control. So if you plug a Logitech, XBOX, or other supported gamepad into your TF101, the right stick will control the mouse movement, while the left stick will control the joystick.
3. Virtual On-Screen Mouse Emulation (w/Virtual Joystick)
If you go to the setting Virtual Joystick -> Use Joystick as Mouse, then when you enable to virtual onscreen joystick, it will then control the on screen mouse.
4. Touchscreen Mouse (w/Touchscreen)
The final work-around is to go back to the default touchscreen mouse. Using the above screen scale reduction trick + absolute mode will allow for scrolling in games that work with absolute mouse mode. Relative mouse mode is not affected by the scrolling issue.
I'm having an issue while using DOSBox:
I can't play shooters like BLOOD etc. using the right analog stick of the Samsung Gamepad for Android (GP-EI20) which is connected via Bluetooth to my Galaxy Note 3.
Everything else works but the right analog stick is just not being recognized (simply as if there wouldn't be one).
I'd like to use the right analog stick for mouse strafing but don't know how to solve / configure this.
Any suggestions?
Im curently using a half size bluetooth keyboard paired to my phone (nexus 4) which is running RemoteDroid. That is used to forward keystrokes to my PC. Why? because I have a broken collarbone and cant use my fullsize wired keyboard properly So im using my phone as an intermediate device (BluetoothK/B->Phone->WiFi->PC) to be able to use the bluetooth keyboard. Putting the phone in close proximity to the K/B means It has a much better range and signal quality via WiFi. The phone itself also has a better bluetoooth receiver than any laptop or desktop USB bluetooth receivers ive tried, giving much more reliable keystrokes at higher typing speed than gong straight to PC
The problem is some of the keys dont work correctly and I believe its because Android is interpreting them differently. i.e. 'Tab/Delete/Insert/Home/End/num +/ num -.. etc' dont get forwarded to the PC,And some keystrokes are simply incorrect` i.e. the right shift key acts more like CTRL for some things. Shift+2 becomes " instead of @ (need to press alt 2 instead) and so on
In addition I have a touchpad on the little keyboard and that only works in a limitted fashion
Is there an app out there that can 'grab' the Android inputs of a device and remap them? so i.e. mouse click could be emulated as pressing the Enter key if I so wished
Additionally` is there a progam that can forward these 'raw inputs' to a PC via USB/WiFi/Bluetooth? remotedroid does indeed forward some inputs of key presses as best it can (arrow keys for instance) but it seems to do it 'after' the android OS (i.e. alt+tab makes the android program switch applications, rather than forwarding the 'alt' and 'tab' keys to the PC)
It does not however forward mouse inputs (havnt tried gamepad) so its not possible to use a mouse or trackpad as intended. I have to emulate a screen press (hold left click on trackpad and move the cursor across the remotedroid screen)
Hope the above makes sense, and yes im aware I could simply bluetooth directly to the PC but wheres the fun in that?