Related
I haven't had much luck searching/googling so I thought I'd ask. Is there any way I can set the value that the phone's proximity sensor will read? I'll try to explain.
My phone has the issue where the screen turns black after I receive a call. The only ways to get access to the phone again are to either plug it in to wake up the screen or pull the battery. I added a line to my build.prop file (gsm.proximity.enable=false), but otherwise I haven't touched anything to do with my proximity sensor. Obviously that command didn't work. I've also tried having "keep screen awake" checked, and "always use proximity" unchecked.
Anyways, when I run AndroSensor app, it tells me my proximity sensor reads "1.2 in". I was wondering what would happen if I could force that value to be 12 inches instead? I'd rather my screen perpetually stay on during a call than what's happening now.
Is there a file I can edit that would make this possible? I didn't see any other lines in my build.prop that said "proximity" in them anywhere. Phone is rooted, currently running cm7 stable ba2tf. I have ghost finger issues that are really bad on any rom running faux123 kernel, yea my phone's quite the lemon. Replacing this year, but it needs to last a bit longer. Help!
http://rootzwiki.com/topic/2804-app-free-propmodder-by-n00bware-updated-11211/ here's a link for prop mod its from the developer on rootzwiki. It should help with the proximity value and with other tweaks.
Sent from my MB860 using Tapatalk
unforgivenmercy said:
here's a link for prop mod its from the developer on rootzwiki. It should help with the proximity value and with other tweaks.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I had high hopes when I installed this app but sadly it didn't work. I opened up the app and changed the proximity sensor delay to 0 and rebooted, called the phone from my house, still a black screen as soon as I slide the screen to answer. Went back and changed the value to "remove prop entirely" and rebooted. Same result.
Thanks tho
papabri said:
I had high hopes when I installed this app but sadly it didn't work. I opened up the app and changed the proximity sensor delay to 0 and rebooted, called the phone from my house, still a black screen as soon as I slide the screen to answer. Went back and changed the value to "remove prop entirely" and rebooted. Same result.
Thanks tho
Click to expand...
Click to collapse
I used it on cm7 hybrid and works perfectly. What rom and you try to change the build prop with rom toolbox or another app of the like.
Sent from my MB860 using Tapatalk
When I go to about phone I get:
Mod version
CyanogenMod-7.1.0-Ba2tF-Olympus
Build number
GWK74
Kernel version
2.6.32.39-MB860-CM7-g54722f1
[email protected] #4
What line(s) would I need to put in build.prop
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Mr.Preacher said:
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Click to expand...
Click to collapse
See if enabling wake on volume helps:
Settings > Display > Volume rocker wake
Mr.Preacher said:
Is there a workaround or fix to the proximity sensor issue when using CyanogenMod 10.1? It doesn't matter which dialer I use, my screen goes blank and I can't get it back on to use the keypad or hang up.
Thanks in advance.
Click to expand...
Click to collapse
If you are using a screen protector, there is a known issue regarding placement. If the protector cutout is too close to the sensor, it will interfere with the proper operation of the sensor and blank out the screen too easily.
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
retrostudd said:
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
Click to expand...
Click to collapse
I don't have a screen protector. This solved it for me. Many thanks.
That said, the settings I'm using are a little weird. I have the Low set to 81, and it doesn't seem to matter what the High is set to (currently 100).
This fix works
retrostudd said:
I ran into a similar issue, turns out the tinting on the screen for the sensors had gotten dirty inside and I had to disassemble my phone and clean the sensor Windows. However if you don't like the idea of disassembling your phone, the HTC rezound proximity calibrator app on Google play might be helpful to you. I would try the app first before doing something more extreme.
Click to expand...
Click to collapse
this totally worked to fixed this same issue I have had. I used to have to go outside on a sunny day for my screen to come on while making a phone call. Once I used this app I was able to get it to come on in a dark room with hardly any light. I may at some point open her up and actually clean the inside of the sensor cover, but for now this worked like a charm.
Thanks for the tip.
One item to note, if you do decide to open your phone and clean the sensor windows, don't clean too aggressively or you will remove the tint from the backside of the glass. Just a tip.
I'm glad you guys have gotten your sensors working again.
I just had this problem today. Previously I never had issues with prox sensor, but just a couple days ago I did a complete wipe (data, cache, dalvik, system and internal SD card) and installed RC1 with a fresh install. The app mentioned above DID fix my issue however I know its a ghetto fix. Before running the app, the proximity sensor would work normally in good light, but not in low light. After running the app it works even in dark light which is great. However, I know its a weird fix. I can actually see the red proximity sensor during calls, when I couldn't previously. I'm glad I got it working, but I know there is something wrong still, and it's definitely ROM related as opposed to hardware because just 2 days earlier it worked fine before the clean install. Hmm..
Sent from my Incredible 4G LTE using xda app-developers app
Check this video ... hope developers will fix this ASAP ...
Note : You need an extra camera to see the Proximity light. Remember, you can't see this with open eyes ! Just like Infrared sensor.
greatricky said:
Check this video ... hope developers will fix this ASAP ...
Note : You need an extra camera to see the Proximity light. Remember, you can't see this with open eyes ! Just like Infrared sensor.
Click to expand...
Click to collapse
sorry but you can't see anything, I cannot read any of those blurred text lines.
the best solution for this is either to stop using it temporarily or switch to aosp4.3/cm10.2. all those sensors that samsung added only drain more battery.
broodplank1337 said:
sorry but you can't see anything, I cannot read any of those blurred text lines.
the best solution for this is either to stop using it temporarily or switch to aosp4.3/cm10.2. all those sensors that samsung added only drain more battery.
Click to expand...
Click to collapse
nevermind, just keep your eyes on the proximity sensor . It doesn't disappear after an incoming phone call !
anyway , how to stop that sensor permanently ?? it turned it off from > settings > call > turn off proximity sensor ! but still the light is visible ... it disappears after phone reboot !
ive noticed this as well
That's probably an air gestures thing.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
That's probably an air gestures thing.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hmmm mine is always shutdown i guess....that purple color is new to me (from the vid)
If you display turns off when coming close to the sensor with your hand during a call, the sensor is active, you just can't see.
Some cameras can see the light, some don't. You can check with an it remote control from your TV!
David
have noticed how this is on. i was gonna go through each individual service running by the system and shut it down and see if it turns off. Its gotta be an APK or jar file doing it. Unless the kernel itself is for some weird reason.
elesbb said:
have noticed how this is on. i was gonna go through each individual service running by the system and shut it down and see if it turns off. Its gotta be an APK or jar file doing it. Unless the kernel itself is for some weird reason.
Click to expand...
Click to collapse
I already turned off all sensors and installed several firmwares (omega ,arrow, wanam) and kernels ... but still ... it's so annoying
The proximity sensor requires 0,350mAh power. That's < 1% usage since we have 2600mAh battery I *think*....
greatricky said:
I already turned off all sensors and installed several firmwares (omega ,arrow, wanam) and kernels ... but still ... it's so annoying
Click to expand...
Click to collapse
Do you know if its still there on CM or Google Edition ROMs?
how to turn it off????
nik511 said:
The proximity sensor requires 0,350mAh power. That's < 1% usage since we have 2600mAh battery I *think*....
Click to expand...
Click to collapse
So I guess you mean it takes 0.35mA.
So if you have a runtime of 15 hours, it takes 5.25mAh... really not that much.
David.
davidbaumann said:
So I guess you mean it takes 0.35mA.
So if you have a runtime of 15 hours, it takes 5.25mAh... really not that much.
David.
Click to expand...
Click to collapse
Yeah
omg on all world doesnt exist app which works on rooted phone and can kill proximity and gesture sensor???
The app Elixir say 0,75mah for my Samsung S4, but also 0,75mah for an original battery of 2600mah is few energy, 2600/0,75= 3467 hours.
EDIT:I fixed it! turns out it was a hardware problem which occured after i replaced the screen. It was fixed by following instructions on this youtube video,called "How to Fix Proximity Sensor Issue for Samsung Galaxy S3, S4, or Note 2" ( i can't link right now because I'm new, so just look it up on youtube.) so if anyone encounters the same problem hope this video will help!
Hey guys. New to the forum I tried to do a bit of searching but couldn't really find an answer.
So I have two questions/problems I guess.
First off when I go into a call, sometimes the phone screen goes black as soon as I start the call, and won't turn back on until I hang up using the power button. From what I understand it's due to the proximity sensor always being on? But I have not been able to find a solution to this.
Secondly is, I've noticed with the lock screen notifications, when I ticked the option for wakescreen when receiving notifications, and when the screen is off, the proximity sensor is on. and when i untick the wake screen option, it goes off again.
I'm using Fusion-Boeffla Rom latest version as of now, 26-02-14 one. But this problem has been around when I was testing different roms such as temasek unofficial CM.
Any ideas how to fix this?
Thanks in advance!
1- go to calls -> settings -> uncheck turn of screen during calls.
Sent from my GT-I9300 using Tapatalk
amirTor said:
1- go to calls -> settings -> uncheck turn of screen during calls.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I can't find that setting unfortunately, also is this a hardware problem or software?
Jerryxmas said:
I can't find that setting unfortunately, also is this a hardware problem or software?
Click to expand...
Click to collapse
www.youtube.com/watch?v=z7kx27c1Iao&cd=1&ved=0CDQQtwIwAA&usg=AFQjCNHPZTtRTQj2KfBVwUOb3cUm-UNSkA
And its probably a kernel / rom issue
Sent from my GT-I9300 using Tapatalk
i can't click the link, but i've seen that option in stock samsung roms before, but i can't seem to find it on my rom. And you're right, its very likely its a rom/kernel issue, i may try a different rom or even stock to see if it helps =) thanks
Hello!
My new Kitkat device (LG optimus L80) takes really long for display to turn on after I get the phone off my ear. Display remains black for a second or two - ridiculously long! I'd prefer a time of maybe 0.3 - 0.5 seconds. Is there a way for me to change this timeout period? Maybe some Xposed module does this?
Thanx!
losmilosmi said:
Hello!
My new Kitkat device (LG optimus L80) takes really long for display to turn on after I get the phone off my ear. Display remains black for a second or two - ridiculously long! I'd prefer a time of maybe 0.3 - 0.5 seconds. Is there a way for me to change this timeout period? Maybe some Xposed module does this?
Thanx!
Click to expand...
Click to collapse
Adjust the proximity sensor value this will solve your issue I think xposed module is also available .....
Just give a google search
Sent from my x604 using Tapatalk
The-Immortal said:
Adjust the proximity sensor value this will solve your issue I think xposed module is also available .....
Just give a google search
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
I have indeed googled for stuff like proximity sensor display timeout and similar but I haven't found what I need.
losmilosmi said:
I have indeed googled for stuff like proximity sensor display timeout and similar but I haven't found what I need.
Click to expand...
Click to collapse
Use x-blast tools .....you can find proximity sensor times in build.prop tweaks of xblast tool ...
If you don't wanna use module then add this line to your build.prop using a text editor or root explore
persist.service.xrfm.mode=1mot.proximity.delay=0
This will remove proximity delay
Sent from my x604 using Tapatalk
The-Immortal said:
Use x-blast tools .....you can find proximity sensor times in build.prop tweaks of xblast tool ...
If you don't wanna use module then add this line to your build.prop using a text editor or root explore
persist.service.xrfm.mode=1mot.proximity.delay=0
This will remove proximity delay
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
I have modified build.prop but still no result.