Hello,
My Raphael 100 dpad buttons are not working in android roms!
I can't go 'back' or to 'home' in Android
"Home" button and "call" button act as navigation key (left)
"back" button and "call end" button act as navigation key (right)
I have tried numerous roms (neofroyo, thunderbolt, hercules, cbv2, cherrypie and more), even non-cwm roms (frx07, froyob v5, v6)
Non of them worked
I also tried with several different kernels (very old, old and new) but still same.
Does anyone have solution for this?
Haven't had that problem in a while but then again I haven't really played with XDAndroid about that long. Even still, never had that much of an issue. Usually I could just cycle the screen off then on and the problem was gone.
Is it possible that you are constantly sliding across the buttons? I know I can get it to go crazy after sliding across the buttons a few times...
No its completely not working only in android roms as if the keys are not mapped
I even tried FRX03 (which was working fine couple of months back in the time) but somehow the keys are not working now... really strange
That's a new issue to me. I take it the d-pad works in winmo but not after you boot into android? Have you filed a bug report yet?
Curious, does the screen react to touch?
Curious said:
Nope it doesn't light when I touch dpad
Click to expand...
Click to collapse
So the d-pad doesn't work in winmo or does it?
it works ! but will take full advantage of your d–pad, your driver must generate the proper virtual key codes ~ http://msdn.microsoft.com/en-us/library/bb821761.aspx
Related
Right, I can't see an Issues list for this device yet so I'll start one:
1. A couple of times now, I've left my phone to charge overnight and woke up to an unresponsive device. Power button does nothing, screen is off and only way to get it device back up and running is to poke the soft-reset button OR remove and reinsert the battery.
2. Unresponsive buttons: every now and then the "right" button of the D-Pad does nothing, then suddenly it will start working again, same with the "Back" button though much more infrequent/noticable than the D-Pad issue I've experienced.
I did not expierence the first problem with the charging issue.
To close and app you can use the (arrow pointing left) key but sometimes i have to push it like 3 or 4 times before it respond.
Same with the touchscreen but i fixed that by increasing the touchpad sensitivity with a regedit.
My device has reset a few times while I been reading email or texts.
John
Guys. The whole phone besides the keyboard is touch sensitive. So the whole front keys and touchscreen. Increase sensitivity and it should work fine.
Kraize92 said:
Guys. The whole phone besides the keyboard is touch sensitive. So the whole front keys and touchscreen. Increase sensitivity and it should work fine.
Click to expand...
Click to collapse
Erm, I'm sorry but that's not right is it. The D-Pad, Send, End, Home and Back buttons are actual buttons as opposed to touch sensitive.
The zoom wheel is obviously a "touch" area too. The issue I am descriping seems to suggest that the switches might be a bit flakey rather than anything else.
no he is right all the buttons are PRESSURE (he said touch) sensitive..when they unvieled the diamond the ceo of htc demonstrated that the keys are pressure sensitie and even the cameria button can SENSE when your finger is approaching to ready the zoom ..here is the youtube vid
http://www.youtube.com/watch?v=YTd3SUPSJsMit
pazookie said:
no he is right all the buttons are PRESSURE (he said touch) sensitive..when they unvieled the diamond the ceo of htc demonstrated that the keys are pressure sensitie and even the cameria button can SENSE when your finger is approaching to ready the zoom ..here is the youtube vid
http://www.youtube.com/watch?v=YTd3SUPSJsMit
Click to expand...
Click to collapse
Sorry my bad. WM phones used to be called touch sensitve but in reality they're pressure sensitive. The only touch sensitive phones out currently are the iPhones and the Omni I would say.
Syphon Filter said:
Erm, I'm sorry but that's not right is it. The D-Pad, Send, End, Home and Back buttons are actual buttons as opposed to touch sensitive.
The zoom wheel is obviously a "touch" area too. The issue I am descriping seems to suggest that the switches might be a bit flakey rather than anything else.
Click to expand...
Click to collapse
If the were actual buttons they would be capable of being pushed in which it's not possible to do
Issues:
HTC task man doesnt work properly.
Poor reception
Too many startup apps/services put on by htc to provide touch interface (which i hate)
why on eart you use operaloder on phones stratup just to get 2-3 more seconds fast load time for opera.
i think htc just over done this touch crap.
could anoyone access setupfiles on rom so i can use plain wm6.1
Kraize92 said:
If the were actual buttons they would be capable of being pushed in which it's not possible to do
Click to expand...
Click to collapse
Hang on, you clearly don't own either Touch Pro or a Diamond, the D-Pad, Call, End, Home and Back buttons CAN BE PUSHED IN. They are actual buttons.
Syphon Filter said:
Hang on, you clearly don't own either Touch Pro or a Diamond, the D-Pad, Call, End, Home and Back buttons CAN BE PUSHED IN. They are actual buttons.
Click to expand...
Click to collapse
No. I'm sure of it. I have demoed both a touch pro and a diamond. I meant that they CANNOT be pushed in as you can on the kaiser. I know this for a fact and on every video you will see that it is mentioned as a pressure sensitive all around except for the keyboard. I'm sure of that. They are not real buttons. I guess you could push it in if it's just a piece of glass and paper underneath the actual pressure sensitive touchpad, but it wouldn't make it real buttons. I know what I'm talking about Unless HTC suddenly decided to make them real buttons which would kill their profits so I'm assuming that they wouldn't do that either. I demoed it about 2-3 weeks ago.
Syphon Filter said:
Right, I can't see an Issues list for this device yet so I'll start one:
1. A couple of times now, I've left my phone to charge overnight and woke up to an unresponsive device. Power button does nothing, screen is off and only way to get it device back up and running is to poke the soft-reset button OR remove and reinsert the battery.
2. Unresponsive buttons: every now and then the "right" button of the D-Pad does nothing, then suddenly it will start working again, same with the "Back" button though much more infrequent/noticable than the D-Pad issue I've experienced.
Click to expand...
Click to collapse
1 - Not had that problem - hopefully that'll go after your next hard reset or ROM update - these damn things always have, and always will behave differently for different people, it seems!
2 - My Back button missed my press once or twice, but I think it's more of a hardware issue than a software issue though (or possibly user error!). I'll tell you now though, hitting the "Right" button on my Diamond was next to impossible. It was extremely stiff, and would eventually register as a press on the "Hang Up" button. Drove me absolutely mental! But I think I was the only Diamond user who had that problem, and my Raphael is fine.
having got one in my hand - they are tactile push bottons - i.e you push them until it clicks before an action happens.
ardsar said:
having got one in my hand - they are tactile push bottons - i.e you push them until it clicks before an action happens.
Click to expand...
Click to collapse
Then I must be crazy. Since all I have to do is touch the button and a action happens. But my pressure threshold is very high.
Kraize92 said:
No. I'm sure of it. I have demoed both a touch pro and a diamond. I meant that they CANNOT be pushed in as you can on the kaiser. I know this for a fact and on every video you will see that it is mentioned as a pressure sensitive all around except for the keyboard. I'm sure of that. They are not real buttons. I guess you could push it in if it's just a piece of glass and paper underneath the actual pressure sensitive touchpad, but it wouldn't make it real buttons. I know what I'm talking about Unless HTC suddenly decided to make them real buttons which would kill their profits so I'm assuming that they wouldn't do that either. I demoed it about 2-3 weeks ago.
Click to expand...
Click to collapse
I'm not going to get into an argument over this but the 9 buttons (Home, Back, Call, End, Up, Down, Left, Right and the centre of the D-Pad) on the face of the Diamond and the Touch Pro are buttons which have a tactile feedback, a press will not register until you "feel" the button pressed. The only thing in that area that is a "touch sensitive" thing is the zoom wheel.
Just because the area looks flush does not mean they are not buttons. There's a single piece of material that covers that area but I can assure you there are individual switches under there that provide a tactile feedback. You HAVE to feel that feedback for the button to do anything, simply touching it will have no effect unless you are using the zoom wheel functionality.
If you believe anything else you are wrong.
Kraize92 said:
Then I must be crazy. Since all I have to do is touch the button and a action happens. But my pressure threshold is very high.
Click to expand...
Click to collapse
1. What do you mean "my pressure threshold is very high"? Are you talking about the registry settings?
2. I thought you didnt have a Touch Pro or Diamond?
I said I didn't own one. Doesn't mean I don't have one in hand right now I have family members and friends that work for HTC america and AT&T.
Yeah. Registry settings/Advance Config for diamond
Kraize92 said:
I said I didn't own one. Doesn't mean I don't have one in hand right now I have family members and friends that work for HTC america and AT&T.
Yeah. Registry settings/Advance Config for diamond
Click to expand...
Click to collapse
Yes. Ok.
Anyway, so you're saying that device you have in your hand right now has no tactile feedback on the front face buttons?
If have insiders at HTC why did you ask for donations so you could get a Touch Pro in the other thread?
Syphon Filter said:
Yes. Ok.
Anyway, so you're saying that device you have in your hand right now has no tactile feedback on the front face buttons?
Click to expand...
Click to collapse
EDIT: Okay. Maybe I'm mistaken. It's only the d-pad that's pressure sensitive. The buttons are tactile even though they feel as if they are pressure sensitive because I don't push into it like I did with the front face buttons on my kaiser.
ah, you've seen the light. The button DOES push in but the panel is one solid "sheet" that covers all the buttons.
The "wheel" is the only touch sensitive bit. The 5 navigation functions of the d-pad (up down left right select) are all tactile buttons that work off little switches.
Syphon Filter said:
ah, you've seen the light. The button DOES push in but the panel is one solid "sheet" that covers all the buttons.
Click to expand...
Click to collapse
Actually. I should show you the light I'm right.
[Link]
Click number 3 and read this caption: "Swipe your finger across the screen to scroll through contracts, zoom, and pan web pages, browse your music library, and more, or press the touch-sensitive buttons to navigate and control your phone."
So concluding to that original fact that I was indeed right
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!
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:SoftKey1and
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
I tried TouchLockPro.
It seems that it cannot read the HD2 G-Senor properly. From time to time, it gets the correct orientation, but most of the time its doesn't sense any changes. For example, I flipped the phone around (using the movement defined by the default setting) more than five times and I succeeded in unlocking only once. Is anybody else using it?
Everybody happy with the G-Sensor in Touch Lock Pro? I have no idea why it isn't working on my HD2.
No, it doesn't work reliably on the HD2. I tried it for a few days previously, and sometimes, it would become impossible to unlock, using G-sensor, Vol down/up or even the light sensor. So, I've uninstalled it.
I've been using it for a couple of months now and I've not had a problem. Seldom does it not respond first time when I get the gesture correct. It never fails to respond to the volume control. My only problem with it is that it clashes with Throttlelock after going into standby so that I have to remove the battery.
and i have no time when it responds correct;y...almosy everytime it mess up everything, so i am back to standart lock-by pressing the end key
creed said:
It never fails to respond to the volume control.
Click to expand...
Click to collapse
Volume control? How does it work in TouchLockPro?
alex fung said:
Volume control? How does it work in TouchLockPro?
Click to expand...
Click to collapse
With default settings it will unlock by pressing Volume Down followed by Volume Up.
ZuinigeRijder said:
With default settings it will unlock by pressing Volume Down followed by Volume Up.
Click to expand...
Click to collapse
Ah! This is not listed as one of the ways to unlock (2.4 how to unlock) so I never knew that it was possible.
TouchLockPro on HD2 does not disable buttons in call
Hi, I cannot configure TouchLockPro to disable my hardware buttons when receiving an incoming call. I have switched on the Telephone API but still I can answer incoming calls using a button, which I try to prevent. I have played with the option of thye TAPI configuration screen without succes. What am I doing wrong? Who owns a HD2 and have it working and want to post the correct settings? Thank you.
regards, Danny Groeneveld
I have a Touch Pro2, and I have my G-Sensor set to unlock on upside-down, Portrait, upside-down, Portrait. What I've noticed is that it makes a difference HOW it gets down and then back up. For instance, it works fine as long as I rotate the phone (it's facing me) counterclockwise down and then clockwise back up. But if I rotate clockwise down and then counterclockwise back up, it never unlocks. Doing a clockwise rotate down and back up does work just fine if it's followed by either a forward or backward flip and then back up. But two full 360 degree turns in ANY direction don't seem to work.
Fortunately, I'm right-handed, so it's working out well for me.
P.S. This is one of the best apps EVER! Thanks SOOOOOOOOOOOO much to the author for developng it!!!!
Hello!
I'm experiencing some problems with my o2 Touch Pro.
Hardware buttons on the bottom of the phone (d-pad, home, back, call, end call) are not working properly (they work fine only 20% of the time, it's random i guess).
When i press "call" button, device responds as if i pressed the "left" button. It's very annoying. The circle used to zoom in, and out around the "enter" button is problematic as well. It zooms - but but in a very chatoic way - a bit of of zoom in, then zoom out, another zoom in. Functions are just messed up.
Another time, it's all working...
How can i fix it? Is it a hardware problem?
I'm using the Energy Rom - titanium version.
Thanks for your help in advance...
Honestly, if you can't deal with it, get another device. Either that or stick with the stock ROM, less problematic (you can also keep the full function of the d-pad) but then again it may introduce other issues. Someone mentioned this being more a hardware than a software issue. Since I cannot reproduce this on my at&t Fuze, that is all I can suggest on my end.
I get some of that with my fuze; mostly, the d-pad doesn't read gestures properly. If I run compact heaps (from sk tools) periodically, it helps. Soft resetting obviously helps as well. I think it's more of a hardware issue. My problems have definitely gotten worse over time. You can also check out this tool (from an HTC test rom dump; can't remember where I got it). It's a debugger for the d-pad. At least you can see how accurately the button presses and gestures work.
Thanks.