Hi
I have a problem with sensors. Sometimes they work, and sometimes they don't (Compass Magnetometer, Proximity sensor, Accelerometer, Ambient light sensor, Gyroscope). Checked also service tests (*#*#7378423#*#*).
I bought Z3 as used device. Had to replace microphone and week later LCD. Everything was working properly before and after replacing elements except sensors.
What can be the cause?
I have android 6.0.1 since I have Z3
When you check proximity sensor in service test does it works?
For me it seems like something was crashed or not connected properly because jack, microphone, proximity and ambient light is connected with one flex tape .
P.S. Today I had to disassembly Xperia Z3 because there was also problem with proximity sensor - at my case it works from time to time in service menu. Finally my problem was solved after revoming dust
If the sensors work, they work everywhere. Everything seems to be fine, also in service test. But if they don't work, also service tests are fail.
Proximity sensor and Ambient light sensor are on this element
gsmforyou.pl/files/313240969/tasma_gniazdo_zlacze_hf_czujnik_sony_z3_d6603 .jpg
but Compass Magnetometer, Accelerometer, Gyroscope are on mainboard.
So why they all don't work at this same time? I could change the element from the link but will this solve the problem?
Related
My Galaxy S has a problem with the Light Sensor, every time i make a call my phone freezes or black screen, I tried running some sensor tests but also does same when i try the light sensor, so that must be it. have this problem for a year, at first i thought it was the proximity sensor.
When my headphone is plugged in, i dont have this problem because the light sensor wont interfear then.
I want to disable the startup of the light sensor,
I already setup ADB, so im ready to push and pull, but i don't know wich file i need to edit. remove a # here and there
Can anyone tell how wich file it is?
Got inspired by :
http://forum.xda-developers.com/archive/index.php/t-764368.html
Sure its not the proximity sensor? Cause I got the same problem. When I accept a call screen goes black, the upper bar is visible and after a while the screen turns off. Im ceratin that is a problem with the proximity sensor or not?
Same here, yeah think its the proximity, but my light sensor also doesn't function properly, auto brightness adjustment doesnt work also.
Very anoying problem.
Hello,
I have HTC Radar and trying to enter bootloader i entered this Omega System Loader Menu http://store.picbg.net/pubpic/BC/B9/ef1a07a1500bbcb9.JPG
When i managed to exit this menu my proximity sensor went red and i was like "wtf - Hal 9000!"
after restart the red proximity sensor was gone and i installed new rom. later i entered Navigon and under Reality scanner a massage appeared:
"Your device doesnt support this feature. Possible causes:
-the devicde doesnt dispose of a motion sensor.
-the motion sensor doesnt work properly"
Can you tell me what is that red sign and did i broke my htc
thank you
That's a bit too bright for a proximity sensor, but the light it emits is red, but more like infrared like the one found in Kinect. And about the motion sensor, I think it means the gyroscope, the Radar doesn't have this sensor.
Make a call and look on proximity sensor. Red means is working during call.
yes, yes, it is very slight red signal. so everything is working normal
I have a XT1031 running on Boost Mobile. I'm currently running official SlimKat build 9 but switch back to stock when I am expecting alot of calls since I can't find a voicemail app that works with Boost Mobile on custom ROMs. I've searched for months for a fix that works to correct the faulty proximity sensor but haven't had any luck. Does anyone know of a way to completely disable the proximity sensor?
BaumerGXP said:
I have a XT1031 running on Boost Mobile. I'm currently running official SlimKat build 9 but switch back to stock when I am expecting alot of calls since I can't find a voicemail app that works with Boost Mobile on custom ROMs. I've searched for months for a fix that works to correct the faulty proximity sensor but haven't had any luck. Does anyone know of a way to completely disable the proximity sensor?
Click to expand...
Click to collapse
I guess it is not possible to disable it... If you want to fix the proximity sensor you must flash your phone with an stock room...
The proximity sensor has been bad since I received the phone. It was a gift and out of warranty. My issue is there no matter if the phone is stock or running a custom ROM. I was hoping a dev would have some insight to disabling it with a prop/hex editor or something.
Caution DO NOT DO THIS unless you want your proximity sensor completely disabled!!!
Also you're doing this on your own risk!
So if your proximity sensor is not working at all, you can disable it completely by chopping it off the board. The light sensor is separate, so this won't affect your auto-brightness.
Open your phone (14 torx screws), pop out the back panel.Barware not to lose your Power and Volume keys.
You don't need to detach the battery, just go ahead and lift the board carefully ( there are videos on YouTube how to do that ).
Flip the board to your right hand side, be careful, the display flex is still attached, you don't want to break that.
You can now find both sensors on the top right corner of the board, the proximity sensor is the LEFT one when you face the board straight up.
Use a small flat screwdriver and with a semi-gentle push in its base you can chop it off.
You're done!
Reassemble carefully.
Thanks for the suggestion I'll try to find some of those YouTube vids you mentioned. But from what I've been reading is that the sensor is just an ambient light sensor that can detect proximity when coupled with an IR-LED so I'm not understanding how I can just chop off the prox sensor. I can't post the link but the article is on Andrux & me blog titled CT406: proximity and light sensor on MotoG
Sent from my Moto G
BaumerGXP said:
Thanks for the suggestion I'll try to find some of those YouTube vids you mentioned. But from what I've been reading is that the sensor is just an ambient light sensor that can detect proximity when coupled with an IR-LED so I'm not understanding how I can just chop off the prox sensor. I can't post the link but the article is on Andrux & me blog titled CT406: proximity and light sensor on MotoG
Sent from my Moto G
Click to expand...
Click to collapse
Proximity and light sensors are separate, so chopping off the proximity one won't affect anything, besides proximity not working and the circuit will report "open", which means no object near, hence your screen won't turn off.
There are many types of sensors and they might differ in the way they work.I seriously don't see what y you've said is related at all.
For anyone interested, I found a module for Xposed Framework called Disable Proximity Sensor and it works flawlessly
Sent from my XT1031
Hello everyone.
I use M8Sx Single SIM Europe variant.
I changed my up and bottom covers of front, and my proximity sensor doesn't work.
It works after I use Rezound Proximity Sensor Calibrator app or some proximity sensor detection app, but after a reboot, I have to reopen the app and calibrate it again.
Is there a solution for this?
Thanks.
My pixel 4a's proximity sensor related functions (tap to wake, always on display, screen off during call) are not working properly
The hardware seems working fine while checking.
What may be causing the issue, and is there any way to fix this on latest versions???? Please someone help
The problem was with the device itself. By checking with sensor test application, proximity sensor shows value 0.5cm and covering the sensor shows 0.0cm. The problem is it won't turn back to value 0.5 ( not covering condition).
It stays at 0.0
By just applying some pressure to my display on the edge, it's working fine.
Recently I dropped my phone and the display might have some gap with the frame or something.
I have seen so many people on the internet have complaints similar to this across different pixel devices, that's why I thought of it might be a software issue.