Database Info

Jiayu G3 (MTK6577) Proximity Sensor Calibration

Hi I have a MTK6577 based Jiayu G3 (original version) which has developed a problem recently whereby the proximity sensor seems to have lost it's calibration settings. When in a call the screen will turn off when the phone is against my ear but then won't turn on again when I take the phone away again. I've cleaned the lens over the proximity sensor but this makes no difference. This is confirmed by using the Android app 'Proximity Sensor' which acknowledges when the sensor is covered but then does not change when uncovered.
I can calibrate it successfully in MobileUncleTools by going to 'Engineer Mode -> Engineer Mode (MTK) -> PSensor' and perform the calibration procedure. The proximity sensor will then work as expected until a reboot after which it is back to the same problem again. So I have to perform this recalibration after every reboot.
So what I would like to know, Firstly, is if anybody knows why the calibration in MobileUncleTools is not saved and does anybody know where the calibration settings should be saved to so that I can manually alter the settings. I have looked through all the system config files and I cannot find anything relevant.
Secondly, does anyone know of any other method of calibrating the sensor that would survive a reboot. I've tried various proximity sensor calibration app on the Play store but they all seem to be dedicated to a particular phone (HTC, ZTE etc) and don't work on mine.
Thanks for any help
Russell

Has no-one got any ideas about this then.

g3 Psensor calibration issue
Russell_S said:
Hi I have a MTK6577 based Jiayu G3 (original version) which has developed a problem recently whereby the proximity sensor seems to have lost it's calibration settings. When in a call the screen will turn off when the phone is against my ear but then won't turn on again when I take the phone away again. I've cleaned the lens over the proximity sensor but this makes no difference. This is confirmed by using the Android app 'Proximity Sensor' which acknowledges when the sensor is covered but then does not change when uncovered.
I can calibrate it successfully in MobileUncleTools by going to 'Engineer Mode -> Engineer Mode (MTK) -> PSensor' and perform the calibration procedure. The proximity sensor will then work as expected until a reboot after which it is back to the same problem again. So I have to perform this recalibration after every reboot.
Click to expand...
Click to collapse
Same problem here, tried different roms without sorting it out.
Have you already tried to go back to stock 4.0.4?
cheers
carlo

cavecar said:
Same problem here, tried different roms without sorting it out.
Have you already tried to go back to stock 4.0.4?
cheers
carlo
Click to expand...
Click to collapse
Yes, I've restored the Nandroid backup from when I first got the phone and it still is not calibrated.
There must be some way to save the calibration but I have no idea how. I've reported this problem on the official Jiayu Facebook page, I have emailed Jiayu direct and not had any response to either message. I have tried emailing the developer of MobileUncleTools as to why the calibration is not saved but, again, got no response.
So I really don't know what to do now.

Do you tried to install firmware again with the Flash Tools?

-aleco- said:
Do you tried to install firmware again with the Flash Tools?
Click to expand...
Click to collapse
I have recalibrated the proximity sensor as per Russell's instruction and then backup and restore. Sensor lost calibration again after reboot.
-kinetix118

Proximity sensor Issue - SOLVED
kinetix118 said:
I have recalibrated the proximity sensor as per Russell's instruction and then backup and restore. Sensor lost calibration again after reboot.
-kinetix118
Click to expand...
Click to collapse
GOOD NEWS!
I've just flashed a new ROM, 4.2.2, ( vredniiy stable v1) and the proximity sensor issue has been solved!
ROM also fixes GPS issues.
Good work vredniiy !!
cheers

cavecar said:
GOOD NEWS!
I've just flashed a new ROM, 4.2.2, ( vredniiy stable v1) and the proximity sensor issue has been solved!
ROM also fixes GPS issues.
Good work vredniiy !!
cheers
Click to expand...
Click to collapse
What vredniiy did in the 4.2.2, is add a init.d file contains
Code:
#!/system/bin/sh
echo 900 > /sys/bus/platform/drivers/als_ps/psthd
This is the Proximity Calibration trig.
vredniiy's stable v3 ROM is good and stable enough, thought.

please help- when i try to install this new rom, my systems keeps saying installation aborted. what am i doing wrong...i have a jiayu g3
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
cavecar said:
GOOD NEWS!
I've just flashed a new ROM, 4.2.2, ( vredniiy stable v1) and the proximity sensor issue has been solved!
ROM also fixes GPS issues.
Good work vredniiy !!
cheers
Click to expand...
Click to collapse
please help- when i try to install this new rom, my systems keeps saying installation aborted. what am i doing wrong...i have a jiayu g3

Russell_S said:
Hi I have a MTK6577 based Jiayu G3 (original version) which has developed a problem recently whereby the proximity sensor seems to have lost it's calibration settings. When in a call the screen will turn off when the phone is against my ear but then won't turn on again when I take the phone away again. I've cleaned the lens over the proximity sensor but this makes no difference. This is confirmed by using the Android app 'Proximity Sensor' which acknowledges when the sensor is covered but then does not change when uncovered.
I can calibrate it successfully in MobileUncleTools by going to 'Engineer Mode -> Engineer Mode (MTK) -> PSensor' and perform the calibration procedure. The proximity sensor will then work as expected until a reboot after which it is back to the same problem again. So I have to perform this recalibration after every reboot.
So what I would like to know, Firstly, is if anybody knows why the calibration in MobileUncleTools is not saved and does anybody know where the calibration settings should be saved to so that I can manually alter the settings. I have looked through all the system config files and I cannot find anything relevant.
Secondly, does anyone know of any other method of calibrating the sensor that would survive a reboot. I've tried various proximity sensor calibration app on the Play store but they all seem to be dedicated to a particular phone (HTC, ZTE etc) and don't work on mine.
Thanks for any help
Russell
Click to expand...
Click to collapse
Well, I guess this is not an isolated issue. Here's what I did after doing a Factory Reset on the phone:
1. Go to Settings
2. Click on Display
3. Make sure that your phone is on a flat surface, and then click on Als_ps calibration and proceed to placing an object over the phone.
(I used a folded sheet of paper and placed it over the phone and pressed the calibrate button. Once it was done, I got the completion message.)
After doing this, I was able to place and receive calls without the screen blacking out. Even when it did, I was able to wake up the phone's screen by pressing the power button.
Hope that helps.

Sony proximity sensor bug?

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 ?

Dialer Screen going blank on incoming calls and also when dialling out : please help

I have tried every single ROM on this Forum for Moto G 2015 Osprey 1GB version. However I am having same issue on evry ROM . Often I recieve a call my screen goes blank and I am not able to answer the call . Also when dialling out my screen goes blank after pressing dial . As a result I am not able to put teh call to loud speaker or use any other in call options . Can some please help me how to fix the issue . (I know work around to use Power Button to end calls and Volume to answer calls however that doe snot suite me as I ended up answering few calls which i did not wanted while mobiel in my pocket ).
Things I have done so far
I have tried this with both a screen protectoron and now have taken screen protector off . Issue still there
I have a a backup of orignal Motoroal ROM and this issue does not happen on orignal ROM
I have installed Nano gapps to make sure I have unough RAM free issue still there
I have tried most of the ROM 7.1.1 and even 6.0.1 all ROMS including Cynogen mod+ Lineage 13 and 14, ressurection remix, AOPS . Experience, Slim, AOKP, Cosmic , AOSP extended and list goes on and on but issue is still; there
Is there any specific reason for this issue ?
Is this to do with RAM, Sensor or custom ROMS issue ?
Is teher any way to turn teh sensor off which turn screen off whiel in a call and when i take mobile near my face (I am thinking if sensor incorrectly so wanst to check if turning thsi off makes any difference )
Can anyone please help

So your proximity sensor is acting up... are you on current baseband and firmware? I would suggest flashing the latest factory image completely via fastboot, verify operation of the proximity sensor, then flash your ROM again. A backup and restore in TWRP of stock is not sufficient to update firmware.

acejavelin said:
So your proximity sensor is acting up... are you on current baseband and firmware? I would suggest flashing the latest factory image completely via fastboot, verify operation of the proximity sensor, then flash your ROM again. A backup and restore in TWRP of stock is not sufficient to update firmware.
Click to expand...
Click to collapse
Thanks acejavelin you are always helpfull. I know how to flash Stock Formware however How can I verify operation of the proximity sensor?
I have found a copy of orignal firmware under XDA thread however I am not sure whether it is up to date firmware or not . How can I confirm if this is up to date firmware ?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639​
Retail UK (1GB) - XT1541_OSPREY_RETGB_6.0.1_MPI24.107-55-2_cid7
Can you please help on this bit

chungomungo1 said:
Thanks acejavelin you are always helpfull. I know how to flash Stock Formware however How can I verify operation of the proximity sensor?
I have found a copy of orignal firmware under XDA thread however I am not sure whether it is up to date firmware or not . How can I confirm if this is up to date firmware ?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Retail UK (1GB) - XT1541_OSPREY_RETGB_6.0.1_MPI24.107-55-2_cid7
Can you please help on this bit
Click to expand...
Click to collapse
Just take the newest one there... Best you can do.
As far as testing the proximity sensor, make some calls and have someone call you... You can try a sensor tester app like https://play.google.com/store/apps/details?id=com.mtorres.phonetester too

Brilliant , Thanks alot . will try that

FACING EXACTLY SAME PROBLEM ON XT1550
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:
FACING EXACTLY SAME PROBLEM ON XT1550
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
There is only one fix. find where is proximity sensor, usually it is on the top near front camera . when ever screen goes blank dry your thumb and clean screen with teh thumb where proximity sensor and screen will wake up .
Also you need to keep you pockets extra clean. It is better if you can hoover inside them as most of the time I noticed there was a little dirt always on my screen when screen went blank. I am noit sure if my mobiel screen has gone very catchy to dirt after 1 year use
I intially though iut was due to custom ROMS and I have gone back to stock ROM and recieved two motorola security updated still issue is there so this is not because of the ROM .

Try this
Goto settings​ and search default from the search button then select phone app and set the default app.

Just saw this and thought I'd try Phone Tester. covered or uncovered, my proximity det always said Far. I tested phone by making a call and then covering it and the screen immediately went black. I would suggest that some screen protectors might interfere a bit but you've already taken that into account. Note where it is (on my xt1540 top just right of ear speaker) and make sure surface is clean. Otherwise just may be defective.
EDIT: if you feel it's "defective" You might consider replacing the screen/digitizer in hopes that that would fix it and it's not a motherboard issue.

Facing same issue
My stock rom on moto G3 2015 was working fine. Yesterday i rooted and installed tesla when this issue started. Frustrated i tried ASOP Extended and here too same issue.
It's not the issue of the sensor since Stock rom was fine till 2 days ago.
Have tried Phone notificaion settings as well.
Any updates on this or else i may have to reinstall Stock ROM

Proximity Sensor Issue OP7P

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

Proximity sensor and others not working properly after android 10 update

My Pixel 3's proximity sensor reads 0cm after android 10 update(using Sensors Multitool), and double tap to wake and lift to wake not working.
I've search on the internet and I read the post of "FIXED - Android 10 - Sensors Bug". and also tried using proximity sensor reset or calibrate app, but all seem not working.
In my case, all other sensors works perfectly(Active Edge,Ambient Light Sensor, Auto-brightness, Accelerometer, Auto-rotation), but proximity sensor have reading of 0cm all the time. Which make the screen black when having a phone call. And double tap/lift to wake is not working(although my accelerometer is working according to sensors multitool).
I don't have screen protector, and this problem happened just after i first updated it to android 10. so i think it might be just a software problem.
I had the october update already, but it is not fixed.
And this is a phone that never oem unlocked or rooted, no trwp installed ever, so it might be a different problem rather than that FIXED one.
I live in a country that I could not send the phone back for repairing or replacement, and i have to use adb sideload to install every ota
(and most of time when I switch my camera to frontfacing camera, it will buzz and vibrate, but when i switch back to rare and back to front, it can be fixed. this is another small issue, but it happened before this update already, maybe i just need to mention it)
Any idea what might cause this and how can I fix them?
Thanks.

https://forum.xda-developers.com/showthread.php?t=3967525&p=80233629

TonikJDK said:
https://forum.xda-developers.com/showthread.php?t=3967525&p=80233629
Click to expand...
Click to collapse
i read this already and my issue is not the same one as mentioned...
in that issue, all sensors are dead, but not in my case.
my device is never unlocked or rooted, no twrp installed, so maybe nothing has right to write the persist?
and if it is the same one, it should be fixed in october patch, but mine is not FIXED at all.

zhangcx93 said:
i read this already and my issue is not the same one as mentioned...
in that issue, all sensors are dead, but not in my case.
my device is never unlocked or rooted, no twrp installed, so maybe nothing has right to write the persist?
and if it is the same one, it should be fixed in october patch, but mine is not FIXED at all.
Click to expand...
Click to collapse
I factory reset my device yesterday and it fixed a lot of errors I was getting. Have you tried factory reset?
Be sure the phone has backed up to the google drive