• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Proximity Sensor Problem (Solved)

23 posts in this topic

Posted (edited)

My G3 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.

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.


Russell

 

 

 

I have now found a fix for this issue. See post #15 in this thread.

Edited by RussellS
0

Share this post


Link to post
Share on other sites

Posted

wow! seems like there's an issue with the parts Jiayu's been using..their phones are degrading a few months into use..

0

Share this post


Link to post
Share on other sites

Posted (edited)

wow! seems like there's an issue with the parts Jiayu's been using..their phones are degrading a few months into use..

I don't know if I could make that assumption. I have rooted the phone, installed CWM and loaded a couple of custom roms even though I am now back on the last official ICS release. So this may have been self inflicted. I really cannot say for sure.

It would be fine if the sensor calibration was saved because the phone works perfectly until it is rebooted. I can't help feeling this is a software issue and not hardware.

Actually, thinking about it, I do have a Nandroid backup of the original rom the phone was supplied with. So I may try restoring that and see if the proximity sensor works ok with that.

Edited by RussellS
0

Share this post


Link to post
Share on other sites

Posted

I have the same problem now using the MIUI rom and set the call end with power button. Its only an issue now for me when I need to do something with the phone while in a call. Started for me when I used a Lewa rom.

0

Share this post


Link to post
Share on other sites

Posted

I don't know if I could make that assumption. I have rooted the phone, installed CWM and loaded a couple of custom roms even though I am now back on the last official ICS release. So this may have been self inflicted. I really cannot say for sure.

It would be fine if the sensor calibration was saved because the phone works perfectly until it is rebooted. I can't help feeling this is a software issue and not hardware.

Actually, thinking about it, I do have a Nandroid backup of the original rom the phone was supplied with. So I may try restoring that and see if the proximity sensor works ok with that.

well to be fair to Jiayu, some issues may have been self-inflicted, but from what I've seen on the other forums, they've had a lot of issues even since the G2 days..

please try to roll back to your backup..format everything first so you won't have any "leftovers" from your previous ROMs..and please let us know how this goes..

0

Share this post


Link to post
Share on other sites

Posted (edited)

I have now restored various Nandroid backups goping right back to the original rom that the phone came with and the proximity sensor is uncalibrated the same on all of them. I can still calibrate it with MobileUncleTools on all the roms and it will work fine but none of them will survive a reboot.

So I can only think that the sensitivity of the proximity sensor has changed since the phone was new causing it to require a recalibration. It is just unfortunate that the calibration is not saved.

There must be a file in the system somewhere that stores the calibration information for the various sensors but I haven’t found it yet. I have left a message on the Jiayu Official Facebook page requesting information about calibrating the proximity sensor but I'm not holding out much hope for a useful reply.

In the meantime I'm still hunting for a file somewhere in the Android system that might contain the calibration data.

EDIT: I have also emailed the contact email address on the Jiayu website regarding this to see if I get any help that way. However, once again, I'm not holding my breath.

EDIT2: I have also emailed etotalk.com which is where I purchased the phone from.

Edited by RussellS
0

Share this post


Link to post
Share on other sites

Posted

Hi did you get any joy with this from Jayiu? I still have the problem and on my copy of mobile uncle tools I don't have the psensor option can you upload me your copy of the apk please?

0

Share this post


Link to post
Share on other sites

Posted

Hi Coffer52,

Sorry I didn't respond earlier but I've had a lot on and haven't been on Modaco for a while. In answer to your question, no I have had absolutely no response from Jiayu at all. I also emailed the developer of MobileUncleTools to see if he had a solution to the problem of the calibration not being saved, but I got no response from him either. The only response I did get was from Etotalk where I bought the phone from. They were more helpfull and emailed me a APK file to calibrate the proximity sensor. Unfortunately it didn't work though and only works wityh HTC phones.

So, I'm still in the same boat at the moment not being able to save the sensor calibration.

With respect to MobilerUncleTools, they have moved the PSensor calibration in later versions so it is no longer where I originally said it was.

It is now in: 'Engineer Mode --> Engineer Mode (MTK) --> Other Extra --> PSensor'

The version of MobileUncleTools I am using is 20130619v2.9.3 and is the latest available in the Play store.

Hope this is helpfull

0

Share this post


Link to post
Share on other sites

Posted

Hi russellS I don't have the extra option menu so no psensor adjustment! I think I'll flash the original 4.2.1 b1 rom and start again. One of these roms has screwed the OS.

0

Share this post


Link to post
Share on other sites

Posted

What version of MobileUncleTools are you running?

0

Share this post


Link to post
Share on other sites

Posted

Hi sorry for the delay I'm running 2.9.5, but strangely when you install a Lewa ROM the last sub menu (other extras) disappears. Must be something to do with permissions. I have installed the original 4.1.2 beta firmware and the Mobile Uncle sub menu has returned, the Psensor problem has also gone! Stay away from Lewa ROMs for this handset I would recommend!!

0

Share this post


Link to post
Share on other sites

Posted

Hi sorry for the delay I'm running 2.9.5, but strangely when you install a Lewa ROM the last sub menu (other extras) disappears. Must be something to do with permissions. I have installed the original 4.1.2 beta firmware and the Mobile Uncle sub menu has returned, the Psensor problem has also gone! Stay away from Lewa ROMs for this handset I would recommend!!

That's strange, I'm on the 4.1.2 beta firmware and I've still got the proximity sensor problem.

0

Share this post


Link to post
Share on other sites

Posted

Hmm, I agree it is very strange. It's early days for me with this Rom as I never stuck with it for long the first time around! As a matter of interest have you tried the Roky v2.3 from the needrom website? I checked the original site for this room (russian) and he claims to have sorted the proximity problem in his room.

0

Share this post


Link to post
Share on other sites

Posted

Hmm, I agree it is very strange. It's early days for me with this Rom as I never stuck with it for long the first time around! As a matter of interest have you tried the Roky v2.3 from the needrom website? I checked the original site for this room (russian) and he claims to have sorted the proximity problem in his room.

yes I have tried the Rocky v2.3 rom from the Needrom site but it made no difference to the proximity sensor problem. The rom was very good except for the fact that the email, calendar and messaging apps were a horrible white text on a black background. This made those apps very difficult to read and looked horrid. Therefore I have reverted back to the official Jelly Bean beta rom. As I said though I still had to recalibrate the proximity sensor after each reboot.

0

Share this post


Link to post
Share on other sites

Posted

After much searching and piecing together various snippets of information from various internet sources I have now found a solution to this proximity issue.

See this reply to my post on the xdadevelopers forum regarding this which refers to a new custom ROM which has a fix for this applied.
http://forum.xda-developers.com/showpost.php?p=46641282&postcount=8

So basically this fix can be applied to any ROM whether it be custom or stock and consists of a script which is run at at startup. The only criteria is that the ROM must be rooted. I'm afraid I can't offer any advice on this as I rooted mine a long time ago and I can't remember what method I used. However, if you check out the 'Jiayu G Series' forum on Modaco you will find advice regarding this.

If you are running a custom ROM which has init.d support then the script can be placed in the init.d folder and will automatically be run as the phone boots up. However, if you are running a stock rom as I am then it will not have init.d support and so the script will have to be run another way. What I have done is to use a free android app called SManager (link at bottom of post) which has the function of running scripts at boot time.

Create a file with the name '99proximity' and the following contents: (copy & paste from this box)

#!/system/bin/sh
echo 900 > /sys/bus/platform/drivers/als_ps/psthd

Copy this file onto the SD card in the phone. I suggest putting it in a folder called 'scripts' rather than just loose on the SD card.

I have also attached the script file to this post to save you creating it yourself.

Then install SManager and then proceed as follows:

Launch SManager and navigate to your 'scripts' folder (or wherever you put the script file):
SManager1small.jpg

...Open the scripts folder where you will see the script you created earlier:

SManager2small.jpg

...select the script which will bring up the following screen:

SManager3small.jpg

when you first enter this screen all the option buttons (Fav, Su, Boot, Net, Blth, Wlck & Ntfy) will be greyed out as they are not yet selected.

Press 'Su' and 'Boot' which will then show up as activated as in the screenshot. These options specify running the script as root at boot time.

Press save, exit SManager and then reboot the phone Hopefully when the phone has booted up the promity sensor will work properly.

 

This fix has been working on my phone for a few months now so I know it works. Hopefully this tutorial is complete but it is mainly from memory so I may have missed something. If you do have any problems post back here and I will do my best to help.
 

 

 

Link to SManager on Google Play Store - https://play.google.com/store/apps/details?id=os.tools.scriptmanager

99proximity.zip

2

Share this post


Link to post
Share on other sites

Posted

It doesn't work for me. I use a Miui Rom version 3.10.04. Please help solve this problem.

0

Share this post


Link to post
Share on other sites

Posted

Which part is not working. Try running the script direct from SManager by pressing the 'Run' button in the following screenshot.

 

SManager3small.jpg

 

That will at least confirm if the script itself is working.

 

Also, I think your MIUI rom has init.d support so it should work by just putting the script in the init.d folder. However, test the script first by just running it and see if that works.

0

Share this post


Link to post
Share on other sites

Posted

After much searching and piecing together various snippets of information from various internet sources I have now found a solution to this proximity issue.

See this reply to my post on the xdadevelopers forum regarding this which refers to a new custom ROM which has a fix for this applied.

http://forum.xda-developers.com/showpost.php?p=46641282&postcount=8

So basically this fix can be applied to any ROM whether it be custom or stock and consists of a script which is run at at startup. The only criteria is that the ROM must be rooted. I'm afraid I can't offer any advice on this as I rooted mine a long time ago and I can't remember what method I used. However, if you check out the 'Jiayu G Series' forum on Modaco you will find advice regarding this.

If you are running a custom ROM which has init.d support then the script can be placed in the init.d folder and will automatically be run as the phone boots up. However, if you are running a stock rom as I am then it will not have init.d support and so the script will have to be run another way. What I have done is to use a free android app called SManager (link at bottom of post) which has the function of running scripts at boot time.

Create a file with the name '99proximity' and the following contents: (copy & paste from this box)

#!/system/bin/sh
echo 900 > /sys/bus/platform/drivers/als_ps/psthd

Copy this file onto the SD card in the phone. I suggest putting it in a folder called 'scripts' rather than just loose on the SD card.

I have also attached the script file to this post to save you creating it yourself.

Then install SManager and then proceed as follows:

Launch SManager and navigate to your 'scripts' folder (or wherever you put the script file):

SManager1small.jpg

...Open the scripts folder where you will see the script you created earlier:

SManager2small.jpg

...select the script which will bring up the following screen:

SManager3small.jpg

when you first enter this screen all the option buttons (Fav, Su, Boot, Net, Blth, Wlck & Ntfy) will be greyed out as they are not yet selected.

Press 'Su' and 'Boot' which will then show up as activated as in the screenshot. These options specify running the script as root at boot time.

Press save, exit SManager and then reboot the phone Hopefully when the phone has booted up the promity sensor will work properly.

 

This fix has been working on my phone for a few months now so I know it works. Hopefully this tutorial is complete but it is mainly from memory so I may have missed something. If you do have any problems post back here and I will do my best to help.

 

 

 

Link to SManager on Google Play Store - https://play.google.com/store/apps/details?id=os.tools.scriptmanager

Awesome work, thanks man :D

0

Share this post


Link to post
Share on other sites

Posted

Awesome work, thanks man :D

 

No problem, I'm glad it worked.

0

Share this post


Link to post
Share on other sites

Posted

Thank you.

0

Share this post


Link to post
Share on other sites

Posted

I have the same problem. I checked your way to solve the problem, but in tke last step, when i press "Run" button i get information "can't create /sys/bus/platform/drivers/als_ps/psthd: No such file or directory".

Can You help me?

0

Share this post


Link to post
Share on other sites

Posted

first iam new member here.

 

i would thank you very much Diehard because it worked for me in my JIAYU G5S.

regard.

0

Share this post


Link to post
Share on other sites

Posted

Most likely, there is a dirt around the proximity sensor ( upper left corner ) or you may have put a new cover on the phone, put the phone in a zip bag or put a protection on the screen.

 

Or, something else happened as incorrect re calibration.

 

Or, I do not know. Proximity sensors are very difficult to deal with.

 

However, You can monitor the proximity sensor values in order to obtain more information whether your proximity sensor works or not and what may cause the problem as well as to virtually disable the proximity sensor when in calls, made and received and, also, to make the proximity sensor control the screen with the application Proximity Sensor and Screen. There is a good description how tom use the application inside the application.
 
Here is more information.
 
How to download and install :
 
Look for Version 2.0 or higher of Proximity Sensor and Screen by Steven Stanley Bayes.
 
The application does not require neither root access nor any third party frames nor products.
 
Here is more information how to download and install the application :
 
https://play.google.com/store/apps/details?id=stevenstanleybayes.proximitysensor&hl=en
 
OR
 
Go to Google Play Store with your device. Click " APPS ". Click the magnifying glass of the search. Type exactly, character by character, :
 
***************************************************************
Proximity Sensor and Screen by Steven Stanley Bayes
***************************************************************
 
PLEASE, NOTE : MUST BE TYPED EXACTLY AS SHOWN, EXACTLY AT THE " APPS " TAB OF GOOGLE PLAY STORE, BECAUSE THE SEARCH ENGINE OF GOOGLE PLAY STORE IS VERY SENSITIVE.
 
Click on the displayed app with the same name and author to download and install. The application is also available in many other app stores and online which may or may not show after a general purpose search with google.com and a web browser but some forums where the links are posted may show.
 
READ THE INFORMATION INSIDE THE APPLICATION FIRST.
 

ProximitySensor.apk

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.