Related
Hi,
I just saw today, that there was a very weak red light just next to the proximity and light sensor. It looked like it was flickering at a very high rate!
I tried to restart the phone normally, but the light didn't disappear. After that I tried a reset by holding the power button down for 10 seconds. That made it vanish.
What the f**k was that all about???
Best regards
Casper
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Moved To Q&A
This is best in the Q&A section, as it been written as a question.
h.han said:
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Its The Goverment Spyin On us...Making Sure We Dont Flash Anything Or Even Root...If So It Will Say Tampered And The S.W.A.T. Team Will Come Crashin in Our Homes...
That red light is in fact the actual proximity sensor and it's in use while in a call. If you where not in a call then that was a strange occurance unless you ran some of these sensor testing apps...
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
cawith said:
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
Click to expand...
Click to collapse
That was an odd one... maybe it was a temporary fluke? Strnag nonetheless...
I often use face unlock. The red light turns on when the front cam turns on.
Sent from my HTC VLE_U using XDA
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
decalex said:
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
Click to expand...
Click to collapse
Same here. Have to restart to get it off again. Any help? (TrickDroid 4.3)
Anytime you make a call by any means other than handset to your ear, the proximity sensor will come on and stay lit until reboot or until you make another call via handset.
Example:
Place call> turn on speaker phone> hang up - proximity sensor will stay lit after call;
To fix do this:
Place call from handset (not using speaker phone or hands free) and hang up right away, or reboot device and light will go out.
Same seems to go for calls through hands free as well.
These guys are lying its a bomb isn't it obvious flashing red light HTC controls it if u do something they don't want u to do boom ur hands are no more why do u think the phone heats up so much its a warning don't believe me read the thread in forums about heats in the one s another reason they don't want us to remove back well see the bomb :what:
Sent from my HTC One S using xda premium
Hi All,
My One S also does this. I'm finding it a pain to have to make a call after using speakerphone to turn the proximity sensor off again. Has anyone found out what the cause of this is?
I've tried clearing cache partition with HTC support but still no fix.
Hi all, I forgot to mention that the issue on my phone only happens when the call is ended with speakerphone active. If I turn off the speakerphone before ending the call it does not happen.
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Sv3TL10 said:
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Click to expand...
Click to collapse
You maybe have turned off Viber doing this: http://www.boards.ie/vbulletin/showthread.php?p=80972874
Does it come back after restarting Viber?
Sometimes a restart fixes the problem.
I had the same problem. I uninstaled Viber and the light disipired.
foner81 said:
You maybe have turned off Viber doing this:
Does it come back after restarting Viber?
Click to expand...
Click to collapse
Later I realized that Viber is the reason. Yes. But now it seems that Viber is fixed after last update, and no red light when viber is turned on
Hi all, I'm a little worried as I love my Nexus 5 coming from a Desire Z but I'd say from as little as 30 mins to up to 8 hours or so I have to reset my phone as all the sensors stop working. Installing a sensor monitoring app it says the output is blank on them all.
Screen rotation, compass, maps and the barometer all stop working.
Anyone else getting this?
I don't think its hardware as a reboot fixes it for a while.
Thanks
Edit:
It also seems to have resolved itself after a while, when I installed a step counting app I checked and the sensors and they were all working again.
A bit odd...
I am having the same problem. Which step counting app did you install to keep it working?
brandnamebob said:
I am having the same problem. Which step counting app did you install to keep it working?
Click to expand...
Click to collapse
Hi
It was an app called Moves - but it ate an absolute load of battery life so I uninstalled it rather quick, it was also pretty crap.
I have this issue very rarely now, I just wish I knew what the problem was caused by.
Have you in the past enabled the ART library?
LaurenceGough said:
Hi
It was an app called Moves - but it ate an absolute load of battery life so I uninstalled it rather quick, it was also pretty crap.
I have this issue very rarely now, I just wish I knew what the problem was caused by.
Have you in the past enabled the ART library?
Click to expand...
Click to collapse
I have not used the ART library yet.
The app I noticed the problem in is 'Reddit is Fun' but It is most likely a background app that is causing the issues.
I uninstalled a bunch of them, including Elixer and PressureNet, just to see if I continue to have the issue.
Ahh OK. I installed an app called barometer+ so I could make use of the pressure sensor. I think it has background logging as well. Perhaps it is this causing it.
I'm having the same issue. Right now I'm just restarting my phone whenever I notice it.
smalovic said:
I'm having the same issue. Right now I'm just restarting my phone whenever I notice it.
Click to expand...
Click to collapse
smalovic do you have any weather apps or pressure sensor apps (or anything like that)?
Have you tried the ART libary at all?
Thanks
LaurenceGough said:
smalovic do you have any weather apps or pressure sensor apps (or anything like that)?
Have you tried the ART libary at all?
Thanks
Click to expand...
Click to collapse
I have PressureNet installed. I switched to the ART library but I'm getting the same problem.
Hi all,
Same issue here. I'm using syspressure app for background pressure logging. I switched to a every 5 mins sample rate instead of 1. Now I will try to see if it's happening again.
Sent from my Nexus 5 using xda app-developers app
My Barometer+ app was set to hour updates...
I guess we can all relate to a pressure app, probably the cause...
Setting SyPressure sample rate to 5 minutes has done nothing.
After about 30 mins of standby all sensors stopped working again.
Now I have disabled the widget of SyPressure that means no background logging anymore.
I will update the status.
---------- Post added at 09:16 AM ---------- Previous post was at 08:54 AM ----------
UPDATE:
After about 30 mins of standby all sensors still WORKING.
Now I will try to wait much more than 30 minutes
I will update!!
UPDATE 2:
After more than 1 hour, sensors still OK!
I will try overnight and check it out.
Anyway also battery perfomence seems to be better, 1 hour ago charge was at 33% and now is still alt 33%
PS. Sorry for my english
I uninstalled PressureNet yesterday and left it overnight. Everything's still working this morning!
It must be some glitch with the barometer apps.
Same problem here. I also have sypressure on my phone. I've uninstalled sypressure a day ago, and for now everything work fine
I have the same infuriating issue.
My device: Nexus 5
Build: KRT16M
Unlocked, TWRP Recovery, Root, Chainfire's SuperSU
I also have "pressureNET" app installed for logging pressure readings.
After reboot all sensors work fine. Installed app "Sensor Sense" confirms this. Then randomly at some point in time, 2 or 5 or 8 hours later most sensors stop working and it is always the same ones.
Battery, Location, Light, and Proximity all continue to work fine indefinitely.
Pressure, Accelerometer, Gravity, Gyroscope, Linear Acceleration, Rotation, and Magnetic Field all fail and no apps can make a call on these sensors as part of their function.
This is most readily and frequently apparent in (i) the "Gallery" in which rotating the screen no longer results in auto-rotation of images, (ii) orientation of recorded images and videos with "Camera" in which the capture is locked into one orientation and videos shot in landscape (for example) end up with an on-their-side portrait orientation when viewed, and (iii) YouTube videos can no longer orientate when playing and the screen is changed to a different orientation e.g. load video in portrait mode, flip horizontal, and video no change or adaptation occurs, (iv) going into a PhotoSphere results in a black screen of nothing, (v) "Compass" doesn't work, (vi) "Skymap" doesn't work, etc. etc.
Would love to see a resolution to this issue; this is the first forum or instance of discussing the problem on the Web that I have found.
Robooting the device resets everything and all sensors (and apps) work fine as normal.
markbruce said:
My device: Nexus 5
Build: KRT16M
Unlocked, TWRP Recovery, Root, Chainfire's SuperSU
I also have "pressureNET" app installed for logging pressure readings.
After reboot all sensors work fine. Installed app "Sensor Sense" confirms this. Then randomly at some point in time, 2 or 5 or 8 hours later most sensors stop working and it is always the same ones.
Battery, Location, Light, and Proximity all continue to work fine indefinitely.
Pressure, Accelerometer, Gravity, Gyroscope, Linear Acceleration, Rotation, and Magnetic Field all fail and no apps can make a call on these sensors as part of their function.
This is most readily and frequently apparent in (i) the "Gallery" in which rotating the screen no longer results in auto-rotation of images, (ii) orientation of recorded images and videos with "Camera" in which the capture is locked into one orientation and videos shot in landscape (for example) end up with an on-their-side portrait orientation when viewed, and (iii) YouTube videos can no longer orientate when playing and the screen is changed to a different orientation e.g. load video in portrait mode, flip horizontal, and video no change or adaptation occurs, (iv) going into a PhotoSphere results in a black screen of nothing, (v) "Compass" doesn't work, (vi) "Skymap" doesn't work, etc. etc.
Would love to see a resolution to this issue; this is the first forum or instance of discussing the problem on the Web that I have found.
Click to expand...
Click to collapse
Uninstall pressureNET, reboot, and you should be all set.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Resolved
I confirm that "pressureNET" was the app causing the other sensors to crash.
50 hours after uninstalling and rebooting there has been no recurrence of the problem; all sensors and the handset have worked flawlessly throughout.
markbruce said:
I confirm that "pressureNET" was the app causing the other sensors to crash.
50 hours after uninstalling and rebooting there has been no recurrence of the problem; all sensors and the handset have worked flawlessly throughout.
Click to expand...
Click to collapse
Reading the other replies, it seems as though any barometer app causes the issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app
smalovic said:
Reading the other replies, it seems as though any barometer app causes the issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Damn, I'm having the same issue intermittently. Might have to uninstall the app until they get this sorted out, which is a shame because the sample size for reading in my region is probably very small.
Looks like the pressureNET dev is working on a fix. He posted on Reddit: http://www.reddit.com/r/Android/comments/1qzg0n/nexus_5_sensor_issues_whats_going_on/
Sent from my Nexus 5 using XDA Premium 4 mobile app
I think there is something wrong with some permissions on my Feiting H9500+. After booting my phone both of the internal cameras works fine. But after opening the camera app for the second time, the screen shows up green (check screenshot which i included as attachment). The only solution i know to fix this is to reboot my phone again. Which is ofcourse very annoying.
Does someone know a more permanent solution for this 'green screen camera' problem?
W0kk3L said:
I think there is something wrong with some permissions on my Feiting H9500+. After booting my phone both of the internal cameras works fine. But after opening the camera app for the second time, the screen shows up green (check screenshot which i included as attachment). The only solution i know to fix this is to reboot my phone again. Which is ofcourse very annoying.
Does someone know a more permanent solution for this 'green screen camera' problem?
Click to expand...
Click to collapse
I have that problem sometimes too, have the same devices.
There is no fix or patch, couze nobody is or has worked on the fix..
But trying a diffrent rom, helped me..
www.needarom.com
Same phone and same issue here...
W0kk3L said:
I think there is something wrong with some permissions on my Feiting H9500+. After booting my phone both of the internal cameras works fine. But after opening the camera app for the second time, the screen shows up green (check screenshot which i included as attachment). The only solution i know to fix this is to reboot my phone again. Which is ofcourse very annoying.
Does someone know a more permanent solution for this 'green screen camera' problem?
Click to expand...
Click to collapse
I have this H9500+ I bought at Aliexpress. After a couple of months this issue start to happen. I think it has something to do with software and not hardware because if you poweroff, remove the battery, put back and turn on it will come back to normal. At least for some more time!
It probly has something to do with some software I have installed. But since I have installed a ton of apps I don't know witch one coused this to happened. Best bet I think would be to installed a new fresh ROM from scratch and see if the problem persists.
Cheers,
Hi
My phone was working perfectly until yesterday, I downloaded some apps and then Uninstall them but then I started noticing the rotation wasn't working then I put on auto still not working. Then installed some sensors test and cpu z but all showing not supported or don't even have accelerometer and gyro, not working or stuck is another thing but not competible or don't even have made me think it's a soft problem, that's why did full reset but same results. Put it on safe mode same results. Also when I open maps now only show round dot. So Idk it's software or hardware that's why came to ask you guys
Don't have an answer to the problem. Just letting you know you posted in the wrong forum (see pinned post). You might get more eyes on your issue in the Q&A/Help section.
https://forum.xda-developers.com/lg-g3/help
Guys!
Do you experience proximity sensor issues while answering calls on OP7P?
For me while I'm on calls. The display comes on and gets disturbed and get pressed by my ears all the time.
Also any idea of where the proximity sensor is located on OP7P?
Thanks ?
Yes, I'm having the same issues. While I'm on calls I often activate the notifications pulldown. It would be nice to know how to fix this.
If you pull down the notification shade, the sensor is located just above the fifth icon on the first row. IE behind the screen.
If you pull the shade all the way down it is above and between the third and fourth icons. Easiest way to describe it. Put your thumb over that area with auto brightness on to watch the slider move.
Annoying while on a call that the screen comes on.
I'm experiencing the exact same issue with the caller app.
I also tried to make a flip cover to turn screen on or off with a proximity sensor detection app and it didn't work either.
I search a little in engineer mode (*#808#) and found that there is multiple proximity sensor, the IR sensor work quite well but it doesn't seem to be the default one.
The default one seems to be the ultrasonic sensor which works really bad.
There is also a "TP" proximity sensor which seems to be a near field detection which seems to work if I move my hand near the screen.
The sad thing is that in dedicated app to use or test proximity sensor (and in antutu or else) only one proximity sensor is listed (The ultrasonic one I guess) so you cannot switch to use the one which is working well.
Isn't this in the wrong place? Shouldn't it be in the Questions and Answers section?
Mods?
Probably just here looking for a mod to improve the situation
Actually I was going to open a new thread in Q&A when I found this one with the same subject and problem.
Do you think I need to open a new thread?
Is any of you experiencing the same issue as I described in my answer?
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
I tried to with no luck but as I explain in my first message the IR sensor is only used when screen is off (that's why it could help with double tap to wake)
But when screen is on another or couple another sensors are used and you can't calibrate them.
I think ultrasonic sensor is used when screen is on.
Do someone tested proximity sensor with any app on the play store? (Like proximity sensor test)
Put it on a table and check if it's working, mine is absolutely not. If I hold it like I was about to phone it works a little but it's not impressive.
Since I got 9.5.7 (EU version) earlier this evening screen turn off when I make a call.
I'm having this issue since 9.5.8... It's very annoying and I'm really disappointed, I often turn on airplane mode during a call... I tried to calibrate but it doesn't work.
I'm very very frustrated
schmeggy929 said:
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
Click to expand...
Click to collapse
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
dallasnights said:
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
Click to expand...
Click to collapse
This...
I've been having issues with phone calls but more so with pocket issues.. When I had the 6t pocket mode kept the phone neutral but this phone doesn't seem to have an accurate prox sensor.. Is there a way to activate a pocket mode?
Sent from my [device_name] using XDA-Developers Legacy app
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
pinzarualex said:
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Click to expand...
Click to collapse
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
But I have had this issue since release.. Do you a link to this information? If that's the case maybe someone can look into the firmware and see if it's minor tweak that can fix it?
Sent from my [device_name] using XDA-Developers Legacy app
Jack_Sparrow_ said:
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Click to expand...
Click to collapse
Of course it didn't fix anything...
Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
j0hnee said:
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have reported this to Funk wizard on the OOS support thread and he said he cannot reproduce it anymore on the latest test build, so... We have to wait for next firmware release and see if that is indeed the case