I just started noticing that the proximity sensor seems to be having a difficult time keeping the screen off while I am talking. The screen flashes on and off but it seems to be only when its up to my right ear, which makes sense given the sensor position being offset to the left of the earpiece. No matter how I adjust the phone or press it more against my face, the screen wont consistently stay off during a call when its up to my right ear. I'm not sure if it was like this before the JI6 update but I sure didn't notice it before. It acts like it isn't quite sensitive enough. Anyone else experiencing this?
fooldog01 said:
I just started noticing that the proximity sensor seems to be having a difficult time keeping the screen off while I am talking. The screen flashes on and off but it seems to be only when its up to my right ear, which makes sense given the sensor position being offset to the left of the earpiece. No matter how I adjust the phone or press it more against my face, the screen wont consistently stay off during a call when its up to my right ear. I'm not sure if it was like this before the JI6 update but I sure didn't notice it before. It acts like it isn't quite sensitive enough. Anyone else experiencing this?
Click to expand...
Click to collapse
if you did the froyo update i do believe this is a bug within it. I notice that when i call out it isnt doing it as badly as when someone calls in to me. Hopefully this gets resolved with the official froyo for our phone. I dont think there is any fix for this either.
Im running JH7 though, not JI6 (<-Fixed). So I am still on an official Eclair build. But if it is happening in Froyo too, then that's not very comforting. I wonder if there is a parameter buried somewhere in a service menu that controls the sensitivity.
i used the testing applications (dont remember the code for it) and when you put your finger near it, the screen would turn green and vibrate indicating it detected something.
Well, if you do it quickly, the screen will get stuck on green/vibrate even if nothing is still there. idk if they all do that, or this one sucks.
fooldog01 said:
Im running JI6 though, not JH6. So I am still on an official Eclair build. But if it is happening in Froyo too, then that's not very comforting. I wonder if there is a parameter buried somewhere in a service menu that controls the sensitivity.
Click to expand...
Click to collapse
Are you sure you get JI6?
JI6 = unofficial Froyo build
JF6, JH7 = official Eclair build
There is no JH6.
fooldog01 said:
Im running JI6 though, not JH6. So I am still on an official Eclair build. But if it is happening in Froyo too, then that's not very comforting. I wonder if there is a parameter buried somewhere in a service menu that controls the sensitivity.
Click to expand...
Click to collapse
yea ji6 is the unofficial build. I noticed this too when i flashed it. One way of making sure this is something wrong with that build and not the phone would be to flash back to stock.
Sorry guys. I dont know what I was thinking. Im running JH7 OTA. I got it all screwed up. Didn't mean to confuse everyone. Im going to edit that post.
stuff said:
i used the testing applications (dont remember the code for it) and when you put your finger near it, the screen would turn green and vibrate indicating it detected something
Click to expand...
Click to collapse
Do you know where I could find the code for that test? I just did a search for it but I didn't return anything useful.
I'm also having this quite irritating problem! Running the latest cognition beta.
yup....i was rooted on JI6 beta, and now on the latest cog, and have had the problem. I don't really remember it on eclair though. Updated my gf's captivate to the 2.2 beta and when we talk, one of us ends up muted or hung up on. Between both of us having the same problem, it is inevitable.
This problem is AMAZINGLY annoying, and hope for a fix soon!
The Proximity Sensor is one of the few things that actually work on my phone.
IIRC, proximity sensor is one of the common hardware defects on Captivate along with random shutdown, random button press and GPS.
I get the feeling that if you upped the sensitivity on the sensor (if possible) that the problem would go away. Then again, I don't fully understand how a proximity sensor works so I may be off base.
fooldog01 said:
I get the feeling that if you upped the sensitivity on the sensor (if possible) that the problem would go away. Then again, I don't fully understand how a proximity sensor works so I may be off base.
Click to expand...
Click to collapse
i can't see that being the problem because even if you have it up to your ear, sometimes it still turns the screen on
Related
Hello,
Since it seems like no one has ever asked this question before I've decided to post about it.
On the Droid when you dial a phone number and put the phone up to your ear it locks the phone's screen. Then if you are dealing with a PBX or menu system on the phone that requires you to press a certain option and you move the phone away from your ear to tap the dialer, the screen automatically auto-unlocks. This is, by far, the best feature I have seen in a phone to-date.
Where do I get a dialer that supports that feature (it obviously uses the accelerometer)? Somehow I doubt you can just rip the APK out of the Droid image and have it work on a G1. Or does that feature just not work on the G1 for some reason?
Any replies are appreciated.
--Nickhttp://forum.xda-developers.com/showthread.php?p=6419439#post6419439
nbetcher said:
Hello,
Since it seems like no one has ever asked this question before I've decided to post about it.
On the Droid when you dial a phone number and put the phone up to your ear it locks the phone's screen. Then if you are dealing with a PBX or menu system on the phone that requires you to press a certain option and you move the phone away from your ear to tap the dialer, the screen automatically auto-unlocks. This is, by far, the best feature I have seen in a phone to-date.
Where do I get a dialer that supports that feature (it obviously uses the accelerometer)? Somehow I doubt you can just rip the APK out of the Droid image and have it work on a G1. Or does that feature just not work on the G1 for some reason?
Any replies are appreciated.
--Nick
Click to expand...
Click to collapse
The Droid uses a proximity sensor to tell when it goes up to your ear:
pocketnow.com said:
The Motorola Droid also has a proximity sensor so that the screen shuts off when you hold the phone close to your face. This helps to conserve battery life while at the same time prevent accidental screen input if your cheeks press upon the screen.
Click to expand...
Click to collapse
Not sure how you would do the same thing with the Accel.
That feature actually uses the proximity sensor, which the G1 unfortunately lacks.
jshealton said:
The Droid uses a proximity sensor to tell when it goes up to your ear:
Click to expand...
Click to collapse
Oh. That makes sense.
jshealton said:
Not sure how you would do the same thing with the Accel.
Click to expand...
Click to collapse
Not sure why it would be so hard. Accel can tell how it's positioned and the position next to your ear is completely different from that of holding your phone in front of you. It would just require some evaluation and data recording of degrees and ranges.
nbetcher said:
Oh. That makes sense.
Not sure why it would be so hard. Accel can tell how it's positioned and the position next to your ear is completely different from that of holding your phone in front of you. It would just require some evaluation and data recording of degrees and ranges.
Click to expand...
Click to collapse
Not sure about that. If I remember correctly the accell only sees if the phone is in landscape or portrait orientation, and when you are talking on the phone it is almost straight up and down. Not sideways. Will venture to find an answer.
Edit: You almost have to have the phone on its side for the accel to see that you have moved your phone. Don't know about you but when I talk on the phone it is almost up and down.
jshealton said:
Not sure about that. If I remember correctly the accellerometor only sees if the phone is in landscape or portrait orientation, and when you are talking on the phone it is almost straight up and down. Not sideways. Will venture to find an answer.
Click to expand...
Click to collapse
That certainly can't be since many games, namely Armageddon Squadron (flying game) use the X and Y axis on the phone (roll vs pitch). Also think of rolling objects in games that you have to "steer."
nbetcher said:
That certainly can't be since many games, namely Armageddon Squadron (flying game) use the X and Y axis on the phone (roll vs pitch). Also think of rolling objects in games that you have to "steer."
Click to expand...
Click to collapse
That may be true. I don't have any games on my phone that use the accel. I can only go by logcat durring screen orientation. I am sure you can now, the only problem is at what amout of tilt does the screen lock. And you would have to tie it in to when there is a call connected. Would hate for my sreen to auto lock when I am laying in bed playing with my phone.
jshealton said:
And you would have to tie it in to when there is a call connected. Would hate for my sreen to auto lock when I am laying in bed playing with my phone.
Click to expand...
Click to collapse
Well, of course it's connected to the dialer - that's its only purpose. If the dialer doesn't have foreground then it won't auto-lock.
If developing for Android wasn't such a pain in the ass (compared to C++) and I knew more Java classes/methods then I'd probably just implement this myself. I'll probably get the myTouch Slide soon enough though.
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible... If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..." I know just enough Java/Android to cause some trouble, so it could only be good ;-) If not the dialer, then an app could be started as a service, with an intent to snag the call, and listen for a good jostling. I wonder what this would do to the battery/performance and how often I would have to make it poll the sensor? Hmm....
I'll see if I can poke around and find ANYTHING. Haven't googlified anything yet... I do need something constructive to add to my workload.
And yes, the accelerometer measures force applied to the X, Y and Z axis. you can technically program it to sense when you've dropped (or are dropping) the phone.
boredpcguy said:
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible... If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..." I know just enough Java/Android to cause some trouble, so it could only be good ;-) If not the dialer, then an app could be started as a service, with an intent to snag the call, and listen for a good jostling. I wonder what this would do to the battery/performance and how often I would have to make it poll the sensor? Hmm....
I'll see if I can poke around and find ANYTHING. Haven't googlified anything yet... I do need something constructive to add to my workload.
And yes, the accelerometer measures force applied to the X, Y and Z axis. you can technically program it to sense when you've dropped (or are dropping) the phone.
Click to expand...
Click to collapse
try looking here.
http://github.com/cyanogen/android_packages_apps_Phone
edit: It should be possible, since it looks like a feature to "turn over to silence" has been implemented.
boredpcguy said:
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible...
Click to expand...
Click to collapse
I'm not sure if shaking my phone is really much better than tapping the screen twice - both require similar times for completion.
boredpcguy said:
If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..."
Click to expand...
Click to collapse
Here's a tar.gz of the source-code that was released with the Droid https://android.git.kernel.org/?p=p...9af2e10e23c7c21f22abec5f3d7fa05d6406a2;sf=tgz
Not sure if it's still out and compatible with the newest builds, but the app Shake Awake did this quite some time ago.
Hairybroness said:
Not sure if it's still out and compatible with the newest builds, but the app Shake Awake did this quite some time ago.
Click to expand...
Click to collapse
I used to use this on android 1.1. iirc it stopped working on cupcake, and I haven't checked on it since then.
I don't think this would work, because what if you're laying down with the phone? I'm pretty sure it would mess up with the Accel. I'm not too much into this, but when playing a game like teeter for example, the side of your phone has to be horizontal with..the horizon (correct me if I'm wrong)
Dialer wake-up w/o real sensor
Shake Awake never worked too well for me.
I have always wondered in the back of my non-programmer brain if one who was really good could implement a sonar/feedback type code whereby when the phone was close to an ear, the amount of feedback from the earpiece to the mouthpiece was quite low, but drawn away from the ear increased just enough for the phone to pass through to the code through an intent (is there anything like a feedback intent? I bet Meltus would know!), which would issue the commands to unlock and wake-up.
More ideally would be a program which got the earpiece to put out a search tone up around 20 kHz, which would be analyzed by the mouthpiece. Sound present = user has moved the phone away from the ear, wake up and unlock to touchpad, sound muffled or totally gone = user is still using the earpiece, don't unlock.
BTW, all 2.1 eclair ROMs I've used in the past 3 months have a setting for a substantial improvement to screen awake times during calls.
Hi,
Every now and then, while my phone is in my pocket and I do receive a call, I pick it up to answer and the screen is totally unresponsive. I can't slide to answer or do anything at all. I tried to power it off and on again quickly, and then it seemed to get back to normal and I can answer the call. Most of the time this happened during incoming calls. Anybody noticed this behaviour as well?
I read in the HD2 Android forum that it was due to the light sensor. But I'm not sure.
Thanks,
-Gus
I'm experiencing the same issue...
Me too. anyone?
Same here. It happened on the Nexus one as well. Perhaps is a stock android issue.
I have created a bug report. Please help me by staring this report so that it gets Google's attention.
http://code.google.com/p/android/issues/detail?id=13853
Any update/fix on this issue yet? I'm having this problem on stock ICS, CM9 & AOKP as well.
I have this problem even without having the phone in my pocket, when I have it on the table and someone calls me, I have to wait for five seconds before answering, because before that the phone is irresponsive and it FC's, which rejects the call. It gets very annoying.
I've seen a lot of problems on the web about this. It might be the proximity/light sensor.
As a side note, have you cleaned the upper left corner of your screen (where the light sensor is located)? Or at least make sure nothing is actually over it (maybe a case or plastic, screen protector, etc).
Any update on code recently? Are you on stock ROMs or it happens on different custom ROMs/Kernels (good to test with several kernels instead)?
Some apps like AndroSensor or Phone Tester can give you insights about the proximity and light sensor. You might want to check it out and test this with a flashlight or something, and see if values change.
From the bug report, has someone actually tested comment 44 and 46?
Or tested this app DHD Proximity Sensor Recalibrator?
Some have even noticed missed connectors when phone was dissembled (this requires more effort).
Hi there, I'm currently running Darky's Rom 8 on my Samsung Captivate and for some odd reason shortly after installing my accelerometer went dead. I can hear it role around and move when I move my phone but theres no activity with the accelerometer.
I'm not sure If its the ROM or if its my phone.
Any suggestions?
(Sorry if this thread is in the wrong place.)
KyleTroy said:
Hi there, I'm currently running Darky's Rom 8 on my Samsung Captivate and for some odd reason shortly after installing my accelerometer went dead. I can hear it role around and move when I move my phone but theres no activity with the accelerometer.
Click to expand...
Click to collapse
What? You can hear it roll around?
Ya you Should not hear it rolling around
Sent from my SGH-I897 using XDA App
That makes it sound bad. I can hear it (I think its it) with the battery and the back cover off and my ear against the phone.
KyleTroy said:
That makes it sound bad. I can hear it (I think its it) with the battery and the back cover off and my ear against the phone.
Click to expand...
Click to collapse
Flash back to stock and see if that fixes it. If it doesn't, then you have a broken sensor. If it does, then it's a rom issue.
My accelerometer sometimes doesn't respond, when switching screen modes in web browser or similar. Good thing I got insurance for my phone in case I need to get it replaced for any reason.
att8525user said:
My accelerometer sometimes doesn't respond, when switching screen modes in web browser or similar. Good thing I got insurance for my phone in case I need to get it replaced for any reason.
Click to expand...
Click to collapse
If the hardware fails in your phone it is a warranty issue not insurance.
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
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
so far you are the only one that has ever reported anything like that,ya know it could be a hardware defekt
sent via my bamfed out tbolt
Nope I'm in the same boat as im sure are many others. I have only ever had it actually impact me I think twice on phone calls out of almost a hundred or so that I have had since I purchased the phone. All the others times though it was extremely annoying to keep hearing the click sounds of the screen turning on and off on and off on and off etc.
I keep hoping for a software update that addresses the sensitivity of the sensor, but still no
I also wonder how much the battery is affected by the screen turning on and off repeatedly while in a phone conversation...
I get the same. More on my right ear than my left, but it will often take a digit that I just typed for an automated system and try to dial it, resulting in an alarm tone in my ear during the conversation.
sorry but i have 3 different bolts,the 1st one was rooted stock had that problem but it also went into the brick loop so it got replaced,rooted that one but never had the prob again,this one has the bamf 2 prev 3 on it and no probs that is why i suggested harware cause my first one had major hardware issues
sent via my bamfed out tbolt
i get it too. but i dont call so much. so i dont really care lol
I too had this problem, and did some quick searching on Google. Stumbled upon someone who said to spray it with canned air to clean it out. To my surprise, it worked. There is just enough room between the screen and the body of the phone for dust/crap to get in and it hinders both the light and proximity sensors.
You might be holding the phone in a weird position?
THUNDERBOLT
Damn, you lean something new every day, this thing makes phone calls too!
I've had the issue too recently. But it only started when I returned the last phone to stock. Before that, I had a small issue with it, but it didn't happen often.
pnd4pnd said:
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
Click to expand...
Click to collapse
I have the screen turn on during calls, but I've never had a face hang up. Honestly I think the screen turns on for me, but can't be interacted with.
Scratch that just did a test. I guess I'm lucky. Then again I don't hold the phone flat to my face. So I guess I would never hit it...
i have had hangups, the mute button pressed, and a 3 way call started. i just tried blowing the screen out with some compressed air as someone suggested. it seems better - will give an update after some testing.
No issues with hang ups for me. Had that problem all the time coming from the X.
Sent from B.A.M.F. 1.7 using Tapatalk
I have the same problem and have had it with every Rom I've run and stock. I'm surprised we don't have a way to adjust the proximity sensor yet, that's something I really miss about my Droid X.
After answering a call and putting the tb to my ear, my screen stays on.
Sometimes my ear dials numbers, sometimes the screen stays illuminated but doesn't respond to any touch! I have to toggle the screen on/off with the power button to get the touch response working again.
I have never had an issue. Been on mostly whatever the latest bamf release since rooting.
It happens to me whenever I forget the bluetooth especially after working out or anytime facial area is warmer then normal. I have a screen protector and clean the screen frequently.
I am having the same issue, so I called Verizon yesterday and they are sending me a new phone. I hope it works, because it makes talking on the bolt almost impossible.
Sent from my ADR6400L using XDA App
this is the first I am hearing of this. No problems for me.
Have the same problem...its really annoying man....will not get a refurbished unit until they fix the reboots