Hi, Iam in Viperx v2.7.1. The proximity sensor is not working in this. Can anybody advice me?
greatervoice said:
Hi, Iam in Viperx v2.7.1. The proximity sensor is not working in this. Can anybody advice me?
Click to expand...
Click to collapse
What is your hboot version?
Sent from my EndeavorU
Hi
My hboot is 1.12
Then your problem could be from a bad flash(reflash the latest version of the rom)
Sent from my EndeavorU
Did it work perfectly before flashing the ROM?
Mine's currently getting it's proximity sensor fixed. It was hardware related...
Actually I bought four months old phone. I have not checked at the time of purchasing. After rooting and flashing custom rom proximity sensor is worked where weak. From two days onwords it is not yet all working. So, please anybody advise me. I checked two other custom roms also. But no use.
peedub said:
Did it work perfectly before flashing the ROM?
Mine's currently getting it's proximity sensor fixed. It was hardware related...
Click to expand...
Click to collapse
Actually I bought four months old phone. I have not checked at the time of purchasing. After rooting and flashing custom rom proximity sensor is worked where weak. From two days onwords it is not yet all working. So, please anybody advise me. I checked two other custom roms also. But no use.
Proximity Sensor Finder from the play store can help.
I found that when I squeezed the phone just below the camera, the sensor would work temporarily. It seems it's not an uncommon fault.
Related
Hi all,
I recently received a replacement Desire for my 'faulty' one. I tested all basic functions before walking away and everything checked out.
After I rooted it and installed Modaco r17 ROM, My proximity sensor sensitivity dropped dramatically. When I make or receive a call, the screen blanks as it should, but when I move the phone away from my face, it stays blank. I can't end the call or use speakerphone or keypad. The only way to bring the screen back is to hold it under a very bright indoor light, or direct sunlight...or pull the battery, of course.
I loaded a sensor test tool (SensorList) and it confirms that the sensor is reacting only to very bright light. I've checked that my cover doesn't obscure the sensor and tested that the behavior is the same with or without the screen protector.
I tried a couple of other ROMs, Modaco r19 and Shadowfrost v13. I un-rooted my phone and dropped a stock HTC ROM back onto it...and the problem is still there!
I'm waiting on a reply from HTC service about it...but in the meantime...any advice? I've seen a few posts around the web with this problem, but no definitive solutions or answers.
Question Added to Developers
I've noticed a smattering of people in various forums, with various of the newer android phones having proximity sensor problems. Perhaps these are not quite as finely calibrated as the other sensors, or not as reliable. Have any of you developers seen a way calibrating or adjusting the sensitivity? Perhaps a value in a system file we can change?
Thanks in advance.
Added question and bumped
Apols if this is pushy. I added a question to you developers, so giving this a bump.
phantomfisho said:
Apols if this is pushy. I added a question to you developers, so giving this a bump.
Click to expand...
Click to collapse
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Daelyn said:
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Click to expand...
Click to collapse
Images:
1. Holding hand over phone screen
2. Clear view of the screen in dimly lit room (it's quite cloudy )
3. While running FroYo
This does seem like Sensor List correctly detects and measures the proximity/light sensors in FroYo on an HTC Desire, or am I mistaken?
Ditto Issue
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
nayajoeun said:
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
Click to expand...
Click to collapse
Thanks John. I tried the same thing with the same result.
I ended up taking it in to HTC. Luckily I came across a good service rep. He said they'd seen some quality problems with the first batches of Desires and mine was not the first faulty proximity sensor they'd seen. My guess is the timing with the rooting was coincidental.
They would have replaced it, but they didn't have any replacement stock at the time...more evidence of early quality issues. They gave me priority and repaired it in 24 hours. It's been running fine under a number of ROMs since.
BTW I had problems de-rooting and reloading the stock ROM. Then I realised I just had to have the original goldcard in the phone and presto! One day I'll learn to RTFM properly.
Cheers mate and good luck with yours.
I have also this problem. When I make a phone call screen goes black immediately and there's nothing you can do. After the call is over I can wake up screen by pressing power button. I'm not sure when it started because there's been so many variables. I even destroyed my invisibleshield thinking it caused the problem.
Sensor list and sensor dump says that max value for proximity sensor is 1. Screenshots above there was at least 9. Also light sensor doesn't work at all.
I tried to unroot and go back stock but the problem still exist.
Have anybody found a way to control these sensors or do I have to send my phone to HTC to get it repaired?
Thanks in advance!
Hi, I have the same problem here with my proximity sensor since I have used a custom ROM (I don't remember wich one because I have tried so many Froyo ROM before the OTA).
I can't send my desire to HTC because my phone is out of waranty since I have installed all these ROMs.
Does anybody's got an idea, some help from devs ?
OK,
Maybe I'have found a solution to the proximity sensor's problem... At least my proximity sensor is working normaly now.
What I have done (you can found all in the xda posts) :
1. Going back to Hboot 0.80 => forum.xda-developers.com/showthread.php?t=741672
2. Rooting the desire and install the new recovery using unrevoked
3. Installing the OTA 2.2 without the Radio 5.09 (not a leedroid or djdroid or any other ROM, just a 2.2 rooted)
4. Configuring my phone
5. Installing the 5.09 Radio
I don't think that I have doing anything else, but now I can call someone even in the dark and my screen doesn't stay blank anymore !
Hope this could help someone.
is there a way we could use light sensor as a proximity sensor. I saw some thing like this for hero ? .
Im on CM7.1 RC1
Why would you want to? The DHD has both already and seperate.
raze599 said:
Why would you want to? The DHD has both already and seperate.
Click to expand...
Click to collapse
Cause i have encountered multiple times the proximity sensor fails to work.... tried the proximity sensor config app multiple times on multiple rom's/multiple kernels ! and it works for some time but then starts failing after some time.. I know its not my hardware fault as it is a new mobile.
Did it work properly on the stock ROM? Even new handsets can develop faults.
raze599 said:
Did it work properly on the stock ROM? Even new handsets can develop faults.
Click to expand...
Click to collapse
Yup it did
Hi!
I got a rooted DZ with several rom's tried out.
I believe that in the Stock OTA-ROM everything worked fine.
Now I'm at the Vision-Desire-HD-Sense 3.0 .
The light sensor is working a bit, but shows at darkness 10, at daylight 40 and in the sun 160. Another Handy shows 160 at daylight and 360 in the sun.
The proximity sensor always shows 9.0 ...
Is the sensor damaged or can I replace some library's or config files in the ROM?
Thx!!!
Domi
maybe is the rom. Try reinstalling it.
domi65
Did you find the solution?
I guess I have the same problem.
I have the same problem. Tried differebt ROMs, but it still don't work.
Did anyone solve the problem?
CaKTYC said:
I have the same problem. Tried differebt ROMs, but it still don't work.
Did anyone solve the problem?
Click to expand...
Click to collapse
If it's anything like my Desire Z, your phone will be permanently affected by this. My light sensor just stopped working one day, and never started working again.
LiquidRain said:
If it's anything like my Desire Z, your phone will be permanently affected by this. My light sensor just stopped working one day, and never started working again.
Click to expand...
Click to collapse
so, the only way is service center?
As title says: since i rooted my desire hd and flashed a custom rom, the proximity sensor ( G-sensor) and compass aren't working anymore. Tried to calibrate, reset, hard reset, flashed other roms, nothing helped. While calibrating, nothing moved, not the levelers and not the needle of the compass.
What relation do they have together? Is it one part? Could it be a hardware problem or just software?
I noticed some threads about a locked G-sensor. Tried to "shake" them loose. No result. Who can and is willing to help me? thnx.
Mine proximity s. isn't working either. I guess I will take it apart and have a look at it, could be dust or smth.
-SmOgER said:
Mine proximity s. isn't working either. I guess I will take it apart and have a look at it, could be dust or smth.
Click to expand...
Click to collapse
I replaced my Earspeaker yesterday since the sound had been really bad for som time.. while doing this I removed loads of dust located behind the Grid at the top the phone.. doing this ofc fixed the sound, but i also made my Proximity sensor work again.. and made the GPS get a better signal.. so really try cleaning it.. does wonders...
stormyb said:
As title says: since i rooted my desire hd and flashed a custom rom, the proximity sensor ( G-sensor) and compass aren't working anymore. Tried to calibrate, reset, hard reset, flashed other roms, nothing helped. While calibrating, nothing moved, not the levelers and not the needle of the compass.
What relation do they have together? Is it one part? Could it be a hardware problem or just software?
I noticed some threads about a locked G-sensor. Tried to "shake" them loose. No result. Who can and is willing to help me? thnx.
Click to expand...
Click to collapse
Try a fresh install of an RUU (going back to stock).
If it doesn't work then it shouldn't be a software issue.
Normally rooting does not affect those things.
When I flashed cm7 to my DHD the proximity sensor stopped working. It was an issue with the sensitivity settings of the sensor not being correct for AOSP roms. I fixed it using the app in this thread.
http://forum.xda-developers.com/showthread.php?t=951858
my device is LG-G3-D855.
after upgrading the software to android 5.0 from LG PC Suit, and after a day passed, I noticed that my auto-rotation is not working, and the proximity sensor is not responding during a call and the screen remains active.
I tested the sensors through hidden menu and saw that they are actually working and they are not stocked.
what is the solution? is it a software problem?
I also did downgrade the OS to the stock one and the problem still remains.
I'm sorry I am not able to help, but I am able to tell you I came to the forums today to post the exact same issue.
I had been using Liquid and CM12 for a while and my proximity sensors and brightness sensors (as well as screen turning off when I bring phone to my ear) were not working. I simply assumed it was an AOSP problem.
I just recently flashed the new stock lollipop rom that's on the development forum and I am having the same problem still. I do not know how to fix it and I'm hoping someone out there can help us!
edit: everytime I try to recalibrate the proximity sensor in settings, settings 'unexpectantly closes'
theraker007 said:
I'm sorry I am not able to help, but I am able to tell you I came to the forums today to post the exact same issue.
I had been using Liquid and CM12 for a while and my proximity sensors and brightness sensors (as well as screen turning off when I bring phone to my ear) were not working. I simply assumed it was an AOSP problem.
I just recently flashed the new stock lollipop rom that's on the development forum and I am having the same problem still. I do not know how to fix it and I'm hoping someone out there can help us!
edit: everytime I try to recalibrate the proximity sensor in settings, settings 'unexpectantly closes'
Click to expand...
Click to collapse
Have you had any luck on finding a solution to this? I've been in the same boat for a couple months now.
cotes10 said:
Have you had any luck on finding a solution to this? I've been in the same boat for a couple months now.
Click to expand...
Click to collapse
No, I'm afraid have found nothing to solve the problem.
ansari.srm said:
No, I'm afraid have found nothing to solve the problem.
Click to expand...
Click to collapse
Dang, same thing on my end. I've tried several different Roms/Kernels and still nothing. If I find a solution, I'll be sure to let you know!
Bump
Im having this issue as well. Anyone?
I've just resolved the same issue. No matter ROM I flashed to my LG G3 all the sensors were gone. The only thing it fixed that was flashing TOT using lg flash. More details on : htt ps: //forum.xda-developers. com/showthread .php?t= 2785089
ADD: The updated method worked for me NOT the original one.
Fingers crossed.