[IDEA/REQ] In-Call Lock Screen with Light and G-Sensors

[lpaso]

Hi,

I recently bought a HTC Touch HD, and I think that the "shutdown-screen-when-you-answer-a-call" function of phones like Diamonds, Touch Pro and HD is the dumbest way to prevent accidental presses on the touch screen.

Our devices have a light sensor, that could be used to switch off the screen if the phone is near the ear (like the phone using an "i" word ;)) and keep it on when you answer with loudspeaker for example.

The "problem" with this function is that when you're already in a "no-light" environment, the screen lock function doesn't work.

To resolve this issue, I think we could use the G-Sensor. Indeed, if the place has no light, then, the phone cannot detect the proximity of a ear. But when you put the phone next to the ear, you hold it a the vertical...

To make it short, the app should do :



Do nothing in normal use.



When a call arrives :

- it monitors the ambient light


If there's light :

- when you answer the call, if there's light then no more (you stick the phone next to the ear), it switches off the screen and continue to monitor.
- while in call, if there's light again (you want to see some info on the screen for example), it switches on the screen and continue to monitor.
- and so on until you end the call



If there's no light :

- when you answer the call, but let it at the horizontal (you let it on the desk for example), it does nothing
- if you take the phone on the vertical position (you stick the phone next to the ear), it switches the screen off.
- if the phone, during a call, goes from vertical to horizontal of horizontal to vertical, the screen is switches on/of
- and so on until you end the call


Obviously, you could replace the "switch on/off screen" with "lock/unlock screen".

What do you think about ?


UPDATE :

After playing a bit with the HD, it appears that HTC DOES use the light sensor for turning the screen off during a call.

Let's do a test :

In a place with plenty light :
- put your mobile with the face up
- call a number (always face up) : the screen will not be switched off until the light sensor detects a loss of luminosity or a timeout set in the registry.

So, my conclusion is that HTC already use the light sensor to switch the screen off during a call, but they do it in an absurd way :

- they poll the sensor just to shut down the screen, not to switch it on.
- once the screen has been switched off, they do not longer poll at all.

Do you think it could be a way to "hack" their system to do what we want to do ?

[lpaso]

no one has an opinion on this idea ? if there's nobody that want / have the time to develop a soft, I understand, but at least please, give me just your opinion :)

[custardo01]

I agree with your idea for such an application. I must admit that I am very used to just pushing the power button when I answer a call (from Polaris use) to ensure I am not going into other programmes as I rub the phone against my ear. On the other hand I am trying to get used to the Touch HD's modern automatic method but I can't help not feeling relaxed that it has worked and keep trying to look at the screen in the corner of my eye to see if it did go off or not.

If it does not come now I am sure there will be such an app very soon just as you describe especially as all the latest models now have it.

[nir36]

i'd use the half of it that doesn't require the G-sensor as i don't have a diamond or HD...
but i'm certainly sick and tired of my ear operating my touch screen while i'm speaking.

[fireweed]

I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.

[lpaso]

I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.


Maybe the simpliest way to "protect" the screen is to switch it off. I suppose it must be some API to do that ?

Concerning the "locking", I think the simpliest way is to put on focus an empty window (transparent if it can be ;)).

I'm really happy to know that you're working on an app like that :D

[iosub]

Hi,

I recently bought a HTC Touch HD, and I think that the "shutdown-screen-when-you-answer-a-call" function of phones like Diamonds, Touch Pro and HD is the dumbest way to prevent accidental presses on the touch screen.

Our devices have a light sensor, that could be used to switch off the screen if the phone is near the ear (like the phone using an "i" word ;)) and keep it on when you answer with loudspeaker for example.

The "problem" with this function is that when you're already in a "no-light" environment, the screen lock function doesn't work.

To resolve this issue, I think we could use the G-Sensor. Indeed, if the place has no light, then, the phone cannot detect the proximity of a ear. But when you put the phone next to the ear, you hold it a the vertical...

To make it short, the app should do :



Do nothing in normal use.


When a call arrives :
- it monitors the ambient light


If there's light :
- when you answer the call, if there's light then no more (you stick the phone next to the ear), it switches off the screen and continue to monitor.
- while in call, if there's light again (you want to see some info on the screen for example), it switches on the screen and continue to monitor.
- and so on until you end the call



If there's no light :
- when you answer the call, but let it at the horizontal (you let it on the desk for example), it does nothing
- if you take the phone on the vertical position (you stick the phone next to the ear), it switches the screen off.
- if the phone, during a call, goes from vertical to horizontal of horizontal to vertical, the screen is switches on/of
- and so on until you end the call


Indeed, you could replace the "switch on/off screen" with "lock/unlock screen".

What do you think about ?


I searched the forum for an existing app that could do this, but I didn't find anything.

If there's already an app that do this stuff, I'm truely sorry for this post.

I'm looking for this.. If you find a solution send me a PM, I will do the same

Thanks!

[donbronzi]

We need this app, how does the iphone acheive this?

I think the 'easiest' way to make this app would be to keep the phone doing what it does currently (put the phone on standby when answering a call) then have the light sensor take the phone out of standby when it receives light, (taking it away from your ear)?

Obviously if its dark then we would have to use the power butten as we currently do now or have the Gsensor do it with a twisting motion (vertical to horizontal).

If anyone has an idea how to program this i'm willing to help in any way, the current systems seems so crude on such tech devices!

DB

[exidler]

Hi,
I searched the forum for an existing app that could do this, but I didn't find anything.


There a program, that can help you. Not full, but it can switch off screen, using g-sensor. However its using not vertical aligment of the phone. There are using changing orientation of the phone to decide when phone near the ear.

http://forum.xda-developers.com/showpost.php?p=2622590&postcount=45

[johnchan78]

I have always wondered why our WM phones don't do what the iphone does...

For the SE Xperia X1, the light sensor is right near the earpiece (along with the little front facing camera), so it would go to virtually 100% darkness when near the ear. I would presume unless you are using the phone also in 100% darkness (which should be pretty rare I would guess) then it would work like the iphone.

I have also been quite annoyed by the fact that after a phonecall, sometimes I found i'm in a note taking program or weather program or something else. It just seems dumb, considering our phone HAVE these lightsensors?!

[quicksite]

no one has an opinion on this idea ? if there's nobody that want / have the time to develop a soft, I understand, but at least please, give me just your opinion :)

I would rank myself this way:

Not a newbie who's just gotten a touchscreen phone and is now discovering the quirks when holding screen to ear,

and not a developer,

but a power-user. I have installed all sorts of XDA-developed features/enhancements for my phone.

But now I have 4 years experience -- starting with the T-Mobile MDA, and its successor, the T-Mobile WING. And despite all of the advancements expected in that time, STILL, I inadvertently end a call, or put it on hold accidentally, ALL THE TIME. Between that and trying to retrieve the phone from my pocket just to answer the damn ringing phone, I would say I have, on the average, a 20% success rate -- and 80% of the time the call is disrupted. And at least once a day my ohone, in my pocket, even when using s2u2, manages to REDIAL my latest conversation, so mcuh so that all my friends say "why don;t you get rid of that phone. It does all these whiz bang things but still can't reliably manage a basic phone call.

My most recent experiment was to call someone, then when they answered, press the s2U2 key to lock the phone screen. Only I came to find out from A_C that this is no good: S2u2 does not have recognition that you're ending the call, thus, since it's in lock-mode, the "END CALL" or Hang-Up hard key does not work.

So by all means, I would even pay for an app that once and for all handles the baseline problems of simply making a phone call. Thanks for making this request.

[quicksite]

There may just be perfect synergy between the two of you. His "best of breed" screen-lock app is widely used -- and other developers, like supbro, for example, author of iDialer, have collaborated on small code-bits from A_C to solve some integration problems.

If for any reason you are unfamiliar with A_C, go to his website: www.ac-s2.com -- where his apps are explained, and all link back to XDA.

He's even managed to make the screen lock work, yet, have it selectively overridden when you insert headphone jack -- such that his s2p (slide to play) app opens and allows you to switch music tracks etc while otherwise the screen and buttons are all fully locked...

I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.

[lpaso]

Hi,

After playing a bit with the HD, it appears that HTC DOES use the light sensor for turning the screen off during a call.

Let's do a test :

In a place with plenty light :
- put your mobile with the face up
- call a number (always face up) : the screen will not be switched off until the light sensor detects a loss of luminosity or the timeout set in the registry expires.

So, my conclusion is that HTC already use the light sensor to switch the screen off during a call, but they do it in an absurd way :

- they poll the sensor just to shut down the screen, not to switch it on.
- once the screen has been switched off, they do not longer poll at all.

Do you think it could be a way to "hack" their system to do what we want to do ?

[Chatty]

I think HTC does not only switch off the display but goes to standby (phone works independent if you didn't know yet). Your idea is a lot different in terms of programming.

[lpaso]

I don't know if it goes to standby : when the screen is switched off during a call, a press on any button switch it on again. In the registry, the key controlling the timeout before the screen is shut off is named "LightSensorToScreenOff" so I think it is just switching off the screen...

[johnchan78]

I don't know if it goes to standby : when the screen is switched off during a call, a press on any button switch it on again. In the registry, the key controlling the timeout before the screen is shut off is named "LightSensorToScreenOff" so I think it is just switching off the screen...

Well if thats the case, its HALF of what the iphone does... it turns off the screen based on the light sensor going dark suddenly (next to ear) but then fails to turn the screen back on after you move the phone away from your ear...

Anyone know how to enable this?

[Hennyb]

Interested in having this feature too. Isn't it possible to have the G-Sensor determine when the phone is vertical and shut the screen and then when it is lying flat to turn the screen back on again. Believe that the Iphone does it this way, not with the light sensor.

[Section9]

Hmm... I never had my ear 'navigating' my phone during in-call before....

I never allowed the screen to touch my face anyway, and the speaker is facing the ear canal, when I receive or make calls...

But i do understand that s2u2 can do what you guys might need, it locks the screen during in call.

[Section9]

Interested in having this feature too. Isn't it possible to have the G-Sensor determine when the phone is vertical and shut the screen and then when it is lying flat to turn the screen back on again. Believe that the Iphone does it this way, not with the light sensor.
I think the Iphone has something called proximity sensor, which senses the distance from the ear to the phone, hence when the phone rest on the outer ear, the phone screen shut off.

Or am I wrong?

[lpaso]

I think the Iphone has something called proximity sensor, which senses the distance from the ear to the phone, hence when the phone rest on the outer ear, the phone screen shut off.

Or am I wrong?

No, you're right. It uses an iR sensor to know if there's something near the phone.

[johnchan78]

No, you're right. It uses an iR sensor to know if there's something near the phone.


I would like to remind everyone, that if you're lying down using the phone, or using it on the side, the g-sensors (with the Xperia X1 doesn't have, but just saying) will not be accurate.

The light sensor ALONE should be sufficient. All it needs to do, as soon as an incoming call is detected, or maybe for the next 1-2 seconds, read the light sensor. As long as there is a TINY bit of light, it should not show as complete darkness. Assuming once you put the phone to your ear, the light sensor is 99.99% dark, then it will know when you've got it on your ear and when you move it away from your ear.

Now if the room is 100% dark at the beginning, then just leave the screen on the entire time.

Hopefully this makes sense?

[lpaso]

the problem is that the accuracy of the light sensor seems to be not great. You can test it with a program like G-light : in a room with only one light , and if the phone is not turned in the direction of the light, you'll have a "0 lumens" value...

But, in this case, the solution is to go back to the "normal" mode : when the call is answered, the screen is shut off directly.

[ZuinigeRijder]

the problem is that the accuracy of the light sensor seems to be not great. You can test it with a program like G-light : in a room with only one light , and if the phone is not turned in the direction of the light, you'll have a "0 lumens" value...

But, in this case, the solution is to go back to the "normal" mode : when the call is answered, the screen is shut off directly.

Indeed the sensitivity of the light sensor is not good enough, in too dark lighting conditions it will not work. Therefore I used the lightsensor only for unlocking in TouchLockPro, which works also for the Touch HD (http://forum.xda-developers.com/showthread.php?t=457039).

In the upcoming version TouchLockPro 1.9 I will introduce the ScreenOffWhenCallConnected option, so you cannot accidently press stuff with your ears. Also I will introduce the option UnlockWhenCallConnected, so you can still use the hardware keys, when the screen is off (e.g. for ending the call) and it is not locked when the call is ended from the other side.

So this might be the solution for:
[IDEA/REQ] In-Call Lock Screen

[lpaso]

I'll be pleased to test your next version ! It seems to exactly answer the REQ :)
Thank you.

[lpaso]

I tried to make a prototype using the API from the author of Klaxon, and I'm a bit disappointed... When the screen is off, the light sensor sends random data (especially between 300 and 450 lumens).

[johnchan78]

Indeed the sensitivity of the light sensor is not good enough, in too dark lighting conditions it will not work. Therefore I used the lightsensor only for unlocking in TouchLockPro, which works also for the Touch HD (http://forum.xda-developers.com/showthread.php?t=457039).

In the upcoming version TouchLockPro 1.9 I will introduce the ScreenOffWhenCallConnected option, so you cannot accidently press stuff with your ears. Also I will introduce the option UnlockWhenCallConnected, so you can still use the hardware keys, when the screen is off (e.g. for ending the call) and it is not locked when the call is ended from the other side.

So this might be the solution for:
[IDEA/REQ] In-Call Lock Screen

Hopefully you can keep us SE Xperia X1 users in mind too. We don't have a g-sensor but we do have the light sensor :-)

[iosub]

Indeed the sensitivity of the light sensor is not good enough, in too dark lighting conditions it will not work. Therefore I used the lightsensor only for unlocking in TouchLockPro, which works also for the Touch HD (http://forum.xda-developers.com/showthread.php?t=457039).

In the upcoming version TouchLockPro 1.9 I will introduce the ScreenOffWhenCallConnected option, so you cannot accidently press stuff with your ears. Also I will introduce the option UnlockWhenCallConnected, so you can still use the hardware keys, when the screen is off (e.g. for ending the call) and it is not locked when the call is ended from the other side.

So this might be the solution for:
[IDEA/REQ] In-Call Lock Screen

Hi

touch HD already has "ScreenOffWhenCallConnected" a least for me.
Let me explain, when the other "partner" the one I'm callling pickup the call, my screen on the HD is locked automaticaly(get blank)...
The problem that I have is "ScreenOffWhenCallSTARTED".. when I start a call if the light sensor does not detect that the phone is near my ear and before the partner pickups the call the screen is not blank... so my ear can push the screen.. So the good feature should be.."ScreenOffWhenCallStart" just is the moment that I push the "call button"

Thanks!

[ZuinigeRijder]

I tried to make a prototype using the API from the author of Klaxon, and I'm a bit disappointed... When the screen is off, the light sensor sends random data (especially between 300 and 450 lumens).

Yes, when the screen is off, it looks like the light sensor is also deactivated. I also had the idea, to automatically lock the phone, when in the pocket, but then the ligh sensor does not work.

[ZuinigeRijder]

Hopefully you can keep us SE Xperia X1 users in mind too. We don't have a g-sensor but we do have the light sensor :-)

You could try TouchLockPro, if it works on SE Xperia X1. But I do not know if the same software libraries are on that phone.....

[johnchan78]

Yes, when the screen is off, it looks like the light sensor is also deactivated. I also had the idea, to automatically lock the phone, when in the pocket, but then the ligh sensor does not work.

Damn that is quite disappointing... there must be a way to reset the light sensor after screen deactivated or something... :-(

[ZuinigeRijder]

I just uploaded version 1.9 on my new website.
See TouchLockPro thread for more details. (http://forum.xda-developers.com/showthread.php?t=444215)

Many thanks to Dennis van de Sande, alias Mr_Q from XDA-Developers, for sponsoring/donating the website and domain.

I wish you a merry christmas and a happy new year!

[quicksite]

I just uploaded version 1.9 on my new website.
See TouchLockPro thread for more details. (http://forum.xda-developers.com/showthread.php?t=444215)

Many thanks to Dennis van de Sande, alias Mr_Q from XDA-Developers, for sponsoring/donating the website and domain.

I wish you a merry christmas and a happy new year!

ZuinigeRijder, thank you for all your hard work. I just wrote a note of praise (http://forum.xda-developers.com/showpost.php?p=3068912&postcount=701) re your excellent website documentation of the app and the process you used -- over on the App release thread. You can see it here :)
http://forum.xda-developers.com/showpost.php?p=3068912&postcount=701

Now, my question: I see very clearly that my HTC phone, the Herald (T-Mobile WING), does not have the required hardware/sensors to use this app. So, is there anything on the Wing/ Herald that could serve as some kind of method to try to minimize the problem of accidentally hitting the HOLD button or other undesired app when holding the touchscreen to the ear? :)

And also, related: Are there any dialers out there that could be used to solve another problem -- Once a call is SENT to dial, the numeric keypad gets replaced, removed. So, if I am calling a customer support line, or leaving voicemail for someone, and have to enter a menu #, or extension #, I have to first hit a small target area with my finger to "SHOW DIALPAD". I'm not an engineer so i still don't understand why great dialer software like supbro's iDialer (http://forum.xda-developers.com/showthread.php?t=429984) can't fully replace the built-in dialer, and why simple problems like I just mentioned are so hard to solve :confused:

[pitchbend]

there has to be a way to use the light-/g-sensor to switch screen off/on when in call... i always have problems when making a note or adding a new contact while talking on the phone - as soon as i put the phone back to my ear the cursor jumps to another place.

[iago_00]

I guess using g-sensor to make the screenlight go of when in vertical position+active call would be an idea; integrating light sensor would make it more accurate. I'm willing to see an app that would do this ...

[hilaireg]

Agreed,

I've used a Motorola MPx220 Smartphone (WM2003SE) for years and although it does not have G-Sensor & Light Sensor capabilities, the Lock & Security functionality is bar-none the best IMHO.

When I enable the security function, the keyboard automatically locks after elapsed time (30 sec in my case) and the Left Soft Key display 'Unlock' and the Right Soft Key is 'Blank'. The Today screen is visible and pressing *any* key or Left Soft Key displays the Enter Simple PIN Password screen - the Left Soft Key display 'Unlock' and the Right Soft Key displays 'Cancel'. When a call comes, in the Left Soft Key displays 'Answer' and the Right Soft Key displays 'Reject'.

IMHO, it would seem that the functionality required would be:

Stand-by Operation
- Disable screen and most buttons when Locked - present today
- Display Today screen - present today

- Pressing the 'Unlock' Soft Key (or pulling stylus) unlocks the device if Password is not set
- Pressing the 'Unlock' Soft Key (or pulling stylus) displays the Password screen if a Password is set then Unlock device on success else it returns to display Today screen


In Call Operation
- The screen should remain on if the call is initiated by the device - for more than 5 seconds for interaction; voicemail, call trees, etc.
- The screen should 'turn off' when near the ear and 'turn on' when moved away via G-Sensor and/or Light Sensor


Configuration
- Indicate which applications cause auto-unlock
- Specify which hardware buttons remain unlocked
- Option to switch from In-Call Status to Keypad
... existing TouchLockPro functions


Since this type of functionality has not yet been made available in an application; I assume that there are limitations preventing developers from achieving the intended behavior.

That said, TouchLockPro is getting there :)

Cheers,

[quicksite]

Without dismissing the rest of your presentation for solving accidental touchscreen activation in-call, or in pocket, THIS is the part that I care about the most... in fact it's sort of ALL I care about. Because for all occasions OTHER than my making or receiving a phone call, I can use S2U2 to lock the screen from accidental screen-touches.


In Call Operation
- The screen should remain on if the call is initiated by the device - for more than 5 seconds for interaction; voicemail, call trees, etc.
- The screen should 'turn off' when near the ear
and 'turn on' when moved away via G-Sensor and/or Light Sensor


My quibble with your first line above, in the quote, is that many a time one calls a company, or doctor's office, or tech support line -- and encounter a menu tree where you have to listen and enter #s -- so the keyboard should be activated by default... but in my view, it stays active until I put that phone to my ear -- or -- immediately re-appears when I pull the phone away from ear.... Because there are times you have to wait 15-20 minutes or more on hold and then finally you get inot a phone queue where you have to enter more phone number and account # information. And there is currently no phone I have used or see that "just handles this" logically. Stated again. LEAVE THE KEYBOARD ACTIVE -- blank it and the whole screen and buttons when phone approaches the ear -- immediately as phone moves away from ear, return everything to former state -- keyboard displayed, all device hard buttons working, and after I enter data, same thing, as it goes to ear, blank the screen and hard buttons.

I am less interested in the LOCK-PINCODE component of all of this. I would praise dah good lawwd above if I could just get something as simple as above! :) It would handle 95% of all my phone needs and accidental touch screw-ups when phone is in pocket and the phone rings, and I am fishing the damn thing out of my pocket along with the headpiece that is often plugged in -- and by the time i get all that out of my pocket, it's a miracle if I have not pressed a hard key ending the call, or a soft key putting it on hold, or 1001 things OTHER than enabling me to press the green button and say "hello!"

9 times out of 10 when I receive a call, i have to call someone back from all the disruptive crap and margin for error that some engineers at MS forgot to consider as "human factors" :)

[Prof.Kamil]

well..

fyi the nokia 5800 have this as well

and it uses the light sensor to do that

so we still have hope that this could work on our phones

[golightlygl]

To those of you have "nearly" got a solution, may I make a suggestion.

It appears that the biggest problem is that the light sensor goes off when the screen goes off. OK, so let's keep the screen on.

Pocketshield is a great locking app (and I know others really like S2U" as well). I don't know about S2U2 but Pocketshield will "lock" the screen rather than turn it off after a call has been placed. And you can easily disable the HTC screen-off routine with a registry hack.

If you have developed the code that detects "away from face" mode, this can simply be used to call Pocketshield's unlock routine (and even better if it can display the KEYPAD at the same time for DTMF entry). And the "close to face" mode can call his "lock" routine.

I know you'll have to interface with pocketshield but the author seems wiling to help develop his app. The only issue I can see is the conflict between community-based support and his paid-for app. But maybe he can be encouraged to donate a proprotio of income to XDA-Devs if he incorporates your code.

It seems that various bits of this requirement are out there - we just need to bring them together. When I say "we", of course I mean the clever ones amongst you - not me!

[quicksite]

To those of you have "nearly" got a solution, may I make a suggestion: (working cooperatively)

I'm just looking at this whole thing from afar, and though I know that in order to connect all the dots of various scenarios and sequences of when one wants the screen to lock and when not, it's quite a puzzle to figure out, nonetheless I'm astounded by how really ESSENTIAL this capability is, yet WM or HTC haven't solved it? To me it's like having a toilet designed, but someone forgot to solve the little hooking gizmo that gets controlled by the flush handle to lift the seal that allows the tank of stored water to flow.

Sorry for the analogy, but I am rather fascinated in a befuddled way: I have never seen a more responsive thread and application author than ZuinigeRijder and his Touch Lock Pro thread. And this is a salute, not a dis. But despite all the controllable elements, still, large percentages of people are having problems achieving their basic functional desires.

I'm just amazed this is so vexing of a problem -- and that the touchlockpro version only works with X-class of phones, so here in this thread we're not even eligible for that fix, when it gets ironed out.

It appears that the biggest problem is that the light sensor goes off when the screen goes off. OK, so let's keep the screen on.

Pocketshield is a great locking app (and I know others really like S2U" as well). I don't know about S2U2 but Pocketshield will "lock" the screen rather than turn it off after a call has been placed. And you can easily disable the HTC screen-off routine with a registry hack.
I'm a S2U2 user, and I have not yet been able to determine which settings override which other settings. It's a super-featured app -- yet I still have probs with playing music when the screen blanks using an app other than his own s2p.

My point is that for all we know, the correct functionality already exists, it's just a matter of, as you say, setting it properly so that apps coordinate this intention with each other.

If you have developed the code that detects "away from face" mode, this can simply be used to call Pocketshield's unlock routine (and even better if it can display the KEYPAD at the same time for DTMF entry). And the "close to face" mode can call his "lock" routine.

I know you'll have to interface with pocketshield but the author seems wiling to help develop his app. The only issue I can see is the conflict between community-based support and his paid-for app. But maybe he can be encouraged to donate a proprotio of income to XDA-Devs if he incorporates your code.
I see that as a huge obstacle -- as in -- not a chance in hell -- and I think correctly so. This whole issue is going to get chafed at, I predict, as the "App Store Wars" heat up. But for now, to me the better collab is A_C and s2u2 than a for-fee piece of software mixed in with XDA-community code.

It seems like we need to find a leader with stature, like the King of Spain or Queen of Englad to convene a Summit whereby we ask A_C to help solve this problem that everyone needs solved :rolleyes:

[golightlygl]

Sorry to be a bit thick. Who or what is A_C?

[quicksite]

Sorry to be a bit thick. Who or what is A_C?

No problem, sorry... so many acronyms around here! In this case this is the username of the author or "Slide To Unlock 2", or "S2U2". He has also authored other finger-friendly apps that many people find essential, such as "S2V" (Slide to View) and "S2P" (Slide to Play).

You can see more about, and download, his apps at his website: http://www.AC-S2.com .

[Ston]

http://forum.xda-developers.com/showthread.php?t=488991

Just in case someone comes across this thread... the above does this.

[RaudelJr]

http://forum.xda-developers.com/showthread.php?t=488991

Just in case someone comes across this thread... the above does this.

I would like to say that the link in the quoted text above is the solution!!!!!!!!!

All of you with g-Sensor hardware won't regret installing it!!!

Raudel

[psycho_maniac]

touch in call is the best solution for this i love this app

[clamsg]

This is what makes me miss my iPhone a great deal. The proximity sensor in the iPhone not only works but works great, highly responsive and extremely accurate regardless of how many times I put to my ear or away from my ear.

[spastickyle]

I think Touch In Call is the perfect solution! It even beats the iPhone's proximity sensor with it's added features (I love the auto-speakerphone feature).

[microbespecialty]

Here's another program that does the same and works with the Samsung Omnia for those not using an HTC device.

Auto Call Locker (http://www.modaco.com/content/i9x0-omnia-http-omnia-modaco-com/290425/autocalllocker/)