The script didn't work but blasting compressed air into the ear piece worked like a charm! Thanks!
This method was working previously but now it returns number -127 when executing the script. .what might be the reason?please make nandroid backup..just in case anything goes wrong
for those wanted to run as script (i haven try as i no longer own note 2)
*create a file, copy the syntax below and put it in extSdCard, use script manager to run as SU and at Boot
#!/system/bin/sh
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
i assume u was using script manager rite?This method was working previously but now it returns number -127 when executing the script. .what might be the reason?
Please help...
opps.. sorry for the late reply.do I have to root my note 2 to perform this?
As I amalso beginner when I do input the first ''echo 0 > /sys/class/sensors/proximity_sensor/prox_cal'' it says no such file or directory exist...something like that...I am on omegadroid 28...I am beginner so please explain me I using with Terminal emulator and type on terminal emulator
Su
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
and than I don't know how to continue...?? so please explain step by step or screen recorder
Send from N7100 Dn3 v5
Im currently running cm11 and have this problem but this solution works only on stock rom.......can you try and fix it on custom roms???...….......the first thing i notice after updated to the latest firmware, dme6 or dmf2 is either efs corrupted or in my case is the proximity sensor not working well.
during in-call, the screen off but when move away from face, the screen would remain off.
so i poke around in the system file and found some solution after few days of testing
and now its work very well
the only method works for me is re-calibration via terminal/adb shell
u need to type 'su' without the quotation mark and then follow by the code
by echoing it 0, it force the sensor to resetCode:echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
by echoing to 1, its actually force the sensor to re-calibrateCode:echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
my guess is, the calibration value are stored in efs so if there are chances for it to corrupted, there's small chance that the sensor goes haywire, well it happen to me. so i hoping this helps some user that facing proximity sensor.
*ps : okay, so i did some experiment and found that for it to recalibrate properly, it is recommend to do it under a bright environment
So, i decided to put in solution/fixes for those problem that occur on GT-N7100(Galaxy Note II International) that i cant find the solution.
the solution is based on my experience so i DID manage to fix it
**update : another method which i found online, forgotten from where, give a hard blow on the earpiece. i remember saw some user (not from xda) posted that this helps the problem
as reported from user, only working in SAMSUNG stock rom
for those having problem for the fix to stick
for those wanted to run as script (i haven try as i no longer own note 2)
*create a file, copy the syntax below and put it in extSdCard, use script manager to run as SU and at Boot
1. After flashing a ROM, you booted it and when you long press the home button, suddenly the system ui force close, but you DID FLASH the rom ACCORDINGLY to the OP's instruction ;
This should work on all ROMs...Im currently running cm11 and have this problem but this solution works only on stock rom.......can you try and fix it on custom roms???...….......
the first thing i notice after updated to the latest firmware, dme6 or dmf2 is either efs corrupted or in my case is the proximity sensor not working well.
during in-call, the screen off but when move away from face, the screen would remain off.
so i poke around in the system file and found some solution after few days of testing
and now its work very well
the only method works for me is re-calibration via terminal/adb shell
u need to type 'su' without the quotation mark and then follow by the code
by echoing it 0, it force the sensor to resetCode:echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
by echoing to 1, its actually force the sensor to re-calibrateCode:echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
my guess is, the calibration value are stored in efs so if there are chances for it to corrupted, there's small chance that the sensor goes haywire, well it happen to me. so i hoping this helps some user that facing proximity sensor.
*ps : okay, so i did some experiment and found that for it to recalibrate properly, it is recommend to do it under a bright environment
So, i decided to put in solution/fixes for those problem that occur on GT-N7100(Galaxy Note II International) that i cant find the solution.
the solution is based on my experience so i DID manage to fix it
**update : another method which i found online, forgotten from where, give a hard blow on the earpiece. i remember saw some user (not from xda) posted that this helps the problem
as reported from user, only working in SAMSUNG stock rom
for those having problem for the fix to stick
for those wanted to run as script (i haven try as i no longer own note 2)
*create a file, copy the syntax below and put it in extSdCard, use script manager to run as SU and at Boot
1. After flashing a ROM, you booted it and when you long press the home button, suddenly the system ui force close, but you DID FLASH the rom ACCORDINGLY to the OP's instruction ;
I do not have such a directory proximity_sensor. When I ls sensors I get a directory with a name which contains accl, I gues this is the directory for the accelerometer.the first thing i notice after updated to the latest firmware, dme6 or dmf2 is either efs corrupted or in my case is the proximity sensor not working well.
during in-call, the screen off but when move away from face, the screen would remain off.
so i poke around in the system file and found some solution after few days of testing
and now its work very well
the only method works for me is re-calibration via terminal/adb shell
u need to type 'su' without the quotation mark and then follow by the code
by echoing it 0, it force the sensor to resetCode:echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
by echoing to 1, its actually force the sensor to re-calibrateCode:echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
my guess is, the calibration value are stored in efs so if there are chances for it to corrupted, there's small chance that the sensor goes haywire, well it happen to me. so i hoping this helps some user that facing proximity sensor.
*ps : okay, so i did some experiment and found that for it to recalibrate properly, it is recommend to do it under a bright environment
So, i decided to put in solution/fixes for those problem that occur on GT-N7100(Galaxy Note II International) that i cant find the solution.
the solution is based on my experience so i DID manage to fix it
**update : another method which i found online, forgotten from where, give a hard blow on the earpiece. i remember saw some user (not from xda) posted that this helps the problem
as reported from user, only working in SAMSUNG stock rom
for those having problem for the fix to stick
for those wanted to run as script (i haven try as i no longer own note 2)
*create a file, copy the syntax below and put it in extSdCard, use script manager to run as SU and at Boot
1. After flashing a ROM, you booted it and when you long press the home button, suddenly the system ui force close, but you DID FLASH the rom ACCORDINGLY to the OP's instruction ;
You are too good. Thanks Alot. :good:the first thing i notice after updated to the latest firmware, dme6 or dmf2 is either efs corrupted or in my case is the proximity sensor not working well.
during in-call, the screen off but when move away from face, the screen would remain off.
so i poke around in the system file and found some solution after few days of testing
and now its work very well
the only method works for me is re-calibration via terminal/adb shell
u need to type 'su' without the quotation mark and then follow by the code
by echoing it 0, it force the sensor to resetCode:echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
by echoing to 1, its actually force the sensor to re-calibrateCode:echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
my guess is, the calibration value are stored in efs so if there are chances for it to corrupted, there's small chance that the sensor goes haywire, well it happen to me. so i hoping this helps some user that facing proximity sensor.
*ps : okay, so i did some experiment and found that for it to recalibrate properly, it is recommend to do it under a bright environment
So, i decided to put in solution/fixes for those problem that occur on GT-N7100(Galaxy Note II International) that i cant find the solution.
the solution is based on my experience so i DID manage to fix it
**update : another method which i found online, forgotten from where, give a hard blow on the earpiece. i remember saw some user (not from xda) posted that this helps the problem
as reported from user, only working in SAMSUNG stock rom
for those having problem for the fix to stick
for those wanted to run as script (i haven try as i no longer own note 2)
*create a file, copy the syntax below and put it in extSdCard, use script manager to run as SU and at Boot
1. After flashing a ROM, you booted it and when you long press the home button, suddenly the system ui force close, but you DID FLASH the rom ACCORDINGLY to the OP's instruction ;