hey guys
have an i-mate SP5 which i was using last year (i've since upgraded to a Palm Treo 750). the reason why i stopped using it was because the far right soft key wasn't working.
i've tried hard-resetting the phone to no avail. every now and then it works then drops out... so i can't access any menu functions at all.
does someone have experience in opening it up? i thought maybe a cleanup might fix the problem... or maybe something's preventing the button from making contact with the board...
or shall i just pay someone to do it?
Right soft key not working? You might need to clean up the keypad, someone in modaco posted a tutorial
http://www.modaco.com/Mate-SP5-Tornado-Disas-t241033.html
As variant: Try AE Button Plus. By this program you can remap your button.
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!
Starting a couple of days ago, the hardware keyboard on my Fuze started randomly repeating keys: I'll be typing along and suddenly a character will insert itself a number of times. It seems to happen once every 30-50 keystrokes on average.
I'd write it off as a busted keyboard and take it back to the store for an exchange, but it doesn't feel like a hardware issue. For one thing, whatever key it is always repeats 6, 7, or 8 times. Keyswitch bounces in my experience generally insert fewer spurious characters than that. For another thing, there's no pattern that I can discern to which keys repeat; a hardware problem usually affects one particular key or key grouping.
What I'm seeing looks more like the key release event is being delayed until after the long-press repeat processing takes over; then the release event fires within a fairly narrow timing window. If I watch the screen as I'm typing, I see exactly what I would see if I held the key down: I get one character, then after a short pause, I get 5-7 more of them. This started happening about the time I installed AE Buttons Plus; however, I've uninstalled that and the problem persists. (However, uninstalling often doesn't undo all the registry changes that were made, so AEBP could still be the culprit, I suppose.)
I'm probably going to hard reset tomorrow when I have some free time so I can play around some more with the GPS starting from a clean slate, and that will give me a chance to test whether AEBP is, in fact, responsible. In the meantime, does this sound at all familiar to anyone? Any suggestions for what I might look at in the registry?
A quick update on this: I have verified that AE Buttons Plus is, in fact, responsible for the repeating keys. I set the new key that was added for the PTT button to "Do not touch" in AEBP and soft reset. I have had no repeating keys since then.
I have emailed the author, describing the problem, but I haven't heard back from him yet. I'm hoping that he can either fix AEBP or suggest some workaround to prevent the repeating keys. The short_PTT.lnk/long_PTT.lnk solution recently presented here works fine, but it only gives two assignments, while AEBP can do three (or four, if you can live with the Home button doing the same thing as the single-press PTT button).
If I hear anything encouraging, I'll post again. Otherwise, people should use the shortcut approach for remapping the PTT button.
The send key and the end key work correctly every time after a fresh restart. But they both will "disappear" after a while of using. The "home" function will replace the "send" and the "backward" will replace the "end",
Does any body here have the same issues? Am I having a bad HardSPL, I had tried several 6.1 and 6.5 rom, no good news for me.
Update: installed the cleanRam program, the function of those keys work again, every time after Ram Cleaning. But, I have to say, keys malfunction after a while again.
question
1. how does the keypad work? send key and the home key they are too close? is there any sensor area around the surface?
2. If I keep pushing the buttons when send key and end key malfunction, the phone will dead. Indicating something wrong with the phone?
Thanks
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.