Map Phone Button to Dialer - Droid Eris Android Development

On the latest Cyanogen ROMs, the green phone button (buttom left) will open the call log. I would like to open the actual dialer "number pad" when I press this button.
I have not explored the system files as of yet, and was hoping someone could point me in the right direction as to which files to look at; and maybe save me some time or vain attempts.
Or...is this a compile time option in the phone/dialer?
Thanks for any input.

I happen to also wish I could directly go to dialpad. I've downloaded dialer one and they have revamped that app. looks pretty cool...

Related

Messaging; missing body, list of msgs

Hi All,
I've tried various search strings looking for an answer to my issue but found nothing related. Anyone else have an intermittent problem whereby pressing softkey for "Messaging" yields no body or list, only a title bar and softkey menu as normal? When it occurs, I just see the Today Screen where either the message contents or list of messages should be displayed. After some fumbling and clicking around I can usually get the content/list to appear. I only noticed this problem when I first loaded summiter's ROM but now I have the official Cingular ROM loaded and problem still exists.
Thanks in advance for any thoughts or solutions.
can you access the messaging if you go through the start menu or do you have the same problem there??
is your soft key mapped right to the messaging link?
softkey mapped
Thanks for response, yes, softkey is mapped; as I mentioned earlier, when you launch messaging, I get only the top and bottom elements of the program (Title, New, Menu) but the middle content (message, list of) is missing)--you see only the Today Screen in foreground.
It happened to me as well once I started to force 'exit' on all the apps instead of just minimizing them. Part of Pocket Plus close button.
I'm not sure if this is the same case as you are experiencing but it looks like after the Messaging program is completely terminating, the softkey cannot launch the complete program. I was still able to launch it from the start menu with no problems (sounds very strange, I know).
The way I recovered from that is to put the "Messaging" program in the exception list of the close program; this way it stays in memory and I get the messaging complete program every time I press the softkey now.
I *Hope* that helps...
maybe???
interesting thought... well, i don't use that program BUT i am using smartkey and that likely shares the same process SO i will try that from now on after soft-reset and report back...
Thanks for the tip! It's definitely one of those hard to track down the cause kind of issues, how did you come about that as a solution?

useful in contact manager - yet HTC support doesn't know enything about this.

Hello everyone,
I've discovered quite useful thing about contacts manager, but unfortunately don't know how to turn it on or off, it starts, let's say randomly.
Sometimes when (on today screen) i press right softkey which is by default assigned to 'contacts' and i get a list of names, i see something like a pop-up window with letter 'A' and by using the jogdial on the left side of the TyTN i can switch between the first letters of the names in contacts. Then i can select exact name without scrolling through all of the contacts in between A and f.e. G.
Unfortunately i don't know what is the cause of starting this feature, people at HTC support don't know nothing about it, and told me that it must be some kind of software glitch however I find it very useful, maybe someone else got the same thing? And someone does know how can it be turned on that it happens every time i want to find a contact? that would really be operating with one hand then
thanks in advance for opinions and advices
If it's what I think you mean, go to contacts.
For example, hold down down (on the dpad). It'll start scrolling the list for approx 5 seconds. After that, the large letter A will show up. Use the dpad to select appropriate contact start.
Otherwise use the sip to start typing your contact.
V
szturchen_pl said:
Hello everyone,
I've discovered quite useful thing about contacts manager, but unfortunately don't know how to turn it on or off, it starts, let's say randomly.
Sometimes when (on today screen) i press right softkey which is by default assigned to 'contacts' and i get a list of names, i see something like a pop-up window with letter 'A' and by using the jogdial on the left side of the TyTN i can switch between the first letters of the names in contacts. Then i can select exact name without scrolling through all of the contacts in between A and f.e. G.
Unfortunately i don't know what is the cause of starting this feature, people at HTC support don't know nothing about it, and told me that it must be some kind of software glitch however I find it very useful, maybe someone else got the same thing? And someone does know how can it be turned on that it happens every time i want to find a contact? that would really be operating with one hand then
thanks in advance for opinions and advices
Click to expand...
Click to collapse
It works on all variants of the Tytn, you just go to contacts, press and hold down on the d pad and in a couple of seconds the 'pop up window' appears with a large letter, it just makes it easier to scroll through the contacts without having to get the stylus out.
Thanks guys !!
That's the 'pop-up' that I meant. Pressing and holding d-pad works. However I occasionaly get it when using jog-dial. In my opinion that would be even better for operating TyTN with one hand. Any clues on this one?

MobileMute - Mute/Unmute calls via hardware 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

Problem with dialer (using Launcher pro)

If I swipe right on a contact, make a call, but exit out of the call window and hit the dialer on screen, it doesn't show the current phone call. It just shows the default dialer. The only way for me to end a phone call is to use the drop down menu.
Basically, it is really annoying and I am wondering if it is just some small user error that I am committing.
I have been running LP since 30 min of getting the phone (couldn't stand TW interface) and almost a week with my phone here and no problems with LP at all. Try reinstalling the app or doing a master reset.
Mark271 said:
If I swipe right on a contact, make a call, but exit out of the call window and hit the dialer on screen, it doesn't show the current phone call. It just shows the default dialer. The only way for me to end a phone call is to use the drop down menu.
Basically, it is really annoying and I am wondering if it is just some small user error that I am committing.
Click to expand...
Click to collapse
I noticed that earlier today when I was reading a tracking number to someone over the phone. It's such a pain. I just tested it today, went back and forth between Launcher Pro and TouchWiz. I hope it's not something that will be too difficult for the Launcher Pro devs to fix, and not some weird TouchWiz thing that can'e be worked around.
I have noticed the same issues with not being able to easily get back to an in progress call. If you press and hold the home button you can then tap on the dialer and get back to your call no matter what launcher your using. ADW does the same thing by the way. This is why I have not been able to jump to either alternative launcher.
I thought this happened because the dialer shortcut was linked to whatever action the pull down status bar icon was assigned to, but even if I create a home screen shortcut to the dialer, it still works the way it should while in TouchWiz.
I started a thread on the Launcher Pro forums. I copied and pasted the above onto it.
Edit: None of the Activies under either of the Dialer menus seem to work. I thought I could find whatever that static icon does and create my own shortcut.
ahorriblemess said:
I just realized... this is obviously because the static/unremovable dialer icon in the TouchWiz dock is linked to the same action as using the pull down menu and tapping the dialer icon. Still, I wonder if there's a workaround for this.
I started a thread on the Launcher Pro forums. I copied and pasted the above onto it.
Edit: None of the Activies under either of the Dialer menus seem to work. I thought I could find whatever that static icon does and create my own shortcut.
Click to expand...
Click to collapse
The contacts for me does not work by default either. I had to replace their contacts shortcut by long pressing and changing shortcut with the application contacts stored in our phone. I am sure this has to be an easy fix.

How do I change right hand dock "phone" to "wifi"?

Sorry for this one, I have had a quick search...
On the right hand side, the small dock that shows Browser, Apps and Phone.. how can I change this, on the stock rom I had, the phone was wifi, which was much more useful, given that the advent doesnt have native phone hardware!
It depends a little bit on the launcher you are running, but on most, if you press and hold an icon, even in the dock, you can 'bin' it and drag a new icon into its place from the desktop.
Cant tell which launcher it is, currently using Corvus5 rom, but even the Modaco rom had the same launcher... but Corvus5 has Phone (for some reason), rather than Wifi, and I would like to change it....
Holding down the icon doesnt do anything other than launch the app when you release it...
Cheers
I think that is the ADW or the VTL Launcher (both quite similar). Does anything happen if you hold and drag the icon off the dock position?
Nothing happens, you cant do anything other than press them... and the app launches when you take your finger off...
I haven't got my Vega with me at the moment so can't check till later. I guess it may be worth a look in the Launcher settings. I recall these are not obvious to get to. At the desktop, hit the menu button and then go to Settings or Advanced and I think you find Launcher settings somewhere around there.
I have the same problem.
The icon is not part of the normal launcher bit, its the small tool bar on the right hand side that also has the browser and app button so you cant select it and drag it into the bin.
I wish there was a way to remove the phone parts of the corvus rom... i think i need to do some reading
Ok so I got mine sorted, long press on the phone symbol, select edit then wifi setup. I'm using awn, so hopefully helps someone else.
I dont know why i never remember to long press stuff... haha
Thanks for the tip dude!
Does anyone know how to make the tile spaces smaller on the home screens to get more icons on the screen? i can only fit 4 icons across the screen, loads of wasted space
A number of the Launchers have configuration options for number of icon rows and columns. At the Home screen access the Menu and then see if you have some Launcher options accessible under the More button.

Categories

Resources