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

[Q] Light sensor issue on Android 3.1?

I updated my Xoomto 3.1 right after unboxing it. Then I found that its light sensor does not work.
Setting screen brightness to auto has no effect, it just keep the same brightness regardless of ambient light. So I must set the brightness manually, it is very annoying.
I installed some sensor utilities such as AndroSensor, Light Sensor,... but they don't display any value (just "waiting for event").
Does anyone meet the same problem? Is this an error in the sensor or a bug of Android 3.1?
(My Xoom is CDMA version)

Yeah I noticed the same thing the other day. Auto does nothing.

Could you give more details?
Did it work before upgrading? How is it now?

I'm not sure if it was doing it with 3.0, just noticed mine the other day.

Same here...

I have no light sensor issue--before or since the update.

I downloaded a sensor app and confirmed that i have no light sensor readings. I'm jusrt not sure when it happened or if it ever worked. could it be a kernel thing?

Thank you all for your replies.
Same here...
Click to expand...
Click to collapse
What do you mean? Does it work or not on your Xoom?
Anyway, as I see, this is not a common issue, so I returned my Xoom.

Actually I take it back, the auto brightness is working for me

I didn't even notice mine wasn't working until this thread. I'm just going to go with it.

so this is weird. I upgraded to the new Tiamat kernel today and my light sensor is working again. It must be a kernel thing. I'll post a message in that thread.

[Q] Cubot A890/ M6589 (MTK6589) screen issues during/after call

Hey!
The Issue: During a phone call the screen turns dark and will not reactivate...it will pop back up after the call disconnects. Hitting any of the site buttons does nothing.
I have tried flashing with the newest firmware (http://blog.geekbuying.com/index.ph...-firmware-released-0502-version/#.UtMOWM93vVI), and although it says this issue has been resolved, it does not fix the problem for me.
I heard that custom ROM fix the solution? (Saw it on this http://forum.xda-developers.com/showthread.php?t=1518663).
But last time I tried one of those, the phone bricked and it took me a while to get it back working (finding stock followed by lost IMEI).
Anyone know a solution? Or possibly a good solid custom ROM that will work? I would really appreciate your help!

I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help

alrightiwill said:
I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help
Click to expand...
Click to collapse
Hey! Not sure if this be of any help, but for me removing the screen (plastic) cover fixed the issue. I assume the screen cover was blocking a sensor thus resulting in my issues.
Just thought I let you know what worked for me...although I doubt your issue can be solved like this.
BTW, I suggest you start a new post, as this one is old and I doubt anyone will read it! also, check out geekbuying.com blog in regards to your phone. They might have more info.

50% inverted touch after flash??

Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading

john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Have you tried resetting the phone ( as in completely wiping out everything including OS) and then try installing MIUI, if it still persists try a custom ROM

Same issue here, China version in use and went to 10.3.9.0 where issue popped up. Tried to go back 10.3.5.0 but issue still exsist. Absolute annoying issue and makes phone totally unusable.:crying:
resetted of phone and etc, but no help.

Mine's now in a drawer, awaiting any form of fix.
I bought an Umidigi F1 Play while waiting......
Terrible issue and absolutely no support from Xiaomi.
Have personally owned Xiaomi phones since the Redmi 2 and never had any issues with flashing software.
Never again.

Try to flash china rom lowest version of miui 10 which is stable. Works for me.

Does not help, lowest u can flash is 1035 which will not fix the issue.
EDIT: flashed custom ROM, still issue persist

john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Looks like there's a hardware defect in your device, maybe you got a faulty device, try going to a recognised mi store and get it replaced

This is not hw defect, mine was fully functional before firmware update to 1.0.3.9.

mlackke said:
This is not hw defect, mine was fully functional before firmware update to 1.0.3.9.
Click to expand...
Click to collapse
What If the phone was dropped or smth..

Hi,
I have the same problem which occurred after update.

Bump. Has there ever been a software-related fix to this issue? I currently have the same problem as described by the OP on a XIAOMI MI 8 Lite (128GB, 6GB RAM), although it only appeared after unlocking the bootloader and flashing a custom recovery. I've been flashing ROMs for quite a few years now and also double-checked all the software I've been using, I am certain that I made no software-related mistake. Since encountering the issue I have reflashed various original stock firmwares from xiaomi using both the flashtool and twrp, all to no avail. I've even relocked the bootloader, just to be absolutely certain. Since the entire touchscreen still registers input, I find it hard to believe that it is a hardware related issue, especially since I never dropped my phone and it also never experienced any physical trauma (so to speak). Would really appreciate any further input.

john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past

mlackke said:
Same issue here, China version in use and went to 10.3.9.0 where issue popped up. Tried to go back 10.3.5.0 but issue still exsist. Absolute annoying issue and makes phone totally unusable.:crying:
resetted of phone and etc, but no help.
Click to expand...
Click to collapse
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past

Has anyome fixed that yet? Is it even possible? I have tried everything, dowloaded tons of GB of roms, flashing programs, watched milion vids on YT, and still cant find anything. So i you find somethink, let me know <3
Prakashr09 said:
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
Click to expand...
Click to collapse

Is there any update ? Strange thing is, it seems not that many devices have this problem ... or I couldn't find other threads about this

Microphone and ambient light sensor issues, software or hardware?

Hi there!
First off: I used the search, but am not confident I haven't overlooked something.
If so I'm sorry!
I have a google pixel with lineage-for-microg, whose battery I had replaced some months ago.
Afterwards I wanted to reflash stock android to start afresh and then reflash lineage.
I'm back on lineage 17 (derived from Android10) and have the following problem:
During calls the microphone in speaker mode doesn't work at all, meaning, the person on the other side doesn't here a thing.
The same happens for speaker calls in other apps.
What still works, is audio in videos I take with the camera.
Also the ambient light sensor seems to have stopped working as the automatic luminosity doesn't work and I have to set the light by hand.
And then the proximity sensor during calls doesn't work.
I'd like to fix these and therefore I would like to find out, whether it is more probably a software or a hardware problem.
I found on this forum that it may have to do with the persist.img, that may have been corrupted by twrp.
Unfortunately I don't know where to get a hopefully working persist.img to try that out.
Things that are maybe relevant are these:
1. The battery was changed, so maybe the engineer doing that broke something
2. During reinstallation of lineage17 I had some problem with twrp not working. Afterwards using lineage recovery worked for installing lineage, but I'm not sure, twrp might have broken something.
3. The same issue also is there on stock android 10.
Can anyone point me in some direction?

I realized that the easiest check for software/hardware distinction would be to just flash a new persist.img.
Is anybody out there, that has a pixel sailfish device with working android 10 that would drop me a message? I should be able to just transplant your persist.img to my pixel sailfish.
I would greatly appreciate it!

Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.

Bongzerker said:
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Click to expand...
Click to collapse
Nonetheless, thanks for your time!
If I may ask for even more of it:
Not sure, whether Pixel XL and Pixel are similar when it comes to their hardware ( I have a Pixel, not a Pixel XL), but if you have repaired many of them, do you think it is at all possible, that the hardware shop that changed my battery somehow broke these sensors or forgot to reattach a cable to them?
I don't plan to hold them accountable, as I really like them, just would like to have a hint, whether going to the hassle of bringing my phone there and thus not having it for a few days has a reasonable chance of success.