Database Info

[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

ATT HTC ONE X, Camera Close Focus bug.

I want to see if anybody else is experiencing this issue.
Please post if you're rooted/unrooted and if you are rooted, what ROM you're using.
At this point in time, I have submitted a support ticket to HTC as well.
If you are in a low light/low-ish light setting (maybe even more, haven't tried all of them), and you hold your camera close to an object, the phone has trouble auto-focusing. It will attempt to focus, then revert to the blurred image. It seems that the only way to get focus is to find a way to get the camera to focus that image at a moderate distance and move it in close...but very slowly. That doesn't even work all the time. I think this is a SW bug...but I'd like to be sure.
I'm running CleanROM 3.1. (I've experienced this on CleanROM 3.0 as well )

Opened up camera and had the same problem you were describing, then just focused on a farther away object and tried to refocus up close and it worked fine (not using the focus on the object and slowly move closer method)

I tried that, it works sometimes and doesn't work other times (Automatically tries to re-focus and then reverts to a blurry, pre-focus image). It seems inconsistent, but it can work to get focus on close objects. I'm still hoping that HTC irons this one out

yellowfddriver said:
I want to see if anybody else is experiencing this issue.
Please post if you're rooted/unrooted and if you are rooted, what ROM you're using.
At this point in time, I have submitted a support ticket to HTC as well.
If you are in a low light/low-ish light setting (maybe even more, haven't tried all of them), and you hold your camera close to an object, the phone has trouble auto-focusing. It will attempt to focus, then revert to the blurred image. It seems that the only way to get focus is to find a way to get the camera to focus that image at a moderate distance and move it in close...but very slowly. That doesn't even work all the time. I think this is a SW bug...but I'd like to be sure.
I'm running CleanROM 3.1. (I've experienced this on CleanROM 3.0 as well )
Click to expand...
Click to collapse
I have been looking at this since I picked up the HOX on release day. I'm now running fully stock ROM on the official 1.85 OTA release and I have seen a major increase in up-close focusing from the camera. I haven't made any changes to settings, but since the OTA I have absolutely noticed a marked improvement in ability to lock focus on macro-level objects, even when not in macro (Close Up) mode.

I've had this and even replaced my phone, AND tried several store units and they all do it.

yellowfddriver said:
I tried that, it works sometimes and doesn't work other times (Automatically tries to re-focus and then reverts to a blurry, pre-focus image). It seems inconsistent, but it can work to get focus on close objects. I'm still hoping that HTC irons this one out
Click to expand...
Click to collapse
Did some further testing, I can get it to work but it is inconsistent

News flash, cameras struggle to focus on subjects in low-light. My $5000 Nikon D4 doesn't always achieve focus correctly. So expecting a cell phone to be perfect in low light is ridiculous.

My One X can't focus on anything close up regardless of light level.

feanor512 said:
My One X can't focus on anything close up regardless of light level.
Click to expand...
Click to collapse
Have you tried the close up setting?
Sent from my HTC One X using xda premium

kleeman7 said:
Have you tried the close up setting?
Click to expand...
Click to collapse
Yep. No effect.

feanor512 said:
Yep. No effect.
Click to expand...
Click to collapse
Hmm, mine works great, I did flash the 20mbps camera mod, but that wouldn't effect that.
Sent from my HTC One X using xda premium

In 4.2.2 you just press and hold the screen while trying to take a picture and it does AF and AE but I tried the same thing in 4.1.1 but I can't get it to focues. Especially while taking pictures at night. Does anybody know how to lock AE and AF in 4.1.1?

Dark slow motion video recorder

Has anyone else experience this issue? Every time I go to record a slow motion video the screen gets dark. I can see the video but it's really dim and plays back really dim. This only happens indoors. When I first got the phone I just thought that must be the way it is. However, I installed a particular ROM on my girlfriends phone (HTC Amaze) and it has slow motion video baked into the ROM and it records perfect without dimming itself. Furthermore, it does it in 720p. So there must be a way to fix this in our One S phone's. Someone with enough knowledge please help.

Same thing happens on my One S running on Trickdroid 6.1.0

theNOOBuser said:
Same thing happens on my One S running on Trickdroid 6.1.0
Click to expand...
Click to collapse
I noticed it right out of the box. So it has nothing to do with Trickdroid (FYI). But I know there is a way to fix this. I just don't know how to go about it...

Same here. Happened on stock Rom straight out the box. :/
Sent from my HTC VLE_U using xda app-developers app

That comes with taking a slo motion video. You need lots of light when taking them. This isn't a DSLR.
When you shoot in slow motion, you are taking pictures quickly. And when you take pictures quickly, light has less time to create an image in your camera. Shoot in lots of light otherwise you'll get the dark and gloomy.

I understand that our phones are no DSLR camera. However, my girlfriend's HTC Amaze can record in slow motion with no low light issues what so ever.. Obviously you didn't read my first post... And it records in 720p slow motion. Better then our One S phones. There is a fix or a camera.apk replacement somewhere. I could use her apk from her ROM but then if I did I'm sure I wouldn't have the "Continuous shoot mode" which I love.

i was using slow motion video thing on my sensation and it was greate one s have a big problem in this case also on new 4.0.4 update too

[Q] Camera Issues when led flash on.

Hello, i'm from Colombia and my english is not that good.
But i'll try.
27th Dec 2012 i bough and HTC One X at&t from Amazon, got delivered by Jan12 Saturday 2013 about 15:00 hours, retrieved, unboxing bla bla bla, i was testing the device, i came with ICS 4.0.4, Sense 4 and RUU 2.20, everything was working fine, data, wifi, screen, sound, but, when i was about to try the LED Flash of the Camera (to find out if it has AF Assist Lamp, witch it hasn't) i found a very weird artifact
This is it, i took 2 photos to a paper on a tablet.
The left one <-- was taken with LED Flash On (NOT AUTO, ON) and the right one --> was taken with it off (OFF, NOT AUTO)
This is so frustrating, practically there is no way to take photos with flash, is not a hardware issue (i think cuz when i record a video and take a photo while recording with LED LIGHT ON, the photo is fine, there is no such artifact), another way was changing the auto whitebalance to fluorescent and the photo becomes a little decent, and i thoght that i can handlet it, but no, when on Instagram, Facebook Cam, Cymera, etc. There is no sense Cam interface to take Photos while recording a video, neither the auto white balance option to get rigde of the "sephie like effect" so, i decided to change the ROM just to try:
Tried Vyper XL 3.0 and 2.4 and was the same ****, so i decided to reflash the device back to stock with and RUU 2.20, right now it has OEM ROM with Bootloader relocked and no root. and is in the same that was when i got it.
So, the Q are:
Is there another person who has experience the same issue?
Is there a way to fix it? Since i think it is a software problem, maybe yes maybe not.
Thanks.
I was thinking about sending back to LA for Warranty but... It will cost me $74 and a month of waiting.
i searched on Google and here but found nothing.

UP (?)

I don't think there is anything to "fix" here, and the camera is basically working as intended. It looks like just a matter of taking a picture of a completely white frame combined with the flash, which is throwing off the white balance. I'm sure there a plenty of other color/light combinations that will similarly result in odd white balance results. Its just a computer algorithm that is trying to interpret the lighting conditions and guess the "best" white balance, and its not going to be correct all the time.
You've already found the workaround, which is to either turn off the flash, or change the white balance manually. Or you might be able to fix the color after the fact with the built-in editing feature or 3rd party apps. I certainly wouldn't suggest warranty service, and don't think it will fix the problem anyway.
Flash isn't recommended for macro/close range shots, anyway. You get unsightly reflections like the one in your example. Even aside from the "sepia" tone, your second (no flash) example just plain looks better in every way. So why even use the flash, unless you for some reason have a need to regularly take photos of documents in low light, requiring a flash?

redpoint73 said:
I don't think there is anything to "fix" here, and the camera is basically working as intended.
Click to expand...
Click to collapse
Wtf? xd
I have also a Infuse 4G, 8 Mpx too, LED Flash, and the results with the Flash on, no matter if it's needed or not, are as it should be.
But this? here are two more examples, and i just took about 50 pictures, all with the LED On, and the sephie tone is everywhere, from a bathroom with zero light to outside, with sunlight, and even blocking the LED light with the finger.
This is so frustrating. I hope that is there a fix .

Another factor may be that the white balance by default is significantly "over-saturated", presumably by HTC to make colors more vivid and "pop" more. This could be why you are seeing this effect on this phone, when you don't on other phones or digital cameras.
But the latest photos you posted look pretty funky. Also, I've also tried to duplicate the effect by taking a picture of a printed page, and can't get the sepia tint. In fact, my photos actually look more white with the flash (more of a yellowish tint with flash off). These factors make me re-think my previous statement that it is working the way its supposed to.
Does the yellowish tint happen with subjects farther away too? Such as taking a picture of a person or landscape?
Defect with the camera? Maybe.
A "fix" aside from repair or exchange? Doubtful. The fact this issue persists across multiple ROMs suggests it may be a hardware problem.

redpoint73 said:
Does the yellowish tint happen with subjects farther away too? Such as taking a picture of a person or landscape?
Yes, no matter what, if the flash is On, the "sephia like effect" persist
Defect with the camera? Maybe.
A "fix" aside from repair or exchange? Doubtful. The fact this issue persists across multiple ROMs suggests it may be a hardware problem.
I have tried Viper XL 2.4 and 3.0 but not with CM 10 or AOSP ROMs.
Click to expand...
Click to collapse
:V

Negruka said:
I have tried Viper XL 2.4 and 3.0 but not with CM 10 or AOSP ROMs.
Click to expand...
Click to collapse
Couldn't hurt to try a AOSP-based ROM. ViperXL uses a different camera from stock 2.20 firmware, although its a newer version of the Sense camera.

Issue with screen's backlight

Hello everybody!
Recently i bought one Motorola Photon Q and I found one weird problem with my Photon Q.
I cannot regulate the screen's backlight. When it is on 100% it is very bright, but anything below this point (in example 99% or 50%) it goes very dimmed. So, basically I have two levels of backlight. Minimum and maximum. Nothing in the middle.
I tried to regulate it from the recovery mode, but issue stays the same.
Phone already had TWRP and CM 13.
Any ideas what can I do about it?
Regards.

Wow you joined in September 2008 and this is your first post?
Congrats!!
As for the issue, it almost sounds hardware related. Like someone swapped the proximity sensor for the ambient light sensor... If the issue persists in recovery, I'm not sure flashing stock would do you any favors (not that you would want stock, it would just rule out any low-level software issues if you flash thru RSD Lite).

Yes yes, I know. There was nothing I could give from my side. Just usual user.
Changing the sensor? But does it have anything in common, while backlight sensivity is chosen manually?
I'll try to flash it by RSD lite.
Thanks.

MarioK15 said:
Changing the sensor? But does it have anything in common, while backlight sensivity is chosen manually?
I'll try to flash it by RSD lite.
Thanks.
Click to expand...
Click to collapse
Honestly was just firing off the hip based on you description - it sounds hardware related not software, especially since it persists in recovery...
To rule out software entirely, RSD Lite is the best way IMHO. Good luck.
Assuming it is a hardware issue... I'm not sure replacing that sensor is worth the effort. I guess it depends on your desire (and ability) to get this old PQ working properly

It might be the hardware problem. I installed some application to check sensors, and it does not detect proximity sensor.
I was wondering about dismounting this sensor, but probably it would not help at all.