Does anyone have problem with proximity sensor not working properly in different situations? I have already mentioned 6 owners facing that issue. Still no info whether this is a hardware or a software problem. Nokia tech support answers casually to all requests with this issue.
We need more reports about that to be heared in nokia support, so everyone who has ever had that issue please add a post there describing when and how it happened.
Same here, sensor died after almost 4 weeks of normal operation. Not really died, though - sometimes it started to work fine, then failed, then again... For what is worse, I couldn't find any dependencies (even that some people say it fails under the direct sunlight).
Anyone else?
Sensor seems to work fine on test apps but when calling the screen does not black out.
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 ???
I recently bought a Zenfone 2 (ZE551ML) which works exceptionally well however today I've noticed something odd (probably would have noticed it before but the phone was actually a gift so not at all times with me).
During a call the proximity sensor will only turn off the screen when the phone is close but it will not turn the phone on when I move it away. I've gone through many online articles and in the majority of cases it was a problem with the screen protection. However, I do not use any kind of screen protection.
Additionally I've noticed something really odd. Zenfone 2 has an inbuilt testing suite (SMMI Test) which allows testing various parts of the hardware. The proximity sensor test consists of three steps (NEAR, AWAY, NEAR). They should be self-explanatory (NEAR triggers when an object is close, AWAY when its far). In my case the first step (NEAR) always triggers after the test starts but the other two (AWAY, NEAR) simply won't. That's until I use the app switch button (next to the home button) to re-enter the test application again. The other two steps then complete successfully.
Considering the behavior can I rule out a hardware problem and pin the issues to the software?
The proximity sensor issue was successfully resolved by reverting back to the 2.20.40.90 firmware. The 2.40.40.97 version (at least WW) obviously has issues with it.
You can find detailed instructions on how to perform stock recovery in this topic (http://forum.xda-developers.com/zenfone2/help/reverting-to-stock-firmware-t3225632).
Once again props to kanagawaben and all the people which contributed to this topic.
I've put up with the proximity sensor malfunctioning once i take or make a call, the touch screen not working [restarting it solves the problem, after i had the screen replaced due to complete failure to function, which seems to be evident of a software issue] and the UI keeps crashing. I know this isn't a very smart question, but would rooting to the right ROM solve all these bugs? These seem to be a software issue, but again; I'm nowhere close to an expert on this. Also, what I mean by the proximity sensor malfunctioning is that when the phone is in a call, the screen doesn't turn on even if it isn't close to my ear or anything else.
Hi
I'm searching for anyone else having the same problem as me and other people that i've seen in Lenovo Forums
I'm having different problems, but the most important for me is the proximity sensor, because once I answered a phone call, it makes impossible to hang up because the display turns black and it doesn´t "wakes" until the phone call has ended. The same problem with audios in whatsapp.
Another problem is that Moto Actions like turn on the flashlight with a shake, and open the camera with a twist doesn´t work anymore. Plus, the vibrator started to fail, having an unusual behavior until it just stopped.
And the device is not recognized correctly in any computer I've tried, it just appears as "unknown device", and the device doesn't show the options that use to appear when connected to a computer, it just says "charging".
I want to think that all of them are software problems, and not hardware problems, because they all started after the june 2019 update, and, as I said, there are other people having the same problems, and I think it would be a big coincidence if all of us have the same problems with our hardware.
If any of you have had the same problems, could you tell me if you could find a way to fix it? Or, anyone has any idea how could I solve, at least the proximity sensor problem, it would be better if the device don't turn off the screen anymore during phone calls.
I've tried reinstalling the drivers in 3 different pc's, and any of them worked, but when I tried with another device (Moto z2 force) they all worked. I've done factory reset three times, and one hard reset, with no changes. Could someone help me?
Thanks for reading.
Well, sound like... simply failing phone ? RMA ?
emcom said:
Well, sound like... simply failing phone ? RMA ?
Click to expand...
Click to collapse
Do you think that? I've had this phone for a year and a half, and I've never had any issue, until the last update on june 2019.
Maybe is a coincidence and my phone started to fail just after the update, but to be sure, I want to know if there's someone else having the same issue, and maybe someone could fix it.
I've had these problems a few months ago too, but back then I was thinking it was related to a hardware problem cause I had to send my phone to fix the screen (broken glass) and after that I noticed that the moto actions wasn't working properly, as the flash light from the frontal camera and the most annoying of the problems, the proximity sensor that would stop working when I got a call or audios in whatsapp. All of these was solved a couple weeks ago tho, after I had to fix my screen again (yes, 2 times in 3 months, congrats), just days before the android pie was released, so I can't say exactly what fixed it
Hi guys,
Lately I've noticed that my fingerprint sensor does not work properly anymore.
Not sure if it's a hardware or software issue?
Though, the test HW for Fingerprint Sensor from Smart Doctor app reports Good status during all tests.
The behavior is strange and not consistent, most of the times it will work fine but from time to time I cannot unlock/wake the phone with the fingerprint sensor, it's not like the fingerprint is not recognized, it's more like putting the finger on the sensor and nothing happens (it doesn't vibrate like is reading it or not) . Not sure if is related to the phone being in standby for longer period, or I don't know ...
I'm more inclined to believe it's a software issue, and seems to have occurred lately after last update to Android 10 (v30f-EUR-xx, phone type LM-G710EM).
I've tried may method, deleting the finger prints and add them again , even did a factory reset but the issue seems to come back.
Do you guys have such issue?
Any idea how to diagnose this further?
dinoc said:
Hi guys,
Lately I've noticed that my fingerprint sensor does not work properly anymore.
Not sure if it's a hardware or software issue?
Though, the test HW for Fingerprint Sensor from Smart Doctor app reports Good status during all tests.
The behavior is strange and not consistent, most of the times it will work fine but from time to time I cannot unlock/wake the phone with the fingerprint sensor, it's not like the fingerprint is not recognized, it's more like putting the finger on the sensor and nothing happens (it doesn't vibrate like is reading it or not) . Not sure if is related to the phone being in standby for longer period, or I don't know ...
I'm more inclined to believe it's a software issue, and seems to have occurred lately after last update to Android 10 (v30f-EUR-xx, phone type LM-G710EM).
I've tried may method, deleting the finger prints and add them again , even did a factory reset but the issue seems to come back.
Do you guys have such issue?
Any idea how to diagnose this further?
Click to expand...
Click to collapse
Make sure your battery isn't swollen. A swollen battery will take out the fingerprint sensor first because it's right on top of the connection.
Hmm, interesting, from the outside I can't feel any difference, the back seem flat.
Exactly the same problem here. But if I check the sensor while it is not working I get a "sensor not respondong error".
Did you solve somehow?
Thank you