Disable Zoom and Teams from being considered "calls" (phone icon) - General Questions and Answers

The camera prox sensor shuts off your screen which is useful when actually making a phone call but zoom and teams often involves screen sharing with the phone not being put up against your ear and this is a huge pita. How can I tell Android to exclude those two apps from being considered "calls" so the camera prox sensor stops blanking out my screen when my hand or finger happens to barely pass over it?
Thank you!

Related

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

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.

Tasker : Help needed to create profile

Hi,
I would like to use Tasker to control screen on/off times based on following conditions:
1) Keep screen on when reading/using mobile:
a)IF SCREEN IS ON: If handset is in vertical position (reading position), either in portrait or landscape depending on orientation set in android then screen should stay on. This would presume mobile is being used.
b) When handset is laid down on table then screen should turn off after 7 secs automatically or when screen is manually turned off.
note: It would be nice to have a window period of 10 secs after screen off wherein if the handset is picked up within that period, (after the initial 7 secs and before another 10 secs) then screen automatically turns on.
2) NOTIFICATIONS
If notifications are received, have a window period of 15-30 secs where if position of android is changed from desk horizontal to vertical then screen automatically comes on without the need to press power button.This presumes we picked up mobile to view the notification event.
Again first rule applies and screen stays on when reading and turns off auto or manually as per first rule
I have tried but not able to configure rules.
One conflict in mind:-
What if mobile is kept in trouser pocket and notifications are received? Here the gyro won't change as it will go from vertical to vertical position....how to deal with that? Also rule 2 should not auto trigger upon receiving notifications, sensing orientation is vertical when in trouser pocket.
Any help?
Thanks in advance
About the conflict, I think I saw that you can implement a profile that check if your face is in front of the tablet or not (like on S3).
As a personal comment, I would go all way to this aproach: check if you are in front of the camera and decide when to turn screen on.
okty2k said:
About the conflict, I think I saw that you can implement a profile that check if your face is in front of the tablet or not (like on S3).
As a personal comment, I would go all way to this aproach: check if you are in front of the camera and decide when to turn screen on.
Click to expand...
Click to collapse
Hi,
The problem with using the front camera is that it will cause battery drain. The camera would constantly have to keep checking for movement and this would definitely drain battery. I am more inclined to use the gyro for this.
I agree with you, but you can at least double the gyro with camera check. even if it will consume some battery, it will avoid other problems.
Or maybe you can also use the proximity sensor?
Another way I can think is to try and detect the shakes (combination of proximity and gyro). Considering the power of Tasker, I think it can be done.
If you manage to succeed, please let me know. I am also interested in something like this, I just never have the time to build such complex scenarios.
okty2k said:
I agree with you, but you can at least double the gyro with camera check. even if it will consume some battery, it will avoid other problems.
Or maybe you can also use the proximity sensor?
Another way I can think is to try and detect the shakes (combination of proximity and gyro). Considering the power of Tasker, I think it can be done.
If you manage to succeed, please let me know. I am also interested in something like this, I just never have the time to build such complex scenarios.
Click to expand...
Click to collapse
I could not get it to work thats why asking for help.

Changes after installing 30O OTA

So overall, great update to 4.4.4
But how would I go about changing just one aspect of the new update?
I would like to keep everything but take out the way the phone just disables anything involving gestures if there's something within close proximity to the sensor. First off, I never really had an issue with the phone turning on while in my pocket, or the torchlight turning on in the same situation. But now with the new update, I can't use the pause/play, next track, back track gestures because my finger accidently passes the sensor or a piece of paper is on top of the sensor OR the sensor "senses" the denim in front of it while the phone is in my jean's pocket.
Would I be looking for specific code in system files? Can I just go into build.prop and disable proximity sensor verifications? What am I even saying? Total noob.
No you cannot go into the build.prop and manually disable that feature. Its a feature thats built into the ROM and that would consist you of downloading from source and removing it yourself.
Thats too much work, if you really want the proximity sensor check off, you're best off downloading a custom ROM with this feature or you can just not touch the proximity sensor. The proximity sensor is at the top of the screen, not sure how you accidently passes the sensor and would hide it. The phone scans whether or not its blocked quite fast that it should realize that its not blocked by the time your hand reaches to the touch screen.

Fingerprint symbol always visible - possible burn in display?

Hello guys
I've ordered my Nex and cannot wait to get my hands on it (Hurry up gearbest!).
One thing bothers me:
On a youtube video I saw recently the reviewer mentioned that the display of the nex is super amoled. He then explained concerns that if the fingerprint logo - to show the position of the in display finger print reader - is always visible on the display this could result in a burn in on the Nex display.
What are your thoughts about this?
Thanks and BR
It's not always visible, only when you need it or when you shake your phone.
"to avoid burn-in is to ensure that your display doesn’t show the same thing in the same place for LONG periods."
So does the Nex have a pocket mode which prevents a wake up? - I mean this thing gets moved a lot in the pocket.
I would say yes but im not sure where ...
In constant movement the scanner is off.
This phone has a sensor that detects when the phone is near your face and shuts the display off when your on a call. This same sensor knows when your phone is in your pocket and prevents the fingerprint from turning on when in your pocket.

Question Hyperactive and misplaced Proximity Sensor

Hey everybody,
from my P6P I was used to being able to navigate my smartphone whilst making a call over the speakers or listening to a voice message over whatsapp.
Now, when doing this, my 7P will again and again shut off the screen because the sensor is triggered. This seens really out of proportion, since it happens far down and only on the left site (i attached an image with the blue trigger zone).
Is this sth you experience as well and can check for me?
Thanks!!
I was also experiencing this annoying issue. It was driving me crazy.
Was able to find a fix though: activate Developers Options and open it. Look for Quick Settings Developers Tiles menu and tap to it. Then tap to Sensors Off to enable it. This will add Sensors Off tile in tiles list in the scroll down top menu of your phone. If you activate (tap on it) it will disable all sensors, proximity sensor included.
The changes will apply immediately so you can do this whilst on phone/video calls and then enable it back after the call. Works like a charm.
Whilst its tempting to leave it disabled all the time, I won't recommend it as it disables all the sensors, for example, automatic screen brightness sensor or auto rotate sensor, so not very convenient.
Yeah, the cut off point is pretty early. I'd recommend using one handed mode to reach for the top of the screen or just trigger speakerphone.
VirtualWaver said:
I was also experiencing this annoying issue. It was driving me crazy.
Was able to find a fix though: activate Developers Options and open it. Look for Quick Settings Developers Tiles menu and tap to it. Then tap to Sensors Off to enable it. This will add Sensors Off tile in tiles list in the scroll down top menu of your phone. If you activate (tap on it) it will disable all sensors, proximity sensor included.
The changes will apply immediately so you can do this whilst on phone/video calls and then enable it back after the call. Works like a charm.
Whilst its tempting to leave it disabled all the time, I won't recommend it as it disables all the sensors, for example, automatic screen brightness sensor or auto rotate sensor, so not very convenient.
Click to expand...
Click to collapse
Nice find and it may help some people some of the time. However, would it not be better to just turn on Screen Attention? YMMV
xflowy said:
Hey everybody,
from my P6P I was used to being able to navigate my smartphone whilst making a call over the speakers or listening to a voice message over whatsapp.
Now, when doing this, my 7P will again and again shut off the screen because the sensor is triggered. This seens really out of proportion, since it happens far down and only on the left site (i attached an image with the blue trigger zone).
Is this sth you experience as well and can check for me?
Thanks!!
Click to expand...
Click to collapse
I had that same issue on the P6P and the P7P. It's annoying

Categories

Resources