Database Info

Fuze: adjust 4-way rocker sensitivity (going "back" constantly)?

New Fuze user and new user to WM in general. I like the device, but it's been a bit overwhelming trying to get things together and tweaking it.
My biggest gripe right now is the sensitivity of the 4 way directional pad. Up and down work pretty well, but left and right are tricky to hit and I usually wind up going home, canceling, or going back. It's quite frustrating and I'd much rather use the directional pad than peck on the touchscreen in many situations.
I'm a bit befuddled: is navigation via the directional pad touch sensitive or is it a physical button? Is there anyway to adjust the sensitivities or sensor zones/regions so as not to accidentally hit one of other hardware buttons?
Thanks.

Got the same issue. The up / down navigation works fine, but left and right is just horrible. It would almost be better if you could use the touch sensitive part, rather than having to press the buttons fully down.

yup its a problem on all i think

lbhocky19 said:
yup its a problem on all i think
Click to expand...
Click to collapse
Wow, how did this get pass R&D and QA? The lack of responsive and accurate left/right keys is abysmal (makes me unable to use Calendar). I sure hope there will be some remedy ....

Yeah, I agree, the d-pad is sorely lacking. It seems to be getting a little easier as I get accustomed to it, but the d-pad from my 8525 was much better.

I agree 100%. And like vexingv said, this is particularly annoying in the calendar application. The D pad on my 8525 was far easier to use.

And all this time i thought i just kept messing up. I have the same problem also.

calendar is where the problem really does shine

This is the WORST part about this new phone redesign. It's almost as if MARKETING came up with this idea than actual engineers.
I wonder if we can just cut the surface so we get the d-pad left-right back and so it's not shared with other buttons.
Thanks a lot HTC! You now have THREE buttons that do the same thing instead of 2 last time on the Kaiser:
Home goes back to Home
Back (formerly OK), goes back to home anyways
Hangup goes back to Home anyways already!
So hitting left or right you have 66% of it going straight back to HOME.
Then, you take away the scroll-wheel capability and replace it with rocker buttons for volume that only do that and nothing else.
Genius by HTC.

NuShrike said:
This is the WORST part about this new phone redesign. It's almost as if MARKETING came up with this idea than actual engineers.
I wonder if we can just cut the surface so we get the d-pad left-right back and so it's not shared with other buttons.
Thanks a lot HTC! You now have THREE buttons that do the same thing instead of 2 last time on the Kaiser:
Home goes back to Home
Back (formerly OK), goes back to home anyways
Hangup goes back to Home anyways already!
So hitting left or right you have 66% of it going straight back to HOME.
Then, you take away the scroll-wheel capability and replace it with rocker buttons for volume that only do that and nothing else.
Genius by HTC.
Click to expand...
Click to collapse
Well, the scroll wheel does work, but its ability is to zoom/decrease the text size, which for most intents and purposes is a waste.
For clarification, is the directional rocker currently touch-sensitive or is there a physical button that is being depressed (albeit poorly).
If this keeps up, how about mapping some of the other 4 hardware buttons to provide some L/R functionality?

Okay guys. Here is the weird crazy part. I had the same problem, I just flashed the original stock att rom back (Well, tried to freeze in the middle to return ) but I had the att rom on it, I tried to re-install via the microSD card, and after it went through all the customization, I was so suprised that the left and right were working, it blew me away. I was like, "wdf? Is this the same phone." I have no idea what happened, but they seem more responsive. No tricks. At first I thought it was just me, but I started to use it more and more and it was working much better than before. No idea what fixed it, but I'm a happy camper

Here's some pictures of a guy who dropped it. http://forum.xda-developers.com/showpost.php?p=2904011&postcount=1
Looks like distinct buttons. We just need to keep the face plate from sharing the presses.

Stock rom here... Moving 'left' seems to work okay but 'right' either hits Call End or Back. And here I thought I was doing something wrong.

NuShrike said:
Here's some pictures of a guy who dropped it. http://forum.xda-developers.com/showpost.php?p=2904011&postcount=1
Looks like distinct buttons. We just need to keep the face plate from sharing the presses.
Click to expand...
Click to collapse
Seriously! Whose idea was it to make all those buttons into 1 face plate! stupid idiot designer. At least they could've separated the d-pad somehow, maybe a very precise circle.

Yeah with the new excitement with touch interfaces, HTC seemed to have left their minds/brains elsewhere. But judging from the pictures in the linked thread above, it seems like none of the 4 directions have physical buttons.

Count me in on this problem...
For the Calendar I just open the keyboard and use that D-pad on the bottom right.
SOLUTIONS...
I propose someone should create software to do 1 of 2 things:
1) Use the G-sensor to control scrolling. This function would be activated by touching, not pressing/clicking, the center of D-pad. Similar to how you focus the camera. This action would activate the software thus allowing scrolling in all 4 directions by tilting the device.
2) Change the input so we only have to Touch the D-pad (like how we zoom in on pictures/Opera) to move in the desired direction.
So who's up to the challenge of developing some software to make this happen? I will gladly donate $$$ as the D-pad is the ONLY thing I dislike about the Fuze/Touch Pro.

it took me 10 days to realize how to left and right buttons work (sprint).

Hmm...maybe the designers/engineers meant for BOTH hardware buttons on either side to be depressed nearly simultaneously in order to register navigation to either the left or right?
Eg.: Placing the tip of my right thumb parallel with the end the bottom of the phone between the two hardware buttons (farther away from the D-pad than one normally would) such that both buttons depressed, I was able to get much better accuracy navigating to the right. Can get the same response on the left side, but it's not as feasible due to the awkward positioning of the hands/fingers.

I got tired of this problem before so I used G-controller. It works.
[Link]

The buttons are both touch-sensitive and physical buttons. The problem is if your thumb is touching any of the big buttons, it will prefer that over the directional click. Add to that the fact that the area the phone considers to be part of the non-directional buttons is much bigger than what it considers to be the directional buttons and it is a problem.
I wish people would stop following Steve Jobs's design ideas. Fewer buttons does not a better product make.

Android 3-DOF Controller App

Hello guys. I've just released my app's source code as well as a short video at:
http://androidcontroller.googlecode.com/
--necessary improvements list--
on the Android side:
* service discovery so that the client and the server can find each other on the local network (it's very annoying having to manualy enter an IP address in a textfield that's why I change the source code every time and compile with the new ip )
* kalman (or some other kind of) filtering to smooth the sensor output
* improve menus/configuration/interface
* look for a marker and calibrate automaticaly
on the windows side:
* switch model you're rotating somehow (ability to load models via xaml files?)
* interact with the object (I'm already transmitting the touch screen's x/y event)
* smooth the sensor data on the windows side to take the load off the android app
* sounds
* transmit images to display on android or sounds?
I would appreciate VERY much ANY help that anybody could provide. If you are interested in contributing code please contact me and I will add you to the project members list.

Well Done !
congrats

HES A JUBEH IMPOSTER
Just kidding, awesome app btw

wow...this is pretty cool. I would love to help but due to my lack of knowledge in this. Keep up the good work!!

Great work, I'd love to see how this develops.
Starred in google code.

Everybody thanks for the encouraging remarks

re
Génial___$$$$$$$$

Draw custom buttons to the touch screen which send keyboard commands to windows, and implement gamepad support for the sensors? Then this could be used as an input device for a computer.

bjehsus said:
Draw custom buttons to the touch screen which send keyboard commands to windows, and implement gamepad support for the sensors? Then this could be used as an input device for a computer.
Click to expand...
Click to collapse
But if I do that then the touch screen becomes just another gamepad, and a bad one for that matter since touch screens have no tactile feedback (i.e. the finger is not aware of wether it has pushed the button or not). Tactile feedback could be implemented via vibration or perhaps even audio feedback with sound for button press but both those scenarios are impractical for a gaming situation where buttons are being pressed at a frantic pace.
Besides I wanna do more than just pushing buttons. Something with touching/swiping gestures etc. Transmitting data from the pc to the mobile device, or sounds? ooor.. dunno^^
I need some good ideas on what more one could do with this ^_^

I'd be more than happy to help, unfortunately the most I can do for you is clean up images and menu buttons. If you need any of that done feel free to hit me up.

woah
This is really cool. Are there any real apps available yet?

henrynhl said:
This is really cool. Are there any real apps available yet?
Click to expand...
Click to collapse
Plx define 'real' apps.

Actually this is a great idea, I'm surprised no one had thought of it yet.
Blender (open source 3d suite) supports NDOF devices nowadays - I'll see about giving this a try when I get a chance, and perhaps contribute some code (and we'd need a linux server as well, which shouldn't be too big of a deal)

Jubei said:
But if I do that then the touch screen becomes just another gamepad, and a bad one for that matter since touch screens have no tactile feedback (i.e. the finger is not aware of wether it has pushed the button or not). Tactile feedback could be implemented via vibration or perhaps even audio feedback with sound for button press but both those scenarios are impractical for a gaming situation where buttons are being pressed at a frantic pace.
Besides I wanna do more than just pushing buttons. Something with touching/swiping gestures etc. Transmitting data from the pc to the mobile device, or sounds? ooor.. dunno^^
I need some good ideas on what more one could do with this ^_^
Click to expand...
Click to collapse
I have an idea, heh...use it to control the mouse on a PC.
There are remotes that work using accelerometers and such...by tilting the remote up, it moves the mouse arrow on the screen up, left goes left, etc. Then simply have the screen react to a short tap(which would be a single click), double tap (which would be a double click), and a long press (for right click).
That is certainly something that I would use on a daily basis.

jmhecker said:
I have an idea, heh...use it to control the mouse on a PC.
Click to expand...
Click to collapse
Thanks for your feedback jmhecker! Do you mean like a wiimote? If so then unfortunately that's not possible with the HTC Dream unless the user performs some kind of calibration process first (because the device has no way of knowing where the monitor is). So first some sort of calibration would be necessary, which could be done by placing a marker/qr code on the monitor then pointing the camera OR just pointing the device to the middle of the screen and pressing a button (which is what i"m doing now to calibrate).
Jubei

Jubei said:
Thanks for your feedback jmhecker! Do you mean like a wiimote? If so then unfortunately that's not possible with the HTC Dream unless the user performs some kind of calibration process first (because the device has no way of knowing where the monitor is). So first some sort of calibration would be necessary, which could be done by placing a marker/qr code on the monitor then pointing the camera OR just pointing the device to the middle of the screen and pressing a button (which is what i"m doing now to calibrate).
Jubei
Click to expand...
Click to collapse
Kind of like that, yes. But, not exactly.
Basically, the phone knows when it is in 'zero' position. IE: lying flat on its back.
Now, I tilt the phone (rotate) to the left a smidge, so it look like / (when looking at it if it were in front of you...what oyu see is the bottom (where the plug is) of the phone. Now, when you tilt it like that, the mouse cursor moves left. Then when you turn it like \, it moves right...tilt the phone forward, it moves down, and tilt it backwards, and it moves up.
Kind of what you have being done already with the video and the plane in it...but, rather than move the plane, move the mouse cursor.
Does that make sense?

This with remote droid...
jmhecker said:
Kind of like that, yes. But, not exactly.
Basically, the phone knows when it is in 'zero' position. IE: lying flat on its back.
Now, I tilt the phone (rotate) to the left a smidge, so it look like / (when looking at it if it were in front of you...what oyu see is the bottom (where the plug is) of the phone. Now, when you tilt it like that, the mouse cursor moves left. Then when you turn it like \, it moves right...tilt the phone forward, it moves down, and tilt it backwards, and it moves up.
Kind of what you have being done already with the video and the plane in it...but, rather than move the plane, move the mouse cursor.
Does that make sense?
Click to expand...
Click to collapse
I could see this working with RemoteDroid, or something of that nature. Make the tilt like a joystick, and the screen with a touch pad and buttons. That would make a killer game controller

jmhecker said:
Kind of what you have being done already with the video and the plane in it...but, rather than move the plane, move the mouse cursor.
Does that make sense?
Click to expand...
Click to collapse
It does yes. But i think it would require a lot of work to be usable because isometric or isotonic (speed of cursor relative to tilt angle) devices are not nearly as usable as mice. So in the end you'd spend so much hours coding just to have another mouse, whereas I think this device can be more.
it has a speaker, a display, vibration, buttons, keyboard, a trackball, sound. It has a lot of potential to be used just as a simple mouse.

Use mouselook with classic controller in Quake 3?

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.

Gametel bluetooth game controller now available in US. [pic plus review]

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

[Q] BT keyboard woes

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.)