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.
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 know the title sound complicated but i don't think the idea is. I either saw this in a dream or in another forum and haven't been able to find it again. Anyways my idea is pretty simple:
When the phone is turned up to it's proper position as if your holding it in your hand (the screen is facing up) the phone automatically unlocks it self without the need to press the damn menu button twice or do a silly pattern. When you put it down on a surface, you put it screen down and then when you pick it up and turn it over, it wakes up easy as that. If the phone is facedown and rings it wakes up. And you want the parameters of the phone tilt to be strict enough the phone won't wake up when it's in your pocket. Also, when you put it facedown, the phone will go to sleep.
I sadly don't know if you can overwrite the unlock of the phone (that has no pattern lock) nor do i have the porgraming skills to do this. If it's not possible to bypass the lock screen with a program, maybe u could emulate the menu button being pressed twice? Just my idea. If there is something like this out there already, just post the link. Thank you!
This app already exists. You can download it in the Market. Unfortunately I can't remember the name...it was one of the first apps I installed on my phone.
OK--I looked it up, and the app I was thinking of is not what you asked for. The app is Ring Control, which focuses on controlling the ringer based on position.
However, it uses the same inputs that yours would, so maybe you should contact the programmer? He has a long post about the programming of it here, and it doesn't seem to far from what you want:
http://fognl.blogspot.com/2008/11/android-ring-control.html
Bump!!! come on guys...make this happen.
I personally never use the hard call button to make a call, and it is still often a source of accidental calls.
I use Exidler's Hd2ProximityScreenOff, so i don't need in theory a screen lock. Very, very usefull. Some accidental calls have been made though.
Here is what i found so far :
- Vangrieg InCall Lock is great, but works only when a call is received.
- Aebutton plus doesn't help for long press on call button.
- I searched on whole registry for "cprog.exe" (The dialer processus) without interesting founds.
I would be so grateful if someone find a way to remove this call function when pressing the button, if possible using with no process in background ...
Why dont you just enable the lock screen that way you cant accidentally make a call when it comes on.
thank for your reply optiknerv.
with hd2proximityscreenoff, I think we are in a new and intuitive way to use phones, something apple did not patent already ! ;-)
we dont need anymore a screen lock, but kind of key lock can be, in very rare cases, useful.
I guess it is impossible to map this button ...
Have you ever tried AEBPlus??
It locks every kind of key - software keys too - and make them addressable to other application
You'll find it on http://ae.inc.ru
Sichroteph said:
thank for your reply optiknerv.
with hd2proximityscreenoff, I think we are in a new and intuitive way to use phones, something apple did not patent already ! ;-)
we dont need anymore a screen lock, but kind of key lock can be, in very rare cases, useful.
I guess it is impossible to map this button ...
Click to expand...
Click to collapse
Why insist to map the button? Screen lock solves your problem. Try S2U2 or TLP. They will make sure you don't press the green hard key by accident. If you use proximity to auto unlock, there is no extra action on your side. The green hard key (and the phone) is locked whenever the phone is in your bag or pocket.
thanks you very much alex. touch lock pro solved my problem and can use well proximity sensor after some settings.
As i know that touch pro is not only can be touched on the screen but also the hard button area ( home, back, call, hang up buttons)
How can i use that feature
Which software that i need to install or how can i active it
Thank for reading my topic
What do you want exactly? Do you want to remap hardware buttons?
the hardware buttons are enabled by default. you don't have to 'activate' them.
No! My point is how can i use the sensor of hardware button ^^
Well,did you mean to use the capacitive surface of those sensors,not the buttons itself? And what exactly do you want? Please explain.
google for "G-scroll"
TomasNM said:
Well,did you mean to use the capacitive surface of those sensors,not the buttons itself? And what exactly do you want? Please explain.
Click to expand...
Click to collapse
My point is
Instead of pushing down the 4 hard buttons (call, back, home, hang off) i just need to touch it on the surface?
You can buy gscroll (mobilesrc.com), but unless you can get the 1.x series, I'd pass. The 2.x series is buggy as hell, and it seems like development has stopped. There are some free apps you can find around here as well. I'm thinking Dredscroll is one, and there was another app called Butler (I think, lol) that allowed you to use it as a launcher with gestures on the area. Gscroll lets you swipe to scroll (it's good for reading ebooks, when it's working) as well as to launch things, but it has the annoying habit of going on smoking breaks.
As I know HTC testing software,I can say,it could not be a problem to create an app of this kind,but...
- Do we have SDK for it(I didin't searched for it yet)?
- Currently I don't know,how to send keyboard hooks to the system
- I cannot prevent/disable default keyboard hooks
So that means,I am not able to solve your puzzle. Sorry.
That was my honest opinion...
I don't think he's asking about the Vibrant-Scroll Wheel, I think he's talking about the Optical Track, itself.
[As the Home, Back, Answer, & End Call buttons require you to actually PUSH them down.]
You know, the "OK/Enter" button. When you place you finger on it [NOT PRESS IT], by default, it lights up the Bottom Hardware Keys, as well as brightens the screen.
If it's not working for you, I recommend Backing up your Important Information with either SPB Backup or Microsoft MyPhone, and flashing a New ROM. There are certain Drivers that control the Optical Track. What they are, however, is beyond me.
Everyone in this forum (well there are exceptions) and using HD2 have issues with hard buttons, including myself, while working my Proximity Screen Off app, I thought of a completely new way of navigation for HD2!! How about using combination of sensors??
1) Shake to go back to home
2) If proximity sensor blocked less than a second go Back
3) If proximity sensor blocked less than 2-3 seconds and more than 1 second trigger
menu.
4) If proximity sensor blocked more than 3 seconds launch search
Haven't started on this yet, I need to know if this community really needs an app like this. Also please share your ideas!!!
I think it would be awesome, especially to show off
Might cause problems if the screen accidentally comes on while in your pocket.
Otherwise I like the concept.
Seems like that could have a lot of flaws, because wat if the sensor get blocked by accident while navigating through traffic
Sent from my htc_bravo using XDA App
itsme_4ucz said:
Everyone in this forum (well there are exceptions) and using HD2 have issues with hard buttons, including myself, while working my Proximity Screen Off app, I thought of a completely new way of navigation for HD2!! How about using combination of sensors??
1) Shake to go back to home
2) If proximity sensor blocked less than a second go Back
3) If proximity sensor blocked less than 2-3 seconds and more than 1 second trigger
menu.
4) If proximity sensor blocked more than 3 seconds launch search
Haven't started on this yet, I need to know if this community really needs an app like this. Also please share your ideas!!!
Click to expand...
Click to collapse
Mmmm i dunno i think the seconds issue is a bit difficult bcz not everyone is able to guess how many seconds passed everytime
!
I guess that a navigation based on acceleration values and sensors is a good idea:
I mean say:
1) Shake to go back to home (<--- ur idea excellent)
2) If proximity sensor blocked then trigger menu
3) Positive or negative values of acceleration along Z (vertically) determines going up and down
4) Positive or negative values of acceleration along X (horizontally) determines navigating left or right
I don't know if that can be done and how It's just an idea
Thanks for your effort
I like the shake idea using the g sensor, but the proximity sensor isn't really in an area that is easily accessible with your finger
Sent from my HTC bravo using XDA App
mm... interesting idea
but i'm not sure it will be very useful though... for me
I've not had any problems with my hard keys so not sure that this would do it for me.
However I have always thought that albums (photo and music) should go through the pictures/album covers if your device was tilted to the left or right.
On second reading you're not talking about adding this feature to apps are you, just to have some new menu and home ideas!!
is it posible to use gesture on gsensor? like moving your handset in circle to "search", move your phone from right to left to go "back"?
honestly I think this would be impractical and a waste of time.
I like the idea of G Sensor doing things though, like maybe shake to launch an app or an address to map to or something like that.
If you can solve all the technicalities, I believe this would be awesome. I guess the software would have to have a value of:
Locked screen = normal proximity sensor
More than 5 seconds blocked plus angle = call = screen off
On the other hand, what about shake the phone and a bar with soft buttons comes up on the bottom of the screen covering the launcher and not the icons, shake or press a swipe the bar and the bar goes off.
Wish I knew programming.
What about shake phone to wake up?
Not unlock but just wake up as is this is the most used action which involves hardware keys.
***sorry about my english***
indrema said:
What about shake phone to wake up?
Not unlock but just wake up as is this is the most used action which involves hardware keys.
***sorry about my english***
Click to expand...
Click to collapse
so your phone is turning on in your pocket when you walk? not good
i'd say do it, but that way that blocking proximity for a tiny bit (very short, like just swype over with hand)) will bring up menu such as Vol +- (overlayed over any app) and it contains back, menu search etc...any block longer will be overlooked(so it's not doing if u sheild ur phone from sunlight or hide it in school(lol)
for waking up u can already use all buttons so shift them.
Nice idea.
I think gestures on screen with fingers are better.(if it's possible)
Like: Move with 2 fingers from right to left would be the same as a click on the "back button".
Edit:
Otherwise... i think there are some Apps who have some of these gestures... There might be problems.. :/
Please work on an app for this. That would be awesome. The proximity app is is so useful too
Or maybe just implement most used or just one or two functions like search, back, menu, etc.
Or even better let it be user defineable.
Sent from my HTC HD2 using XDA App
Not a bad idea...it certainly would be in invention worthy of the name.
And it would also make our lovely HD2s super marvelous!!!!!.......atleast for showing off!!
App Button Savior has all of it. It is faster than using the proximity.
1. This would surely be usefull if you are in a car and must navigate through the menu/programm.
(button savior icons are too small for this if you are in a car)
usefull for back/forward/start programm like google voice etc etc.
2. Option automatic activate the app if the phone is hooked to micro usb.