I hear these AT&T commercials talking about this feature, my verizon TP2 does not do that. The speaker phone button on the back does not do anything either. Is it a setting?
In my stock HTC TP2, in Phone settings (Windows Mobile's, not TouchFlo's), last tab (should be "Advanced"). There's an option that said "when the phone is facing down during a call, use loudspeaker". Check if your phone has this setting?
I don't get all these modifications by providers... in Hongkong phones are sold as is, even when bundled to a certain provider's plan. Many of those modifications aren't really improvements either...
My AT&T Tilt 2 stock rom does this by default!
Cool little feature!!!
not to hijack the thread or anything, but im having the same problem except with the t-mobile version. when its flipped, the mute button lights up but the speaker doesnt activate. the windows option is checked. i messed with some registry settings to enable two way recording (didnt work btw). but that cant be the problem as my brother is having the same problem with his unmodified tmo tp2. his option is checked too.
any ideas?
bump bump, anyone know whats wrong?
Do you have ANY sound? I was using Resco Audio Recorder and I couldn't use the speakerphone when it was working either.. I uninstalled it and no problems since.
i turned this off. it came on once when i was on the couch and it was loud near my ear and freaked me the f out.
I posted about this about a week ago, my solution was to get a new one.
My new one has about 75 dead pixels, so it's going back too.
I'm not satisfied with the build quality at this point...
the speaker does work... when you click the speaker button once in a call. it's just that it doesn't automatically do that when turned over in the call. only the mute button lights up green.
EDIT-
nevermind, it works now. i read this on your thread.
MCbrian said:
I'd say that unless you've been setting it down on an uneven surface -- or not actually setting down at all as the other guy suggests-- there must be something wrong with your phone.
There's no setting/configuration that would cause the inconsistent erratic behavior you describe -- going on then off, vibrating, etc -- if it's setting on a flat table-top or similar.
Click to expand...
Click to collapse
apparently i wasn't lying it evenly face down. i was trying it on the couch so that doesn't help. i layed it evenly this time and it vibrated and the speaker went on. then i did a couple of other tests at angles and sure enough you have to have it evenly face down. at one angle, i had it vibrating like a maniac because it thought it was even and then uneven.
problem solved!
You have to make sure it is even on the surface. Also doing a g-sensor calibration may help as well.
lehmaj said:
you have to make sure it is even on the surface. Also doing a g-sensor calibration may help as well.
Click to expand...
Click to collapse
cheers mate! Workd :d:d
Related
Hi folks,
I am experiencing some strange problem, since leedroid rom mod 1.4 this feature isn't working anymore. I've tried a few different roms after I recognized that the volume stays the same after almost "throwing" the device in all possible directions I've wiped everything before installing the different roms but no change, it won't work for some reason and I don't no what this may caused.
It's a nice feature and I really don't want to miss it. Could this be perhaps a hardware related problem ? It's driving me nuts because I have no idea at the moment
Every help is appreciated ! Thanks in advance.
Hi again,
I've run some more "tests" and actually found out that it's working when the phone is lying on the desk, then the volume is getting reduced after grabbing it but when I hold the phone in my hand and shake it during an incoming call nothing happens unless I put it with the face down on a table.
So my question is this how it's supposed to work ? I actually don't know which sensors are being used for this feature :s
m8tix said:
Hi again,
I've run some more "tests" and actually found out that it's working when the phone is lying on the desk, then the volume is getting reduced after grabbing it but when I hold the phone in my hand and shake it during an incoming call nothing happens unless I put it with the face down on a table.
So my question is this how it's supposed to work ? I actually don't know which sensors are being used for this feature :s
Click to expand...
Click to collapse
The feature only works if the phone is completely still when it starts ringing in my experience.
If you're holding it in your hand and you call it then it won't happen. If you leave it on the desk and then call it, it will happen. The sensor being used is the Accelerometer, I think. Which is incredibly sensitive.
Budadank said:
The feature only works if the phone is completely still when it starts ringing in my experience.
If you're holding it in your hand and you call it then it won't happen. If you leave it on the desk and then call it, it will happen. The sensor being used is the Accelerometer, I think. Which is incredibly sensitive.
Click to expand...
Click to collapse
I really appreciate your answer !
That's what I actually thought and thanks a lot for your confirmation The sensor seems to be very sensitive in this case but as long as it's working I'm ok with it because I leave it almost all the time on my desk at work, I just thought that it also had worked while taking it from the pocket but I was obviously wrong.
I was checking voicemail today.. put in my password thru the keypad.. and then once i put the phone back next to my ear.. i kept pushing the keypad buttons with my cheek. until the promixity sensor caught on..
anyone else getting this prob? just an fyi.. i have the SGP Oleophobic Screen Protector on my phone.. i'm not sure if that decreases the reaction time for the sensor or not.. but its a pain..
No mine does that too. I've been using google voice to keep my old number, which asks to hit a 1 or 2 to accept/decline thus keeping the keypad up.
When I'm on a call and shufflin' (everyday I'm shufflin') sometimes the screen pops back on with my face on it and all of a sudden you'll hear a bunch of tones over the phone. lol. Everyone asks, "What was that?!" and I just giggle and say, "Don't worry about it" or "I didn't hear anything" lol.
But yea. It's a tad slow. Probably just a setting. I'm sure it'll get fixed soon.
I thought I was the only one experiencing this issue! I had this proximity sensor issue on my Iphone 4, but it was hardware related. This only appears to occur when the dialpad is still on during a voicemail or phone call. This is BEYOND ANNOYING and I hope that Google is able to address this via software fix. I'm surprised they let this one slip through the cracks.
Proximity sensor slow
Yep. Mine too.
I just found out why this is. The GNexus requires the phone to be upright before the proximity sensor will turn off the display. If it is laying flat, it won't work. Because of the complexity (the requirement to satisfy both conditions), it seems to react slower.
The hardware itself isn't the problem. It's the stock dialer.
To demonstrate, I made a video. I used the stock dialer and GrooVe IP (a dialer I use for Google Voice). GrooVe IP turns off the screen right away when I put my hand over the proximity sensor. Also, it does not cause accidental ear dialing.
I hope Google will fix this in the next update. It's certainly by design (a bad decision), and can be fixed by software.
http://www.youtube.com/watch?v=cjTGQaK1Qvw
This thread is pretty dead, and I haven't found too many other posts regarding this issue. I'm shocked to not see any replies, including the ones who already wrote in this thread. I was hoping to get some confirmation if their "slow" responding phones are also exhibiting this correlation with the accelerometer.
Is this not a wide spread issue? Is what I demonstrated not expected behavior? Do I need to exchange my phone?
I hope not - I bought this from a Amazon merchant, so I don't know how hard it is to get warranty work done (since it's imported).
I'm in the US, and this is a GSM version. We only have the CDMA version (Verizon) officially.
Forgot to post here regarding this issue. Not fixed, but I think it's more of a software issue than hardware. I wrote and made a video that might explain why I think it's a software issue:
http://www.guytechie.com/articles/2012/1/22/galaxy-nexus-slow-proximity-sensor.html
naddie said:
This thread is pretty dead, and I haven't found too many other posts regarding this issue.
Click to expand...
Click to collapse
Probably because no-one else has this problem? I know I don't anyway, mine is always instant and works flawlessly. Sounds like a hardware issue or your screen protector?
case0 said:
Probably because no-one else has this problem? I know I don't anyway, mine is always instant and works flawlessly. Sounds like a hardware issue or your screen protector?
Click to expand...
Click to collapse
It's an issue for me, no screen protector and the timing's almost sporadic when holding it naturally. But it could also be how I hold it as said earlier in the thread
I also have the same issue when checking voice mail. My damn cheek always hits a number or some button after putting in my pin.
Screen orientation in general seamed slow to me on 4.0.2. 4.0.4 speeds things up a bit, it's listed as one of the improvements.
Same issue here. I just tilt the phone so that the top (where the sensor and speaker are) touches my ear for a second, then flatten the phone against my cheek. This gives the sensor time to activate and never results in accidental keypresses.
Sent from my Transformer TF101 using xda premium
ericshmerick said:
Same issue here. I just tilt the phone so that the top (where the sensor and speaker are) touches my ear for a second, then flatten the phone against my cheek. This gives the sensor time to activate and never results in accidental keypresses.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
this is what i do too it's a pain though - i hope we get 4.0.4 in the UK on o2 soon! im tired of waiting for faster screen rotation and more responsive proximity sensing
All my P sensor issues were fixed after flashing the PrimeLA03 bootloader.
Hi people. I have the same issue on 4.0.4 (Stock OTA).
The proximity sensor shows no output after testing it with "Sensor List" and with "Elixir 2".
Any ideas? Thx.
I have this issue too!
I have it too, I just tilt the phone to touch the ear first and then bring it close to my face.
edit with a rom
If your using a Rom like AOKP, you can edit it to be faster and better in your desired ways.
Done it and it works the second I raise my phone to my ear when necessary.
Emergency Call from lock screen
Never had a problem GV or the stock phone but the orientation affecting the proximity sensor might explain why I am making emergency calls from the pattern lock screen.. wish there was at least a simple swipe needed to make the emergency call.
naddie said:
I just found out why this is. The GNexus requires the phone to be upright before the proximity sensor will turn off the display. If it is laying flat, it won't work. Because of the complexity (the requirement to satisfy both conditions), it seems to react slower.
The hardware itself isn't the problem. It's the stock dialer.
To demonstrate, I made a video. I used the stock dialer and GrooVe IP (a dialer I use for Google Voice). GrooVe IP turns off the screen right away when I put my hand over the proximity sensor. Also, it does not cause accidental ear dialing.
I hope Google will fix this in the next update. It's certainly by design (a bad decision), and can be fixed by software.
Click to expand...
Click to collapse
Not fix even on 4.1 ...
my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.
chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?
From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.
networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.
i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.
thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.
well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.
There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.
actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.
Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.
Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.
Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?
we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.
It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent
So today I noticed that my HOX doesn't vibrate anymore. Not even at the startup.
I can't remember dropping it or something else. One thing that made me curious, I can't use *#*#3424#*#* for the Diagnostic Test. Everytime I'm typing it into the dialer the damn phone won't do a bloody thing. The code just disappears. So could this might be some weird software thing? Or is it really the vibration motor that's not working?
Is there a way to fix this? Maybe a lose connection?
Ok I just noticed that my sound is bugging too. Everything is turned to the max but the phone won't ring on a call. But the speakers definitely are working because I can hear music and other stuff.
schlabbadibabba said:
So today I noticed that my HOX doesn't vibrate anymore. Not even at the startup.
I can't remember dropping it or something else. One thing that made me curious, I can't use *#*#3424#*#* for the Diagnostic Test. Everytime I'm typing it into the dialer the damn phone won't do a bloody thing. The code just disappears. So could this might be some weird software thing? Or is it really the vibration motor that's not working?
Is there a way to fix this? Maybe a lose connection?
Ok I just noticed that my sound is bugging too. Everything is turned to the max but the phone won't ring on a call. But the speakers definitely are working because I can hear music and other stuff.
Click to expand...
Click to collapse
Hey,
what rom are you using ?
Did you flashed it recently? If yes did you do a full wipe before flashing ?
The motor connector is unlikely to get disconnected( it gave me hard time to remove it when replacing my screen).
The speaker on the other hand is not connected with connector - its basically 2 pins making contact with the motherboard of the phone, so my suggestion is to try and apply some pressure on the grid on the back of your phone and check if there is a difference - if there is then you should open your phone and bent those pins upwards so the have better contact with the motherboard.
There is the possibility of speaker's driver being stuck( usually moisture) and my advice(old nokia trick) is to suck and blow the speaker so it gets unstuck
Good luck
schlabbadibabba said:
So today I noticed that my HOX doesn't vibrate anymore. Not even at the startup.
I can't remember dropping it or something else. One thing that made me curious, I can't use *#*#3424#*#* for the Diagnostic Test. Everytime I'm typing it into the dialer the damn phone won't do a bloody thing. The code just disappears. So could this might be some weird software thing? Or is it really the vibration motor that's not working?
Is there a way to fix this? Maybe a lose connection?
Ok I just noticed that my sound is bugging too. Everything is turned to the max but the phone won't ring on a call. But the speakers definitely are working because I can hear music and other stuff.
Click to expand...
Click to collapse
Try this ...
http://forum.xda-developers.com/showthread.php?t=1683634
pleaze check this. this will help for you Fix vibrate.. 5 methods
so pretty much im laying down talking on the phone and during the call all of a sudden the other person cant hear me, i can hear them but they cant hear me. so at first i thought its the signal, but i have full bars. then i turned off the option where if you place your phone facing down that itll mute, but the problem continues. so today i noticed that when that happens, i leave the phone where it is, press the speaker option and it works! so it isnt the signal! can any body tell me if its a setting im missing or is it something i should take it back to the att store?
are you sure the screen is shutting off? perhaps your cheek is hitting the mute/unmute icon (speaker icon)?
Ive had this exact problem for the last year with my s4. Always assumed it was something with the gyro inside. Its really annoying
m_reyna_16 said:
so pretty much im laying down talking on the phone and during the call all of a sudden the other person cant hear me, i can hear them but they cant hear me. so at first i thought its the signal, but i have full bars. then i turned off the option where if you place your phone facing down that itll mute, but the problem continues. so today i noticed that when that happens, i leave the phone where it is, press the speaker option and it works! so it isnt the signal! can any body tell me if its a setting im missing or is it something i should take it back to the att store?
Click to expand...
Click to collapse
I faced the same problem once, last week. But I just ignored it, imagining it would be something to do with bad network. I should try to simulate the issue again and see if it's persistent..
Maybe try turning off the motion options in the settings? I turned those off right when I got the phone and I haven't had this issue.
xlr8shun said:
are you sure the screen is shutting off? perhaps your cheek is hitting the mute/unmute icon (speaker icon)?
Click to expand...
Click to collapse
To be honest ive wondered that myself, but even tho i havent checked, last night when it occurredto me to try and press the speaker button to see if it will work (which it did) it did not have the mute button pressed... so because of last night, id have to go with no, it isnt pressed and the screen is black
blastedbilly said:
Ive had this exact problem for the last year with my s4. Always assumed it was something with the gyro inside. Its really annoying
Click to expand...
Click to collapse
Did u investigate for any issues like that online?
phoenix2241987 said:
I faced the same problem once, last week. But I just ignored it, imagining it would be something to do with bad network. I should try to simulate the issue again and see if it's persistent..
Click to expand...
Click to collapse
Let me know if it happens again
whoamanwtf said:
Maybe try turning off the motion options in the settings? I turned those off right when I got the phone and I haven't had this issue.
Click to expand...
Click to collapse
No, loke i said... that feature was turned on then i turned it off having the same effect
So anyone know a fix or know if i should take it to att for a replacement ?
issue I'm having is odd...I think it correlates to Bluetooth, but still working with advanced tech support. when I change towers, whether I receive or make a call, the phone drops all connection and says "out of service area". then comes right back. seems better without Bluetooth, but still happens. tech has no answers yet. already replaced sim twice and registered phone several times.
EDIT: I turned on the UTMS HD Voice using the hidden diagnostic menu and after 5 test calls today, no drops. Not sure if it is coincidence or something else...
Experiencing call issues too
m_reyna_16 said:
so pretty much im laying down talking on the phone and during the call all of a sudden the other person cant hear me, i can hear them but they cant hear me. so at first i thought its the signal, but i have full bars. then i turned off the option where if you place your phone facing down that itll mute, but the problem continues. so today i noticed that when that happens, i leave the phone where it is, press the speaker option and it works! so it isnt the signal! can any body tell me if its a setting im missing or is it something i should take it back to the att store?
Click to expand...
Click to collapse
I've also been experiencing similar issues, 2 issues in particular
1. During a call, I suddenly can't hear the other person or they suddenly can't hear me and I have to end the call and call back
2. I attempt to place a call, it rings and then when the other party picks up I hear nothing, they hear nothing. I sometimes have to call twice or three times before there's a successful call and I hear them and them hear me.
These issues occur randomly, with and without bluetooth. I've tried factory resetting the phone but the problem has continued.
I purchased my phone from Amazon.
IT Rider said:
issue I'm having is odd...I think it correlates to Bluetooth, but still working with advanced tech support. when I change towers, whether I receive or make a call, the phone drops all connection and says "out of service area". then comes right back. seems better without Bluetooth, but still happens. tech has no answers yet. already replaced sim twice and registered phone several times.
EDIT: I turned on the UTMS HD Voice using the hidden diagnostic menu and after 5 test calls today, no drops. Not sure if it is coincidence or something else...
Click to expand...
Click to collapse
I've used that menu but when clicking on the UMTS option nothing happens? How'd you select anything? Thanks
brittoking said:
I've used that menu but when clicking on the UMTS option nothing happens? How'd you select anything? Thanks
Click to expand...
Click to collapse
I didn't notice any sound difference when setting the UTMS HD Voice to "enabled". Did you see the two options for "enable/disable"?
IT Rider said:
I didn't notice any sound difference when setting the UTMS HD Voice to "enabled". Did you see the two options for "enable/disable"?
Click to expand...
Click to collapse
Yea I found them last night, I'd missed them somehow before. I have it enabled but haven't noticed anything as far as being more clear or a specific icon on the screen. I remember having seen another thread on this, maybe it was in the Verizon forum, that stated the UTMS was not even the right network option to enable the HD though? Does anybody know for sure?