Dear devs,
I'm not a developer (I shouldn't even be posting here)
Maybe it's possible to use the light sensor for "dim/waking screen" during a call.
It would be tricky ofcourse because what if you're in a dark environment
But perhaps it's possible to let the sensor scan the intensity of light right after pressing the call/pick-up button, whether you call someone or pick up a call yourself.
Since I don't have any experience in developing whatsoever, I hope this idea may be a great pain in the *** / project.
Sincerely
DaanJordaan
P.S. It's a shame we haven't got a proximity sensor, but we do have Android
P.P.S
G-Sensor waking just does not work
This would be a great app to make however I dont think we have access to the light sensor. If there is an api for it that would be great though.
Just realised something, is the sensor even sensitive enough to register small changes in light intensity? (If you're in a dark environment i mean)
this is totally possible, since HTC has done this with WM phones.
The HTC Eris (Verizon's HTC Hero) has that function already , if someone can actually get the eris coding maybe we can it out.
awsy44 said:
The HTC Eris (Verizon's HTC Hero) has that function already , if someone can actually get the eris coding maybe we can it out.
Click to expand...
Click to collapse
Did the Eris not have a hardware proximity sensor?
And the part about the WM phones was right, although I think that this method used the front facing cameras
i am afraid if it was that easy htc would have done it in the first place... don't see that feature coming too soon tbh.
E2K said:
Did the Eris not have a hardware proximity sensor?
And the part about the WM phones was right, although I think that this method used the front facing cameras
Click to expand...
Click to collapse
Lol i don't believe that... that would reduce battery lifetime by 20x + it take to much time to start camera so fast as you can pick up youre phone
jaapschaap said:
Lol i don't believe that... that would reduce battery lifetime by 20x + it take to much time to start camera so fast as you can pick up youre phone
Click to expand...
Click to collapse
then use a htc diamond and cover (only) the front-camera hole when in a call and see what happens
Its a nice idea, however as far as I can tell we have no access to the light sensor, which is a right pain. If anyone knows how please post it! Need access for another program I'm writing and cannot work it out!
Hmm, the Diamond does have a light sensor (left next to the ear speaker). Not quite sure either if they use the camera for this. Same as the other poster, I would assume that takes quite some battery. But then again, you know what they say about assumption
I'm not an Android developer, so don't know if it's possible to access the light sensor. However, the sensor is used already with the automatic backlighting. But it depends on how that's implemented obviously.
It should be possible to read the light sensor on the Hero from android.
Have a look at:
http://developer.android.com/reference/android/hardware/SensorManager.html
There might be some examples regarding sensors in the ApiDemos in the SDK.
packetlss said:
It should be possible to read the light sensor on the Hero from android.
Have a look at:
http://developer.android.com/reference/android/hardware/SensorManager.html
There might be some examples regarding sensors in the ApiDemos in the SDK.
Click to expand...
Click to collapse
Yep tried that, but if you run the following code on a Hero:
Code:
List<Sensor> sensorIDs = sm.getSensorList(Sensor.TYPE_LIGHT);
xViewA.setText("Light Sensors = "+sensorIDs.size());
sensorIDs = sm.getSensorList(Sensor.TYPE_ALL);
xViewO.setText("Sensors Total = "+sensorIDs.size());
You get
Light Sensors = 0
Sensors Total = 4
???
Guess that means that there is no API access to the light sensor then.
thought the hero had a real proximity sensor, mainly because the display powers off when i call somebody and put the phone near my ear.. doesnt it?
felikz said:
thought the hero had a real proximity sensor, mainly because the display powers off when i call somebody and put the phone near my ear.. doesnt it?
Click to expand...
Click to collapse
It depends on how long you've been talking...talk for more than 30 seconds (or however long your phone is set before it turns the display off) and poof it goes off. Talk shorter than that, and it stays on.
F the Diamond
I owned a Diamond before and even if dim/wake was supposed to work, it didn't Sometimes it would and sometimes it wouldn't plus if you didn't do anything the screen would just automaticly dim after ten seconds or so. On top of that it wouldn't wake again.
Is there anywhere I can look in the hero source to work out how to get it working? Really need access to the light sensor in code!
Just stumbled upon this thread and all of you are saying that there is no API level access to the light sensor in the HTC Hero, so I thought to myself, "shouldn't the value of the light sensor be available for reading through the /sys kernel interface?"
Just did a quick search using the find command through adb shell and found /sys/devices/platform/i2c-adapter/i2c-0/0-0066/light_sensor which appears to be reporting the light sensor value, however only when the screen is on. Also /sys/devices/platform/i2c-adapter/i2c-0/0-0066/status appear to report the value in a different format (when the screen is on).
Hopefully this will be of any value to someone interested in doing more research into this.
Happy hacking!
Related
Touch InCall Screen Tweak was just posted in the Raphael forums: http://forum.xda-developers.com/showthread.php?t=488991
It's the work of 600GOL and Steve Pritchard. I just tested it and it worked on a Touch HD unbranded (Stock ROM).
This is their work - just sharing it so you guys know it works for the Touch HD as well. The app is attached.
brief write up here http://www.fuzemobility.com/in-call-screen-timeout-solved-really/
It works based on screen orientation - if the screen is face up the backlight turns on - if the phone is vertical it turns off. So it is gsen based and not light sensor based. You can keep turning the phone face up/vertical and it keeps toggling the backlight.
Thanks for sharing !
You will make some happy persons I thing
WOW, great job!! I hope can use it in cook rom
Thanks for posting it!
It don't work well with my HD.
Only worked for one episode.
Then it stopped working now.
on my HD dutty rom v2.1 it is working like a charm !!!
Installing Touch in Call Screen Tweak
I am new to the Touch HD. Can anyone tell me how to install it. Probably a dumb question, but I have nothing to go on.
Many thanks in advance.
Regards
O
It's just a cab file so just move the cab to your phone and run it. Once installed it works without an configuration. A new version was released today that fixes a bug with it sometimes not working so if you have any issues you should try the newest version. It's a great app.
Backlight control
Thanks for that. I have another basic question. Where do I put the cab files? The manual for the HTC Touch is frankly not particularly helpfuland a trawl through the stufff which is already on it does not really help.
M<any thanks for your assistance.
Regards
Oliver
Backlight Tweak
OK, I can save you the trouble now with many thanks. I have found an excellent YouTube demeonstration which I attach here for all the other ignoramuses (ignorami) like me.
http://www.youtube.com/watch?v=NWgsxvkE2f8
Thanks again.
Oliver
Thanks a lot
Oh, that's slick!!
Thanks!
Didn't work for me, I'm afraid.
I was making a call that required me to hit numbers on the keypad, and I kept having to turn the screen back on manually, every time I was asked to enter something.
Are there any configuration issues, maybe caused by settings on the phone? (I'm also using HD Tweak, but assume others that have used this have HD Tweak too.)
johncmolyneux said:
Didn't work for me, I'm afraid.
I was making a call that required me to hit numbers on the keypad, and I kept having to turn the screen back on manually, every time I was asked to enter something.
Are there any configuration issues, maybe caused by settings on the phone? (I'm also using HD Tweak, but assume others that have used this have HD Tweak too.)
Click to expand...
Click to collapse
Did you hold the screen so it is 'face up'?
Why is this so difficult??
I have seen hundreds of posts on this topic. I am not a programmer and I do appreciate every effort the code writers put into their work on this forum; but it seems this would be an easy one. Simply trigger the light sensor to come on when a call begins. Have the light sensor be polled every second or two during a call so if it is near your ear it turns the screen off. When away from your ear, like when you need the keypad, it turns the screen on. Thats it! At the end of the call it goes back to normal use. What is so difficult about this? I have had my HD not 2 months and the simpliest thing in the world...making a phone call...becomes a chore on this phone. It is really a pain in the a$$. Just calling voicemail is a nightmare because I have to pull away and press buttons and go back. Can someone help?
ryahia said:
I have seen hundreds of posts on this topic. I am not a programmer and I do appreciate every effort the code writers put into their work on this forum; but it seems this would be an easy one. Simply trigger the light sensor to come on when a call begins. Have the light sensor be polled every second or two during a call so if it is near your ear it turns the screen off. When away from your ear, like when you need the keypad, it turns the screen on. Thats it! At the end of the call it goes back to normal use. What is so difficult about this? I have had my HD not 2 months and the simpliest thing in the world...making a phone call...becomes a chore on this phone. It is really a pain in the a$$. Just calling voicemail is a nightmare because I have to pull away and press buttons and go back. Can someone help?
Click to expand...
Click to collapse
There's always been a conflict of light sensor and gsensor and light sensor isn't great anyway because they put it in the earpiece so it is in the shade in a lot of angles... anyway, you can try this as well: http://forum.xda-developers.com/showpost.php?p=3296423&postcount=382
it keeps the backlight on for 1 min then it dims the backlgiht and leaves the screen on without a backlight...
Great work, thanks!!!
hey thanks, this works great
This tweak utilizes the light sensor. Does this mean that it won't work when answering a phonecall in a dark room ????
Why use your phone in a darkroom? haha sorry for that...
I am using the program now on Davideuck v3 rom and its working flawlessly till now..
I also have HD Tweak activated, off course but the program overrules i think:
In the program it selves i have activated ignore light sensor, and also ignore first screen off...
So it works.
Sadly I don't think this is working properly with Duttys 2.3 Xtreme
Update on Issue #1: 2010.11.29
This issue appears to affect all unlocked Froyo devices on the Rogers network. It MAY affect all Froyo devices, regardless of network lock status, but we have been unable to confirm this (yet) on the only Froyo device locked to Rogers - The Acer Liquid e.
There are currently 4 threads (that I am aware of) scattered around XDA. As this problem affects multiple devices I will start posting updates in the General Discussion/Q&A thread, and will stop posting updates here. If you are looking for more information, please refer to:
Main Thread: http://forum.xda-developers.com/showthread.php?t=845152
Other Device Specific Threads:
N1: http://forum.xda-developers.com/showthread.php?t=849969
DZ: http://forum.xda-developers.com/showthread.php?t=848793
SGS: http://forum.xda-developers.com/showthread.php?t=850784Wanted to see if this is isolated to my phone or if others have these issues.
_________________________________________________________________________________________________________________
Phone is Rooted, S-Off, Paul Obriens Custom ROM with HTC Sense on Rogers Network.
1. Cannot get a location lock unless I use GPS, it will not give me a location in Maps at all unless I turn on GPS.
2. Display is set to Automatic Brightness but the screen stays the same no matter if i'm in direct sunlight or in a pitch black room
3. Have SMS Timestamp fix but am still getting messages which sometimes show hours behind or hours ahead
Bump
Sent from my HTC Vision using XDA App
For the GPS issue, you should post this up in the thread on Paul's ROM, to see if others have the problem. I presume your GPS worked fine on the stock ROM ?
Others have reported issues with the automatic brightness setting. I suspect it doesn't work at all, even on the stock ROM.
Also have issue with automatic brightness adjusting not working.
ayewhy said:
Also have issue with automatic brightness adjusting not working.
Click to expand...
Click to collapse
I don't think I've seen anyone saying that it *does* work for them in the stock ROM. Anyone ?
steviewevie said:
For the GPS issue, you should post this up in the thread on Paul's ROM, to see if others have the problem. I presume your GPS worked fine on the stock ROM ?
Others have reported issues with the automatic brightness setting. I suspect it doesn't work at all, even on the stock ROM.
Click to expand...
Click to collapse
Will do, hopefully it can get fixed. The GPS works fine, locks fast. It's when I don't have GPS enabled that it won't give a location using the wireless network now.
Wonder if making a single thread regarding auto brightness would be good. I've emailed HTC and they gave the typical "pull battery, factory reset" garbage. And after "exhausting" those "fixes" they simply say to call and RMA the device...ugh
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away. It changes back after going to sleep and unlocking. Also, it won't go below approx. 50%.
Edit: I checked it again and it does change back, it just takes a few seconds.
Sent from my HTC Vision using XDA App
andijvie42 said:
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away. It changes back after going to sleep and unlocking. Also, it won't go below approx. 50%.
Edit: I checked it again and it does change back, it just takes a few seconds.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Can you take a video possibly of this, what are the details of your phone? Rooted? S-Off?
The screen will "dim" when the backlight times out but it never actively dims because of the sensor on my phone.
Stealth1985 said:
Can you take a video possibly of this, what are the details of your phone? Rooted? S-Off?
The screen will "dim" when the backlight times out but it never actively dims because of the sensor on my phone.
Click to expand...
Click to collapse
My phone is completely stock. The dimming might be too little to be noticed, have you tried to shine a light directly in the light sensor, while being in a fairly dark room, so that you can observe the maximum change of brightness?
You could also download one of the sensor apps out there and see if the sensor works. Mine says light level 0 in a darker room, and max when i shine a light in the sensor.
I doubt the sensor is very useful though, as the brightness only goes from approx. 50 to 80%...(going from zero light to lightest) might be better if these values could be set.
About the video, the only camera I have right now is the DZ, so I'll see what I can do.
Sent from my HTC Vision using XDA App
andijvie42 said:
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away.
Click to expand...
Click to collapse
That's interesting, thanks, I'll give that a try.
Sounds like the auto-brightness and the keyboard/cap buttons backlight (both of which use the light sensor) might both suffer from the same thing - i.e. very poor programming/implementation.
I have issues 1 and 2 (but not 3).
I would like to add that auto-brightness seemed to work fine when I (briefly) used CyanogenMod RC2, though I have no other Android devices to compare with.
I dumped the stock Sense ROM pretty quickly so this might have worked fine on the original ROM.
This definitely sucks, what ROM do you have that the location doesn't work too?
Pretty disappointed that I'm having these issues and HTC's response is send it in. I am not paying to re-unlock another phone because they can't make something that fully works.
Sent from my HTC Vision using XDA App
I have some bad news for you about point 1. It looks like a number of people on various unlocked android devices (N1, Desire, SGS i9000m) are experiencing the network location problem.
http://forum.xda-developers.com/showthread.php?t=845152
There is w (crappy, but still functional) work around, but...
For most of us it started sometime around Nov 14th.
It has some pretty unhappy implications for those of us who prefer android and want a top-end phone.
Good luck.
Damn Rogers seems to have screwed things up.
Sent from my HTC Vision using XDA App
Yeah. Maybe.
It seems to be an interaction between Rogers and unlocked android phones. We don't know whether it is all unlocked android phones, though, or even if it is specific models (i.e. would an unlocked Rogers Captivate have the same problem), or a specific OS (i.e. we don't know yet if the problem happens on eclair - while not directly useful to the DZ owners, it would at least help to pinpoint the problem and might help to get Google to step-up).
There are just too many unknowns, and how do you speak with someone with sufficient knowledge to speak intelligently? Rogers tech support hasn't been much help, and Google and Rogers seem to want to bounce the problem between each other.
Auto-brightness: Using My sensors free market app, checked the light sensor. All the sensors but the light gives live info. Looks like it doesnt work at all, like not switched on.
Uk htc z, stock rom.
-- sent from htc z using xda app
tbalden said:
Auto-brightness: Using My sensors free market app, checked the light sensor. All the sensors but the light gives live info. Looks like it doesnt work at all, like not switched on.
Click to expand...
Click to collapse
Could be that the app doesn't work with the DZ light sensor properly though ? I know my light sensor does something, because the keyboard/cap keys backlight turns on and off kind of randomly depending on light levels (and if you block the sensor then the lights come on).
Thats true. It happens here too. But still might be related...
-- sent from htc z using xda app
Ok.with very bright flash light around it gives data with the my sensors app. Then its the levels its moving light level between,as mentioned in this thread before.
-- sent from htc z using xda app
tbalden said:
Ok.with very bright flash light around it gives data with the my sensors app. Then its the levels its moving light level between,as mentioned in this thread before.
Click to expand...
Click to collapse
Cool, kinda sounds like it works, just very very badly.
Hi,
I've searched high and wide for a solution (other than sending it back to Motofailure repair) and am failing at finding one so far. So I'm hoping I can get some help from here.
So, this is the situation: I make a call, screen instantly turns dark and will only light up again when I press on the area where the light (&) proximity sensor is.
I've already tried the following.
1.) Done a factory reset (3x) - with mem card, with reformatted mem card, w/o mem card.
2.) Clearing the dust on the earpiece hole using an air duster.
3.) There were times that I worked properly after I've uninstalled apps but the issue came about again after a couple of tries.
So, now I'm thinking that I might want to root my Defy to set things right. I'm quite familiar with RSD Lite as I've used it before on my RAZR2 V8.
A bit of background: I bought my Defy on pre-order so this is one of the earlier models. I had the earpiece problem and sent it to Motofailure repair and the whole process took a month (32 days to be exact - long story. I'm avoiding having to send this PoS back. They updated the software when I got it back.
As far as I can recall, I didn't had this problem before the earpiece problem. And I'm thinking it might be a software problem hence I'm now looking at a solution by rooting and flashing the ROM with an original one.
I have no way of finding out (as far as I know) whether this is a hardware problem (hence hesitating to have it sent back to Motofailure repair).
What I've also observed is that when there is direct bright light, it works normally but when its dim, then the problem appears.
I don't have any screen protectors, just so you know.
Can anyone advise me on what to do?
During a call proximity sensor is activated to turn off the screen at the moment it detects proximity and asumes you are using the phone against your hear, so it turns off screen to save energy.
I think you might have some app installed in your phone, using and reversing the sensor status so it detects proximity when there isnt, and viceversa
You might want to try removing apps using that sensor and see if problem gets solved, there is also an app in the masket called sanity; which makes extensive use of proximity sensor for vaqrious things, and have an option to reverse proximity sensor, you might want to try it and see if problem gets fixed.
You might try this things: remove apps using proximity sensor, test phone. Deactivate in pocket detection; test phone, and install sainity, test phone, install a new rom?
If speaker is bigger than original one, or there was an assembly error, light/proximity sensor won't fit into right place.
I've seen such reports and you can't do anything unless you open up thing and check the problem, but you haven't seen the right assembly so you may not know the right place.
Are you using any screen protector? I know some screen protectors cause this problem.
Edit: Nevermind, I see that you're not using any.
how to calibrate the proximity sensor?
My new defy 's proximity sensor seems cannot work correctly,when i making a call ,the screen shut off immediately，and the screen could not light on by any key,but when i touch the proximity sensor with my finger,the screen may be light on!
so i download a app to test the proximity sensor which name's"Android sensor data",this app fingue out the state of proximity sensor,"near" or "far",sometimes I just passing my finger over the proximity sensor, the reading will show 'near' and then remain 'near' even when my finger is moved away!
Can anyone else help me to calibrate the proximity sensor?google told me some android phone can do this ,such as htc, zte etc.
goole tell me android phone have some standard testcode,such as *#*#4636#*#* can show the phone statue,it works correstly in Defy,*#*#0588#*#* test the proximity sensor ,but it doesn't work in defy!!!
I don't think this issue could be solved trough software tweaks. Chances are this is a hardware problem. Maybe you should contact the Motorola support.
try disabling in-pocket detection
have the same problem. it started 2 days ago. Im using CM7. It just turns dark and wont wake up unless someone else is calling me. Just got it tested, and when i cover the sensor with my finger it says 0cm distance for long time.
I've tried data wipe and similar, but nothing helped so far.
EDIT: I've just tried wiping the place where proximity sensor is with some soft cloth and alcohol and for the time being, it works. O.O
Could Wipe Dalvik help?
Hey guys,
hope someone can help me.
I've the feeling that my light sensor might be damaged.
The setting is on automatic light regulation and i've the feeling that the
screen is very dark. Is there any possiblity to check if the light sensor still works fine?
I've already put my finger for a few seconds on it and nothing changes.
I also read in the guide that the screen should wake up when you wipe over the switched off device.
Unfortunately nothing happens when i do so.
Thanks a lot for your support
schelde_sun said:
Hey guys,
hope someone can help me.
I've the feeling that my light sensor might be damaged.
The setting is on automatic light regulation and i've the feeling that the
screen is very dark. Is there any possiblity to check if the light sensor still works fine?
I've already put my finger for a few seconds on it and nothing changes.
I also read in the guide that the screen should wake up when you wipe over the switched off device.
Unfortunately nothing happens when i do so.
Thanks a lot for your support
Click to expand...
Click to collapse
Autobrightness has been too dark since the S2. The S3 also suffers from that bug as does the Note 2. Unless Samsung fixes it with a update you`ll have to wait for a hack and root the phone to be able to change it.
gee2012 said:
Autobrightness has been to dark since the S2. The S3 also suffers from that bug as does the Note 2. Unless Samsung fixes it with a update you`ll have to wait for a hack and root the phone to be able to change it.
Click to expand...
Click to collapse
Thanks a lot for this information. I didn't know this, as it's my first Samsung mobile.
But my impression is that it worked fine, and unfortunately the note 2 fell down at weekend and
now i've the feeling that the regulation is not correct since then. Is there any test to try if the light sensor still works?
And normally the switched off screen should wake up when i swipe over the screen, right? Because it doesn't work, or is it necessary to set up some settings?
Thanks a lot again for the help!
schelde_sun said:
Thanks a lot for this information. I didn't know this, as it's my first Samsung mobile.
But my impression is that it worked fine, and unfortunately the note 2 fell down at weekend and
now i've the feeling that the regulation is not correct since then. Is there any test to try if the light sensor still works?
And normally the switched off screen should wake up when i swipe over the screen, right? Because it doesn't work, or is it necessary to set up some settings?
Thanks a lot again for the help!
Click to expand...
Click to collapse
I think there's a light sensor test in the service menu (can't remember the dialer code to access it though) and for the phone to wake when you swipe over the screen you need to enable "Quick Glance" in Settings > Motion
schelde_sun said:
Hey guys,
hope someone can help me.
I've the feeling that my light sensor might be damaged.
The setting is on automatic light regulation and i've the feeling that the
screen is very dark. Is there any possiblity to check if the light sensor still works fine?
I've already put my finger for a few seconds on it and nothing changes.
I also read in the guide that the screen should wake up when you wipe over the switched off device.
Unfortunately nothing happens when i do so.
Thanks a lot for your support
Click to expand...
Click to collapse
Hello bro,
You might want to test it with *#0*# code using dialpad.. hope this help..
Sent from my GT-N7100 using xda app-developers app
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
My understanding is that proximity sensor in note 2 is set for 8 cm and values are either 0 or 1 above or below 8cm
Sent from my SGH-T889 using xda app-developers app
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I have this exact problem here was my thread a few months ago:
http://forum.xda-developers.com/showthread.php?t=2099898
and the only response was to factory reset (which I haven't done yet and from what you're saying that won't fix the problem either...)
Quick question, I only see 1 light coming out of the two holes at the top of the phone, are there supposed to be 2 lights? (you can check using another camera since it uses infrared)
-- edit --
just found this thread on sprint forums:
http://community.sprint.com/baw/message/544084
apparently the person had a tech open it up and air out the sensor
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
same issue
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I had the exact same problem with the proximity sensor and other weird sensor issues. I had never rooted or anything. T-mobile exchanged my phone for a new one.
vaghotstuff said:
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
Click to expand...
Click to collapse
This fixed for me too. But the sensors start acting up like every couple weeks and I'd have to blow air into the ear piece.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
TRY THIS
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
Thanks for advise! I'll try it and revert!
BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
It didn't help! After the fix is installed the sensor works at the same manner... Is it possible to try something else?