Related
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
Hi Guys,
I am currently using a Cell Pro Rom and I find that my it keeps flipping to landscape too often when I have my phone in portrait.
I always have to give it a shake to fix itself and it does get a bit annoying.
Does anyone know how to fix this?
(I remember I may have (not certain) that I might have changed the Sensor registry when I first got it, but I am not certain, does anyone know the default measurements?)
Any ideas are welcomed.
Many thanks in advance!
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
kimtyson said:
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
Click to expand...
Click to collapse
I'm fearing the fact that I may have changed something in the registery as I got all excited the day i got the phone and went through the tweaks in the wiki.
I am not certain if I made any changes regarding the g sensor so I was wondering if anyone knows the defaults or if there is a .cab or ROM to flash to system restore.
Any clues?
Many thanks in advance
To me the g-sensor is a gimmick. I find it annoying and totally useless so I've turned mine off altogether. If I want the screen to rotate I push the keyboard out. I really don't see any use for it.
I did think the only use I had for it was the face down hands free thing but have since decided that I'd be quite happy to push a button for that. Hardly a hassle.
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
AidanBell said:
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
Click to expand...
Click to collapse
BY default I thought in all roms the proximity sensor would turn the screen off when its pressed against our heads so buttons wouldnt get pushed?
If that doesnt work you can always just push the power button... which I sort of do by default for some reason anyway. But... yeah there is a way so the screen turns off when its close to your face. Someone else will chime in with it I'm sure.
AidanBell said:
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
Click to expand...
Click to collapse
I'm using the Titanium version without TouchFlo or Sense, and my screen turns off.
This is absolutely a feature of all versions of the TP2, and works regardless of whether TF is used of not. Have you tried a hard reset? Also, does flipping the phone onto its face during a call activate the speaker phone? This involves the proximity sensor (along with G-Sensor), so it might give you a clue if your proximity sensor is somehow disabled, etc.
I dug around the registry for a second, and found the following values under:
HKLM\Software\HTC\Proximity
Name: ProximityDetectStatus
Value: 0
Base: Decimel
Name: ProximitySensorOn
Value: 0
Base: Decimel
Name: PSensorDebounceTime
Value: 300
Base: Decimel
Name: UnexpectedWakeup
Value: 0
Base: Decimel
Some of the values seem counterintuitive (I would think the "ProximitySensorOn" would be 1, not 0). But in any case, it might help to check your registry settings.
Many thanks for your response.
To answer your questions: I've recently upgraded to WM6.1, but didn't like that and so flashed 6.1 back again, and in fact re-flashed that again the other day, so the machine has been through quite a series of hard resets of late, however to the best of my knowledge I have never had a working during-calls-screen-protect other than the brief period during which I was trying out TouchFlo when I first had the phone.
Yes, flipping the phone to activate the speaker works flawlessly, I use it often.
In my registry under HKLM\Software\HTC\Proximity; "ProximityDetectStatus" "ProximitySensorOn" and "UnexpectedWakeup" are indeed all set at "0". However I do not have an "UnexpectedWakeup" setting. Could this be the problem? If so, I'm afraid I'm a bit of a novice with reg tweeking, so would you mind talking me through setting that value?
AidanBell said:
Many thanks for your response.
In my registry under HKLM\Software\HTC\Proximity; "ProximityDetectStatus" "ProximitySensorOn" and "UnexpectedWakeup" are indeed all set at "0". However I do not have an "UnexpectedWakeup" setting. Could this be the problem? If so, I'm afraid I'm a bit of a novice with reg tweeking, so would you mind talking me through setting that value?
Click to expand...
Click to collapse
If you are using Total Commander, go to the appropriate location on the registry, and the first entry is "Add value". Select that, then pick "DWORD", type the name of the value (UnexpectedWakeup). Hit OK, then enter 0 for the value and select OK again.
If you are using another editor besides Total Commander, the process should be the same. I use TC, so I only know that exact process.
Are you flashing to an "official" 6.1 ROM, or a cooked ROM?
Did you run Task29 before flashing the new ROM? This will wipe/format the memory completely, and will sometimes clear up random problems. Its recommended to do this before flashing a cooked ROM, but I don't know if using an "official" ROM is a problem with Task29 or not.
http://forum.xda-developers.com/showthread.php?t=649191
I'ver never heard of Task29!
However, firstly they were both "official" ROMs, from Vodafone, but secondly it seems the reg tweak has done the trick; the screen now Blanks when in call, as it should do. So all is well.
Many thanks indeed for that.
No problem. Happy to help.
But it was the "UnexpectedWakeup" entry that fixed it? That name/description doesn't really seem to fit. In fact, I can't even imagine what that description even refers to, lol!
AidanBell said:
I'ver never heard of Task29!
However, firstly they were both "official" ROMs, from Vodafone,
Click to expand...
Click to collapse
I don't know if there are any potential issues with using Task29 and official ROMs, I've only used it with cooked ROMs. Although, it seems like it would work and serve the exact same purpose. Task29 just guarantees that no fragments of the remaining ROM will interfere with the new ROM. It seems to help prevent random issues with cooked ROMs.
They say honesty is the best policy, so let me share with you what I have embarresingly discovered was actually the reason for my problem - especially remembering what this forum is for and that it might perhaps help anyone else with a similar issue:
I was told that a good way of testing the proximity sensor is to press your thumb against the loudspeaker during a call while looking at the screen. This did not work ... until I removed the plastic protection case! I have always had my phone protected by a two-piece plastic\silicon casing, and I've only now discovered that when this is on the phone the proximity sensor fails, but when removed it works perfectly! Thinking back that makes sense because when I first got the phone and was using TouchFlo the phone had no protective casing.
As it happens I've just bought an expensive cradle for the phone for my new car, which requires that I remove the plastic casing in order for it to fit, therefore the timing is good as it means I can now use the phone with a fully-working proximity sensor.
However, having dropped the phone only once in the year that I've owned it, don't you just know that the moment I start using it without the protective casing .... !
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 ...
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Oliie23 said:
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Click to expand...
Click to collapse
If its anything like mine, you'll start getting some even weirder behavior. When I would answer a phone call (or place one), the proximity sensor wouldn't work and the phone would reboot itself within 5-10 seconds.
I downloaded an app called "Hardware Disabler" which allows you to disable the proximity sensor on the Gnex (its the one labeled 4-0044). It works for me...only annoyance is having to turn my screen off/on during phone calls manually. But, its better than having no phone (i.e. soft reboots).
Anyway, to answer your question, i'm not sure there's much you can do (other than disable). I've read that the proximity sensors on these GNex's are a little buggy.
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
I have had this issue. Do you use a ROM with the active display feature? A lot of ROMs have been including this lately. I feel like my issue started when they added that. It has a "Pocket Mode" option that uses the proximity sensor and I've always felt like it messed up my proximity sensor during calls. I never had reboots but the screen would flicker on and off during a call. Sometimes just staying on. I have turned Active display off all together and sometimes it will work right and sometimes it will flicker. But for me, it seems to have started when ROMs started including that feature.
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
amir-kia said:
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
Click to expand...
Click to collapse
It sometimes does it for me too, but it's very very rare. Sometimes the phone just freezes during a call (when swipe to take the call).
iLeopard said:
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
Click to expand...
Click to collapse
Can't speak for others, but I tried everything that could be tried. Flashed different Roms, kernels, and even went back to stock using the images provided by Google. Nothing fixed it until I realized it was a hardware issue. I haven't had a single problem since disabling that sensor.
EDIT: also, to clarify, it wasn't an intermittent problem for me. I could NEVER make/receive calls until I disabled that sensor.
Sent from my Galaxy Nexus using xda app-developers app
Flash Catalism rom and disable Proximity sensor solve my reboot incall problem !