Database Info

Reprogramming for the 'OK' function??? (QTEK 9100/KJAM)

Is there any way to re-program one of the generic four buttons (two on top, two on bottom) of the Qtek 9100 (KJAM/MDA) to use for the OK function, so that we don't have to open the keyboard or use the screen to close the programs?
Thks,
--L

You could possibly use my app VJOkButt to do this. That's what it's designed for.
V

Have a look at this app too : http://forum.xda-developers.com/viewtopic.php?t=41060

smartskey is a much better app... I don't know if it's remappable to the other hardware keys though. I think it's for the soft key buttons right?
V

:?:
OK, what am i missing?
Start>Settings>Buttons>Select Button, Choose "OK/Close"
?

Indeed, the Internet Explorer button (top-right) is ideal for reassigning as Ok/Close since it is closest to the close button on the screen and since any use of Internet Explorer needs the stylus anyway.

Funny, I agree on the button selection, I used the IE button for OK, and the Mail button for "Today".
However i couldn't disagree more about needing a stylus for using IE. With smartskey setup to open my start menu, I have IE there for one handed launching. With the WM5 soft buttons you can do everything in IE with one hand. I even default to full screen mode to get the most out of it. But you can launch favorites, stop, refresh, go back, etc. all with one hand.
Now if you mean typing in new URL's well sure that requires some other input, but for casual browsing of favorites, one hand, no stylus seems fine to me.
YMMV of course.

Raphael hardware keys, remapping?

Has anyone come up with working solution for mapping hw keys?
I found this thread on Diamond, but no help:
http://forum.xda-developers.com/showthread.php?t=398280

I am using AEKMap to enable both latin/cyrillic input on my TP's hw keyboard. You may google it and give it a try.

There is no need for additional software, just follow this post and you'll get the answer. Worked for me.

Try AE Button Plus.
B.

I think you did not quite follow me here.
I dont mean to change layout of QWERTY, but hw-keys like "Back" and "Home" at front panel of TP.
This is becaus I find home and back quite useless and would much more prefer to have ALT+TAB (change program) and close program (REALLY close them, not leave running background as back seems to randomly do).

Taajuus said:
I think you did not quite follow me here.
I dont mean to change layout of QWERTY, but hw-keys like "Back" and "Home" at front panel of TP.
This is becaus I find home and back quite useless and would much more prefer to have ALT+TAB (change program) and close program (REALLY close them, not leave running background as back seems to randomly do).
Click to expand...
Click to collapse
And that is EXACTLY what i also want to know....
The total lack of hardware-keys on this device is already disturbing enough, but being locked out of the option to remap any of them is truely horrid...
Anyone know of any reg-hacks maybe?

I've got Spb PocketPlus 4 installed btw, and it's got a button mapping function as well...
But when i go into the buttons map, some weird black icons appear with no name attached to it. Can anyone make anything of this? As you can see i've been able to map one thing only: the Spb close-button-contex-menu, which allows me to switch task KW-buttons only....
But this is not enough for me, i need ALT-TAB aswell and off course a VoiceCommand button.
And regrettably the Rapael doesn't have that many HW keys to start with...

I want also to use Home/Back buttons for different purposes,but I didn;t found a solution yet.

Gotten a step closer to what i really need over this weekend:
In the button dialogue (with extra generated buttons by Spb PP+4) there was only one other button that had a name...
So i tried this one and go figure: it seems to be the " <= " (or 'back') button. In the dialogue it's called the OK button. I've got it set to the close contaxt menu now, and mapped Voicecommand to long-pressed answer key...
So far, this setup is to my satisfaction, and after two months of use this phone finaly behaves completely the way i want it to...

Hi, guys.
See my post here:
http://forum.xda-developers.com/showthread.php?p=2743845#post2743845
Hope this helps!
Cheers.

helped realy much !!! big thx for that nice instructions

You're very welcome, tk_berlin.
You be sure to let me know if anything in there doesn't make sense or you need any help with it.
Cheers from Canada!

ah cool to see a reply that fast ,)
hmm u got any further with finding out how to set the home button and the backwards button ?
Since the other htc user ,) wrote
In the button dialogue (with extra generated buttons by Spb PP+4) there was only one other button that had a name...
So i tried this one and go figure: it seems to be the " <= " (or 'back') button. In the dialogue it's called the OK button. I've got it set to the close contaxt menu now, and mapped Voicecommand to long-pressed answer key...
so it works with SPB PocketPlus ?
there must be a way to get it work wit the other tool

ah cool to see a reply that fast ,)
Click to expand...
Click to collapse
Lol. I was on my machine all morning and had XDA open in one of my tabs.
Yes, you can map practically any button in AEBPlus no problem.
hmm u got any further with finding out how to set the home button and the backwards button ?
Click to expand...
Click to collapse
AEBP will also *learn* any keys it doesn't have. So you could use the "Add Button" option, press your Home key, and away you go.
The way I have it set up, holding down the phone key will activate voice command (default behavior).
But remember, assigning commands to the Home or OK buttons (that "Back" button is actually an "OK" button) doesn't unmap what they normally do so you will always go home first and then it will perform <x>-function that you assign.
Personally, I don't like to program the Home or OK buttons because I find that they are "trickier" to press. What I mean is, if you tap the OK button near it's center or close to the left, it doesn't register a press. If you tap it sort of with the long part of your thumb (which is more natural when holding the device in one hand), it registers it. I've tried this with two TP's now and the button behaved the same way on both. Due to this, I find it unreliable to map anything to it.
In any case, as I mentioned earlier, the Volume buttons, Phone and End keys will be unmapped once you attach AEBP to them but the others will not.
Oh -- I forgot to mention, you can map the directional pad as well if that is your thing.
so it works with SPB PocketPlus ?
there must be a way to get it work wit the other tool
Click to expand...
Click to collapse
It does work, but it sends an OK command first.
I wrote a little utility for hard-coded buttons such as these for another Pocket PC I had (an ASUS P527) called "DoNothing.exe" but we can't apply that work-around here. What I would do is replace the EXEs of apps the hardware keys called with my DoNothing.exe, but in the case of the TP, we definitely don't want to replace START.EXE (which I believe to be the likely EXE (haven't tested this)).
If I find a way to map those buttons reliably, I will let you know, tk_Berlin. So far tho, I've been quite pleased with just using the four buttons I mentioned. The more I use this device and the more I ponder my decision to stay with TFL3D instead of the normal WM interface, the more I realize that I don't need half the add-ons I used to use prior to having TF3D. I am accustomed to very, very, very *heavily* customizing my device, but the setup I have now works great and I really haven't lost nething from my old WM world. In fact, prolly gained a few CPU cycles and memory to boot.
I don't miss the Today Screen at all!!! Now that I think about it, I never really looked at it.
Cya!

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.

Re-map Home and Back to SoftKeys

I'm using Butler [ http://forum.xda-developers.com/showthread.php?t=464611 ] to use the extra functionality of the hardware keys ... the only thing missing for me now is the possibility to use the 2 top buttons of the touch pro [Home and Back] for the left and right softkey (that's the only thing I miss from the kaiser). Any ideas how to do it without AEB ?
And is there a program you can launch to go to the today screen?

I'd be interested in this also. Thus far Da_G's latest roms have been able to reprogram every button except volume, home, and back keys.
Unfortunately the Volume, Home, and Back keys give me the most trouble. I always keep my phone on vibrate and I never use the Home/Back buttons. Even a good way to simply disable these keys would be a start. I'd much rather be able to use my dpad without ending up at the today screen.
Although someone said they used AEB to remap the Home/Back buttons to ONLY function on a double tap.

i was just thinking about this. i noticed i could change long press for send and end as soft keys. not enough buttons on the device you know.

I also would love to be able to reprogram the home and back keys to be the left and right softkeys. There has to be some way to do it...

I did some more searching on this topic. Try DredSensor. It works for me so far.
drcursor said:
I'm using Butler [ http://forum.xda-developers.com/showthread.php?t=464611 ] to use the extra functionality of the hardware keys ... the only thing missing for me now is the possibility to use the 2 top buttons of the touch pro [Home and Back] for the left and right softkey (that's the only thing I miss from the kaiser). Any ideas how to do it without AEB ?
And is there a program you can launch to go to the today screen?
Click to expand...
Click to collapse

If we can get the home, back button, set as left and right softkeys as well as set pressing the center button in as OK button then i would have zero complaints about my att fuze. Sometimes i turn my tilt back on just to use programs such as opera mini, life is so much easier with softkeys!

DarrenUtd said:
I also would love to be able to reprogram the home and back keys to be the left and right softkeys. There has to be some way to do it...
Click to expand...
Click to collapse
Yes im sure everyone is aware of dredsensor which is what i have to use when running opera mini on my fuze. What we are talking about is setting the home and back button as softkeys for good for all apps by default and also having the center button as OK as well. Do we really need a home and back button anyways? I mean we have touch screen phones, i can drag my thumb to get to home screen and press the center button to go back if set to OK button.

No we don't need an Home and Back button. The home button works the exact same as the End key. The back button is iffy. While I don't use it much, I'm sure "some" people do. There are the occasional situations when the back button is useful.
If you make the Center button "Close/Ok", then you won't have a select button. What WOULD work is set the center button to default, but do an "Close/Ok" on Center Hold.
I wish we had all the buttons unlocked to do what we wish. Using Home/Back as softkeys aren't a big deal to me, BUT being able to at least disable them or remap them in games would be sweet. (yes I know about DredSensor... I'm talking about permanent).
Another thing I am aiming for is a "virtual D-pad" using the touch pad area around the center button. Allowing us to navigate simply by making contact to the "hotspots". This would at least fix the problem with using the Dpad in games without ending up at the today screen.
If we could offload the navigational functions to the touchpad... then we could remap the buttons up/down to launch programs or whatever (left and right too).
So Pressing the buttons on the touchpad could launch apps or be used as softkeys or whatever but touching the touchpad would navigate.
Here is the thread; http://forum.xda-developers.com/showthread.php?t=473023

The last couple of posts have been playing down my earlier suggestion to use dredsensor to remap the home and back buttons to be the left and right softkeys (the topic of this thread). I'm not affiliated with dredsensor in any way, but I wanted to clear up this issue.
Since version 1.1 was posted on 1/17, you can in fact remap the buttons as stated above. In your config.ini file, for the [Default] profile with WindowTitle=* and ClassName=*, you have the entries:
HardKey_Launch1=Key:SoftKey1​and
HardKey_Launch3=Key:SoftKey2​
I'm not sure what you guys mean by "permanent" or "for good for all apps by default", but with this configuration these rules should apply in any app, which would seem to be what you want. I've been using this for a few days now and it works for me in the applications I've used. Anyway, it's just a suggestion. Maybe give it a try and I hope it helps.

i followed your suggestion..but i find the behavior erratic..sometimes it looks like it just goes to sleep and the keys are back to normal, and then out of nowhere starts to run again :\

drcursor said:
i followed your suggestion..but i find the behavior erratic..sometimes it looks like it just goes to sleep and the keys are back to normal, and then out of nowhere starts to run again :\
Click to expand...
Click to collapse
From what I've read, there could be problems if you have G-Scroll installed, or maybe on some specific ROMs. Maybe post the issues you are having so that the developer can fix it in the next version.
http://forum.xda-developers.com/showthread.php?t=472280&page=2

Question about the sensor of touch pro

As i know that touch pro is not only can be touched on the screen but also the hard button area ( home, back, call, hang up buttons)
How can i use that feature
Which software that i need to install or how can i active it
Thank for reading my topic

What do you want exactly? Do you want to remap hardware buttons?

the hardware buttons are enabled by default. you don't have to 'activate' them.

No! My point is how can i use the sensor of hardware button ^^

Well,did you mean to use the capacitive surface of those sensors,not the buttons itself? And what exactly do you want? Please explain.

google for "G-scroll"

TomasNM said:
Well,did you mean to use the capacitive surface of those sensors,not the buttons itself? And what exactly do you want? Please explain.
Click to expand...
Click to collapse
My point is
Instead of pushing down the 4 hard buttons (call, back, home, hang off) i just need to touch it on the surface?

You can buy gscroll (mobilesrc.com), but unless you can get the 1.x series, I'd pass. The 2.x series is buggy as hell, and it seems like development has stopped. There are some free apps you can find around here as well. I'm thinking Dredscroll is one, and there was another app called Butler (I think, lol) that allowed you to use it as a launcher with gestures on the area. Gscroll lets you swipe to scroll (it's good for reading ebooks, when it's working) as well as to launch things, but it has the annoying habit of going on smoking breaks.

As I know HTC testing software,I can say,it could not be a problem to create an app of this kind,but...
- Do we have SDK for it(I didin't searched for it yet)?
- Currently I don't know,how to send keyboard hooks to the system
- I cannot prevent/disable default keyboard hooks
So that means,I am not able to solve your puzzle. Sorry.
That was my honest opinion...

I don't think he's asking about the Vibrant-Scroll Wheel, I think he's talking about the Optical Track, itself.
[As the Home, Back, Answer, & End Call buttons require you to actually PUSH them down.]
You know, the "OK/Enter" button. When you place you finger on it [NOT PRESS IT], by default, it lights up the Bottom Hardware Keys, as well as brightens the screen.
If it's not working for you, I recommend Backing up your Important Information with either SPB Backup or Microsoft MyPhone, and flashing a New ROM. There are certain Drivers that control the Optical Track. What they are, however, is beyond me.