Proxi sensor and Auto-brightness issues - Desire HD Q&A, Help & Troubleshooting

Hi,
Since the weekend both my proxi sensor and auto brightness have stopped working, which I'm assuming is the light sensor and are lined or even the same thing.
I have completed a full wipe and reinstalled both Kernel and Rom (LeeDroid) with no joy.
Is there any definitive way of checking if this is a hardware or software problem.
Thanks in advance.

try lippies proximity sensor calibrator (you can find it in the themes and app section) that should help.

Flash the appropriate RUU for your device, if it persists it's hardware otherwise...

sahirhussain said:
try lippies proximity sensor calibrator (you can find it in the themes and app section) that should help.
Click to expand...
Click to collapse
Yea I have with no joy, should have said really.
ghostofcain said:
Flash the appropriate RUU for your device, if it persists it's hardware otherwise...
Click to expand...
Click to collapse
I'll give that a go - cheers

Related

[Q] Wake up problems during the call

I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.

Bugs in 4.1.0 update

Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Also the volume keys are not working.
no brothers both the capacitive buttons and volume rockers work flawlessly on 4.1.0
all is working for me :-/
Working fine for me.
Working fine for me. Seems like a temp issue or a wrong flash to me. You can try wiping system and flash full zip. If you are fully stock, i would advise to perform a factory reset.
Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Sounds like a firmware issue. I suggest a full reflash.
I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.
Clean flash ..stop making up bs posts
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
As i have been saying repeatedly, the OTAs from OnePlus suck.
Clean flash the full ROM.
andrneumann said:
I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.
Click to expand...
Click to collapse
Please PM me if you ever find a fix for this.. it forced me to use another ROM
Never call it Touch ID... This is not Apple.
works fine here clean flash
azaidi said:
Please PM me if you ever find a fix for this.. it forced me to use another ROM
Click to expand...
Click to collapse
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.
Factory reset solved the problem.
croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
I could never do that
andrneumann said:
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.
Click to expand...
Click to collapse
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)
Anyone who's shortcut to for example a document on the home screen doesn't work anymore?
I already deleted the shortcut and made a new one, but still doesn't work
Ronak Chandak said:
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)
Click to expand...
Click to collapse
I have the same issue...

Sensors are not working !

I am using Pixy Os 9.0 on Default Kernel And Phone Sensors are stopped Working like (accelerometer, proximity etc.).
I've tried going back to Oreo roms but not success.
Should I try changing kernel or something?
Try flashing this
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
That worked. Thank You
That sensor flashing is easy way. However I took a different time consuming way. Writing it down so that it may help some one else.
When I switched from Oreo AiCP to latest Pie AEX, I went via the hard way. You may read it here https://forum.xda-developers.com/le...bootloader-t3868174/post78256476#post78256476
AEX 6.0 worked well but I too was facing sensor issue. I re-flashed the ROM but no effect. CPU-Z sensor page was complete blank. Yes, I knew the sensor.zip available for flashing but I went ahead to REDO the entire ZUI 1.9 to AEX flashing process.
This time around, all sensors are working fine.
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
mirkios said:
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
Click to expand...
Click to collapse
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
satyen_ said:
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
Click to expand...
Click to collapse
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
mirkios said:
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
Click to expand...
Click to collapse
I think the issue is not with any ROM, it is due to the screen and all other replacements, may be after the replacement your proximity sensor is always covered or blocked with something. There are apps on playstore to see the proximity sensor data check if the always shows the same distance/reading i.e. 0 while waving your hand over it, and if yes then the issue might be what I mentioned above. If that's the case you would have to take of the screen and adjust the proximity sensory properly.
Check with this app :
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
I have AOSP 10 on my ZUK. The sensors did not work.
Thank you. Now everything works well.

Question fingerprint sensor calibration needed

ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
applesucksLmao said:
ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
Click to expand...
Click to collapse
Hey, did you ever find out something?
I just got that problem too
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Captain_cookie_200 said:
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Click to expand...
Click to collapse
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Mighty_Rearranger said:
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Click to expand...
Click to collapse
i see..

Question Fingerprint option missing under Security

I am missing the fingerprint scan option under the device Security settings in both stock EEA 14.0.7 firmware as well as any A13 custom ROM. I also flashed 14.0.4 Global but still no fingerprint option.
Is there something I can do from a software side to make the option appear?
I performed the calibration on the fingerprint but the sensor was not recognized.
Hope to hear some suggestions.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Try flashing all files from the above link. One of them should work for you.
ApexPrime said:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Try flashing all files from the above link. One of them should work for you.
Click to expand...
Click to collapse
Thanks. I flashed each one but no fingerprint option appeared.
Any other suggestions?
Strange. Was any hardware changed on your phone recently?
You can try this. Install "Hidden Settings for MIUI". Open it and search for "fingerprint". Click on the one shown in the image below and see if it works.
user0u said:
Strange. Was any hardware changed on your phone recently?
You can try this. Install "Hidden Settings for MIUI". Open it and search for "fingerprint". Click on the one shown in the image below and see if it works.
Click to expand...
Click to collapse
Yes, I had cracked screen replaced.
I'm currently on AOSP ROM so I don't think that will work until I flash to stock.
nickelnine said:
Yes, I had cracked screen replaced.
Click to expand...
Click to collapse
I think that's it. You will need to calibrate the fingerprint sensor. You can search up google for specific instructions for that.
Thank you. I saw a video on how to do it. I will try it and hope for the best.
According to Google and some videos, it seems my fingerprint sensor is broken. When I try to calibrate it, this error appears: Unknown FOD sensor type.
Or maybe this calibration is only for in-display sensor phones. Ours is a physical button so it seems either it is actually broken or the OS is for some reason rejecting to accept it.

Categories

Resources