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.

[HELP] Proximity Sensor problem

I was earlier on cm11s and everything worked fine. Then I manually flashed the cyanogen os 12 ota using stock recovery. Since then the proximity sensor becomes active during incoming calls even if I dont answer the call. During incoming call if the sensor gets covered, the screen goes off. After that I flashed the latest ota with 'OK Oneplus' and the problem was still there. So today I flashed Euphoria Rom (5.1) thinking that this may solve it but the problem still persists. Can anyone tell me the solution to this?
Thanks!

.::[email protected]::. said:
I was earlier on cm11s and everything worked fine. Then I manually flashed the cyanogen os 12 ota using stock recovery. Since then the proximity sensor becomes active during incoming calls even if I dont answer the call. During incoming call if the sensor gets covered, the screen goes off. After that I flashed the latest ota with 'OK Oneplus' and the problem was still there. So today I flashed Euphoria Rom (5.1) thinking that this may solve it but the problem still persists. Can anyone tell me the solution to this?
Thanks!
Click to expand...
Click to collapse
This is only normal!
The goal of this is to not interfere with the screen while the phone is against your face.

néonaloj said:
This is only normal!
The goal of this is to not interfere with the screen while the phone is against your face.
Click to expand...
Click to collapse
But usually the proximity sensor becomes active after accepting the incoming call. But in this case it happens ever if I don't accept it.
This never happened in cm11s

.::[email protected]::. said:
But usually the proximity sensor becomes active after accepting the incoming call. But in this case it happens ever if I don't accept it.
This never happened in cm11s
Click to expand...
Click to collapse
there is a flashback zip file but i don't know where, you can search it up in the forum using the search tool or to disable the sensor from the settings (personally i disabled it)

Does anyone have a fix for this issue. Its extremely annoying that I have to wait for sensor to check if its clear before answering a call. Usually a 2 second delay on incoming call.

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 ?

Proximity sensor turns screen off for incoming calls

So, I have stumbled across this weird issue since January wherein if the proximity sensor is covered during an incoming call, the screen will remain off. What's weird is that this only happens on CM based ROMs and not on AOSP based ROMs. Of course, all full wipes and clean flashes. I have also tried flashing all the Marshmallow compatible modems available but none solved my issue. I'm using TWRP 2.8.6.0 to flash the zips.
CM based ROMs that I have tried so far;
1. Resurrection Remix M
2. Bliss ROM (both official and unofficial)
3. Marsh CM13
The older builds (December and early January) did not have this problem but of late, every CM based ROM activates the proximity sensor for an incoming call. The reason I'm posting this here is because no one else seems to have this problem and it's not specific to any one ROM.
On AOSP ROMs, everything works fine (no matter what modem I use). I have tried Darkobas ROM and I'm currently on CandySix where I don't have any issues with the proximity sensor.
Any idea why this could be happening? I miss all the customization on CM ROMs and I'm not a huge fan of Layers, so help would be appreciated.
Cheers!

This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...

Thanks for your response, mate. But CM seems to have fixed this issue because I just flashed the 02/03 CM13 nightly and the proximity sensor works just as it should during an incoming call; no issues there.
I'm going to try flashing another ROM on top of this.

AcmE85 said:
This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...
Click to expand...
Click to collapse
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.

girishb said:
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.
Click to expand...
Click to collapse
actually i think u messed up a bit mate dont mention calling ! something like screen OFF when i recieve a call from someone even when not answered or something like this ! and now getting back to your query i flash RR and CM13 by jgcaap right now just for checking ur issue and i dont have this i kept the phone on the table , called from my other phone and covered the proximity sensor with my hand ! screen was still ON .. and i should mention my RR build is a bit old ! i have been using jgcaap cm 13 from many days ! so

Well, there was only so much I could put in the title. I think my OP explains the issue clearly.
Also, can you try the latest version of RR or Bliss ROM? Because as I said, I wasn't having this issue on the older builds. I also don't have this issue on the official CM13 nightly or CandySix. I just want to find out what's causing this issue on my phone with other ROMs.

@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?

AcmE85 said:
@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?
Click to expand...
Click to collapse
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht

thepico said:
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht
Click to expand...
Click to collapse
Im on RR 24 and i can still see this issue. Lets see wht RR Mod comments on that.

Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.

girishb said:
Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.
Click to expand...
Click to collapse
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.

YoshiShaPow said:
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.
Click to expand...
Click to collapse
I have tried all modems from this topic (other than the h2os and oxygen one). I have also tried clean flashing the latest CM13 nightly before clean flashing any ROM. I also tried dirty flashing a ROM over the CM13 nightly with no luck. I used TWRP 2.8.6.0 for all of this.
What I can't seem to figure out is why I don't have these issues on the official CM13 nightly build or on CandySix ROM. All other ROMs that I have tried have this issue. If it's a firmware related issue, then shouldn't I be having this problem on all ROMs?

Any solution for this problem coz its really annoying.

I'm having the exact same problem with my phone running CyanogenOS 13.1.2-ZNH2KAS3P0-bacon. The screen doesn't turn on automatically if the proximity sensor is blocked in the beginning of the incoming call or alarm.
If someone finds a solution, please reply to my post

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