Related
2 problems with picodrive. The directional buttens are screwed up. left is up en up is right and so on. I have solved this myself no prob just keep on trying finding the right button.
Next problem is with the ABC buttons of Picodrive. Al the alfabethical keys are mapped to the same keyadress so A=> 0xe5 B=> 0xe5
They al have the same function in picodrive.
Is this a problem regarding the Touch Pro or with picodrive or with a windows setting
somebody else on here has mentioned exactly the same problem with another emulator, so I guess the Touchpro somehow represents it's buttons as the same, either that or what you are seeing is the response from the touch screen not from the button (as was proved in another thread the whole area is touch sensitive not just the screen) in which case turning off the touch feature might sort you out.
Its not the screen im talking about. It is the keyboard.
same with final burn
have the same problem with finalburn (mame emulator). Every key from the keyboard except the directional keys, enter and 2-3 others is beeing mapped / recognized as 0xe5
does somebody has a fix?
Besides that problem - has anyone been able to play either of those emulators to evaluate speed?
I'm concerned that the Qualcomm processor coupled with the VGA screen will result in slow performance.
I'm debating getting this phone, but wouldn't want to if it's too much of a drop off from my 6700.
The speed isn't a problem. Runs flawlessy. The applications are still buggy under some other aspects. But I wouldn't buy myself a device in order to run these emus. There are cheaper ones on the market.
Back to the problem with the keymapping...
I hard resetted the device and skipped the extended rom installation. The problem with the keymapping is still there. Therefore I can exclude the applications in the extended rom causing this problem.
Anyone some advices, fixes or workarounds?
no key mapping
key mapping is weird yes.
Mate of mine has the tytn II with a pocketSNES i loved it And i was in need for a new phone... HTC touch pro / raphael / MDA vario IV was a phone i really looked out fore for a while nice design etc etc etc ... just the key mapping for an emulator is a big .. down for me
Any fixes?
same problem here:
http://forum.xda-developers.com/showthread.php?t=420159
and
http://forum.xda-developers.com/showthread.php?t=425646
SOLUTION HERE: http://forum.xda-developers.com/showpost.php?p=2703133&postcount=3
Hi all...
does anyone know how well the dpad (or the wheel thing) works..
so for example will be able to play games on it... like... a driving game in hori mode??
thx for any help
i will be upgrading from a tytn, so i wanna make sure that it would be better than upgrading to tytn2
It is a technically much more competent device than the tytn 2, but I would have to say that playing games on it would be harder, at least until the tilt sensor is incorporated in to game controls !
thx buddie
but is the touch round (bottom, centre) still able to work as a dpad?
breakpointuk said:
thx buddie
but is the touch round (bottom, centre) still able to work as a dpad?
Click to expand...
Click to collapse
The button in the centre is just that -- a button (i.e. not a DPAD).
The directional controls (DPAD) are around the button just on the perimeter of the round light that surrounds the centre button.
I would have to say that playing games with the DPAD on the TP would be horrendous since there is a tendency to press the Home, OK, Phone and End Call buttons accidentally when pressing a direction. This is fine in daily application use because you can "train" yourself to learn the DPAD but in a game setting it would get frustrating to say that least.
I hope this helps.
I was using the diamond in a store the other day and couldn't get the hang of the dpad. I was surfing the web and couldn't jump in the right direction with the links and I kept accidentally launching links that I was trying to jump from. Th dpad seemed like a horrible design. Is it something that a user can get the hang of to the point that it will seem as easy to use as any dpad?
jamespaulritter said:
I was using the diamond in a store the other day and couldn't get the hang of the dpad. I was surfing the web and couldn't jump in the right direction with the links and I kept accidentally launching links that I was trying to jump from. Th dpad seemed like a horrible design. Is it something that a user can get the hang of to the point that it will seem as easy to use as any dpad?
Click to expand...
Click to collapse
I hardly use it, and from what I can tell the Touch HD (HTC Blackstone) does not even have one (but I might be wrong on that) when web browsing I zoom in on a link I want, tap on it and then read the result zoomed out !
Up / Down buttons are still usable, but left / right are horrible. It's very easy to press home or green button while using them.
Seems HTC is trying to make us stop using it, so they can drop it from their phones
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.
I have issues with the use of the OEM on-screen keyboard of the HTC HD2. It registers the keys next to the ones I press if my finger even begins to slide a little when pressing the desired key.
I would like something much more stable than what it's equipped with. Does anybody know of a better keyboard for the HTC HD2?
MartyLK said:
I have issues with the use of the OEM on-screen keyboard of the HTC HD2. It registers the keys next to the ones I press if my finger even begins to slide a little when pressing the desired key.
I would like something much more stable than what it's equipped with. Does anybody know of a better keyboard for the HTC HD2?
Click to expand...
Click to collapse
try finger keyboard or fingerkeyb...google the forum for it...it works great for me...tried it even on qvga..and still it kicks butt
farukb said:
try finger keyboard or fingerkeyb...google the forum for it...it works great for me...tried it even on qvga..and still it kicks butt
Click to expand...
Click to collapse
Excellent! Thank you. That worked out just fine. It is better than the OEM KB. It also looks better. Is there a touchscreen sensitivity setting somewhere for the HD2, do you know?
EDIT -
Unfortunately the Fingerkeyb has a bug in landscape mode. Pressing the spacebar often brings up the menu because it is so close to the bottom of the screen.
EDIT 2-
Eh...I spoke too soon. The landscape mode doesn't work properly. I thought it was limited to the same size as the portrait mode because that's what shows up when pulling up the keyboard while in landscape mode. But after tapping the small arrow beside the KB selector, and then choosing Fingerkeyb, the landscape mode comes up. Which isn't all that appealing because it separates the keyboard at the middle, putting the directional arrows in the middle, rather than providing larger keys like the OEM keyboard does.
Hopefully the creator of this keyboard will will see these issues and deal with them. I guess I'll just stick to the OEM board for now...much less complex to pull up.
Me thinks this is wrong forum...
And I suggest Swype. It should be on the forums here somewhere.
Well...All is well. I had the 2.0 version installed and found the 2.1 version from a post speaking about it. Googling fingerkeyb brings up a link to the thread in xda with the 2.0 version. After specifically Googling fingerkeyb 2.1, I was able to get it.
2.1 resolves the issues I had and is much nicer too.
I just can't get over how things go wrong when I speak of something working well.
The letter "b/B" is dead in the fingerkeyb. Tapping it does nothing. It doesn't register.
I suppose it's just in the default skin, red/black. I loaded another skin, gray/black, and it now works. Also, the "b/B" works in the default skin if the option to "Show bar" for landscape mode is selected. The "b/B" works fine either way in the default skin in portrait mode.
as already mentioned, google for Swype mate, trust me you'll never use another keybord again
One of the cooked ROMS has a cab for swype within it. Not sure on the legalities of it as it was only released for the Tmobile HD2, but if someone confirms its ok I'll tell you which ROM to save you digging about.
Actually if you are happy with the keyboard and its just the sensitivity issue then take a look at this post...
http://forum.xda-developers.com/showthread.php?t=604831
I had majoy issues with the keyboard and pressing of buttons etc but this CAB worked a treat!
Moved as not software release.
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.