MobileMute is a little program that allows you to mute/unmute phone calls via a hardware button. It will also launch any other program of choice if a call is not in progress (that way your hardware button doesn't get wasted). I had searched for this functionality for while without much luck. So, I decided to write a quick little app to do it for me.
For those of you who had used the first version of this, you may have noticed the slight delay when running the program. This was because it was designed to start, do its thing, and then exit. That being said, it took a second for the program to initialize on startup which resulted in a delay.
I have changed this version to try to figure out what button you have it mapped to. If it can figure that out, it will stay active listening for future pushes to that button. If it can't figure out what button is mapped, it will act just like the first version (which is still functional, just with a slight delay).
I have also added a simple configuration utility for changing the settings (located in Program Files/itsallwright/MobileMute).
I originally developed this for my Kaiser, therefore it was originally posted in the Kaiser section. But, since it can work on other devices, I am posting the new version here. The only problem is that different devices have different button IDs. I will post some instructions for getting your button IDs on the devices that the default Kaiser button IDs don't work for.
I didn't test this version for as long as I tested the original. So if you have any weird problems with it, please let me know.
Original version is posted here http://forum.xda-developers.com/showthread.php?t=386810
Edit: Added MobileMute_v2.1 which adds support for more devices and Kaisers with non-standard ROMS.
Enjoy,
Jay
Button IDs
Here are some instructions to help find the button IDs.
If you do not have Visual Studio or another spy program, I saw a post here http://forum.xda-developers.com/showthread.php?t=251955 that might be able to help.
1) Open Spy Program and connect to device
2) Expand "Desktop Window"
3) Expand all child windows titled "Phone" (or whatever your "Phone" title is)
4) Locate the "Phone" window that has a child named "Mute" (or whatever your "Mute" text may be). If you can't find the correct Phone window, it is possible that is hasn't been started since the last reboot. To start it, make a quick call until you get the call status and hang up. Now you should be able to locate the window.
5) The next steps should be made while you are on a call, so make a call to Voicemail, yourself, or a patient friend . After the call is connected, make sure you are on the "Call Status" screen (the one that has the mute button on the screen).
6) Highlight the "Phone" window found previously and click the Messages button to view messages for that window. You will probably see messages continually being posted to the window.
7) Click "Menu" at the bottom and then click "Mute" (Note: do not click the "Mute" button on the screen as that will not give us the information we need.)
8) Click "Menu" at the bottom and then click "Unmute" (Same note as above applies)
9) Disconnect the call. The message window should stop getting messages.
10) In the message window, find all messages titled "WM_COMMAND" (there should only be 2)
11) The WPARAM value of the first WM_COMMAND message is the "Mute" button ID (Put it into a calculator to convert it to a decimal number)
12) The WPARAM value of the second WM_COMMAND message is the "Unmute" button ID
If you do find your IDs and confirm they work, please post them here with your device and ROM info to save others with that device the trouble.
Thanks,
Jay
just use volume up/down to mute incoming calls...
zuNN said:
just use volume up/down to mute incoming calls...
Click to expand...
Click to collapse
If I'm not mistaken the purpose of this app is not to mute the ringer during an incoming call but to mute the mic during an active call. Also when not in a call it will launch your app of choice so when not in a call you're not occupying an otherwise usable button.
jhw549 said:
If I'm not mistaken the purpose of this app is not to mute the ringer during an incoming call but to mute the mic during an active call. Also when not in a call it will launch your app of choice so when not in a call you're not occupying an otherwise usable button.
Click to expand...
Click to collapse
That is exactly what it is for. It is very usefull if you have to attend a lot of conference calls where you are not required to participate 100% of the time.
Jay
zuNN said:
just use volume up/down to mute incoming calls...
Click to expand...
Click to collapse
This won´t work with my Kaiser with M-Diamond 1.4 ROM.
MobileMute_v2 with HTC Fuze
I have tried version MobileMute_v2 with the HTC Fuze and it does not appear to work. It will launch the program defined in the settings when not on a call, but will not mute the call, when launched while on a call.
I am launching this from the PTT button through the methods described in another thread. I created a shortcut short_ptt.lnk, which launches this application.
I have also navigated directly to the executable and run it while on a call and get identical results.
I am going to uninstall version 2 and try installing version 1.
HTC Fuze and MobileMute
I have now tested the original with the HTC Fuze with similar unsuccessful results.
sounds like a great app ill give it a go on my hermes tonight. thanks for sharing!
JVH3 said:
I have tried version MobileMute_v2 with the HTC Fuze and it does not appear to work. It will launch the program defined in the settings when not on a call, but will not mute the call, when launched while on a call.
I am launching this from the PTT button through the methods described in another thread. I created a shortcut short_ptt.lnk, which launches this application.
I have also navigated directly to the executable and run it while on a call and get identical results.
I am going to uninstall version 2 and try installing version 1.
Click to expand...
Click to collapse
This is most likely because the Fuze button ID for Mute/Unmute is different then the Kaiser.
Have you tried using the steps above to get your button IDs?
-Jay
Mobile Mute and Fuze
I had also tried running the executable directly, not through the remap of the PTT key.
I did that to elliminate the possibility of it being a mapping to a key issue.
This does assume it works when run directly and not from a key.
I suppose it is possible that an exeception is thrown when the program checks what key was pressed to launch it, if there was not key pressed to start it.
As is, with the Fuze, the touch screen has on screen buttons for Mute and Speaker Phone.
I have remapped the long_ptt to Voice Command and the short_ptt to {"\Windows\ctlpnl.exe" cplmain 1} which gives you the lock screen so I can quickly change the timeout. I like it to lock quickly when not running GPS, but not lock at all when running GPS, but this last paragraph is not related to Mobile Mute, other than I no lnger have an available button to map it to.
JVH3 said:
I had also tried running the executable directly, not through the remap of the PTT key.
I did that to elliminate the possibility of it being a mapping to a key issue.
This does assume it works when run directly and not from a key.
I suppose it is possible that an exeception is thrown when the program checks what key was pressed to launch it, if there was not key pressed to start it.
As is, with the Fuze, the touch screen has on screen buttons for Mute and Speaker Phone.
I have remapped the long_ptt to Voice Command and the short_ptt to {"\Windows\ctlpnl.exe" cplmain 1} which gives you the lock screen so I can quickly change the timeout. I like it to lock quickly when not running GPS, but not lock at all when running GPS, but this last paragraph is not related to Mobile Mute, other than I no lnger have an available button to map it to.
Click to expand...
Click to collapse
Check in "/Program Files/itsallwright/MobileMute" for an ErrorLog file. If that file exists and has info, post the contents and I will see if I can figure out what went wrong.
Since it does launch the program you have configured when not in a call, the program at least initializes. If it also launches the program when you are in a call then it can't find the "Phone" window or the "ConnectedText" value. If it appears to do nothing while you are in a call, then it is likely that the Button IDs are wrong.
-Jay
Fuze
A friend of mine with a Fuze let me check it out and I determined why it does not work.
The dialer on the Fuze has Mute/Unmute buttons on the screen, but the buttons do not have text (I suspect it uses seperate Mute/Unmute images instead). That being said, MobileMute determines the Mute State of a call based on the text value of the Mute/Unmute buttons. Therefore, it does not know what command to send.
I am trying to figure out a way to work around this, but in the meantime, I am sorry to say the Fuze is unsupported.
Just as a fyi... the Mute/Unmute button IDs for the Fuze are the same as the Kaiser (21408/21409)
I'll keep you posted on my progress with supporting this device.
-Jay
Trying to use this app on my Mogul/Titan without success. I set it up on the button that would normally be conn mgr, went into cfg and set it to \windows\connmgr.exe
When I go to use the button I get a wait icon, the program launches and hides (still visible in Task Mgr). Opening manually works equally well (not at all).
The tools in the 2nd post don't work ("Class not registered" error).
While in a call the application launches (with a massive delay I might add) then performs its functino properly and mutes the call, no delays after initial launch.
There is no error log in the program's folder.
Help?
jhw549 said:
Trying to use this app on my Mogul/Titan without success. I set it up on the button that would normally be conn mgr, went into cfg and set it to \windows\connmgr.exe
When I go to use the button I get a wait icon, the program launches and hides (still visible in Task Mgr). Opening manually works equally well (not at all).
The tools in the 2nd post don't work ("Class not registered" error).
While in a call the application launches (with a massive delay I might add) then performs its functino properly and mutes the call, no delays after initial launch.
There is no error log in the program's folder.
Help?
Click to expand...
Click to collapse
The initial start of MobileMute does have a delay. That is the reason I created v2 that will stay running. If MobileMute shows in task manager after you run it, then it found the hardware button you have it assigned to and is listening for future presses of that button. Since it does Mute/Unmute the calls, the program is functioning as designed.
As for running "\windows\connmgr.exe". I also cannot run that program (even manually). I don't think it is an app to be used that way. Are you sure you don't actually want to run "\windows\CommManager.exe"?
-Jay
Heh.... umm... oops >.<
That's rather embarassing lol... You're completely right, I picked the wrong exe. It works 100% perfectly now.
I just wish it would hide completely and not show up in my tasks list... I have a tendancy to hit that kill all button rather than pick them out one by one.
thanks. this is a good idea... i'll be using it.
v2.1 with Fuze support
itsallwright said:
A friend of mine with a Fuze let me check it out and I determined why it does not work.
The dialer on the Fuze has Mute/Unmute buttons on the screen, but the buttons do not have text (I suspect it uses seperate Mute/Unmute images instead). That being said, MobileMute determines the Mute State of a call based on the text value of the Mute/Unmute buttons. Therefore, it does not know what command to send.
I am trying to figure out a way to work around this, but in the meantime, I am sorry to say the Fuze is unsupported.
Just as a fyi... the Mute/Unmute button IDs for the Fuze are the same as the Kaiser (21408/21409)
I'll keep you posted on my progress with supporting this device.
-Jay
Click to expand...
Click to collapse
Well, it turns out that the Fuze isn't the only device with that dialer. I recently found a ROM (Phoenix v2) that has touch flo and a similar dialer to the Fuze. I put that ROM on my Kaiser to reproduce this issue on my own.
After quite a bit of research and learning, I found a way to detect the Mute state of a call via TAPI. The Mute/Unmute button text is no longer needed.
I have no way to test with an actual Fuze, but I am pretty confident it will work now. I have added the new version to the original post.
-Jay
I've got v2.1 loaded. Detection on Fuze works, the registry shows mute/unmute id's 21408/21409. I'm using the short_PTT.lnk method. When I press PTT, I can see the titlebar flash 'MoblieMute' text.... but the mic does not mute.
jpn621 said:
I've got v2.1 loaded. Detection on Fuze works, the registry shows mute/unmute id's 21408/21409. I'm using the short_PTT.lnk method. When I press PTT, I can see the titlebar flash 'MoblieMute' text.... but the mic does not mute.
Click to expand...
Click to collapse
When you are not in a call, does it open the configured program (BubbleBreaker by default). Also, if you look in task manager, is MobileMute listed?
-Jay
Related
I wrote a small piece of code to switch between vibrate and sound on. I've created the cab installer. Just follow the instruction below to install it.
1. Just install the cab.
2. Map Button 5 (Press & Hold) to 'Vibra (Switch)'.
Whala... you just got a vibrate switch just like an HTC Wizard!
To start the program in delayed mode you need to apply the /d switch. However, I've created a shortcut for the delayed mode as Vibra (Switch) Delayed. Because of this, you're forced to install the program in the main memory as I don't know how to create a shortcut with parameters in the Cab installer. Anybody care to teach me how?
UPDATES
v1.32 : added switch '/d' to delay 1.0 second start up
v1.31 : Fix bug where flight mode toggle was toggled even when button has been release on silent mode. Also optimized button handling to detect button release during buzzing and in between.
v1.3 : Hold the button even longer (approx another 2 second), will toggle flight mode (while retaining current normal/vibrate/silent settings).
v1.2 : Hold the button longer (approx 1 second), will set the phone to silent mode. (This only works with App button 1-6)
v1.1 : Now run with '/q' parameter to switch mode without vibrating the phone.
EDIT:
There's no more update or any changes will be made to this program as I've lost the source code.
Works great!
Thank you!
Thanks, it works perfect here too. I added it to the wiki FAQs.
vmirage said:
I wrote a small piece of code to switch between vibrate and sound on. I've created the cab installer. Just follow the instruction below to install it.
1. Just install the cab.
2. Map Button 5 (Press & Hold) to 'Vibra (Switch)'.
Alternatively you can use AEButton Plus and map your wheel button (#0086) long press to the shortcut you just made. To map this you probably need to focus on say Shift Key first by clicking on it once. Else your wheel button will press the cancel button when trying to map the key.
one problem though, if you map to #0086, the button still clicks when you hold the button down.
So, you might want to map it to stick to the Button 5 instead.
Whala... you just got a vibrate switch just like an HTC Wizard!
I made the vibrate to sound on a 200 ms vibrate though. Slightly different from HTC Wizard.
Click to expand...
Click to collapse
Great Woooork!
Now i also hacked "Profiles Swtich Application" from IDO and Eten,
If you interested in them,,,you can try.
I tested on my Himalaya WM5 and Vario II and work well.
<Auto answer function of IDO Profiles was missing> :lol:
How about thoes???
Interesting (and good!) work guys, will try both sometime in the very near future
Can anyone do this?
don't you think it would be awesome if there was a way you could push a button on the today screen that scrolled through these four settings,
Silent
Silent & Vibrate
Ring
Ring & Vibrate
And it showwed you on the today screen what setting your on. I don't mean just the ringtone though, I mean all notifications. So when your out you can have it on vibrate cos its in your pocket but when ur at home it don't wobble across the table and disturb everyone without u having to change the settings for each individual alert.
I've tried the ScenariosE program and the Profiles program and they are both half way there. I notice on both of em there is a show icon option? But where does it show the Icon as to what profile u are on. and why does it only change ur ringing tone, not your messages and notifications?
I feel that if we could get this perfect we could really be onto something. I know a fair few people with WM devices that could really benefit from it.
Is there anything that does this or does anyone know enough about the hardware to make something that does this?
EDIT
just noticed whereas profiles doesn't seem to work at all on my Vario II, have found that ScenriosE does only affect the vibrate settings for the atual ringtones and if you adjust volumes using ScenariosE it only affects the notifications volume. The slider for the ringtones does nothing??? Very strange
ipaq hwl69xx and 65xx has today plugin and what u want.
i am on the way to hack!
Just installed the vibra switch cab and assigned to button 3 (the comms. manager, at least on the Vario 2) - works beautifully. Love the much shorter vibrate when it goes off vibra to signify it's back on ringtones again... Nice touch.
The Comms Manager button seemed like the natural choice to me, as it has a little icon of a circle with waves coming out of it, so it fit the bill quite nicely. Anyways, my Comm. Manager is bound to my right softkey, so the button was redundant anyway
Asukal
This is great !
i installed the Scenarios_WWE.cab on my i-mate JasJam and its work good
but i canot see the small icon on the comand bar even after SR
why ?
ori
ASUKAL
"ipaq hwl69xx and 65xx has today plugin and what u want.
i am on the way to hack!"
cheers asukal u are a star. It even switches vibrate on and off for notificaions?
Keep me posted please bud
FaNtAsTiC Mr Q!
@Scenarios>>
I fixed small Icon on the Task Tray.
See capture and reinstall new fiexed CAB.
@hw69xx>>
Sorry it seems not havaing Notifications,
Now i got hack it almost,,,including Tday Plugin.
But iPAQUti.dll which need to read device APIs are not mathc to
the Hermes.
Also tried HTCUTli.dll renamed to iPaqUtil.dll but not worked.
we must modify iPAQUtil.dll to match the Hermes, But no way now.
So i must give up....
Asukal said:
@Scenarios>>
I fixed small Icon on the Task Tray.
See capture and reinstall new fiexed CAB.
@hw69xx>>
Sorry it seems not havaing Notifications,
Now i got hack it almost,,,including Tday Plugin.
But iPAQUti.dll which need to read device APIs are not mathc to
the Hermes.
Also tried HTCUTli.dll renamed to iPaqUtil.dll but not worked.
we must modify iPAQUtil.dll to match the Hermes, But no way now.
So i must give up....
Click to expand...
Click to collapse
Is there no way we can get round this? I'm dying to be able to turn off and on the vibrate function on my alerts? There must be someone out there that has seen something about this?
Or how about just a file that switches off power to the vibrator? Something that simple would be awesome, the phone doesn't know not to vibrate, it still trys but theres no power to the vibrator, n u can switch it on and off. Far short of modding the hardware and adding an extra switch somewhere (seems a bit ott) is there a way we can do it!
Asukal said:
@Scenarios>>
I fixed small Icon on the Task Tray.
See capture and reinstall new fiexed CAB.
Click to expand...
Click to collapse
Asukal
thank you !
i can see the icon now on the comand ber
its work perfect !
8)
ori
@Scenarios>>
i have found another functions in the Scenarios,
New SMS and Miss Call Icons will be come,
And can tap to read SMS on today screen / Go to Call histry,
But above CABs are not fixed those functions and error will shown.
,.so i suggest you guys not use them.
the cabs in 1st upload is better even there was not Icon on Today.
@How about SmartFIlter? can it swtich the vibe for Notification?
pls check <but not free>
Is there a way of just stopping the vibrate motor?>?>
Can I set the phone to both ringer and vibration. I work in a factory enviroment and sometimes it's hard to hear the signal. Sorry if this has been answered before.
yeah just click vibrate and ring in the tone settings
vmirage said:
I wrote a small piece of code to switch between vibrate and sound on. I've created the cab installer. Just follow the instruction below to install it.
1. Just install the cab.
2. Map Button 5 (Press & Hold) to 'Vibra (Switch)'.
Alternatively you can use AEButton Plus and map your wheel button (#0086) long press to the shortcut you just made. To map this you probably need to focus on say Shift Key first by clicking on it once. Else your wheel button will press the cancel button when trying to map the key.
one problem though, if you map to #0086, the button still clicks when you hold the button down.
So, you might want to map it to stick to the Button 5 instead.
Whala... you just got a vibrate switch just like an HTC Wizard!
I made the vibrate to sound on a 200 ms vibrate though. Slightly different from HTC Wizard.
Click to expand...
Click to collapse
-------------------------------------------------------
Good program!
It is possible to obtain the icon of the program of red or black color?
The color gray is little visible.
Thanks
I am running the iMate JasJam 1.31 ROM (which came with the Australian Telstra branded device)
The most common problems so far:
-Sound stops working, will only vibrate. This happen if you switch to silent mode, when you get back to normal sound mode, it stays in silence mode until you reboot. this doesn't always happen. can't reproduce it consistently
-BT turns off by itself once in a while, you have to turn BT on in comm manager
-The most annoying: If you have a data session active (not transfering any data) and a BT connection active (like headset, GPS), then you can't receive a call. The person calling you won't even get to voicemail. it just hangs up on them. if you disconnect the data session or turn off BT then you can receive calls again
-Switching username in MSN will often make messenger crash, you have to kill the process and start it again
-Sometimes will hang for no reason: you need to press the reset button
Then you have the GUI weirdness which make you think: what did they drink the day they designed this software?
Like if you receive a SMS, it will show you an extract of it at the bottom of the screen, you'll get off the following choice:
-Reply on the left soft menu
-More on the right soft menu with the option (delete, call sender, Save as Read, dismiss)
What if I just want to read the full content in the Messaging application? you can't.
If you select Mark as Read immediately it doesn't mark the SMS as read in the messaging application and you still get the notification in the top screen. You have to do "Mark as Read" twice.
Something I miss from my symbian phone, if you have a bluetooth headset paired with a unit (or your car kit) when you answer a call using the BT headset button, the call goes to the BT headset, but if you answer using the device itself, it doesn't go on the BT. This is great if you want to take a personal call in a car for example, and don't want your passenger to hear what's going on.
On WM5, you can't control that. it aways goes to BT if the headset/handsfree is set.
When the keyboard is open, if you tap on a text field, the screen keyboard will show up (and text half of the screen). Why show a software keyboard all the time when you have a full qwerty keyboard available !? Sometimes the keyboard doesn't show up, but I'm yet to understand the logic behind it. it's not consistent
And then of course you have some inconsistencies here and there, like the device will stop working as it did 2 minutes prior. You try it again: bank it works.
I wonder if Microsoft or HTC have any QA !
What other issues have you guys noticed? Or could this be that those problems are unique to thie version of the ROM...
Jean-Yves
I agree, there are quite a lot of interface issues, although I think most of these lie with wm5 as opposed to the unit itself.
here are some of my thoughts:
1) the sms bubble relly annoys me too. why can't I tap the bubble to open the message in full?! often the message is too long to fit in the notification. i'm pretty sure this is a wm5 design fault.
2) the software keyboard bugged me senseless until I realised that if you just keep typing on the 'proper' keyboard it disappears. I used to continually spend the time closing it!
3) the alarms in wm5 are pretty lame. if your phone is on silent they won't sound. you only get a warning if you set an alarm whilst the phone is in vibrate mode. the alarm should simply override the sound settings.
4) contacts - I think searching for contacts is poorly handled which makes one handed operation pretty difficult. it takes too many clicks to select a category to filter by and the display when someone is calling you is a farse! you get a tiny notification with tiny writing! I bought photo contacts pro to help with this and whilt it has its flaws I reckon it is worth it.
having said this, i'm loving my tytn. it is way better than my previous smartphone (nokia 6680). the symbian s60 based phones seem to just be half-assed to me.
cheers
Just to comment on the SMS notification.
I am on MDA Vario II from T-Mobile, and when I get an SMS my left button says read! so If I choose that he whole message is displayed. So I guess it is not the OS but the Operator or manufacturer who screwed up on this one.
I add that in some case the tytn wirless modem function dont work.
So you can use the tytn like modem.
festermania said:
I add that in some case the tytn wirless modem function dont work.
So you can use the tytn like modem.
Click to expand...
Click to collapse
Exactly. Some units work as modem and others not (mine not)
Mine works, but since Vista RC2, I couldn't get the OS to install the drivers.
It worked well in Beta2 and RC1
Ken
danielherrero said:
Exactly. Some units work as modem and others not (mine not)
Click to expand...
Click to collapse
Churchill said:
Just to comment on the SMS notification.
I am on MDA Vario II from T-Mobile, and when I get an SMS my left button says read! so If I choose that he whole message is displayed. So I guess it is not the OS but the Operator or manufacturer who screwed up on this one.
Click to expand...
Click to collapse
well that's quite bugging! i'm also on t-mobile vario ii and mine appears with reply in the bottom left!!
Ha! my OS is in Dutch, so I am not sure it is comparable.
Mine aslso works as a modem just Fine.
I als want to post a small tip. The Envelope (messaging) hardware button on the MDA VARIO II (maybe the same on Vario as well) If you keep on pressing it it sycleds the Outlook Mail, Text messages, Hotmail, MMS accounts. Really nice since you do onot need to hit the menu button...
Cycling Mail
Churchill said:
Mine aslso works as a modem just Fine.
I als want to post a small tip. The Envelope (messaging) hardware button on the MDA VARIO II (maybe the same on Vario as well) If you keep on pressing it it sycleds the Outlook Mail, Text messages, Hotmail, MMS accounts. Really nice since you do onot need to hit the menu button...
Click to expand...
Click to collapse
Churchill
Thanks for the tip, never spotted that before works on HTC TyTn.
Mike
mikechannon said:
Churchill
Thanks for the tip, never spotted that before works on HTC TyTn.
Mike
Click to expand...
Click to collapse
Pressing left/Right on the d-pad does this too.
Cheers
yannyb said:
Pressing left/Right on the d-pad does this too.
Click to expand...
Click to collapse
Yannyb
Thanks for that one too. Perhaps we need a thread for non-obvious key combinations or single presses. Perhaps what seems to be statin' the bleedin' obvious to some folks are just things that others have never thought of or tried. Often I discover things through pure chance. Another useful one I used to need a lot was the D-Pad and messaging key combo to go straight to screen alignment.
Mike
What about a new wiki page for all key combinations of the Hermes?
yannyb said:
well that's quite bugging! i'm also on t-mobile vario ii and mine appears with reply in the bottom left!!
Click to expand...
Click to collapse
Im on T-Mobile too, and for me it depends on the length of the message ive received. If its a message that doesnt entirely fit in the "preview" popup box at the bottom it will give me a "View" option which will open the full message up in Messaging, otherwise it gives a "Reply" option as i have read the whole message anyway...
More to the list
While waiting to get my new phone (used to have PDA2k, and Jamin that I just sold after using for 3 months due to my disatisfactionof performance, sound quality, etc...) I had some chances to play the JasJam (Arabic ROM). First I noted that the call button is very badley placed at the verry bottom of the front as I felt the phone will fall out of my hand (unlike the HTC where the green botton is separatly on the very left side, as I see it in photos).
Second, if pull the out memory card for any reason and push it bacj in, the phone never recognizes the card again unless you soft rest it.
I hope that this issue will be resloved in the next ROM update by imate
Here it is:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Buttons
thanks didn't know about the cycle mail one
darky said:
thanks didn't know about the cycle mail one
Click to expand...
Click to collapse
Yes, I too only discover the mail button could make you cycle between accounts. And this is not in the manual...
Another thing bugging me (I will pass on all the bugs and how to lock the device: there're just too many ways)...
There are 3 OK buttons, all doing the exact same thing. And the scroll wheel just just the same thing as the direction keypad.
If you want to read an email this is extremely annoying as you can't easily read it without tapping the screen to jump to the next screen page ; as up/down or the wheel will jump from embedded number to number.
It would be great if you could differentiate the wheel from the up/down, and if the OK buttons could be assigned another function. Right now there are a few buttons you can't assign.
Ok, this should be a rule to post here: list/describe one bug ...
With activesync program running, try changing the name of the PDA. Will make the device unresponsive for a few minutes.
My experience thus far..
Been using my T-mobile Vario 2 (ROM 1.21.110.3) for a couple of weeks now and have had a couple of problems:
1) The buttons don't work all the time. I've noted this when trying to pick up a call or dismiss a notification of something. I had thought I might have left the device locked but this isn't the case. It's a bit annoying that this only happens sometimes though.
2) About 50% of the time when I call comeone they can't hear me although I can hear them fine.
That's all I've discovered so far, but it's handy to note the comments about the pressing of the envelope button.
Given the problems I've experienced so far are generally located in the lower part of the phone, I'm beginning to suspect the phone has some sort of hardware fault so I've called the shop up and am going to swap it for a new one. Has anyone else experienced these issues?
richieboy said:
Im on T-Mobile too, and for me it depends on the length of the message ive received. If its a message that doesnt entirely fit in the "preview" popup box at the bottom it will give me a "View" option which will open the full message up in Messaging, otherwise it gives a "Reply" option as i have read the whole message anyway...
Click to expand...
Click to collapse
You are absolutely right there. Noticed it today. long message you get a view and if it fits the popup then you get a reply. This is actually quite clever.
I have a Kaiser, and there's nothing more irritating than accidentally bumping a button while having the phone in your pocket, then having random things in your pocket scroll through your address book until it calls someone. Or opens up IE and finds a high-bandwidth website. When you don't have a data plan.
Things like this hurt. I've been trying to find a solution to it, and I happened to stumble upon an olllllld application on another forum. It's called AutoLock. I found it Here.
Anyways, long story short, it uses the built-in Windows Mobile screen lock and turns it on whenever the phone's screen turns on. So hitting the power button is enough to lock your phone. It's super convenient, and for the most part, it's not too buggy.
I've been using this for probably over a month now. It's a lifesaver. I had the .exe on my SD card, and every time I reflashed, I had to make a new shortcut and place it into the startup folder. So tonight, I made a CAB file out of it.
I hope you guys get as much use out of it as I do.
A quick note: It runs in the background. Terminating it will not allow it to function. The CAB will add a shortcut to the startup folder, so a soft reset will start it. Otherwise you can start it from the shortcut in the Programs folder.
Frequently Asked Questions:
Q: Is there a way to disable the program window that pops up after a soft-reset?
A: There is no way to disable the message screen on startup. Just hit the X in the top right corner, and it should minimize out of sight.
Q: When receiving a call, does the answer button and screen stay locked?
A: The answer button and the screen both unlock when the phone is ringing. If the call is answered/ignored/stops ringing, the screen will be re-locked.
Q: Will it work with my phone?
A: This program has been confirmed to work on a few models. I believe that it should work on pretty much any touchscreen device running Windows Mobile. Please, try it and tell me if it works!
Tested Phones:
Kaiser (ATT Tilt)
Touch Pro (Fuze)
Xperia
racer7 said:
I have a Kaiser, and there's nothing more irritating than accidentally bumping a button while having the phone in your pocket, then having random things in your pocket scroll through your address book until it calls someone. Or opens up IE and finds a high-bandwidth website. When you don't have a data plan.
Things like this hurt. I've been trying to find a solution to it, and I happened to stumble upon an olllllld application on another forum. It's called AutoLock. I found it Here.
Anyways, long story short, it uses the built-in Windows Mobile screen lock and turns it on whenever the phone's screen turns on. So hitting the power button is enough to lock your phone. It's super convenient, and for the most part, it's not too buggy.
I've been using this for probably over a month now. It's a lifesaver. I had the .exe on my SD card, and every time I reflashed, I had to make a new shortcut and place it into the startup folder. So tonight, I made a CAB file out of it.
I hope you guys get as much use out of it as I do.
A quick note: It runs in the background. Terminating it will not allow it to function. The CAB will add a shortcut to the startup folder, so a soft reset will start it. Otherwise you can start it from the shortcut in the Programs folder.
Click to expand...
Click to collapse
Nice one mate!
I assume you can also use this on a Touch Diamond??
neways, I will give it a shot....
Thanks for your work
Regards
Jeroen
thanks
racer7 said:
I have a Kaiser, and there's nothing more irritating than accidentally bumping a button while having the phone in your pocket, then having random things in your pocket scroll through your address book until it calls someone. Or opens up IE and finds a high-bandwidth website. When you don't have a data plan.
Things like this hurt. I've been trying to find a solution to it, and I happened to stumble upon an olllllld application on another forum. It's called AutoLock. I found it Here.
Anyways, long story short, it uses the built-in Windows Mobile screen lock and turns it on whenever the phone's screen turns on. So hitting the power button is enough to lock your phone. It's super convenient, and for the most part, it's not too buggy.
I've been using this for probably over a month now. It's a lifesaver. I had the .exe on my SD card, and every time I reflashed, I had to make a new shortcut and place it into the startup folder. So tonight, I made a CAB file out of it.
I hope you guys get as much use out of it as I do.
A quick note: It runs in the background. Terminating it will not allow it to function. The CAB will add a shortcut to the startup folder, so a soft reset will start it. Otherwise you can start it from the shortcut in the Programs folder.
Click to expand...
Click to collapse
this is a very usefull program.is there anyway to disable message screen when program start after softreset?thanks a lot in advance
It's unfortunate that I didn't create this program. I only found it through about six months of searching on the internet. Maybe a friendly XDA-Developer could write a similar program and keep it updated with new features!
As far as I know, there's no way to disable the message screen on startup. Just hit the X in the top right corner, and it should minimize out of sight.
As for if it works on a Diamond... go try it and tell me how it works!
Awesome program! Thanks
Looks interesting. Thx for sharing!
racer7 said:
It's unfortunate that I didn't create this program. I only found it through about six months of searching on the internet. Maybe a friendly XDA-Developer could write a similar program and keep it updated with new features!
As far as I know, there's no way to disable the message screen on startup. Just hit the X in the top right corner, and it should minimize out of sight.
As for if it works on a Diamond... go try it and tell me how it works!
Click to expand...
Click to collapse
yep i am just hitting x .it works in my xperia without problem.thanks again.
So what happens when a call comes? Does it lock the answer button too? And the screen?
kull said:
So what happens when a call comes? Does it lock the answer button too? And the screen?
Click to expand...
Click to collapse
Since it's the inbuilt Windows Mobile locking setup, when a call comes in, the phone is still locked, but the answer skin floats above the lock. So the screen "unlocks" so you can answer or reject the call, but it locks as soon as you answer or ignore it again.
I've discovered, using my Jade, that you can do the same thing by just setting the built-in Windows Mobile device lock to 0 minutes... You'd need to provide a password, though...
First press of the power button puts the phone to sleep... Press it again, it will ask for your password to unlock...
I didn't find anywhere in this forum, but if someone has found it before I apologize.
I normally assign longpress-call button to camera, just because I prefer to take photos with my hd2 on every occasion. Today I recognized that, after opening camera application by longpressing the call button, you can make a shot when you "longpress" call button again.
Normally touching the screen is ok for me, but it can help when taking self-pictures. It is not so easy to find exact touch point when the screen is on the opposite side.
One can prefer other applications but this is easier for me.
wow, i'll have to try it because that sounds very useful and i have never seen this tip on this forum, and i read about 10 newest/updated threads here every night! closest thing so far was scilor's leo camera keys app (see point 2 below).
i am currently using android 24/7 so not sure WHEN i'll be able to try this tip, but i'm sure other readers will report back their findings.
i would like to add a few more notes on your finding just to add more information to the thread:
1. by default, long press send is mapped to speaker-phone mode. so you can long press send when the phone rings to answer the call directly in speaker-phone mode. you can also long press send during an active phone call to switch back and forth between speaker-phone. so speaker phone toggle functionality cannot work if long press send is mapped to camera.
2. scilor's leo camera keys application is also worth checking out because it allows mapping the snap picture action to the volume up/down keys.
so point 2 is the only alternative for those users that want to keep long press send as the speaker phone toggle, while the OP's suggestion does not need any apps to be installed, but will kill the speaker phone toggle shortcut.
yes, great find..good job
I am currently using Autoloudspeaker 1.5 from Zevele. It is very usefull while driving etc.
I tried scilor's app before but It caused some problems (because other applications or my rom which I have used at that time.)
ASCIIker said:
wow, i'll have to try it because that sounds very useful and i have never seen this tip on this forum, and i read about 10 newest/updated threads here every night! closest thing so far was scilor's leo camera keys app (see point 2 below).
i am currently using android 24/7 so not sure WHEN i'll be able to try this tip, but i'm sure other readers will report back their findings.
i would like to add a few more notes on your finding just to add more information to the thread:
1. by default, long press send is mapped to speaker-phone mode. so you can long press send when the phone rings to answer the call directly in speaker-phone mode. you can also long press send during an active phone call to switch back and forth between speaker-phone. so speaker phone toggle functionality cannot work if long press send is mapped to camera.
2. scilor's leo camera keys application is also worth checking out because it allows mapping the snap picture action to the volume up/down keys.
so point 2 is the only alternative for those users that want to keep long press send as the speaker phone toggle, while the OP's suggestion does not need any apps to be installed, but will kill the speaker phone toggle shortcut.
Click to expand...
Click to collapse
long press call does nothing for me, (cooked rom, 2.13 base)
what rom you using, and what version camera you using? ( cam tab, albums menu about)
Good One
Lovely !!!!
Simply too good
Thanks so much for this tip
samsamuel said:
long press call does nothing for me, (cooked rom, 2.13 base)
what rom you using, and what version camera you using? ( cam tab, albums menu about)
Click to expand...
Click to collapse
I am using dutty's rom v6 and albums ver 3.2 2017.1632 where camera version is 6.26 build 2012.1425.
thanks
.....
I'm not sure this is the right subforum for this, but I was coming here to ask how to do this before I figured it out for myself. So I figured I should post about it in case I forget what I did.
I just switched to a shiny new G2, and I'm using the one-button earphones that came with my Nexus S 4G. This is actually the third set of such headphones (I keep breaking and replacing them), so I refuse to have them not work on my rooted but otherwise stock G2.
When I first plugged them in to the G2, it was configured so that the button would control the phone function: one press would open my call history, a double press would redial, and a hold would start up voice dialer. On the Nexus S 4G, the buttons controlled my media player, so that's what I want them to do here.
I tried various button remapping tools like the JAYS Headset Control app, but none of them would take precedence over the default LG actions.
Instead, I modified this approach from the Nexus 4, and changed the key code for the button from the one that the voice dialer controls were intercepting (HEADSETHOOK) to something else (MEDIA_NEXT).
What I did:
1. Have root and install Busybox (for vi).
2. Get a root shell on the device.
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ #
3. Mount /system as read-write:
Code:
[email protected]:/ # mount -o rw,remount /system
4. Edit the default Android keyboard layout to swap the HEADSETHOOK and MEDIA_NEXT keys.
Code:
[email protected]:/ # vi /system/usr/keylayout/Generic.kl
Press "i" to enter insert mode. Move around with the arrow keys.
Change:
Code:
key 163 MEDIA_NEXT
to:
Code:
key 163 HEADSETHOOK
And also change:
Code:
key 226 HEADSETHOOK
to:
Code:
key 226 MEDIA_NEXT
Press Escape, and then press Shift + Z twice to save and quit.
5. Reboot your device for the changes to take effect.
6. Now the button on your single-button headset is the equivalent of the "down" or "next" button on a three-button headset. To configure it, install JAYS Headset Control or a similar application. Chose the three-button headset instead of the one-button headset, and configure the third button to do everything you want your button to do.
7. Enjoy your customizable button!
Sweet! Not having my headset button work for audio was my biggest issue with the G2.
I followed the instructions above, but instead of swapping "key 163 MEDIA_NEXT" I swapped "key 164 MEDIA_PLAY_PAUSE". This caused the default behavior to be "Play/Pause".
I tried using JAYS Headset Control and it works great. Thanks for the find!
Oh my gosh! I've been looking everywhere for this solution. Thank you so much!
My dilemma was that I want to be able to use the headset buttons because I listen to music and switch tracks frequently while walking around the university. Only the Android KitKat ROMs worked for me, but the problem with those ROMs is that GPS has locking problems and/or doesn't work at all.
Thanks for this, it was helpful for me also. Like Myzur I've also used MEDIA_PLAY_PAUSE instead of MEDIA_NEXT.
I had a quick go with the "Headset Button ControllerTrial" app for some extended functionality, but it kept switching from Rhapsody to LG's music app. This was before I saw the comment about configuring things as if it were a 3 button headset, so I'll play around with this some more (and will probably also try the JAYS app). But even as-is, just the ability to play/pause is a very nice improvement over stock behavior (honestly, who uses their phone more for making calls than listening to music.. ).
doesnt work
For some reason this doesnt work with the LG G2 Sprint version, is there any other solution?
pabel101 said:
For some reason this doesnt work with the LG G2 Sprint version, is there any other solution?
Click to expand...
Click to collapse
My phone is LG G2 on Sprint (LS980), and it actually does work for me.
Since my above post, I have actually changed the mapping again to MEDIA_NEXT, and I'm using the Headset Button Controller app (https://play.google.com/store/apps/details?id=com.kober.headsetbutton). The actions in the controller app are all set under "Right button actions" (so exactly according to step 6 in the OP..).
I think any app that will let you configure things for a 3rd/right button should work. The JAYS one is free, but as I recall it asked for a permission I wasn't comfortable with, and I ended up with Kober's app instead, which I think was $2 and to me well worth it (you can barely get a coffee for that these days..). There is a free trial.
This setup works great for music controls (play/pause, next/previous, volume control), but it doesn't seem call control (answer/hangup, mute etc.) is totally working. For me this is mostly about music controls, so I'm not too worried about the call controls and haven't looked into fixing that so far.
By the way, I found out a modified Generic.kl file is enough to cause updates to fail (for ZVC anyway), so you'll want to keep a copy of the original to restore for cases like that.
If you still can't get it to work, what exactly is happening for you, and what app are you using? Did you map MEDIA_NEXT, or MEDIA_PLAY_PAUSE? The Headset Button Controller app I'm using (free trial also) has a troubleshooting feature where it displays the button presses it sees on screen, whether it takes action on it or not, which could be useful to figure things out.
doesnt work
ChoppedLiver said:
My phone is LG G2 on Sprint (LS980), and it actually does work for me.
Since my above post, I have actually changed the mapping again to MEDIA_NEXT, and I'm using the Headset Button Controller app (https://play.google.com/store/apps/details?id=com.kober.headsetbutton). The actions in the controller app are all set under "Right button actions" (so exactly according to step 6 in the OP..).
I think any app that will let you configure things for a 3rd/right button should work. The JAYS one is free, but as I recall it asked for a permission I wasn't comfortable with, and I ended up with Kober's app instead, which I think was $2 and to me well worth it (you can barely get a coffee for that these days..). There is a free trial.
This setup works great for music controls (play/pause, next/previous, volume control), but it doesn't seem call control (answer/hangup, mute etc.) is totally working. For me this is mostly about music controls, so I'm not too worried about the call controls and haven't looked into fixing that so far.
By the way, I found out a modified Generic.kl file is enough to cause updates to fail (for ZVC anyway), so you'll want to keep a copy of the original to restore for cases like that.
If you still can't get it to work, what exactly is happening for you, and what app are you using? Did you map MEDIA_NEXT, or MEDIA_PLAY_PAUSE? The Headset Button Controller app I'm using (free trial also) has a troubleshooting feature where it displays the button presses it sees on screen, whether it takes action on it or not, which could be useful to figure things out.
Click to expand...
Click to collapse
Im sooooo confused by this but is it possible for you to screen shot your settings for Generic.kl? im sorry for the late reply
pabel101 said:
Im sooooo confused by this but is it possible for you to screen shot your settings for Generic.kl? im sorry for the late reply
Click to expand...
Click to collapse
The whole file is over 400 lines long, so a bit too long to fit in a screenshot. There are only 2 lines that you will need to touch however, and they will look like this when you are done with them:
Code:
key 163 HEADSETHOOK
key 226 MEDIA_NEXT
Note that these lines are not next to each other, but they are easy enough to find as they are pretty much ordered by key "number" as you can see.
Sorry if I made things sound confusing.. the steps in the OP are maybe more clear, and exactly what you need to do to get Generic.kl modified the way mine is. Feel free to ask if you need more help/clarification though.
playpause
ChoppedLiver said:
The whole file is over 400 lines long, so a bit too long to fit in a screenshot. There are only 2 lines that you will need to touch however, and they will look like this when you are done with them:
Code:
key 163 HEADSETHOOK
key 226 MEDIA_NEXT
Note that these lines are not next to each other, but they are easy enough to find as they are pretty much ordered by key "number" as you can see.
Sorry if I made things sound confusing.. the steps in the OP are maybe more clear, and exactly what you need to do to get Generic.kl modified the way mine is. Feel free to ask if you need more help/clarification though.
Click to expand...
Click to collapse
ok i did what you said and now my middle button Just skips to next track is that alright?
pabel101 said:
ok i did what you said and now my middle button Just skips to next track is that alright?
Click to expand...
Click to collapse
Yes, this means the re-mapping of the button worked. Now you can use one of the headset control apps to program the button as you please (remember this button is now acting as the "next" or right button, so program as such).
But, you say "middle button" - do you have a 3 button headset? If yes, I think you could have left the mapping alone, and programmed either of the left/right buttons, or both. Not really sure of the best and most functional approach in this case, I've never had anything other than a single button headset. I would think with 3 buttons, if all 3 are supported, you can have some more flexibility.
If you do have a 3 button headset, but only the middle button is supported by Android at all (apparently YMMV depending on the make/model among other things), then ignore everything I just said, keep the mapping as-is, and just program the one working button as you like - still as if it were the right button.
headset
ChoppedLiver said:
Yes, this means the re-mapping of the button worked. Now you can use one of the headset control apps to program the button as you please (remember this button is now acting as the "next" or right button, so program as such).
But, you say "middle button" - do you have a 3 button headset? If yes, I think you could have left the mapping alone, and programmed either of the left/right buttons, or both. Not really sure of the best and most functional approach in this case, I've never had anything other than a single button headset. I would think with 3 buttons, if all 3 are supported, you can have some more flexibility.
If you do have a 3 button headset, but only the middle button is supported by Android at all (apparently YMMV depending on the make/model among other things), then ignore everything I just said, keep the mapping as-is, and just program the one working button as you like - still as if it were the right button.
Click to expand...
Click to collapse
Just to be more specific these are the headphones im using http://www.amazon.com/Samsung-Repla...m-Headset/dp/B007C5S3AU/ref=pd_bxgy_cps_img_y
Help
I really want to do this but I am clueless on what to do. Where do I input this code? The build prop? I don't usually mess with stuff to much but his has been bugging me for a while. Thanks in advance
Ghost_Killer811 said:
I really want to do this but I am clueless on what to do. Where do I input this code? The build prop? I don't usually mess with stuff to much but his has been bugging me for a while. Thanks in advance
Click to expand...
Click to collapse
The file to edit is /system/usr/keylayout/Generic.kl. Of course you need a rooted device to be able to edit it; also you need to mount the system partition read/write (it is mounted read-only during normal operation).
The first post of this thread has the exact instructions on how to do this. Have you tried to follow those steps?
One thing I might add - you will want to keep a copy of the un-edited, original Generic.kl file, because you will typically need to restore it to the original before applying firmware updates. Make a new copy of the original file after every firmware update, since the firmware update sometimes modifies it.
ChoppedLiver said:
The file to edit is /system/usr/keylayout/Generic.kl. Of course you need a rooted device to be able to edit it; also you need to mount the system partition read/write (it is mounted read-only during normal operation).
The first post of this thread has the exact instructions on how to do this. Have you tried to follow those steps?
One thing I might add - you will want to keep a copy of the un-edited, original Generic.kl file, because you will typically need to restore it to the original before applying firmware updates. Make a new copy of the original file after every firmware update, since the firmware update sometimes modifies it.
Click to expand...
Click to collapse
Thanks for the help. I tried reading the instructions, but I got confused. When it says to make a root shell and then gives the code, do I put it somewhere specific in the file or just anywhere.