I dont what's happened to my phone as shown in the picture attached the red light is active during active call and when i keep the phone near my ear the screen does'nt turn off, and the battery got empty just after 1-2 hours
i have to say that the red light is on just during an active call
That is the proximity sensor, it emits IR that can be seen on most CMOS sensors (cameras).
This has already been posted on cfX thread and then i found this thread. I have this problem without making calls at all, too.
Hi,
came from cfX to CM 10.1. did a dirty flash (cleared some apps data) without too much trouble. But there is one thing i encounter quite regularly after a dirty flash. Yes, i know i should do a full wipe but the fact that the problem occured already on YellyTime, CfX, a MIUI rom and this rom after a dirty flash makes me wonder...
its always the same: no problems at daily use but randomly the (i guess) IR sensor starts to glow weakly red on the top right corner behind the grill. As soon as it starts, battery drain is pretty high and there are only hours left for my phone. There is no obvious app with a higher than usual drain.
This is not a request for a fix, rather a call to the community out of couriosity
if somebody maybe has an idea he/she could save me from some full wipes (2 step auth is a pain here)
have a nice evening everybody!
Click to expand...
Click to collapse
after doing a full wipe and installing cfX SR2, situation got worse: now the phone screen stays black occasionally if the red light is on and i have to pull the battery. One thing i noticed is that it mostly happens when there is an internet connection
As has been said allready it's the proximity sensor, not a light.
Install Proximity recalibrator to adjust the threshold values.
ah ... i´ve read your reply too late. already did this
http://forum.xda-developers.com/showthread.php?t=1970972
and it solved my problem. But thanks anyways
Related
Hello,
I got a problem with my flashlight.
It turn's randomly on and off but it's only for about a second.
It doesn't matter if the device's screen is off or on or if the device is connected with the pc or not.
Also the flashlight turrns on for about a second if I restart my device. The flashlight turns on and off and then the screen lights up.
Is there a known bug with an app or radio? I tried already two different roms and two differentt radios.
If there is no way to solve the problem, is there a way to deactivate the flashlight so no app can use it?
greetz Nightskill
Hello all,
I found out, that the Flashlight turns on if I touch the Desire at the top left of the phone. Exactly at the intensity and proximity sensor.
Is there a known Problem with the Desire?
Never heard of it before, but damn that must be annoying
Are you using original rom?
Yes, It's very annoying...
Yes I'm using a pre rooted original Rom. But I tested already other roms.. same problem...
Sent from my HTC Desire using XDA App
Sounds weird, but if you did not do a full wipe when switching ROMs then that may be a cause I'd imagine.
how about removing the Flashlight.apk and install it again
have you tried other application for use the LED as flashlight, like teslaLED etc?
Having the some problem here, and my charge led light has also stoped working but the battery is charging, what can I do do fix this beceause its not showing indications
Very same problem with my Desire. Did not install any custom roms, only the updates that came automatically from HTC.
Yesterday did a 'hard reset', (reboot with volumn down button, and choose 'clear storage', but this did not help. I only needed to install every program i again
On the other hand, maybe this was not a real 'hard reset', because the HTC is still on the 'updated version', not on the android version as it was when I did purchase the phone.
Version now is: 2.29.405.5.
It looks like a bug in the system, not a hardware problem, because the flashlight does work sometimes (as described in the first post).
Searching the internet did not work, there are more people with the same problem, but not any solutions (yet).
Any new Informations?
I'm now using CyanogenMod 7 (7.0.3) but the issue is still the same. The radio is upgraded to the newest version. (32.54.00.32U_5.14.05.17)
Is it possible to swap the LED (and Camara) Modul (or board) without replacing the whole mainboard?
Me too
I got the same problem.
bad luck~~!!
I tried many ROM or RADIO or RECOVERY,but can not slove this problem.
The Problem still exists, but I got interessting news.
The problem is caused by the Proximity Sensor.
You can test this very simple:
Download an app which shows the value of your Proximity sensor.
Hint: My Desire only shows 0cm or 9cm value. This is normal, because our sensor is not capable of reporting all intermediate values. Then just hold something in front of the Proximity Sensor (left top of the Phone) and remove it. The value will change and after you removed the thing, the flashlight will switch on for some miliseconds.
Unfortunaly I don't know how I can solve this problem. I also don't know wheather it is a software or hardware problem.
I hope somebody can give some hints or something else.
I am on CM 7.0.3 and I should admit that I use the flashlight quite often. On the high brightness option.
Everything was ok for months but now I get a blueish tint when the flashlight is on. For example, if the normal colour is white (around 6000k), now I get 8000k. Moreover, the led is not as bright as it used to be.
I have never used the torch app, for more than 4-5 minutes constantly on.
Is the led dying?
Got this problem two times already, not even flashing with RUU helped.
Returned my HTC for warranty, when it arrived flashlight worked fine (as per return slip, some module was replaced) but the light sensor was screwed. During phone calls LCD stayed off all the time, it worked only under direct strong light. went back for repairs this time got mainboard replaced.
After a while flash stopped working again and soon after, or maybe at the same time, LCD stopped turning off during phone calls and touchscreen stayed active.
Went for another repair. not sure if i want the same thing to happen again, if it does, i should get a new phone, but i know that it will be a lot of hassle.
Same problem here. This morning the flashlight was working without problems, now it's dead. So this could get the 3'rd mobile replacement within 2 weeks, the 4'th at all. I've already tried CM7.1RC, InsertCoin1.1.0 and the original RUU - no effect...
Now I'm thinking about returning the mobile (possible after 3'rd replacement/repair when You can present the failure in the shop) and ordering a HTC Sensation instead... Maybe this will be better ???
Thanks to those who earlier gave feedback on installing Froyo. I have since been workign on getting the battery to last longer and such. However three questions that much searching has failed to answer.
1. With the speaker breaking issue, my phone was made October 2010 and the speaker broke in around April. The service center fixed it no prob. Funny thing though was that I often used earphones, but only ones with 4 contact rings on the plug. The day it broke I had used my MP3 earphones with three rings and immediately after the speaker would not work. I had assumed that it was the use of the three ring earphones that broke the speaker. Not so sure now. So, is it possible to use any headphones (even ones without a mic) on a cell phone or do normal earphones break things when put into a phone?
2. What the bleeping heck do the different front LED light colours all signify??? Also, why do I get a dark red glow when reading at night from the LED (no, it is not reflected light)? Lots of bits and pieces but a nice list would be gold.
3. Where (and why) did the 3G widget go? It was there in Eclair but not in Froyo.
Thanks,
TME
And, perhaps one interesting bug that I would like to hear if others have experienced.
On three occasions my phone as reset / rebooted for no reason. I am tracking that down, so no worries, however my SIM chip is locked yet when it reboots I do not need to re-enter the SIM PIN. When I do a normal reboot I do have to enter it. Is this a bug??? Seems so as my original ROM was not like that and it does seem to be a bit of a security lapse. Thoughts???
It's normally called soft reboot that bypass the simlock. And this also applied if phone freeze and reboot itself. A hard reboot would definitely need the sim password. Another term used is soft reset and hard reset...
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.4 - XDA Premium
teachmeenglish said:
2. What the bleeping heck do the different front LED light colours all signify??? Also, why do I get a dark red glow when reading at night from the LED (no, it is not reflected light)? Lots of bits and pieces but a nice list would be gold.
TME
Click to expand...
Click to collapse
i know a few, but not 100% sure on some, like:
1. flashing green - incoming message.
2. flashing blue - incoming/missed call
3. steady white - battery charging
4. steady green - battery full or near fully charged (>90%)
5. red (not sure steady or flashing) - battery low
answer 2nd
I have same prob but that light red led is come from sensor part not from front notification LED .
I don't know why its on but it is coming from sensor part not from LED part.
Regards,
Cheat
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
you can download power setting free version from market and you can have all settings in that wifi/3G/brightness/bluetooth/sync etc..
Thought I'd share my experience about this. I was running Paranoid Android 0.9, no issues at all. One day I was talking on the phone and noticed the screen flickered quickly... then it just stayed on. I hung up the phone a minute later not thinking much of it.
Well today I made some phone calls and the screen never turned off.. I had to manually turn it off via power button. I installed Paranoid 1.1, no changes. I flashed Trinity kernel, no changes. Just a bit ago I fully wiped the device and flashed the latest 6/4/2012 CM9 Nightly and the issue is still present.
At this point I'm guessing there is definitely a hardware issue. I have never dropped this phone and it's in mint condition aesthetically. It's the GSM version bought via Expansys.. and I won't waste my time with warranty through them I'll just bare with using the power button to turn the screen off/on during calls.
Another note, I noticed if I tap or press firmly on the proximity sensor area during a call it will trigger the screen to momentarily turn off.
Could this possibly be a CM9 issue (Paranoid is built from CM9)? I may try flashing a rom not built from CM9. I've searched high and low on the internet and NO ONE has had this issue which is leading me to believe that there's no way this is hardware related.
All roms are based off of AOSP.
I guess I'm the only one.
There are some apps that can test your Proximity sensor, though I can't remeber the app name.
/Edit: Link to the app.
Have you tried franco kernel to check if this happens aswell? You can then pin down the possible kernel related issues.
Firmware again plays a major factor? What firmware are you on? Mines came as an OTB 4.0.2 and I too had this similar issue where I had to manually swipe my finger against it, Upgraded to 4.0.4 and the issue went away. Weird.
Misledz said:
Have you tried franco kernel to check if this happens aswell? You can then pin down the possible kernel related issues.
Firmware again plays a major factor? What firmware are you on? Mines came as an OTB 4.0.2 and I too had this similar issue where I had to manually swipe my finger against it, Upgraded to 4.0.4 and the issue went away. Weird.
Click to expand...
Click to collapse
I'm on 4.0.4. I just flashed Android Revolution (4.0.4 based rom with the stock kernel) and the problem still persists. It's very intermittent. Sometimes the proximity sensor detects an object close thus turning the screen off, but it only turns it off for 2-3 seconds or sometimes not at all. I wonder if a piece of dirt/dust is sitting right on the sensor?
I tried a couple proximity sensor testing apps out there but none of them work and say "If your reading displays nothing or the maximum value then your device does not support reading of proximity sensor values".
The apps display a max of 5cm with a resolution of 5.. and the current value is ALWAYS a 5.
I just find this hard to belive I'm THE ONLY ONE on the interwebz, out of MILLIONS sold, who has reported this problem.
Ok, I'm a complete idiot....
Turns out the Galaxy Nexus proximity sensor ONLY works when the phone is in the upright position!!! I kept testing it with it flat on the table and, by design, it's SUPPOSED to keep the screen lit.
After installing the 5.0.1 update on my ATT Note 4 I noticed the red light was on when I put my phone down. After testing it for a while the heart rate sensor red led comes on when anything touches it. I restarted phone and killed all running apps but nothing stops it. Sometimes it goes off after a few minutes and sometimes it doesn't happen but sometimes it comes on and stay on until whatever made contact with the sensor goes away.
So for now I can't lay my phone down on it's back because the sensor can come on. I can't put it anywhere where anything could touch the sensor because it will eventually come on. No pocket nothing. I never had this problem until right after the 5.0.1 update.
For now I'm stuck putting my phone face down and carrying it because that is the only way I can be sure the sensor won't light up and kill the battery.
I may have never noticed this except that it took the update so long to download and it was bedtime when I finished and noticed the light.
Anyone else seeing this or more importantly anyone able to tell me how to stop it?
@phobia09 made this post in one of the "lolipop is out" threads.. see if it helps you...
http://forum.xda-developers.com/showthread.php?p=59666946
Basically start s health, take a heart rate reading and close s health.. his light stopped coming on
Tried S Health but that didn't work.
Thanks for the info. I previously started SHealth and took pulse, stress and PulseOX readings but it still comes on.
What running the heart rate check in S Health did for me was stop it temporarily. Within an hour of doing that, it was back. Wish it had been permanent. Leave it to AT&T to screw up, I don't believe international N4's had this issue.
Sent from my SAMSUNG-SM-N910A using Tapatalk
This is what I have done so far but it has not solved the problem. I still can't put my phone in my pocket or lay it with the back down.
Wiped the phones cached partition
restarted phone several times
removed battery for about 15 minutes
cleared data and cache from Shealth App
disabled Shealth app
It seems like starting SHealth and taking your heartbeat stops it for a short time but the problem comes back quickly wether SHealth is running in the background or not.
I can put up with some issues but I can't live with this. It seems pretty serious and is a big battery drain.
phobia09 said:
What running the heart rate check in S Health did for me was stop it temporarily. Within an hour of doing that, it was back. Wish it had been permanent. Leave it to AT&T to screw up, I don't believe international N4's had this issue.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Yeah they do. I read the other Note 4 forums too and this issue appears on all Note 4 versions running 5.0.1
Same issue here. I ended up doing a factory reset and starting over with Lollipop. So far, the sensor has not lit up again, but then, I have not started up S Health since resetting the phone. When it was happening it only lit up when I lay the phone down on a light colored surface. On a dark surface, it didn't light up at all.
Fixed
I was told it was Google FIT in another forum and it was a known problem. Uninstalled FIT and now everything is fine!
I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?
I experience the same thing sometimes with stock rom
keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...