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 ?
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 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.
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.
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.
fireweed said:
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.
Click to expand...
Click to collapse
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
lpaso said:
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.
Click to expand...
Click to collapse
I'm looking for this.. If you find a solution send me a PM, I will do the same
Thanks!
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
lpaso said:
Hi,
I searched the forum for an existing app that could do this, but I didn't find anything.
Click to expand...
Click to collapse
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
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?!
I think it's a fantastic idea to solve a VERY FRUSTRATING PROBLEM
lpaso said:
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
Click to expand...
Click to collapse
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.
fireweed, have you contacted A_C, author of s2u2 ?
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...
fireweed said:
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.
Click to expand...
Click to collapse
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 ?
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.
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...
lpaso said:
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...
Click to expand...
Click to collapse
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?
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.
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.
Hennyb said:
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.
Click to expand...
Click to collapse
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?
Section9 said:
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?
Click to expand...
Click to collapse
No, you're right. It uses an iR sensor to know if there's something near the phone.
As we all know, the GPS is very spotty on our Captivate and very often we have problems getting a good satellite lock. However, after work one day I
opened up Google Nav to route myself back home. As usual, Google Nav gave me the usual "Searching for GPS" and it stayed there for at least 5-10 minutes.
Frustrated, I hit the power button and turned off the display. 20 seconds later, the female voice started shouting out directions?? I turned on the display and sure enough I had a lock. Also interestingly, 5 seconds after I switched on the display, the blue circle appeared over my position and I also lost my lock. I turn off the display, lock again. I do get a good lock once and a while with the display on, but if I'm having trouble I'll switch off the display and without fail I'll get one and I'll use the voice prompts to guide me. Anyone else notice this?
I'm running a completely stock GPS settings.
Complete coincidence, would kind of suck for Samsung if this was true.
That's odd. For me, whenever the screen turns off and locks for my Captivate, the GPS shuts down, losing whatever lock it previously fixed if it had one. I always get mad when my screen turns off when I'm using Google Maps as a result...
soloDOTcom1185 said:
That's odd. For me, whenever the screen turns off and locks for my Captivate, the GPS shuts down, losing whatever lock it previously fixed if it had one. I always get mad when my screen turns off when I'm using Google Maps as a result...
Click to expand...
Click to collapse
When you use google maps, yes, the gps shuts down when you turn off the screen. But if you were to use google navigation, the gps stays on even when the screen is off.
I don't remember where it was, but I remember some ceo or engineer claiming that the large screens on most new cell phones were likely to cause major gps issues because of interference. I think it was someone who worked within the GPS industry themself (think: Garmin).
Now I don't know if this person was just speculating or not but it's something to keep in mind.
Well I don't know about anyone else but DAMN! It's true! For me anyway. Screen off, navigate works. Turn the screen on and it immediately stops working and starts searching for gps.
Sent from my GT-I9000M using XDA App
Could be why they replaced the antenna in the Nexus S. A better/different antenna may be more resistant to interference.
I have the screen set to always on (no time out) when I have it in the car, it stays on fine while listening to music or if it just sitting there doing nothing, but no matter if I get a call or I make a call -- the screen will always turn off after a couple seconds even though the screen is set to always stay on, also as soon as the call ends -- the phone automatically locks and I have to log in / unlock it every time. I know on the old Froyo ROMs it would stay on if I had it set to always on -- didn't matter a call or not, it stayed on like it is supposed to do and it did not automatically lock either. I am on the Weapon 3.0ROM and I am using the same widgetsoid app as the the switching mechanism for the "always on" screen setting in a widget on one of the home screens. I have checked the widgetsoid settings and there is no definition between call settings and normal data for the screen time out. Under settings in the main menu, there is no toggle to enable/disable the proximity sensor either, but since the phone face has nothing close to it when it is mounted in the car (like it would be if you had it up to your ear), I don't think that this is the proper setting to manipulate. I really believe that this is a timing setting, and I am wondering if it is separate setting that can be changed or linked to the normal screen time out settings.
Is there a way to stop the screen from timing out on the Weapon3.0 Rom during phone calls and then automatically locking the phone when the call ends? its getting a bit annoying and any help would be appreciated.
Am I really the only one experienceing this?
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
crockashat said:
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
Click to expand...
Click to collapse
I think that is an unwanted "feature" of the 2.3.3 Gingerbread rom. I am not sure of anyway around it without changing to a rom that is not 2.3.3 based.
I'm having an issue where it takes fund minutes to lock location on the phone. The problem is most noticeable on Waze. I turn Waze on every time I get in the car (the speed traps alone are worth it), and sometimes it's half my trip before it locks on.
The location is set to high accuracy, and it does eventually lock on. My 6p would lock on in one second.
Anyone else? Thanks
lanternca said:
I'm having an issue where it takes fund minutes to lock location on the phone. The problem is most noticeable on Waze. I turn Waze on every time I get in the car (the speed traps alone are worth it), and sometimes it's half my trip before it locks on.
The location is set to high accuracy, and it does eventually lock on. My 6p would lock on in one second.
Anyone else? Thanks
Click to expand...
Click to collapse
I've seen issues in Waze as well, with both GPS lock and the Compas going screwy...
Have you guys tried running gps status or gps toolbox?
What settings do you have selected in location settings?
On my v10 if I enable the additional low power Qualcomm IZat location estimation option, gps runs all screwy.
Id like to know if gps is hit or miss, as its another of the main features I need and use on a daily basis, along with Ok Google..
My Pixel is now locking GPS in a few seconds after I open Waze. Probably even faster than my 6P.
For anyone else having these problems, here are all the steps I did (not sure which if any of these actually solved the problem)
1. Uninstalled Waze. Turned off Location. Rebooted into Safe Mode (Long Press "Power Off")
2. Once in Safe Mode, turn location back on, open Google Maps outside, let GPS lock (that time still took a while) and use navigation for a while
3. Rebooted the phone again into safe mode. reopened Google Maps and let GPS lock on
4. Rebooted the phone normally, open Goolge Maps first to make sure GPS was working. Then installed Waze
It's been working pretty well for the past few days.
I'm still seeing issues with the compass, I get a GPS lock quickly, but it always shows I'm pointing 100-160 degrees off from my actual heading. Tried using GPS status to calibrate, it now says I'm calibrated, but I still see the issue, even in GPS Status.The compass points in one direction, then once I start moving, the GPS corrects the heading to my actual direction...
I've never had this issue with any other phone, very frustrating.