Related
[FONT="]On the touch pro, the screen off during a phone call feature is a big annoyance especially if you have to enter number after dialing (passwords, pins, or any other touch tones)[/FONT]
[FONT="] [/FONT]
[FONT="]I absolutely hate the iPhone with a passion. However, I do admire the heatsensitive screen during a phone call. When you put the phone up next to your ear the screen turns off to avoid keypresses, and when you bring it away from your ear the phone screen automatically turns back on. [/FONT]
[FONT="] [/FONT]
[FONT="]I'd like to emulate this function on the touch pro. I say emulate because obviously the touch pro does not have a heat sensor. My initial thought was using the accelerometer configuration in the Gyrator program. [/FONT]
[FONT="] [/FONT]
[FONT="]I've disabled screen off and quick sleep via Shaps advanced config tool. I added the event in Graytor that when in the Phone program and in portrait orientation then turn screen off.[/FONT]
[FONT="] [/FONT]
[FONT="]However, there are some issues with this. I'd like to do this when call only, not in the entire phone program. Also, I can't seem to get the screen to turn back on when the phone is returned to face_up orientation.[/FONT]
[FONT="] [/FONT]
[FONT="]If anyone has any insight, or if this issue has been already posted, or if you have any other ideas I'd love to hear them. [/FONT]
This cab will keep the backlight on during calls: http://www.ppcmobility.com/forums/showpost.php?p=1885&postcount=13
I think what you're better off looking for from a development perspective is something that uses the light sensor (it's just inside of the headset speaker) so if it's dark the backlight is off...light and it's on. Currently the sensor dims the backlight under preset conditions but does not control on/off.
Thanks for the response. I can just make the regedits myself for the backlight always on. But I don't want to do that because then I can press keys on accident.
I do like the idea about the lightsensor though.
you can install slide to answer which includes a canvas that covers the screen like this:
hey, I was trying to avoid that solution,thanks for the post though,
anyone have any ideas on how to use the light sensor or gyrator to do this?
I disable the phone skin and my phone stays on during phones calls. It also got rid of the ring/caller ID delay.
but disabling the skin also gets rid of bluetooth notifier wether its on or not and of course you have the old buttons (yuck)
This is going off topic. I am not looking to keep the backlight on.
I hated it too I think this is what your looking for.
-McMex
mcmexican said:
I hated it too I think this is what your looking for.
-McMex
Click to expand...
Click to collapse
The problem with this CAB is that is changes the G-Sensor Polling to a ridiculous number like 10000, and that causes issues with any programs that rely on the accelerometer to rotate the screen automatically.
cremainsc said:
I disable the phone skin and my phone stays on during phones calls. It also got rid of the ring/caller ID delay.
Click to expand...
Click to collapse
Hmmm.. I didn't get that effect when I tried it.
mcmexican said:
I hated it too I think this is what your looking for.
-McMex
Click to expand...
Click to collapse
this has never done the trick for me
or the reg edits completely
NotATreoFan said:
The problem with this CAB is that is changes the G-Sensor Polling to a ridiculous number like 10000, and that causes issues with any programs that rely on the accelerometer to rotate the screen automatically.
Click to expand...
Click to collapse
Until there is a fix for this. I'm curretly using 600GOL's screen tilt app to get my apps to rotate (opera)
http://forum.xda-developers.com/showthread.php?t=465586
NotATreoFan said:
The problem with this CAB is that is changes the G-Sensor Polling to a ridiculous number like 10000, and that causes issues with any programs that rely on the accelerometer to rotate the screen automatically.
Click to expand...
Click to collapse
Oh I dont use any of the G-Sensor apps I only go to landscape when I use the HW keyboard which is rarely so I wouldnt have noticed. For me if it was between the G-sensor apps or the phone turning off during a call I would choose the phone not turning off. Sorry if I caused any issues to anyone.
-McMex
mcmexican said:
Oh I dont use any of the G-Sensor apps I only go to landscape when I use the HW keyboard which is rarely so I wouldnt have noticed. For me if it was between the G-sensor apps or the phone turning off during a call I would choose the phone not turning off. Sorry if I caused any issues to anyone.
-McMex
Click to expand...
Click to collapse
i would take this 'hit' as well... i see it's not too definite of a fix but... the screen turning off during calls is weak.
*installs no sleep*
I don't think anyone is understanding what I am asking for. I am not asking for a way to keep the screen on during a phone call or to avoid turning it off.
I am looking for a developer to make a program that uses the TP's light sensor durning a phone call to AUTOMATICALLY turn screen on and off.
Example:
When there is full darkness(Phone is up to your ear) - turn the screen off
When there is light shown(Phone away from ear) - turn screen on
I need this but only during phone call.
I am not an expert but I think you have a problem here as the light sensor doesn't work in sleep mode
No it's not a problem.
It's a feature I want implemented using the light sensor.
lol, i think it is rediculious that people dont read his question (who can create a file/program that automaticly change with screen on/off).
Looking forward to see a change, because the screen goes ON or OFF manually isnt the solution.
Whoever makes this guy's program will be a hero.
I like that the screen turns off when I put the phone to my ear but it is annoying to have to turn it on again to enter pin numbers. Especially if you use the autolock feature as this means when the phone is awakened its back on the home screen. By the time I get back to the phone app and into the keypad it's often too late to enter my pin!
Hi,
I just saw today, that there was a very weak red light just next to the proximity and light sensor. It looked like it was flickering at a very high rate!
I tried to restart the phone normally, but the light didn't disappear. After that I tried a reset by holding the power button down for 10 seconds. That made it vanish.
What the f**k was that all about???
Best regards
Casper
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Moved To Q&A
This is best in the Q&A section, as it been written as a question.
h.han said:
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Its The Goverment Spyin On us...Making Sure We Dont Flash Anything Or Even Root...If So It Will Say Tampered And The S.W.A.T. Team Will Come Crashin in Our Homes...
That red light is in fact the actual proximity sensor and it's in use while in a call. If you where not in a call then that was a strange occurance unless you ran some of these sensor testing apps...
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
cawith said:
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
Click to expand...
Click to collapse
That was an odd one... maybe it was a temporary fluke? Strnag nonetheless...
I often use face unlock. The red light turns on when the front cam turns on.
Sent from my HTC VLE_U using XDA
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
decalex said:
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
Click to expand...
Click to collapse
Same here. Have to restart to get it off again. Any help? (TrickDroid 4.3)
Anytime you make a call by any means other than handset to your ear, the proximity sensor will come on and stay lit until reboot or until you make another call via handset.
Example:
Place call> turn on speaker phone> hang up - proximity sensor will stay lit after call;
To fix do this:
Place call from handset (not using speaker phone or hands free) and hang up right away, or reboot device and light will go out.
Same seems to go for calls through hands free as well.
These guys are lying its a bomb isn't it obvious flashing red light HTC controls it if u do something they don't want u to do boom ur hands are no more why do u think the phone heats up so much its a warning don't believe me read the thread in forums about heats in the one s another reason they don't want us to remove back well see the bomb :what:
Sent from my HTC One S using xda premium
Hi All,
My One S also does this. I'm finding it a pain to have to make a call after using speakerphone to turn the proximity sensor off again. Has anyone found out what the cause of this is?
I've tried clearing cache partition with HTC support but still no fix.
Hi all, I forgot to mention that the issue on my phone only happens when the call is ended with speakerphone active. If I turn off the speakerphone before ending the call it does not happen.
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Sv3TL10 said:
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Click to expand...
Click to collapse
You maybe have turned off Viber doing this: http://www.boards.ie/vbulletin/showthread.php?p=80972874
Does it come back after restarting Viber?
Sometimes a restart fixes the problem.
I had the same problem. I uninstaled Viber and the light disipired.
foner81 said:
You maybe have turned off Viber doing this:
Does it come back after restarting Viber?
Click to expand...
Click to collapse
Later I realized that Viber is the reason. Yes. But now it seems that Viber is fixed after last update, and no red light when viber is turned on
Hello All.
Anybody else have the same issue like me?
I have around 4 seconds lag during wake-up phone with double-tap. But only when phone goes to sleep with camera application opened in front.
This is strange.
If camera app is opened in front and phone goes to sleep - long wake-up with double-tap.
With power button wake-up -> phone wake-up immediately.
If phone goes to sleep with any other application opened in front (home screen, any other app) -> double-tap wake up phone immediately.
I have this issue on few last nougat versions. Today I applied Oreo update and still the same issue.
In safe-mode still the same. I have opened service ticket to HTC but I would like to know if anybody else see the same issue?
I have this issue on few last nougat versions. Today I applied Oreo update and still the same issue.
In safe-mode still the same. I have opened service ticket to HTC but I would like to know if anybody else see the same issue?[/QUOTE]
Just tried mine and seems to work fine on double tap
Hello all. Sorry for long reply time. I still have this issue. Please see attached video.
https://www.dropbox.com/s/pnawcdlo4vbvu2l/U11_DoubleTap.MOV?dl=0
see around sec. 00:22 Only DoubleTap when camera application is on top generate this issue. Other combinations wake up phone quick.
nedalnib said:
Hello all. Sorry for long reply time. I still have this issue. Please see attached video.
https://www.dropbox.com/s/pnawcdlo4vbvu2l/U11_DoubleTap.MOV?dl=0
see around sec. 00:22 Only DoubleTap when camera application is on top generate this issue. Other combinations wake up phone quick.
Click to expand...
Click to collapse
Now that I have watched the video,, mine acts the same.
That's a "normal" behavior, on android when the screen brightness needs to change this lag always appear. I develop an app to turn screen off by changing the brightness and timeout times, and happens this same lag in a various devices seems to be an android issue.
So what I did to "hde" the lag was to add a screen with some info like day, date and time.
But on your case there is no solution yet.
Strange. So, why waking up phone with fingerprint scanner or power button wakes it very quick?
Why this "issue" can be seen only when camera app is on top? [if other app is on top phone wake up every time very quick]?
This looks for me like issue in HTC software. Not "standard android behaviour"
nedalnib said:
Strange. So, why waking up phone with fingerprint scanner or power button wakes it very quick?
Why this "issue" can be seen only when camera app is on top? [if other app is on top phone wake up every time very quick]?
This looks for me like issue in HTC software. Not "standard android behaviour"
Click to expand...
Click to collapse
Because camera change the screen brightness, the problem is in changing screen brightness and not the action that you are performing.
ok, this explains question 2. But what about question 1 : "why waking up phone with fingerprint scanner or power button wakes it very quick?" ???
nedalnib said:
ok, this explains question 2. But what about question 1 : "why waking up phone with fingerprint scanner or power button wakes it very quick?" ???
Click to expand...
Click to collapse
That one I don't know for sure, but I think that can be due to the way the it turn the device.
Double tap is controlled by "lockscreen app/kernel", the power button and fingerprint it android native code and kernel, can be that but just htc knows!
Did you tried to ask then about that in twitter or via support emaill?
I just made additional test: manual brightness, full level. The same phone behaviour.
In my opinion this is something in kernel / wake-up procedure. I raised support ticket to HTC.
nedalnib said:
I just made additional test: manual brightness, full level. The same phone behaviour.
In my opinion this is something in kernel / wake-up procedure. I raised support ticket to HTC.
Click to expand...
Click to collapse
Hum, nice ideia.
Ok, let us know what they answer
I have reading the forum and tried contacting 1+7 also but they just say switch off nfc and so on but till today (1 month since I bought it ) I still have the problem . while making a call it goes on hold or connects another call or something or the other happens and the other person gets irritated as if I am doing on purpose. I am still unable to solve this will changing rom be the solution or can someone please help I am fed up with this instrument
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
will try out can you advice reset sensors apps
jonsat said:
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
Click to expand...
Click to collapse
will try out can you advice reset sensors apps
Issue is back again after 9.5.9 update.
IEESH said:
will try out can you advice reset sensors apps
Click to expand...
Click to collapse
Search for "Proximity sensor reset" or similar names. Usually apps like that needs root privileges, btw.
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Superguy said:
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Click to expand...
Click to collapse
Disabling double tap to wake resolved my screen wakeup during calls issue...
UPG to 9.5.10 Plz - Issue has disappeared again.
ram4ufriends said:
Disabling double tap to wake resolved my screen wakeup during calls issue...
Click to expand...
Click to collapse
I'll try that, but I don't think I have that enabled. I disabled NFC for the other tap issues and that helped some.
I really wish there was a screen calibration tool. Samsung curved screens have none of these issues.
Do you have a dirty screen protector?
This is a known bug with the proximity sensor, although, actually, I believe the root cause is something else.
Screen does go black, which indicates the proximity sensor is working and recognizes your face is near... But input is still allowed (meaning it does not lock it).
As a result, during a call your face/ear will press whatever is underneath and trigger random actions.
I believe (I hope?) that OnePlus is aware of this issue and they issue a fix.
I think it was briefly fixed for 9.5.9 and then reverted on 9.5.10 since it introduced other issues.
Quality control has been a bit subpar on the OnePlus 7 Pro builds when compared to my previous OnePlus phones...
Whenever my hand lands on the fingerprint when iam holding the phone it vibrates and its annoying unlike my previous k20 pro i didnt face this problem there must be some toggle or settings that i can enable to remove this problem any suggestions ????? Thank you ....
BassilZ said:
Whenever my hand lands on the fingerprint when iam holding the phone it vibrates and its annoying unlike my previous k20 pro i didnt face this problem there must be some toggle or settings that i can enable to remove this problem any suggestions ????? Thank you ....
Click to expand...
Click to collapse
Add two fingerprints
Sent from my POCO F2 Pro using Tapatalk
Thaiban said:
Add two fingerprints
Click to expand...
Click to collapse
How is tha gonna stop accidental fingerprint detection and vibration??
The solution is to deactivate the fingerprint sensor ?
More seriously, there is no false detection, the sensor is doing its job, as soon as it feels a finger it tries to visualize the fingerprint, I do not see what is boring, If it wasn't so sharp it would be a nightmare to unlock the device !
coyot352 said:
The solution is to deactivate the fingerprint sensor
More seriously, there is no false detection, the sensor is doing its job, as soon as it feels a finger it tries to visualize the fingerprint, I do not see what is boring, If it wasn't so sharp it would be a nightmare to unlock the device !
Click to expand...
Click to collapse
No, you're wrong. It could be set to only vibrate when it detects a correct fingerprint. Which would be much more logical in my opinion. Or give the option to only activate the fingerprint sensor after power button is pressed.
popoyaya said:
No, you're wrong. It could be set to only vibrate when it detects a correct fingerprint. Which would be much more logical in my opinion. Or give the option to only activate the fingerprint sensor after power button is pressed.
Click to expand...
Click to collapse
the vibration is not there to validate the unlocking, something that we see anyway when the home screen opens, but to say that the analysis of the finger starts and that we are at the right place..
The last option might be fine for you, but personally it's a waste of time having to press a key before I can scan my finger, not sure Poco implements this In a future update ! ?
coyot352 said:
the vibration is not there to validate the unlocking, something that we see anyway when the home screen opens, but to say that the analysis of the finger starts and that we are at the right place..
The last option might be fine for you, but personally it's a waste of time having to press a key before I can scan my finger, not sure Poco implements this In a future update !
Click to expand...
Click to collapse
These options should be there for those who want them, they're easy to implement. Options are good I too find it annoying reaching into my pocket and having the phone light up and vibrate unintentionally.
Yeah noticed that also here where it rarely happend with my k20. It's just the new fingerprint placement.
popoyaya said:
These options should be there for those who want them, they're easy to implement. Options are good I too find it annoying reaching into my pocket and having the phone light up and vibrate unintentionally.
Click to expand...
Click to collapse
Yes indeed having more options is positive, I'm just saying that I don't think they will, as it's a pretty special option that very few require.
Normally if you are looking for the device in the pocket, it should not turn on or vibrate because it is deactivated by the proximity sensor, in any case mine remains as dead if I hide the part upper screen..
I hope for you that a function will emerge
For me, it is clear that the "old" hardware fingerprint sensor is much better than the modern software sensor that's imposed on new devices.
But we cannot change this, so yes : some options for lock screen vibration activation-deactivation are welcome. Me too don't like to feel the phone vibration every time I touch accidentally the screen trying to extract something of my pocket, including the phone.
BassilZ said:
Whenever my hand lands on the fingerprint when iam holding the phone it vibrates and its annoying unlike my previous k20 pro i didnt face this problem there must be some toggle or settings that i can enable to remove this problem any suggestions ????? Thank you ....
Click to expand...
Click to collapse
You can disable 'haptic feedback' in the settings, it will disable the fingerprint sensor's vibration too.
Lowxorx said:
You can disable 'haptic feedback' in the settings, it will disable the fingerprint sensor's vibration too.
Click to expand...
Click to collapse
But that disables vibration system wide doesn't it?
oroboros74 said:
But that disables vibration system wide doesn't it?
Click to expand...
Click to collapse
Yes, only for interactions like button press, gestures,etc.