Related
Hi there!
This is a topic that really makes me crazy
I found a thread here that showed how to disable the Start Call Beep...but it didn't work for me...I couldn't find the reg. key on my Trin.
So what beep do I mean exactly? The painfully loud one when you engange in a call, or switch to call history and so on.... Hope you know what I mean...out of lack for a better word I called it "System Beep".
Hope you can help killing this for me!
btw. I use WM 6 with Mary 3.6
thx!!
Same problem here...
I also have same problem, really irritating beep. Please do post if you find solution for this..
Same for me I hate that bip when I press the green or red button
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
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...
Hello,
I am new to the Diamond 2. When the call is in progress the screen gets lock. I have got no option to tap the "END CALL" ono screen. I need to unlock the phonoe by pressing the power button and select/view the call progress .
And if the simple lock is enabled i need to enter lock to view the call status .
This is annoying. So How can I change setting to that if call is in progress the screen should NOT get lock.
PS: I have set the simple lock for my mobile. It gets lock even if the simple lock is not set.
Edit#1:
The screen also get locked when we are playing a movie too this is annoying. I think no one in this fourum has this issue or no one tried to resolve this.
Thanks.
Hi hi...I do face the same problem with you. I am looking for any kind soul out there for help on us to resolve such issue. Millions of thank!
No luck yet. Any senior member/developer who can help us or let me know if that is not possible
Close but not similar is my problem.
The TD2 is about 4 weeks old.
The screens turns black after about 10 seconds whatever settings I apply in the energy savings. WinMo keeps the settings, but does not apply them.
In contrast to the above posts I can end all calls by pressing the "end call button".
Any ideas?
True, we can end the call by pressing "End Call" button.
But can you view the call progress window? can you know how much time you spoke? Can you start another call / conf etc etc. This is tedious, which this phone is missing.
Today I send a query to India HTC tech Support. Lets see what they reply. or they will fix in WM 6.5 when it is released for TD2.
The screen also get locked when we are playing a movie too this is annoying. I think no one in this fourum has this issue or no one tried to resolve this.
if you don't want your phone to lock automatically, go to: all settings - system - power - advanced. There you care disable automatically turning off backlight and device. Hope this helps. It doesn't provide a solution for in-call, but for movies ... it's not very hard to go to this tab and disable it before viewing
Thanks for your reply georgeono. I am also waiting for reply from HTC Tech support. Let see what solution they are giving.
Hi again guys,
i've another problem with S2U2 ver. 2.14.
When i received an incoming calls and i pushed green button on my screen S2U2 doesn't answer to call and it blocked my device.
At that time the only solution is to reset my device.
Any ideas?
Thanks in advance,
Alessandro
Try uninstalling s2u2 and see if it works, if so try installing another version of that app.
And don´t forget to vote for Rhodium!
I had a similar problem. It didn't lock-up my phone, but when I hit the answer button, nothing would happen. I tried uninstalling then reinstalling, but no luck. I ended up turning off the caller ID in the S2U2 settings. Now, when I get a call, it opens up to the default caller screen. When the call is over, it locks the phone back.
i have a silmilary problem,
i have disable slide to answer
and now i think it's work
I use SlideToAnswer and it works great.
But, I disabled the 3rd party phone skin and changed the drawing method to Raw (or something similar).