Hi,
Firstly, please accept my apolgies if this has been covered elsewhere (I have searched, honest )
I have installed the Cyanogenmod from this thread http://forum.xda-developers.com/showthread.php?t=1525148 and it runs really smoothly...However, I have experienced a problem where the Enter button acts as a Space button in any field that requires text input (Google search for instance).
Any ideas what this could be?
Cheers
Update: The Enter button works when entering a pin number on the lock screen, but not in any apps within the OS itself (if that makes sense)
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?
I currently have a Kaiser and I'm planning the following setup:
- left soft key: Dialpad (phone canvas)
- short press send key: Call History.
For the left soft key, it is quite easy, go to:
Code:
HKEY_CURRENT_USER\Software\Microsoft\Today\Keys\112\
and change "Open" to "\Windows\cprog.exe" and "Default" to "Dialpad" or whatever name. Soft reset.
Or simply delete the content of 112 key and soft reset, without it the left soft key defaults to "Phone" linked to the phone canvas.
Call history is also easy to shortcut "\Windows\LaunchMSItem.exe" CALLHISTORY_ALL_CALLS.
The issue is with the short press send key. I searched my guts out but I could not find how to remap it. Found solutions for "long press" but not for short.
I want of course to keep the ability to actually dial a number with it.
I am interested in a simple solution without aditional software, scripts etc.
Help much appreciated.
Regards - Daniel
To my knowledge you can't map the send/end keys for short press unless you start digging real hard in some system files which.. even pauldegroot didn't manage to do.. and supbro is still fighting for with iDialer..
By 'end key' if you mean the Off-hook key (the red button), then you can't remap it without using third-party apps.
In fact, it's a bit of a bother even by using third party apps.
The reason is because the dial and end keys are special keys designed almost exclusively for the purpose of using in the phone app.
For more technical info, and how to go about doing it the really hard way:
http://thefiles.macadamian.com/2008/06/detecting-phone-buttons-on-wm56.html
I use aebutton plus to remap my send and end keys - not short key though - I have them mapped for double press/ tripple press. (long press and short-presshave the old functions..)
-mark
@deXter: it was the send key, sorry for that, I corrected the first post. Your link is still valid however - thanks - it seems I have to do a lot more reading on this.
Any quick solution is still welcome
again, same problem.
Small progress
1. By editing
Code:
HKEY_LOCAL MACHINE\SOFTWARE\Microsoft\Shell\Rai\:MSCprog\1
I can assign any program to the send key.
Trouble is:
- cprog is not starting anymore with the phone, meaning no signal and no dialing.
- the newly assigned program autostarts at boot.
2. In some WM5 documentation, I learned that under
Code:
HKEY_CURRENT_USER\Software\Microsoft\Today\Keys\
you could have four keys, 112, 113, 114, 115, corresponding to the left soft, right soft, send and end keys respectively.
In WM6 only the first two seem to work.
Still searching...
Hi,
I'm on a Topaz with WinMo 6.5 Hebrew enabled but English interface.
Lately the number keys in the phone application are shifted one row down. I mean' when I press a number, the phone thinks I pressed the number one row below that. (i.e. If I press the place showing 5, an 8 will be dialed)
Oddly the "TALK" button and the "backspace" arrow button next to it do function normally, as does the whole screen in any other application.
My verbal explanation is not so clear, so please see the attachment. A screenshot with explanatory text.
Any idea what could have caused this? or how to fix it?
I was thinking about removing and re-installing the phone application, but don;t know how to do that, so any help in that direction would also be welcome.
Thanks!
~Azaria.
What is the right forum for this question?
It really bothers me, so really want to solve it.
So this may seem like kind of an oddball question, as every search I did turned up nothing but requests FOR this button (though it apparently replaced an old smiley button, which seems even more useless), but I was wondering if any modders out there had made a version of swype that had no voice input button. Ideally the real estate would be reclaimed for the space bar and/or enter keys, both of which are positively tiny in portrait mode. As a secondary consideration, it'd be nice to remove the Swype help/options button on the bottom-left, too, and an option for arrow keys (sometimes I like having them and sometimes I don't, but the option would be nice).
Just curious if anyone else cares/has worked on something like this. Thanks in advance!
Today I did a software reset so I could let me fiance use my phone since it was a little better than her outdated Huwei. Upon rebooting the Home button no longer funtioned. It will still wake the screen however it does not function in any other way (so obviously its not a physical issue).
I was able to pull up the files to view the mapped buttons and even tried the app on xda for button remapping. However the crossover comes with an extra function button in the top left corner which doesn't function at all any more. This tells me that the mapping file was over written with an incompatible file. Possibly an issue with a wrong file being assigned after a software reset. Not quite sure.
What I would like to happen is to see if anyone else here has a Pantech Crossover and can simply send me there button assignment files.
Another issue I ran into after the reset was the notification bar (still shows at the top) is not draggable. I am not able to pull it down or even hit the "notifications" button under the menu when you hit the menu button from the home screen.
I am no noob to technology so feel free to ask for anything. If you have a crossover and are unsure on how to get those files please let me know and I will direct you. (Please already be rooted.. there are plenty of great guides on these forums on how to do this for both firmware versions available)