Database Info

? remap green button to speakerphone

I want to map the green "phone" ("send") button to work as speakerphone with long keypress when phone is used, but I can't find any info.
OTOH I notice most ROMs use long press for this button and map usually wireless managers, which would be fine if it would work that way only when phone is not in use (and 'restore' the speakerphone function for long press when phone is in use) but I have not seen such solution yet. Has anyone done/try this?

-888- said:
I want to map the green "phone" ("send") button to work as speakerphone with long keypress when phone is used, but I can't find any info.
OTOH I notice most ROMs use long press for this button and map usually wireless managers, which would be fine if it would work that way only when phone is not in use (and 'restore' the speakerphone function for long press when phone is in use) but I have not seen such solution yet. Has anyone done/try this?
Click to expand...
Click to collapse
Hi,
Deleting Long_Send.lnk might restore original function of long press send key sir,.
Hope it help,.
Regards

Unfortunately, I don't think you can have two different functions based on context. AdvancedConfig has an option to map pretty much anything to the long send.

Garmin said:
Hi,
Deleting Long_Send.lnk might restore original function of long press send key sir,.
Hope it help,.
Regards
Click to expand...
Click to collapse
Thank you, Sir
blue_94_trooper said:
Unfortunately, I don't think you can have two different functions based on context. AdvancedConfig has an option to map pretty much anything to the long send.
Click to expand...
Click to collapse
Well, I was thinking about something more complex than I can do myself, hence my post here.
Idea is to make a small applet which will switch the function of the button based on the processes running (or other ways to determine it) and assigning different shortcut to this button. I.e. when the phone is connected it will assign speakerphone to the "send - long press", when phone is not in use it would redirect "send - long press" to the wireless manager, if you know what I mean (sorry my english); so virtually mapping the "green" button to this app could achieve that, no?

intersted also in your send key LKP!!
-888- said:
Thank you, Sir
Well, I was thinking about something more complex than I can do myself, hence my post here.
Idea is to make a small applet which will switch the function of the button based on the processes running (or other ways to determine it) and assigning different shortcut to this button. I.e. when the phone is connected it will assign speakerphone to the "send - long press", when phone is not in use it would redirect "send - long press" to the wireless manager, if you know what I mean (sorry my english); so virtually mapping the "green" button to this app could achieve that, no?
Click to expand...
Click to collapse
Bump....
I also want exactly the same setup! Great minds think alike!
Your mention about the wireless manager sounds a handy idea also, and I am at present having to use a long keypress on the left hand hardware 'record' button. This is fine, but I also have it mapped to normal press = audio record. But want to use it for something else at some point.The more buttons free the better. To be able to have the sent button act on a long key press to work the speakerphone seems to me like something that should actually be in place by default. I mean, what better way to start the speakerphone!!
I do hope someone is able to shed some light on this, or you manage to pull it off yourself you can count me in to try the fix etc.
PS:: Would a MORT SCRIPT help in this situation I wonder? I am not familiar with MS but sure someone may know a way round it.
Regards
Nick-UK

Thanks for your kind support
I wrote about this year or more ago on another forum, but few responses I got were discouraging at best.
I think if we could do such "app", we could use it for all the buttons and change their "assignments" based on the currently running apps...
With scripts we can do things like rename "Long_Send.lnk" into "Long_Send.disabled" (for example) instantly, and rename it back to "Long_Send.lnk" when i.e. pressed again. But the problem is that I don't know how to "detect" and use it in the scripts what is currently running and discriminate between foreground and background processes that are currently running?
Because what if you have two (or more!) programs that are using the same button assignments but for different purposes and both are running in the same time? say you are on the phone talking - thus long_send is assigned to speakerphone, and you also run (for example) windows media player where you assigned same green button to fullscreen display? The scripts cannot tell which one is running in the foreground by themselves, and (in this example) holding green button could bring the WMP to fullscreen instead of turning on speakerphone. Beforewe use mortscript to "activate" apropiate script, we need to know which process was started last (so - per my example - we would know that the phone was last started and not the WMP, and mortscript would run "speakerphone script for green button" instead of "fullscreen wmp script for green button"... and there is another problem: the phone is always ON on our PocketPCs since boot, and it is running all the time in the background, so it will have to differentiate between phone being active and phone in the "waiting" state...). Apologies if I sound incomprejensible, I tried to make it clearer but I don't know is it less gibberish
to cut it short: I don't think it can be done with simple scripts. But of course I may be wrong.
In theory it should work this way:
1 Long_Send.lnk -> starts our "app"
2 "App" checks what program is currently running on the screen (in the forground, or last started etc)
3 "App" executes apropiate action assigned for this program (i.e. speakerphone for active phone call, or wireless manager for today screen, etc etc)
4 "App" releases/removes/disables the action from previous step and changes it back to the state it was before when the foreground program is closed (i.e. changes back long_send from assignment to speakerphone back to default once the phone call ended)
sounds simple, doesn't it?

Fuze PTT button remapping problem

Before I start, I apologise if this has already been answered elsewhere, as I've spent about five hours trawling through threads looking, in vain, for a solution.
I have bought a new Fuze but the PTT button causes a problem with the aluminium case I bought for it. The problem is that the case is for a Touch Pro and the latch is right where the PTT button is (meaning the button is permanently depressed when the case is closed). It cannot be remapped in Settings/Buttons.
All I want to do is to be able to disable the button completely, or failing that make it an 'OK/Close' button. I have got rid of the PTT link but would greatly, greatly appreciate if someone could tell me what commands should be written in "short_PTT.lnk" and "long_PTT.lnk" to be able to do this. I've tried just leaving both blank but then the PTT button brings up an error message when pressed about not being able to find the shortcut.
Is there a way to achieve either of these solely using the registry, and without using third-party software?
Thanks for your time.

Here's full instructions on remapping your PTT button: http://www.fuzemobility.com/?p=598
To just disable it so it does nothing follow the steps at the beginning:
Using a registry editor delete HKLM\Services\PTT.
Next delete HKCU\Software\HTC\PTT.
Navigate back to the Windows directory and rename PTT to PTT2
Now create a new folder called PTT and set the properties as System and Read Only
If you follow all of those instructions and want to map it to close use this app and map it: http://www.fuzemobility.com/?p=1249

Problem fixed
You're a great person, bugsykoosh. I had done the first part you suggested, but the second link - and use of a tiny program called Zap It - fixed it perfectly.
Thank you heaps.

Okay so what is the joke why does this work for EVERYONE, except me. I mean seriously. I followed the steps but nothing. I press the button and I get nothing at all except the noise that indicates the keypress was succesfull WHAT GIVES.

bugsykoosh said:
To just disable it so it does nothing follow the steps at the beginning:
Using a registry editor delete HKLM\Services\PTT.
Next delete HKCU\Software\HTC\PTT.
Navigate back to the Windows directory and rename PTT to PTT2
Now create a new folder called PTT and set the properties as System and Read Only
Click to expand...
Click to collapse
This is overkill. You don't need to mess around with the PTT directory. If you just stop the PTT service from running, nothing will look in the PTT directory and its contents don't matter.
Just change HKLM\Services\PTT\Dll to an empty string and soft reset. The button will be completely inert. You can then remap it using AEBP or the short_PTT/long_PTT shortcuts, if you choose, or just leave it inactive.

Today
WMM,
If you change as you suggested, it looks like the long and short still work. I've remapped and did all the steps, but it looks like yours may be a little easier/cleaner. I'm curious, and I've looked extensively to no answer, but if I want the short press to just send my Fuze back to "Today" (in TF3D), is there a way to do that? If I press Start the first option is Today and this does exactly what I want. There's no shortcut that I can locate anywhere (and I'm sure it's my ignorance/technical inability) and the next step is to make a copy of that shortcut and name it short_PTT which I can handle. Any suggestions?

So, it isn't possible to map the PTT button from the Settings - Buttons screen? Looks like the method linked to above, with the short_PTT and long_PTT shortcuts, won't allow me to map the PTT buttons to work as the left and right softkeys.

As far as I know (which isn't very far, sometimes), the only way to get the PTT button to execute "Home" or the left/right soft keys is to use AE Button Plus. There may be applications that do those things that you can download (I know there are for things like toggling wifi and bluetooth, killing the current application, etc.) -- these are really tiny utility applications that are specifically intended for mapping to a button -- but I don't know of ones that do those particular things. (AEBP is able to do all those things, as well as giving you four mappable events -- single, double, triple, and long press).

okay seriously here do the links need to have special settings or anything. I mean what attributes should they have. Nothing works!

For the life of me, I can't remap my PTT button.
On a short press, it activates the voice command system.
On a long press, it activates the camera.
This seems to be from flashing NATF's ROM.
Following instructions above, I have no HKLM\Services\PTT or HKCU\Software\HTC\PTT in my registry editor.
I did the short and long_PTT/link and PTT folder in Windows. The links work there, but doesn't change what happens when the button is pushed.
I have AEButton Plus, but can't get it to add the PTT as a button.
Any suggestions where I can find in the registry what is making my PTT button act as it is? I'd rather have it do nothing than what it is doing now.
Thanks,
Chris

txemsdoc said:
On a short press, it activates the voice command system.
On a long press, it activates the camera.
This seems to be from flashing NATF's ROM.
Following instructions above, I have no HKLM\Services\PTT or HKCU\Software\HTC\PTT in my registry editor.
I did the short and long_PTT/link and PTT folder in Windows.
Click to expand...
Click to collapse
Yes, I believe NATF did not add the PTT stuff from AT&T into his ROM; the instructions above are for the stock AT&T ROM. You'll have to ask NATF how to remap the PTT button using his ROM.

jro2020 said:
okay seriously here do the links need to have special settings or anything. I mean what attributes should they have. Nothing works!
Click to expand...
Click to collapse
I'm not sure what you're talking about here. As I mentioned in my last posting just above this one, this probably only works in a ROM that supports PTT, like the stock AT&T ROM; if you're running something that doesn't support PTT, it would be a real surprise if "short_PTT" and "long_PTT" meant anything special, no? Assuming you are running the stock AT&T ROM, here's a step-by-step procedure for creating the short_PTT link to point to the Camera application using the built-in File Explorer.
1) Open File Explorer. If the drop-down box at the upper left says anything other than "My Device," tap the small down-arrow next to the label and then tap on "My Device."
2) Tap on "Windows" and wait a few seconds for the folder contents to appear.
3) Scroll down until you see "Camera" (the one that's 794K). Tap and hold that until the pop-up menu appears and then tap on "Copy".
4) Tap on "Menu" in the lower right, then "Edit", then "Paste Shortcut".
5) Scroll to the very bottom of the folder contents and you'll see "Shortcut to Camera" that was created. (The name may be truncated, depending on the size of the font and the screen orientation. Mine says, "Shortcut to Ca..." in portrait orientation. In any event, it will be the last thing in the folder contents.) Tap and hold on that until the pop-up menu appears and then tap "Rename". Then just type "short_PTT" to overwrite the existing name and hit return.
That's all you need to do. (If the application you want to run with the PTT button is in a different folder from \Windows, navigate there, tap-hold on the application executable, and select "Copy". Then navigate to \Windows and do steps 4 and 5 exactly as above.) This works exactly the same for the "long_PTT" shortcut.
If you do exactly that, does it not work? What happens if you tap the "short_PTT" shortcut in File Explorer? Does it start the camera?

Here is a link to a cab that will allow you to remap the PTT button: http://www.fuzemobility.com/ptt-remapping-revisited-application/

Remap PTT to launch phone Speed Dial?
I have disabled PTT so that I can use the button to launch programs - I just dont know how to launch phone speed dial - Does anyone know if there is a file that will launch speed dial that I can use to link to the PTT button?
Thanks!

pdafish said:
I have disabled PTT so that I can use the button to launch programs - I just dont know how to launch phone speed dial - Does anyone know if there is a file that will launch speed dial that I can use to link to the PTT button?
Thanks!
Click to expand...
Click to collapse
if your goal is to map your PTT button to call a single person check this posting: http://www.mobilitydigest.com/forums/showthread.php?p=3635

Here is another source that gives you step by step instructions.
http://htcblogger.com/2009/06/07/ho...utton-on-your-att-fuze-htc-diamond-touch-pro/

Note that if you're using the stock Fuze ROMs, the updated ROM from HTC adds the ability to remap the PTT button without any registry hacks.

PerfAlbion said:
Note that if you're using the stock Fuze ROMs, the updated ROM from HTC adds the ability to remap the PTT button without any registry hacks.
Click to expand...
Click to collapse
Can you post instructions as to how? I tried it already and the pulldown that shows you the available apps you can pick only shows PTT.
Best regards,
JD

So I followed the registry edit method, and created a file (not a folder) called PTT and things work great .... except ... when its on Airplane mode (Phone, Bluetooth and Data set to off) and I press the button (short or long) the PTT function kick off.
Is anyone else experiencing this?
Anyway to change this behaviour?

jdomi99 said:
Can you post instructions as to how? I tried it already and the pulldown that shows you the available apps you can pick only shows PTT.
Click to expand...
Click to collapse
Something's odd with your phone, then. Mine shows the full list of apps and options. I remapped PTT to VC without an issue.
Is it possible that you've got an application that's taking over the Buttons Control Panel? On mine, I had to remember to shut off SPB Pocket Plus's control over the buttons since it doesn't work with the Touch Pro line. When I first fired up the control panel, it listed no apps until I remembered that I had Pocket Plus running and turned of that feature.

[Q] Non-Touch compactible rom?

Hi guys,
My digitizer has died, and till the new one comes I was thinking of how I could use my T7272, I can write the SMS fine, but I can't send them out, cause the button is on the screen itself... is there a rom I could use freely w/o using the touchscreen?
P.S.
Is the digitizer hard to replace?

You could check out AE Button; it has some options like button presses that will activate soft buttons. I suspect you could send sms's using it. You could also try using mortscripts with AE button that will do stuff you need. There are some pretty simple scripts that will simulate screen taps, and you could assign them to a button push. I'd rather have a working touchscreen, though.
Here are some of the commands:
# 91: startmenu (on some devices it might be home button)
# 92: back key (not the backspace key but back key for closing applications which is available on some devices such as diamnd or blackstone)
# 93: menu key
#112: left softkey
#113: right softkey
#114: accept call (green button)
#115: hang up (red button)
#117: volume up
#118: volume down
#126: data disconnect
#127: toggle speaker
#133: devicelock
#223: power off
I use one to lock the device. Basically, you just put this:
Code:
sendspecial(133)
in a .txt file, and change the extension to .mscr. I call it Lock.mscr, and I have it assigned to a few different actions (like when a call comes in, a script locks the phone). So, sendspecial(112) and sendspecial(113) might help you out. There's also one for hitting 'Ok' in popups, which would probably work for you. I can't find it, though (google 'sendspecial' and you'll find it, it's all on msdn).
Anyway, if you install mortscript (maybe you already have it) as well as AE Button, you could assign button pushes to carry out those actions. Just stick the scripts somewhere easy, like the start menu, and it will be easy to set up.
If you want to get more complicated, there are also mortscript commands that simulate button pushes on the screen. You could set one up that would do just about anything. Also, SK Schema does similar stuff. You can write fairly simple sequences of button pushes that will do just about anything. This is one that I use that runs SK Tools Pim backup (I have it scheduled to run every night in the middle of the night).
#r(\windows\sktstart.exe) #p(STH:20)
#tap(146;602) #sleep(15000)
#tap(110;533) #sleep(500)
#tap(339;455) #sleep(500)
#tap(126;604) #sleep(500)
#tap(114;84) #sleep(500)
#tap(146;99) #sleep(5000)
#tap(310;254) #sleep(90000)
#tap(433;602) #sleep(10000)
#pwr() #sleep(10000)
Click to expand...
Click to collapse
Basically, the backup tool gets launched in line 1, then there are a bunch of screen taps (w/ delays, to make sure everything is ready) in the menus to get the right options selected, followed by turning the device off.

I`m not sure... But i saw somewhere app that emulate a mouse (cursor) and you will be able to control this mouse with your D-pad... But I can be wrong...

I can't install that mortscript w/o the touchscreen though..damn it..: )..

Get MyMobiler, and use it to run your device off of a pc. You should be able to get that working.

Broken Capacitive Button Workaround!

Alright, the Galaxy series, although awesome, suffers from some issues. None are as frustrating as when the damn capacitive (bottom) buttons stop working!
Normally it seems that all four bottom buttons don't fail at the same time, just one or two. This doesn't seem to be as much of a physical problem as a software one, probably an application running in the forefront that is blocking them. Now it is hard to do much of anything if the settings button (left side) fails, as you cannot access most settings for your apps. Both my outside buttons rarely work, the aforementioned settings button (left) and the search button (right). Search button doesn't matter to me, I can call up search on screen easily enough. The other two are home and back buttons. Back is more necessary than home. So to work around this Samsung-induced-pain-in-the-ass, I swapped the search button function for the home.
Here's how:
Make sure you are roted and have a rooted file manager. Root Explorer tends to work best.
1. Open Root Explorer, and make sure it is mounted r/w.
2. Navigate to /system, /usr, /keylayout.
3. Tap/hold Broadcom_Bluetooth_HID.kl, and select 'Open in Text Editor'. If you get a Warning message, that means you are mounted r/o so you just need to click the Mount R/W button above.
4. Change key 139 to read HOME instead of MENU.
Change key 102 to read MENU instead of HOME.
Hit the back capacitive button and choose to save. It will create a Broadcom_Bluetooth_HID.kl.bak file also so if you want to undo this then just erase the new Broadcom_Bluetooth_HID.kl file and then erase the .bak off the other file.
5. Now open the melfas_touchkey.kl file the same way by holding it until it allows you to select 'Open in Text Editor'.
Change key 139 to read HOME instead of MENU.
Change key 102 to read MENU instead of HOME.
Hit the back capacitive button and choose to save. It will also create a .bak file.
6. Open the qwerty.kl file by holding it until it allows you to select 'Open in Text Editor'.
Change key 102 to read MENU instead of HOME.
Change key 139 to read HOME instead of MENU.
Hit the back capacitive button and choose to save. It will again create a .bak file.
7. Back out of Root Explorer and restart your phone.
Now, when you push your home button it will bring up your settings menu in whatever application is open, and your settings button will do the home function (or nothing, as my outside buttons do as they don't usually work). I now use my back button to get me to home, it just takes a few more pushes as it goes one step at a time. Not as much of a pain as not being able to set program functions, that's for sure!
Note: Depending on your setup, the file names might be slightly different on other Android devices, but they will always be very similar. They'll all have a bluetooth.kl, touchkey.kl and qwerty.kl (or whatever your keyboard layout might be). You can also fool around with other key settings if you wish to experiment, depending on what is and is not working at the current time. Just save your original .bak files so you can put it back to normal easily. If you alter the .kl file more than once, it will overwrite the .bak file again (which is not used by the phone) so make sure you copy the .bak's to another directory (such as /sdcard/backups or your regular computer).
Hope this makes your lives easier and don't forget to thank me if I helped you.

Modified Home key acting up
So after using this mod for a little while, it has been working well except for some slight stalling of response from the capacitive buttons (which was happening before the mod) and an awfully annoying habit of backing out of programs by itself due to the modified left button which was originally Settings but I changed to Home with the above mod. When this happens, I can see the left button go dark as if it's been physically pressed, so obviously there is some electrical or software malfeasance happening there.
The fix to this problem is to navigate to your /system/usr/keylayout folder again and:
Delete: "key 139 HOME"
In each of these three folders we altered earlier:
Broadcom_Bluetooth_HID.kl
melfas_touchkey.kl
qwerty.kl
The result is that no action is associated with the leftmost capacitive button, which is fine because it wasn't working properly in the first place. This was becoming problematic as I typed in Terminal or while using my Ubuntu build on the phone.
Now, if there was also a problem with the search popping up by itself then you would just have to delete "key 217 SEARCH". Remember why I initially did this was because the outside capacitive buttons were not functioning properly and I needed the settings button more than home while in programs.

Fully Functioning Capacitive Button Workaround
I actually found a specific need for the home key.
When in Terminal Emulator, if I want to back out to the main screen and access another application, I have to use my back button. Trouble is, the back button also closes out the terminal session, which is a pain in the *ss if I want to just look up something in my browser and then go back to it. I have to then restart my session and retype on the small as hell keyboard. So I was thinking, how am I going to implement a home key function in my drop-down start menu which is always accessible and low-and-behold, here it is:
SoftKeys for Root Users
https://market.android.com/details?...EsIm5ldC5ob29wYWpvby5hbmRyb2lkLlNvZnRLZXlzIl0.
This is a great app. Solves the problem. Starts immediately on boot.
There's also this for just a home key in the start menu drop-down, no start on boot though:
BK Softhome
https://market.android.com/search?q=bk+softhome&c=apps
Problems solved! I now have disabled all 4 capacitive buttons while using Softkeys for Root Users for all functions. (Delete: key 102, key 139, key 158, and key 217 in all three folders listed in original post)

[HOW-TO] Remap capacitive (if you have(or any other)) buttons on any Android device

My original article on this was made for a Galaxy S3/S4/S5/S6/S7 devices because I didn't know that root directory organisation is almost the same.
This tutorial/how-to will guide you trough the process of remapping you capacitive buttons (or any other, I assure you'll figure it out!).
This however does not work on some chinese phones as I was told. Be careful when doing this, you can cause critical or even permanent damage to your device even if you do a smidge wrong.
HOW TO REMAP CAPACITIVE BUTTONS ON ANY ANDROID PHONE
If you're left handed like me, then you might wanna remap your capacitive buttons if you use the back key more often than the multitask button.
You can remap many other buttons such as volume keys and the power button, just use some logic and you'll figure it out.
As we progress on, you'll realize that there are many more things you can remap other than the physical buttons.
!!!DISCLAIMER!!!
I'm not responsible if this doesn't work for you!
I'm not responsible if your capacitive buttons don't work!
!!!DISCLAIMER!!!
1. You'll need root access for this, otherwise it won't let you edit the file
2. Go to Play Store and download any file manager app that supports root access (Best: ES File Explorer, Total Commander, Root Browser)
3. Open the file manager, and go to the root directory
4. Grant it root permissions if it doesn't ask in the begining
5. Go to the system folder, then to the usr folder and then to the keylayout folder
6. Long press on the Generic.kl file and click on Open as, then on Text and then select your prefered text editor
7. Now click on the search option if you have (otherwise you're gonna have a bad time searching)
8. Search for the word BACK, but search for the whole words
9. Change it to APP_SWITCH (make sure it's capitalized!)
10. Search again for the word MENU and change it to BACK (there may be two MENU words in the file so search twice)
11. Search for the word APP_SWITCH and change it to BACK
12. Save the fie
13. Exit and close the file manager
14. Reboot your device and enjoy!​

Nifty little guide! I'd been itching to figure out how to change the hard-mapped ExpressKeys on my Wacom Cintiq Companion Hybrid for a while now!
The only catch is that with this thing, you have to change those mappings in a file called "gpio-keys.kl" instead of "Generic.kl", which only seems to cover USB/Bluetooth keyboard and game controller mappings. At least it's a neat reference for potential key bindings, though by no means a full list.
In other words, if you can't find what you're looking for in Generic.kl, check gpio-keys.kl or even the other .kl files in that directory. You might just find your physical button mappings there.

NamelessFragger said:
Nifty little guide! I'd been itching to figure out how to change the hard-mapped ExpressKeys on my Wacom Cintiq Companion Hybrid for a while now!
The only catch is that with this thing, you have to change those mappings in a file called "gpio-keys.kl" instead of "Generic.kl", which only seems to cover USB/Bluetooth keyboard and game controller mappings. At least it's a neat reference for potential key bindings, though by no means a full list.
In other words, if you can't find what you're looking for in Generic.kl, check gpio-keys.kl or even the other .kl files in that directory. You might just find your physical button mappings there.
Click to expand...
Click to collapse
Thanks for letting me know, the same thing happened to my brother, he owns a sony xperia s or sl i can't remember

i want to add long press menu button for menu and single tap for recent apps. Help
i.e. menu key >long press > menu
---------- Post added at 04:07 PM ---------- Previous post was at 03:53 PM ----------

Hello!
I bought a EP online, but the power button its damaged,it press it self. I managed to root the device and deactivate the press power option by putting a # before the number of the key.
That worked now the phone is not pressing the key multiple times(it does but the action its null)
The problem its that the continuos Hold of the power key its making the phone to be rebooted, even after the power key its "DEACTIVATED" Is there any name for the action of reset that i can deactivate by doing the # thing?
please help!! this is driven me crazy..