Database Info

Looking for another dialer to stop accidental answers

Ok heres the deal my boss bought a sprint touch pro and everytime he gets a phone call even with the phone locked he either accepts or declines the call while he is taking it out of the case.
I have already done a search and this appears to be a major problem with the diamond with no fix really.
On my Hermes I have used a opal canvas dialer skin that you actually have to slide to the left and right to answer a call. Does anyone know of a dialer like that that will work with the touch pro?
I know s2u2 or whatever it is will work but thats too bulky and won't work for him. To me this really seems like a major flaw in the phone design and I may not get the phone myself unless I can find a workable fix..
I'm really surprised this isn't complained about more but a slide to answer reject dialer seems to easiest way to fix to me.
Any help appreciated.

MrDSL said:
Ok heres the deal my boss bought a sprint touch pro and everytime he gets a phone call even with the phone locked he either accepts or declines the call while he is taking it out of the case.
I have already done a search and this appears to be a major problem with the diamond with no fix really.
On my Hermes I have used a opal canvas dialer skin that you actually have to slide to the left and right to answer a call. Does anyone know of a dialer like that that will work with the touch pro?
I know s2u2 or whatever it is will work but thats too bulky and won't work for him. To me this really seems like a major flaw in the phone design and I may not get the phone myself unless I can find a workable fix..
I'm really surprised this isn't complained about more but a slide to answer reject dialer seems to easiest way to fix to me.
Any help appreciated.
Click to expand...
Click to collapse
THIS is what you need!
This disabled the on-screen answer keys, so you can only answer with the hardware keys. Works perfect for me, and it's a very small app.

johanromijn said:
THIS is what you need!
This disabled the on-screen answer keys, so you can only answer with the hardware keys. Works perfect for me, and it's a very small app.
Click to expand...
Click to collapse
Thanks man that looks like its gonna work..He only wants the hard keys to answer..

Doesn't work with CDMA devices
I think he may just return the phone cause its that annoying since none of his calls go through..Even when he has his headset on if he just moves wrong it rejects the call..I have been using his phone for about an hour and it happens to me also..I want to throw the damn phone against the wall!!!
I tried some sensorapp and that doesn't work also and changes the unlock screen too much

If I could just find a dialer like the opal one that you have to slide to the left or right to answer or reject this would be fine..

i think the maker of the program will eventually fix it to support CDMA devices. why not give him a message?

chrisbjr said:
i think the maker of the program will eventually fix it to support CDMA devices. why not give him a message?
Click to expand...
Click to collapse
He does have it under the todo list but it won't do my boss much good since he is missing every single call he gets..
I really thought he was exaggerating so thats why I decided to use the phone and I haven't been able to answer one single call. This is using the case that came with the phone and I can't believe this was not noticed during some testing phase or something..

I noticed you mentioned S2U2, and I'm curious why you decided against it.
As long as you enable Slide 2 Answer, and enable the D-Pad option, your boss' problem should go away. The D-Pad option will allow him to answer calls using the D-Pad and not have to touch the screen at all.

NotATreoFan said:
I noticed you mentioned S2U2, and I'm curious why you decided against it.
As long as you enable Slide 2 Answer, and enable the D-Pad option, your boss' problem should go away. The D-Pad option will allow him to answer calls using the D-Pad and not have to touch the screen at all.
Click to expand...
Click to collapse
It would be fine for me but my boss is kinda weird about installing stuff on his phone and I know when I have used s2u2 on my hermes it took more battery life etc and i sometimes ran into weird glitches. Which is okay for me but he would have a fit.
It needs to be as close to stock as it can be..
If he returns the phone then I won't have to worry about always fixing it LOL so I may just tell him to do that..
It just really amazes me something like this was missed and it also amazes me that the low speakerphone volume is also on this phone. I just noticed that. My hermes is the same way and apparently being able to hear the person on the other end isn't important enough for HTC to worry about fixing. Its not like I wanna hear the other person I'm talking to on my phone..
They did at least fix the MS Voice Command not working with BT headsets!!

I use Sensor Lock. You can customize the gestures to only a 1/2 turn to lock, 1/2 turn the other way to unlock. It works very well. S2U2 doesn't work well on the Touch Pro yet...

MrDSL said:
It just really amazes me something like this was missed and it also amazes me that the low speakerphone volume is also on this phone. I just noticed that. My hermes is the same way and apparently being able to hear the person on the other end isn't important enough for HTC to worry about fixing. Its not like I wanna hear the other person I'm talking to on my phone..
Click to expand...
Click to collapse
There's apparently a lot of variation on volume between different versions of the same handset. I noted in this forum that there were a lot of people complaining about the volume being too low, but there were also a couple complaining about it being too high.
You mentioned low speaker phone volume on your Hermes. I have a Cingular 8525 (Hermes) with the original ROM, and I almost always have to turn the volume down all the way to use the speaker phone. I have to turn it up all the way when I'm using the earpiece (i.e., as a normal phone), but that volume is definitely too high for a quiet room on the speaker phone. (And they didn't give separate volume settings for earpiece and speaker phone, grr...)

MrDSL said:
If I could just find a dialer like the opal one that you have to slide to the left or right to answer or reject this would be fine..
Click to expand...
Click to collapse
Exactly! I've been looking for an Opal-like dialer for the Fuze (Touch Pro) -- but no luck so far. Anybody seen one floating around in .cab form?

Accel. Auto-Unlock for Dialer

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.

[REQUEST] [APP] speaker switcher?

Hey guys i currently upgraded from the nokia n900 to the nexus one. I had this great app on the n900 where it used the proximity sensor to switch the phone call to speaker when its away from your face and then switch back to the regular phone "ear" speaker when its against your face. I tried looking for something like it i downloaded "smart call" and it kinda works but it uses the accelermeter to determine the phones orientation. any help is appreciated THANKS!

This is a surprisingly good idea...

I really want this function also.
I had this in my Touch Pro2 but that used both proximity sensor and accelerometer so when i put the phone on a table with the screen down it started speakerphone. As soon as I picked it up it changed back.
Really good feature if you´re put in hold, waiting for someone to answer.

+1
Brilliant idea.

Ya its great! so basically when the screen turns on when you pull it away from your face so does the speaker lol i think its simple enough for the developers to create right?

nothing?

deng 200 views and no love.

You might want to try asking this in the Tasker thread. I'm not familiar with the program, but it might be able to do what you want.

+1 This is a great idea. I just spent 45 minutes on the phone with Time Warner and was on hold 5-6 times, this would have been handy.

I know for a fact this would suck on my n1. The only noticeable problem i have on my n1 is my prox. sensor sucks, alot of the time it thinks that my head is away from my phone and i end up muting myself and not realizing it and then getting hung up on. Very annoying

_-..zKiLLA..-_ said:
I know for a fact this would suck on my n1. The only noticeable problem i have on my n1 is my prox. sensor sucks, alot of the time it thinks that my head is away from my phone and i end up muting myself and not realizing it and then getting hung up on. Very annoying
Click to expand...
Click to collapse
Mine does the same thing, but like djstoffe had on his Touch Pro2 we should implement the accelerometer so we don't get any 'false alarms'.

After a 12 hours working day I needed to relax a bit...
I just decided to write the app as I like the idea but I'm not sure on the concept how to use it... have to sleep about it.
Anyway you can play with the attached apk and if you would post me a logcat, that would be nice and i can see on which devices/rom's it doesn't behave like on my Nexus with CM6...
Code:
adb logcat|grep SpeakerProximity
Just fire up the app and there is a preference view where you can set it on or off with a combobox.
It's working on my phone but as I'm sleepy I can't test it any further but if you like the app and think it could be usefull, just post your comments and I see that I turn it into a optimized app (this is just a quick afterwork writedown)
Before I forget, I will post the sourcecode after I cleaned up my mess and maybe also write a short tutorial on how I did write this app ;-)
Added a new Version in post #27 => http://forum.xda-developers.com/showpost.php?p=7972710&postcount=27

WORKS GREAT THANKS!!!
Sent from my Nexus One using XDA App

Thanks so much for stepping up and making this, rac2030. I just tested it on my phone and it works great!

Works like a charm!! Thumbs up!!!

Hmmm... scary that it's working without probs... did test it today a bit but expected bugs: because I was tired and just wrote out of my head.
Could you guys feed me some lolcat to see if the values are always right or as I asumed?

Ok came across a problem. Is there a way that the app keeps running but disables when the Bluetooth is connected to a headset? The other day I was using my jawbone and it kept switching from speaker to the jawbone.
Sent from my Nexus One using XDA App

k0shi said:
Ok came across a problem. Is there a way that the app keeps running but disables when the Bluetooth is connected to a headset? The other day I was using my jawbone and it kept switching from speaker to the jawbone.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I will take a look at it, sounds like a good idea...
Note to myself:
- Disabling the speaker switch if headset is connected (bluetootht and wired)
- proximity monitoring should be handled in a proper service that starts with the accept broadcast of the call and ends itself after the end call broadcast
- grabbing it upsodedown (based on G senseor) switch microphone on and off (as a second option in app)

I'm running into a couple problems with the app on my Nexus CM6.
It is functioning properly except for the screen and speaker button. I called myself from Gmail and answered like normal with the phone up to my ear, working so far, then I took the phone away from my head and the screen came on and switched to speaker perfectly, but after that if you put the phone back up to your face the screen doesn't turn off and the speaker button remains green (as if it were still on speaker phone).
Like I said, it switches back and forth from speaker to no speaker flawlessly, so that part is working great. Any one else experiencing this?
Also, it would be amazing if we could utilize the tilt sensor so that if you wanted to set the phone on the table, screen down, it won't switch back to in ear.

dailydR1ver said:
I'm running into a couple problems with the app on my Nexus CM6.
It is functioning properly except for the screen and speaker button. I called myself from Gmail and answered like normal with the phone up to my ear, working so far, then I took the phone away from my head and the screen came on and switched to speaker perfectly, but after that if you put the phone back up to your face the screen doesn't turn off and the speaker button remains green (as if it were still on speaker phone).
Like I said, it switches back and forth from speaker to no speaker flawlessly, so that part is working great. Any one else experiencing this?
Also, it would be amazing if we could utilize the tilt sensor so that if you wanted to set the phone on the table, screen down, it won't switch back to in ear.
Click to expand...
Click to collapse
Have to test this, thx for the info.
Note to myself:
- add tilt Sensor and dont switch back if in speaker and get flipped (make this optional in settings screen)

[Q] Accelerometer went dead

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.

[Q] Tbolt Proximity sensor

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