I'm currently running m2d on my polaris. I was wondering if there was a method for me to map one of the buttons on the phone so that it will open the phone profile windows (ie. normal, vibrate, silent). Its somewhat of a hassle to have to change the profile since it requires several button presses to do so.
Also, another idea would be to have a program that ran in the background and each time you pushed a mapped button on the phone, it would cycle through the different profiles. This way, you might not have to look at the phone when you want to change the profile (food for thought). Not sure if anybody or company has come up with this yet.
"long press end key"... an HTC software, changes between unmuted and vibrate. i use it all the time.
you can also find the shorts to switch between profiles in the forum and map it to hardware buttons (and even use cycles) using HButton
Related
I want to map the green "phone" ("send") button to work as speakerphone with long keypress when phone is used, but I can't find any info.
OTOH I notice most ROMs use long press for this button and map usually wireless managers, which would be fine if it would work that way only when phone is not in use (and 'restore' the speakerphone function for long press when phone is in use) but I have not seen such solution yet. Has anyone done/try this?
-888- said:
I want to map the green "phone" ("send") button to work as speakerphone with long keypress when phone is used, but I can't find any info.
OTOH I notice most ROMs use long press for this button and map usually wireless managers, which would be fine if it would work that way only when phone is not in use (and 'restore' the speakerphone function for long press when phone is in use) but I have not seen such solution yet. Has anyone done/try this?
Click to expand...
Click to collapse
Hi,
Deleting Long_Send.lnk might restore original function of long press send key sir,.
Hope it help,.
Regards
Unfortunately, I don't think you can have two different functions based on context. AdvancedConfig has an option to map pretty much anything to the long send.
Garmin said:
Hi,
Deleting Long_Send.lnk might restore original function of long press send key sir,.
Hope it help,.
Regards
Click to expand...
Click to collapse
Thank you, Sir
blue_94_trooper said:
Unfortunately, I don't think you can have two different functions based on context. AdvancedConfig has an option to map pretty much anything to the long send.
Click to expand...
Click to collapse
Well, I was thinking about something more complex than I can do myself, hence my post here.
Idea is to make a small applet which will switch the function of the button based on the processes running (or other ways to determine it) and assigning different shortcut to this button. I.e. when the phone is connected it will assign speakerphone to the "send - long press", when phone is not in use it would redirect "send - long press" to the wireless manager, if you know what I mean (sorry my english); so virtually mapping the "green" button to this app could achieve that, no?
intersted also in your send key LKP!!
-888- said:
Thank you, Sir
Well, I was thinking about something more complex than I can do myself, hence my post here.
Idea is to make a small applet which will switch the function of the button based on the processes running (or other ways to determine it) and assigning different shortcut to this button. I.e. when the phone is connected it will assign speakerphone to the "send - long press", when phone is not in use it would redirect "send - long press" to the wireless manager, if you know what I mean (sorry my english); so virtually mapping the "green" button to this app could achieve that, no?
Click to expand...
Click to collapse
Bump....
I also want exactly the same setup! Great minds think alike!
Your mention about the wireless manager sounds a handy idea also, and I am at present having to use a long keypress on the left hand hardware 'record' button. This is fine, but I also have it mapped to normal press = audio record. But want to use it for something else at some point.The more buttons free the better. To be able to have the sent button act on a long key press to work the speakerphone seems to me like something that should actually be in place by default. I mean, what better way to start the speakerphone!!
I do hope someone is able to shed some light on this, or you manage to pull it off yourself you can count me in to try the fix etc.
PS:: Would a MORT SCRIPT help in this situation I wonder? I am not familiar with MS but sure someone may know a way round it.
Regards
Nick-UK
Thanks for your kind support
I wrote about this year or more ago on another forum, but few responses I got were discouraging at best.
I think if we could do such "app", we could use it for all the buttons and change their "assignments" based on the currently running apps...
With scripts we can do things like rename "Long_Send.lnk" into "Long_Send.disabled" (for example) instantly, and rename it back to "Long_Send.lnk" when i.e. pressed again. But the problem is that I don't know how to "detect" and use it in the scripts what is currently running and discriminate between foreground and background processes that are currently running?
Because what if you have two (or more!) programs that are using the same button assignments but for different purposes and both are running in the same time? say you are on the phone talking - thus long_send is assigned to speakerphone, and you also run (for example) windows media player where you assigned same green button to fullscreen display? The scripts cannot tell which one is running in the foreground by themselves, and (in this example) holding green button could bring the WMP to fullscreen instead of turning on speakerphone. Beforewe use mortscript to "activate" apropiate script, we need to know which process was started last (so - per my example - we would know that the phone was last started and not the WMP, and mortscript would run "speakerphone script for green button" instead of "fullscreen wmp script for green button"... and there is another problem: the phone is always ON on our PocketPCs since boot, and it is running all the time in the background, so it will have to differentiate between phone being active and phone in the "waiting" state...). Apologies if I sound incomprejensible, I tried to make it clearer but I don't know is it less gibberish
to cut it short: I don't think it can be done with simple scripts. But of course I may be wrong.
In theory it should work this way:
1 Long_Send.lnk -> starts our "app"
2 "App" checks what program is currently running on the screen (in the forground, or last started etc)
3 "App" executes apropiate action assigned for this program (i.e. speakerphone for active phone call, or wireless manager for today screen, etc etc)
4 "App" releases/removes/disables the action from previous step and changes it back to the state it was before when the foreground program is closed (i.e. changes back long_send from assignment to speakerphone back to default once the phone call ended)
sounds simple, doesn't it?
Starting a couple of days ago, the hardware keyboard on my Fuze started randomly repeating keys: I'll be typing along and suddenly a character will insert itself a number of times. It seems to happen once every 30-50 keystrokes on average.
I'd write it off as a busted keyboard and take it back to the store for an exchange, but it doesn't feel like a hardware issue. For one thing, whatever key it is always repeats 6, 7, or 8 times. Keyswitch bounces in my experience generally insert fewer spurious characters than that. For another thing, there's no pattern that I can discern to which keys repeat; a hardware problem usually affects one particular key or key grouping.
What I'm seeing looks more like the key release event is being delayed until after the long-press repeat processing takes over; then the release event fires within a fairly narrow timing window. If I watch the screen as I'm typing, I see exactly what I would see if I held the key down: I get one character, then after a short pause, I get 5-7 more of them. This started happening about the time I installed AE Buttons Plus; however, I've uninstalled that and the problem persists. (However, uninstalling often doesn't undo all the registry changes that were made, so AEBP could still be the culprit, I suppose.)
I'm probably going to hard reset tomorrow when I have some free time so I can play around some more with the GPS starting from a clean slate, and that will give me a chance to test whether AEBP is, in fact, responsible. In the meantime, does this sound at all familiar to anyone? Any suggestions for what I might look at in the registry?
A quick update on this: I have verified that AE Buttons Plus is, in fact, responsible for the repeating keys. I set the new key that was added for the PTT button to "Do not touch" in AEBP and soft reset. I have had no repeating keys since then.
I have emailed the author, describing the problem, but I haven't heard back from him yet. I'm hoping that he can either fix AEBP or suggest some workaround to prevent the repeating keys. The short_PTT.lnk/long_PTT.lnk solution recently presented here works fine, but it only gives two assignments, while AEBP can do three (or four, if you can live with the Home button doing the same thing as the single-press PTT button).
If I hear anything encouraging, I'll post again. Otherwise, people should use the shortcut approach for remapping the PTT button.
Hi guys,
My digitizer has died, and till the new one comes I was thinking of how I could use my T7272, I can write the SMS fine, but I can't send them out, cause the button is on the screen itself... is there a rom I could use freely w/o using the touchscreen?
P.S.
Is the digitizer hard to replace?
You could check out AE Button; it has some options like button presses that will activate soft buttons. I suspect you could send sms's using it. You could also try using mortscripts with AE button that will do stuff you need. There are some pretty simple scripts that will simulate screen taps, and you could assign them to a button push. I'd rather have a working touchscreen, though.
Here are some of the commands:
# 91: startmenu (on some devices it might be home button)
# 92: back key (not the backspace key but back key for closing applications which is available on some devices such as diamnd or blackstone)
# 93: menu key
#112: left softkey
#113: right softkey
#114: accept call (green button)
#115: hang up (red button)
#117: volume up
#118: volume down
#126: data disconnect
#127: toggle speaker
#133: devicelock
#223: power off
I use one to lock the device. Basically, you just put this:
Code:
sendspecial(133)
in a .txt file, and change the extension to .mscr. I call it Lock.mscr, and I have it assigned to a few different actions (like when a call comes in, a script locks the phone). So, sendspecial(112) and sendspecial(113) might help you out. There's also one for hitting 'Ok' in popups, which would probably work for you. I can't find it, though (google 'sendspecial' and you'll find it, it's all on msdn).
Anyway, if you install mortscript (maybe you already have it) as well as AE Button, you could assign button pushes to carry out those actions. Just stick the scripts somewhere easy, like the start menu, and it will be easy to set up.
If you want to get more complicated, there are also mortscript commands that simulate button pushes on the screen. You could set one up that would do just about anything. Also, SK Schema does similar stuff. You can write fairly simple sequences of button pushes that will do just about anything. This is one that I use that runs SK Tools Pim backup (I have it scheduled to run every night in the middle of the night).
#r(\windows\sktstart.exe) #p(STH:20)
#tap(146;602) #sleep(15000)
#tap(110;533) #sleep(500)
#tap(339;455) #sleep(500)
#tap(126;604) #sleep(500)
#tap(114;84) #sleep(500)
#tap(146;99) #sleep(5000)
#tap(310;254) #sleep(90000)
#tap(433;602) #sleep(10000)
#pwr() #sleep(10000)
Click to expand...
Click to collapse
Basically, the backup tool gets launched in line 1, then there are a bunch of screen taps (w/ delays, to make sure everything is ready) in the menus to get the right options selected, followed by turning the device off.
I`m not sure... But i saw somewhere app that emulate a mouse (cursor) and you will be able to control this mouse with your D-pad... But I can be wrong...
I can't install that mortscript w/o the touchscreen though..damn it..: )..
Get MyMobiler, and use it to run your device off of a pc. You should be able to get that working.
I have a upcoming event which I will need to be in constant communication with my peers, but a conference call would not suit the purpose, and I do not own a set of walkie talkies with enough of them. I have however, found a Push To Talk App that I like. There was no setup required, it just uses phone # and data connection /wifi. I tested it with one of my peers who will be at this event, and he had it installed and working in literally no time. However, this app simply sits in the foreground with some info about the "call" and a talk button. However, if you press the sleep button, the screen turns off and the phone locks while the "call" stays active.
I was wondering if anyone knows of a similar PTT app that allows use of a hardware button rather than an on screen talk button to a hardware button, for instance the camera button, or something like that so that it can be used with the phone in locked mode with screen off.
Hello everyone,
I have an unlocked Nokia Lumia 710 running a custom ROM and all in all the phone is good. However, the proximity sensor doesn't seem to work properly (I don't know if the problem is from the custom ROM or from the phone itself but it doesn't really matter) - when I'm in a call I keep pressing the Hold and Mute buttons (no matter how I hold the phone) which makes me really irritated. So I was wondering, there should be registries I guess that make the buttons active when pressed during a phone call. Can someone point me to the correct registries that control if the buttons are active or not when pressed so that I will hopefully be able to completely disable these two buttons (so that when pressed nothing happens)? I don't use them anyways, so completely disabling them would certainly fix my problems. I'm posting in the general WP7 section because I guess the location of these registries would most probably be the same for all phones...
Thanks a lot in advance!
There's a registry value that is updated automatically by the proximity sensor and indicates its current status system-wide, but I doubt you'd want to use it. For one thing, it would almost certainly get immediately reset by the sensor, faulty or otherwise. For another, the Phone app isn't the only thing that uses the proximity sensor; you would end up locking out the touchscreen in some other apps too. Finally, this would also prevent you from pressing the End Call button!
I don't know of a registry value that's specific to the Phone app's use of the proximity sensor. However, even if there is, the first and third reasons above still apply.
I instead recommend that you simply tap the power button when putting the phone up to your ear to talk. This will turn off the touchscreen (and incidentally save power) and you can tap the Power button again to access the Phone app or any other app on the phone when you need them, without interfering with the call.
There may also be a tool in some built-in Manufacturer or Diagnostics app that would let you test and adjust the sensitivity of the proximity sensor. This would perhaps be the best option, but I don't know where or if it exists on a Lumia.
What I want to do is not to play with the proximity sensor itself but rather with the buttons on the screen during a call. I guess I didn't make myself clear enough, sorry about that. The idea is that when I'm in a call, the proximity sensor does not work properly and I always press either the Mute or the Hold buttons. So, these buttons can still appear during a call but when you press them, I don't want anything happening. I mean, the idea is even when the phone is not next to your ear and the screen is active during a call, pressing the buttons to do nothing. I'm just following some simple logic, which might of course be incorrect (or too simple), but I'm thinking that there is most probably a separate registry for each button that controls whether this button does some action when pressed or not. I'm also hoping that they'll be separate registries for each button so that I can, for example, disable the actions for the Hold and Mute buttons, but leave the End Call button active. The problem is that I have no idea where to look for this registry since I'm still new to WP OS.
Heck, it would even be OK for me to completely remove the buttons from the screen during a call (or substitute the current buttons with some 1x1 px transparent images), if that's possible, so if someone knows how to do even that, tell me.
I was also considering using the power button when in call but I first want to see if there is any other way to do what I want. And since I'm not using the Mute and Hold functions at all, I just thought about disabling them.
No, I understood you. I was suggesting the "fix your proximity sensor" option because normally, the problem you're experiencing just doesn't happen; that's what the prox sensor is for. Sometimes it's miscalibrated, though, or something is covering it up (some poorly-cut or installed screen protectors do this, for example).
The "Phone" app isn't a Silverlight app like third-party ones; it's a native EXE that we pretty much can't modify without using a custom ROM. That's going to make changing it the ways you suggest (disabling or resizing certain buttons, etc) quite difficult.
I'm pretty sure you don't want to disable all the buttons always, even if that were possible. For one thing, that would prevent you from hanging up, as I mentioned before. It would also prevent you from dialing any numbers, which would make the use of touch-tone automated services impossible.
The Power button option really seems like the best fit for you. It's easy, doesn't require any hacks, doesn't break any other functionality, and should be the next-best solution beyond actually solving the problem.
I see now, makes sense. In my head it sounded simpler than what it really is. I was considering resizing the buttons because I'm also using iOS and I quite enjoy digging in the OS and changing some elements, so it's possible there to, for example, substitute some buttons with transparent 1x1 px images, etc. But that's irrelevant. Looks like WP is different and I still need some time to get in to it. Anyways, thanks for your help.
P.S. The screen protector was the first thing I "accused" but unfortunately it wasn't causing the problem.
On a custom ROM, you could definitely tweak the Phone app if you wanted to. However, the way WinCE (the kernel behind WP7) works, OS files are almost always marked as "in ROM" which means that the filesystem driver will refuse to modify them while the OS is booted. This makes tempering with the stock OS difficult; we have to find ways to modify the behavior of apps and system features without modifying the apps or features themselves.