My auto brightness sensor is not working properly.. Pls help
Ishann20 said:
My auto brightness sensor is not working properly.. Pls help
Click to expand...
Click to collapse
Maybe bcz incorrect tempered glass application check if it has a cut for sensors if no thn apply compatible glass. If yes then Find nearby service center its a factory defect.
Chek using sensor test app https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
I have this issue , ithink some apps conflict with the light sensor i didnot know which app is that, because in my device i am using lot more apps iam using always on amoled app i think the wrong configuration of this app.. ( not sure)
And the problem SOLVED just restart my device
Try restart your device device and chek with sensor test app
Related
I resolve the HD2 problem for proximity sensor bug during call with this steps:
1. turn off vibration for connecting (go to dialer menu)
2. turn off dialer keypad sound (via HD2Tweak 1.2)
3. install Touch in call screen tweak 1.2
Hi !
Could explain a little bit the "proximity sensor bug during call" you're facing ?
Which ROM verison are you using ?
thanks a lot !
papagon said:
Hi !
Could explain a little bit the "proximity sensor bug during call" you're facing ?
Which ROM verison are you using ?
thanks a lot !
Click to expand...
Click to collapse
When I dial , the screen go off without any association with proximity!
both original & energy ROM
Hi !
Thanks for your answer...
My problem is slightly different, but involves radio ROM and winmo drivers, because everything was fine with stock ROM 1.48.406.1 and radio ROM 2.15.50.14.
Now that I'm using the stock ROM 3.14.406.2 (wich includes radio 2.15.50.14)
when i'm in a call, the screen stays off even if the phone is no longer on my ear...
So that's why I as interested by your solution, but it does nothing on my phone...
With this last official update from HTC, i'm now facing keyboard sensitivity issues (everything was alright with prévious ROM and HTC patch for the sensitivity), and this proximity sensor problem...
i find the case can make the sensor play up as most manufacturers dont account for the sensor
jonpickles70 said:
i find the case can make the sensor play up as most manufacturers dont account for the sensor
Click to expand...
Click to collapse
please explain more.
manufacturers dont put cut outs on cases or they arent big enough so the sensor is then covered
Hi guys, I have a issue with proximity sensor, it happend from 4.4.2 and now i'm in 4.4.4 and still facing with it.
At the first time I think that is my app problem, so I don't care at all. But today, I found it (maybe to late) happend with all thing include call and the test in hidden menu.
This is the way how I made it:
1. cover the proximity sensor
2. start the call
-> screen go off
3. un-cover the proximity sensor
-> screen not turn on even the call ended. All thing you can do is press Power button twice
If this only happend with call, ok, I can accept it like a feature.
But when I try reproduce the issue in *#*#7378423#*#* - Service tests - Proximity Swich test, the result show that the proximity sensor cannotchange state and always "Detected".
So idk the problem is my phone or sony firmware, anyone can confirm that? I did some searching but can't find anything.
Thank you.
i think the problem is in proximity sensor because as u say it happend in 4.4.2 and 4.4.4, and i've use both firmware and i dont face any problem like that, and u can check if u have ur screen guard on ur proximity sensor, because it happens with me once i put my screen guard on proximity sensor thinking nothing will be wrong because screen guard is transparent but that my proximity sensor becomes like what u say, always detect, check it
It's not the problem of sensor, this problem is in firmware. I am facing the same problem and my frd too.
ChetanLokhande said:
It's not the problem of sensor, this problem is in firmware. I am facing the same problem and my frd too.
Click to expand...
Click to collapse
i never face this problem,
which kernel you are using, i am using vinays nitrogen kernel, does this problem occur on stock ?
Hi.
I have this wierd bug. When i call someone. Screen automatically goes off and wont come on until call is finished.
I know this isnt due to proximity. Even when the sensor is not covered up.
I am on stock mm rooted.
..
Does this mean my sensor isn't working or software issue?
gamingdarstark said:
Hi.
I have this wierd bug. When i call someone. Screen automatically goes off and wont come on until call is finished.
I know this isnt due to proximity. Even when the sensor is not covered up.
I am on stock mm rooted.
..
Does this mean my sensor isn't working or software issue?
Click to expand...
Click to collapse
Most likely your sensor is bad and always reporting NEAR, the symptoms you are describing are exactly what would happen in this condition... have you tried a sensor test app from the Play Store to see what the proximity sensor is doing?
Finally worked!!!! had to calibrate sensor
Well thanks i tested the sensor it was always showing 1cm reading.
Calibrated it using an app on playstore. >> Proximity Sensor Calibration <<
Now working fine.
Cheers!! :good::good:
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
abhishekturumella said:
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
Click to expand...
Click to collapse
Your device is a Moto X (1st generation/2013 )? A quick Google search would tell you this is a Proximity Sensor issue, it is device specific whether anything can be done or not, so you might want to check your device's group.
acejavelin said:
Your device is a Moto X (1st generation/2013 )? A quick Google search would tell you this is a Proximity Sensor issue, it is device specific whether anything can be done or not, so you might want to check your device's group.
Click to expand...
Click to collapse
No bro. Mine is a moto g3 xt1550. Searched the forum later yday and found that it is calibrating proximity sensor issue. Will try doing that and check. Thank you for the response
abhishekturumella said:
No bro. Mine is a moto g3 xt1550. Searched the forum later yday and found that it is calibrating proximity sensor issue. Will try doing that and check. Thank you for the response
Click to expand...
Click to collapse
Sorry, you must have typo'd earlier, you clearly said XT1055 which is a valid Moto device. Anyway, sounds like you're on the right track.
acejavelin said:
Sorry, you must have typo'd earlier, you clearly said XT1055 which is a valid Moto device. Anyway, sounds like you're on the right track.
Click to expand...
Click to collapse
Oops. Sorry. It was a typo. Mine is motog3 xt 1550.
abhishekturumella said:
Oops. Sorry. It was a typo. Mine is motog3 xt 1550.
Click to expand...
Click to collapse
please let me know if you can some how fix this issue. I have same issue ands I did proximity caliberatiin as well and it did not resolve my issue
chungomungo1 said:
please let me know if you can some how fix this issue. I have same issue ands I did proximity caliberatiin as well and it did not resolve my issue
Click to expand...
Click to collapse
I too did proximity sensor calibration but it worked only for few times. But the only solution that's working is whenever screen goes blank I rub with my finger on proximity sensor area for 3-4 times as if like cleaning it. Immediately the screen lights up. This is the solution am doing since past few times and its working consistently.
abhishekturumella said:
I too did proximity sensor calibration but it worked only for few times. But the only solution that's working is whenever screen goes blank I rub with my finger on proximity sensor area for 3-4 times as if like cleaning it. Immediately the screen lights up. This is the solution am doing since past few times and its working consistently.
Click to expand...
Click to collapse
Thanks
Can we disable the proximity sensor ???
Mohammed Siamwala said:
Can we disable the proximity sensor ???
Click to expand...
Click to collapse
Yes u can disable the proximity sensor.....
Procedure:
1. The device need to be rooted
2. Install the xposed module
3. After installing search for sensor Disabler apk in xposed module
4. Install sensor Disabler and open the app and select the proximity sensor.
5. Select the value of proximity sensor to Maximum level and save it
6. Do the reboot
This whole procedure will disable ur proximity sensor ie ur screen will no go blank on any call.
Note : Xposed installer for nougat ROM is in development phase ...
Do it ur own risk I'm not responsible for any harm.
All the best :good::laugh:
abhi8939 said:
Yes u can disable the proximity sensor.....
Procedure:
1. The device need to be rooted
2. Install the xposed module
3. After installing search for sensor Disabler apk in xposed module
4. Install sensor Disabler and open the app and select the proximity sensor.
5. Select the value of proximity sensor to Maximum level and save it
6. Do the reboot
This whole procedure will disable ur proximity sensor ie ur screen will no go blank on any call.
Note : Xposed installer for nougat ROM is in development phase ...
Do it ur own risk I'm not responsible for any harm.
All the best :good::laugh:
Click to expand...
Click to collapse
Thanks for your help !!
But will need to wait as I'm using Nougat ROM :laugh:
Any disabling method for 7.1.1 ???
Mohammed Siamwala said:
Thanks for your help !!
But will need to wait as I'm using Nougat ROM :laugh:
Any disabling method for 7.1.1 ???
Click to expand...
Click to collapse
To my knowledge it is not there... U can Google it bro
As I'm also facing this problem...
Some info about xposed....
Xposed is not compatible with Nougat, the truth is it may never be a viable option again due to security changes in Android. The developers have said that Xposed is on it's last legs, the changes in Android and the security are becoming impossible to work around. Remember last year at this time, the developers of Xposed had mostly given up and thrown in the towel and said Xposed was dead with Marshmallow, but they got lucky and found a work around just before completely giving up. They have not as yet found such a exploit to make it work, and if they do it will only be temporary as the next version of Android will probably close it again. They may get it to work with Nougat, or maybe not, either way best bet is to learn to live without it, because it will be gone before too long.
abhishekturumella said:
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
Click to expand...
Click to collapse
hi buddy i have a solution for this hope this will be helpful............
i have flashed the cm 12.1 yesterday on my moto g3 and since yesterday i didn't faced the problem of screen going off on call .....
this conclude that rom is somewhere responsible for screen off during call on some phones( my opinion )
you can try this if u want:fingers-crossed:
This will help you mate
github.com/Alberto97/proprietary_vendor_motorola/blob/cm-14.1/osprey/proprietary/lib/hw/sensors.msm8916.so?raw=true
Paste this in system>lib>hw>
And change the permission to rw- r-- r--
Guys!
Do you experience proximity sensor issues while answering calls on OP7P?
For me while I'm on calls. The display comes on and gets disturbed and get pressed by my ears all the time.
Also any idea of where the proximity sensor is located on OP7P?
Thanks ?
Yes, I'm having the same issues. While I'm on calls I often activate the notifications pulldown. It would be nice to know how to fix this.
If you pull down the notification shade, the sensor is located just above the fifth icon on the first row. IE behind the screen.
If you pull the shade all the way down it is above and between the third and fourth icons. Easiest way to describe it. Put your thumb over that area with auto brightness on to watch the slider move.
Annoying while on a call that the screen comes on.
I'm experiencing the exact same issue with the caller app.
I also tried to make a flip cover to turn screen on or off with a proximity sensor detection app and it didn't work either.
I search a little in engineer mode (*#808#) and found that there is multiple proximity sensor, the IR sensor work quite well but it doesn't seem to be the default one.
The default one seems to be the ultrasonic sensor which works really bad.
There is also a "TP" proximity sensor which seems to be a near field detection which seems to work if I move my hand near the screen.
The sad thing is that in dedicated app to use or test proximity sensor (and in antutu or else) only one proximity sensor is listed (The ultrasonic one I guess) so you cannot switch to use the one which is working well.
Isn't this in the wrong place? Shouldn't it be in the Questions and Answers section?
Mods?
Probably just here looking for a mod to improve the situation
Actually I was going to open a new thread in Q&A when I found this one with the same subject and problem.
Do you think I need to open a new thread?
Is any of you experiencing the same issue as I described in my answer?
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
I tried to with no luck but as I explain in my first message the IR sensor is only used when screen is off (that's why it could help with double tap to wake)
But when screen is on another or couple another sensors are used and you can't calibrate them.
I think ultrasonic sensor is used when screen is on.
Do someone tested proximity sensor with any app on the play store? (Like proximity sensor test)
Put it on a table and check if it's working, mine is absolutely not. If I hold it like I was about to phone it works a little but it's not impressive.
Since I got 9.5.7 (EU version) earlier this evening screen turn off when I make a call.
I'm having this issue since 9.5.8... It's very annoying and I'm really disappointed, I often turn on airplane mode during a call... I tried to calibrate but it doesn't work.
I'm very very frustrated
schmeggy929 said:
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
Click to expand...
Click to collapse
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
dallasnights said:
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
Click to expand...
Click to collapse
This...
I've been having issues with phone calls but more so with pocket issues.. When I had the 6t pocket mode kept the phone neutral but this phone doesn't seem to have an accurate prox sensor.. Is there a way to activate a pocket mode?
Sent from my [device_name] using XDA-Developers Legacy app
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
pinzarualex said:
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Click to expand...
Click to collapse
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
But I have had this issue since release.. Do you a link to this information? If that's the case maybe someone can look into the firmware and see if it's minor tweak that can fix it?
Sent from my [device_name] using XDA-Developers Legacy app
Jack_Sparrow_ said:
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Click to expand...
Click to collapse
Of course it didn't fix anything...
Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
j0hnee said:
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have reported this to Funk wizard on the OOS support thread and he said he cannot reproduce it anymore on the latest test build, so... We have to wait for next firmware release and see if that is indeed the case