Related
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
So my Sensation started freaking out after about a week of usage. First the lock screen was almost unusable, and then it took on the characteristic of being stupidly slow and stubborn. Fast swipes wouldn't register, and the carousal was all but non existent.
Anyway, I stumbled upon the HD2 forums and disabling auto-rotate fixed touch screen and lock screen issues for some peeps over there. So I tried it, and, alas! It fixed it! My touch screen now registers fast swipes! I even re-enabled auto rotate and it still works fine.
Just saying, this worked for me. Hopefully it can help someone else.
EDIT: Fast swipes are indeed back, but the stupid lock screen issues have returned as well xD. I've pretty much come to the conclusion that it sucks that T-mobile customers have to choose between the G2X or the Sensation for dual core devices, because the're both glitchy as hell. This is really beginning to frustrate me......
Did this work for anyone with issues?
Send your device back, that's a legit issue man. Don't even try to tough it out. Wish I could test this out for you, wait not really cause then I've have touchscreen responsiveness problems as well, but mine's been running soothe since launch day.
Sent from my HTC Sensation 4G using XDA Premium App
it would be nice if it was that simple. It is a strange issue and for a lot of people their phone starts working again all of a sudden, no problems at all, but it's only temporary. Its a coincidence that disabling auto rotate fixed it for you. Just like 20 other things in the big thread about what fixed the touchscreen for other users. Almost everybody's posted fix doesn't work for anyone else. Mine has started back working great too, but it messes u again. Always what i thought fixed it the first time, doesn't fix it the next time. It's gotta be hardware. If it was software, it would make perfect sense for a factory default to fix it. I haven heard of anybody having the issue when the phone was brand spanking new. If returning it to that state doesn't fix it, hardware is usually the problem. Unless, like i posted in the other thread, if a factory reset isn't actually setting it back to the exact settings it was at new. Maybe its not wiping everything. That's the only way i could see it being software.
Has anyone experienced ghost touches and gestures? I know the oneplus launcher has a sensitive edge so if your palm was touching the edge it would bring up the notification bar, had to disable that feature, but has anyone else experienced random ghost touches or is it just me and I should return the device?
I'm experiencing it also, and I'm using Nova so I think it's the phone a d not the launcher.
Fatmonk8 said:
I'm experiencing it also, and I'm using Nova so I think it's the phone a d not the launcher.
Click to expand...
Click to collapse
I've noticed it randomly when the phone is not even being touched, I'm not sure if it has something to do with gestures, I've see reviews on TMobile that someone had the same issue that was much worse than I described and returned the phone.
I have to have a case on our I got the screen. Artifact of the curved glass
Yeah I've noticed on some cases it can cause issues, but this is something a firmware update can fix.
I've had this issue also and it seems to be app dependent. Cpu-z triggers it. Check this out: https://drive.google.com/file/d/1-8-O6UchZGLGUA95yJLjQSaqKhbYjljo/view?usp=drivesdk
Using Nova Pro and no never had this issue yet.
Yeah I've had random apps trigger it but then it won't do it at all, not sure how I can even replicate it.
Happens to me too. Interesting sidenote: Switching to 60hz fixes the problem for me.
Yep. Also seeing this issue. Have had it happen twice now, once yesterday and once today. No idea how to replicate. Seems random.
You think it's a hardware issue? Or software?
No such issue, maybe faulty phone. I'd return immediately
haven't had this issue either.
Could you try the CPU-Z app with 90hz enabled? Just keeping this app open makes my 1+ go crazy.
Try taking off the screen protector
I too am having the issue. At first I thought it was the screen protector as well, but taking it off didn't fix anything and I immediately regretted it. The issue is pretty sporadic and going to 60hz does help. I mostly noticed the issue inside the Google Messages app (my primary texting app). And also the CPU-Z trick worked too, my screen went ape sh*t. I'm gonna give OP a week to fix this through software or I'm gonna have to do an exchange.
No issues here. Using Google messaging app n Nova pro.
I've got this issue on mine as well. Started an RMA. If it's not fixed within 2 weeks, I'm sending it back.
https://www.youtube.com/watch?v=GT1U8ilxy4k
Short clip showing the fault:
https://www.youtube.com/watch?v=N-7GnF7AUpQ
I actually had an issue today where I was watching YouTube and my phone started freaking out like I keep touching the screen, something is definitely wrong, but I don't want to go thru T-Mobile to replace it.
NukeBomB3000 said:
Happens to me too. Interesting sidenote: Switching to 60hz fixes the problem for me.
Click to expand...
Click to collapse
Can confirm switching to 60Hz fixes it.
If you enable "Show taps" and "Pointer location" in Developer options it's quite easy to see when it happens. No idea what triggers it, but CPU-Z is definitely the worst one.
I have tried reinstalling the os, root and unroot. Before the newest update I could get into the debug menu, *#808#, there I could see that the accelerometer is giving faulty data. After the update I can't even get into that menu again.
Seems to be a faulty sensor and something with the software. My facking phone is 2 days old........
Anyone else having this problem? Any ideas?
Yeah autorotate sucks for me. Anytime I'm on YouTube and try to watch in landscape it's hit amd miss and i have to keep moving phone to get it to work
hallo dare said:
Yeah autorotate sucks for me. Anytime I'm on YouTube and try to watch in landscape it's hit amd miss and i have to keep moving phone to get it to work
Click to expand...
Click to collapse
Damn. Sounds bad too.
I noticed this while playing Asphalt8 using the accelerometer to steer. It would work for a bit then get stuck trying to drive me into the side of the road!!!
Thinking it may be a bug in the game, I looked at the raw sensor data using Physics Toolbox Suite and saw the same thing. The sensor outputs sensible data for several seconds, maybe even a couple of minutes. Then the values stop changing for about 12 seconds. The length of time the sensor works for is random but the 'dead time' is always about 12 seconds!
Has anyone found a solution to this? Even a hint as to whether it's a software or hardware problem so I can decide if I should send the phone back or wait for an update.
Thanks
Okay thank God someone else has the same issue. I was wondering what was so wrong for the longest time ?
Extremely annoying issue.
It's a software issue. Confirmed.
When I reboot the phone the issue dissapears. Meaning there is something wrong in the OS that tilts the gyroscope readings. At least there is a workaround... Hope OP fixes it soon
I used an OnePlus 5 for 2 years. Now I bought a 7 Pro. I'm wondering doing a downgrade due to this issue. Incredible how a company like oneplus and a premium phone has a software bug like this and there's still no update yet. Months without an update...
The fingerprint sensor also has a bug... Sometimes it simply doesn't work. The touch stops...
OnePlus! Where are you?
anybody got this problem? Fingerprint scanner in my xperia 5 III started asking me to clean it so many times and then just stopped working. I think somethings is wrong because when i am touthing it is buzzing but do not recodnising my fingerprint. Tryed to reset phone but still the same resolts. Sometimes its working but most of the time is not.
Help anybody?
someone just reset his fingerprints and this helped but i also red poeple faced same problems like u.
sad to say but souds like a hardware problem at your phone maybe.
what Android version are u.??!!!
12 and i am pretty sure its a hardwere cos i have don already evrything i could to fix it, and i am sending it back to tech support
One other thread had a suggestion of recording one fingerprint twice.
My fingerprint scanner stopped working at all recently... I think it worked worse after android 13 upgrade, but honestly I believe that it's a hardware problem... Is there a chance Sony will move to scanners like in Samsung and iPhone, that appears on the phone screen?