Well i am very confused whether our phone has a light sensor or not. In the official user manual of I5801 (English-India), at page number 17, its clearly stated that the left one of the two sensors on top left side of our phone is proximity sensor and the right one is light sensor. If there is one, then why is there not any option for automatic brightness? and what its use is? And if its not there, then why is it given in the User's manual ?
Does anyone have any information on this at all? Was/is there any rom that supported automatic brighness via the light sensor?
So why isn't it included in Samsung' Stock Rom ?
Do you think really that no-one ever try to use it .
nishant_713 said:
Well i am very confused whether our phone has a light sensor or not. In the official user manual of I5801 (English-India), at page number 17, its clearly stated that the left one of the two sensors on top left side of our phone is proximity sensor and the right one is light sensor. If there is one, then why is there not any option for automatic brightness? and what its use is? And if its not there, then why is it given in the User's manual ?
Click to expand...
Click to collapse
There is no light sensor on Galaxy I5800/5801. The proximity sensor is actually a pair of sensors, one sends an electromagnetic/Infrared radiation while the other one is to receive it back for the sensor to get activated.
nsm1234 said:
There is no light sensor on Galaxy I5800/5801. The proximity sensor is actually a pair of sensors, one sends an electromagnetic/Infrared radiation while the other one is to receive it back for the sensor to get activated.
Click to expand...
Click to collapse
Wow, this is kinda shocking news!
So I have a problem with my galaxy s2 I bought from Craigslist I was really careless until I came home and notice that the phone does have any screws in it but everything work perfect but I notice that my auto brightness doesnt work...the proximity sensor does work I did use the app called arodone on market to test all the sensor everything had the number jumping but the light sensor stay at 10 I think so my question is it is possible to damage the light sensor without damage the proximity sensor please help me
Sent from my SAMSUNG-SGH-I727 using XDA App
auto brightness is screwey on this phne. So just change brigtness yourself
I was wounding if someone here could tell why Proximity sensor only works at night?
Thanks in advance
no answer
pbazw said:
I was wounding if someone here could tell why Proximity sensor only works at night?
Thanks in advance
Click to expand...
Click to collapse
Has no one ever seen this?
Kernel settings probably or sensor problem.
But you better try another compatible with your ROM kernel or search how to edit it's settings.
touristas0 said:
Kernel settings probably or sensor problem.
But you better try another compatible with your ROM kernel or search how to edit it's settings.
Click to expand...
Click to collapse
I used several different roms and this is always the case.
The proximity and light sensor are different. The intensity sensor sure has more sensitivity at night, but the proximity sensor has its own IR. It will work just well in both day and night.
If you have this problem on all ROMs, you might have a hardware issue. Try updating your firmware.
Happy to help.
Far_SighT said:
The proximity and light sensor are different. The intensity sensor sure has more sensitivity at night, but the proximity sensor has its own IR. It will work just well in both day and night.
If you have this problem on all ROMs, you might have a hardware issue. Try updating your firmware.
Happy to help.
Click to expand...
Click to collapse
I'm running 3.33 firmware and this happens on all roms, not sure why but light and proximity stop working at same time and they both start working when room is dark.
I just wanted to check if this was the same with everyone's phone.
Going into *#0*# and 'Sensor', my accelerometer, gyroscope sensor and magnetic sensor are in a constant state of flux when the phone is just resting flat on a table. The altitude is also constantly changing, but not as frenetically as the others.
Is this the same for everyone or is my phone on the fritz?
Many thanks,
F.
flashish said:
I just wanted to check if this was the same with everyone's phone.
Going into *#0*# and 'Sensor', my accelerometer, gyroscope sensor and magnetic sensor are in a constant state of flux when the phone is just resting flat on a table. The altitude is also constantly changing, but not as frenetically as the others.
Is this the same for everyone or is my phone on the fritz?
Many thanks,
F.
Click to expand...
Click to collapse
have the same, just wish my barometer would actually work, its been stuck on 1011 hPa since I got it
flashish said:
I just wanted to check if this was the same with everyone's phone.
Going into *#0*# and 'Sensor', my accelerometer, gyroscope sensor and magnetic sensor are in a constant state of flux when the phone is just resting flat on a table. The altitude is also constantly changing, but not as frenetically as the others.
Is this the same for everyone or is my phone on the fritz?
Many thanks,
F.
Click to expand...
Click to collapse
All the sensors should be a little jumpy. The apps from the developers just filter the jumpiness of the sensors. So not to worry. at least you have them all working.
There seems to be an issue with the barometric sensor of some units that I have tested (actually all of the units that i have tested, 4 so far).
I started a new thread with the issue.
The sensors should be very sensible, which I see as a good thing.
One question though, is the OIS gyro not supposed to move? That is the only one static for me. If I test it while it's not lying still on a table or I'm holding it with absolutely no movement it fails, otherwise it passes. But the values are constant...?
Hi guys,
Noticed a very interesting thing today: suddenly a white light started to pulse next to the front cam every time I was tilting the phone. It was quick 3-4 pulses with strict intervals as if a sensor was working. It didn't pulse when phone was in a fixed position, only when tilting, in all apps.
A reboot fixed this, but I wonder if there is any sensor there that activated because of something? Never experienced this before!
Any thoughts what it can be? Thx.
Sounds like proximity sensor to me.
znel52 said:
Sounds like proximity sensor to me.
Click to expand...
Click to collapse
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
VirtualWaver said:
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
Click to expand...
Click to collapse
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Thanks for this! I did test my screen and all looks good but this is worrying. However, this only happened once although I use Viber video calls every day.
VirtualWaver said:
Thanks for this! I did test my screen and all looks good but this is worrying. However, this only happened once although I use Viber video calls every day.
Click to expand...
Click to collapse
Im going to try this out myself next week and see what's going on. Mine ain't coming until Monday.
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Hoe bright is it?
Normally it could blink during SOT and with that duty cycle it will outlast many of the other screen pixels.
Or is there something I'm missing???
Are it's pixels IR?
blackhawk said:
Hoe bright is it?
Normally it could blink during SOT and with that duty cycle it will outlast many of the other screen pixels.
Or is there something I'm missing???
Are it's pixels IR?
Click to expand...
Click to collapse
Who's a hoe?
Probably much ado about nothing. But I can't test it. , The only thing that came to mind was screen being full brightness and proximity sensor being on for hours causing this. But just a hunch .
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Limeybastard said:
Who's a hoe?
Probably much ado about nothing. But I can't test it. , The only thing that came to mind was screen being full brightness and proximity sensor being on for hours causing this. But just a hunch .
Click to expand...
Click to collapse
Even at full brightness because it's flashing, it's duty cycle is less than the surrounding pixels plus it will "flash" by darkening its pixels depending on screen color.
If it has specialized IR emitters I could see that happening maybe; if there's a design or manufacturing flaw.
Because it's flashing visible light it would be hard to use a cam to detect IR... which is how I normally check IR emitters.
While it was easily seen on the Note 10 i can't see it on the Note 20
Nastrahl said:
While it was easily seen on the Note 10 i can't see it on the Note 20
Click to expand...
Click to collapse
Interesting. Maybe it uses IR diodes?
If it doesn't display when it's active maybe that's why some think it's "burnt out"?
Lol, until someone mentioned the flashing circle I never noticed it.
blackhawk said:
Interesting. Maybe it uses IR diodes?
If it doesn't display when it's active maybe that's why some think it's "burnt out"?
Lol, until someone mentioned the flashing circle I never noticed it.
Click to expand...
Click to collapse
I don't know.
I've read that they replaced all the sensors with the front camera, and that′s one of the battery killer since a few were completely passive like the ambiant light one, that's now active.
When a passive sensor needs no electricity to operate, an active needs to, and the camera can't work passively so it drains battery.
They advised to turn off all the features that use the front camera as a sensor like the auto brightness, smart stay (and also what can use the accelerometer like smart alert and raise to turn on the screen), etc. to avoid the process Android System to take to much battery.
Nastrahl said:
While it was easily seen on the Note 10 i can't see it on the Note 20
Click to expand...
Click to collapse
Nastrahl said:
I don't know.
I've read that they replaced all the sensors with the front camera, and that′s one of the battery killer since a few were completely passive like the ambiant light one, that's now active.
When a passive sensor needs no electricity to operate, an active needs to, and the camera can't work passively so it drains battery.
They advised to turn off all the features that use the front camera as a sensor like the auto brightness, smart stay (and also what can use the accelerometer like smart alert and raise to turn on the screen), etc. to avoid the process Android System to take to much battery.
Click to expand...
Click to collapse
Even passive sensors use some current although it may be in the microamps.
Autobrightness is a trash apk anyway.
Seems highly unlikely that the whole cam be used for these functions if at all.
VirtualWaver said:
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
Click to expand...
Click to collapse
Not sure if anyone told you this sorry haven't had time to read the thread but I would suggest avoiding viber calls on this phone. The proximity sensor is damaging the screen when on viber. It seems viber is accessing the sensor too aggressively.
Sent from my SM-N986U1 using Tapatalk
warriorvibhu said:
Not sure if anyone told you this sorry haven't had time to read the thread but I would suggest avoiding viber calls on this phone. The proximity sensor is damaging the screen when on viber. It seems viber is accessing the sensor too aggressively.
Sent from my SM-N986U1 using Tapatalk
Click to expand...
Click to collapse
You know this is most likely a digital circuit; a fixed voltage of an either high or low value... those values are fixed and don't change. Even firmware can't alter that let alone apks. Duty cycle rate/length maybe.
This urban rumor about the proximity sensor causing screen damage has been around since at least 2015, long before OLED screens.
A Google search yielded nothing except this:
https://us.community.samsung.com/t5/Galaxy-S10/Proximity-sensor-issues-S10-S10/td-p/498492/page/9
blackhawk said:
Even passive sensors use some current although it may be in the microamps.
Autobrightness is a trash apk anyway.
Seems highly unlikely that the whole cam be used for these functions if at all.
Click to expand...
Click to collapse
Trash apk ? Sorry i meant the built-in adaptive brightness.
---------- Post added at 01:16 AM ---------- Previous post was at 01:15 AM ----------
blackhawk said:
You know this is most likely a digital circuit; a fixed voltage of an either high or low value... those values are fixed and don't change. Even firmware can't alter that let alone apks. Duty cycle rate/length maybe.
This urban rumor about the proximity sensor causing screen damage has been around since at least 2015, long before OLED screens.
A Google search yielded nothing except this:
https://us.community.samsung.com/t5/Galaxy-S10/Proximity-sensor-issues-S10-S10/td-p/498492/page/9
Click to expand...
Click to collapse
I personally never heard about it. Thanks for the insight
Nastrahl said:
Trash apk ? Sorry i meant the built-in adaptive brightness"
I personally never heard about it. Thanks for the insight
Click to expand...
Click to collapse
My opinions.
There certainly are long standing Samsung issues that span more then one generation of phones. The proximity sensor trashing the screen doesn't appear to exist at all. If anything it conserves screen life.
Auto brightness was always twitchy even on my S4+.
Auto brightness was never truly adaptive... and still isn't. Lol, all it does is give me a headache and waste resources.
The other thing is I always try to avoid using my phones in direct sunlight. Very rarely do I ever go past 65% brightness.
Direct sunlight+high ambient temperature+high power consumption can really overheat a phone fast.
Even worse...
Auto brightness on+charging+sunlight+accidental screen turn on that's not noticed, can fry a phone in a few minutes. Real easy to do in the car... been there.
blackhawk said:
My opinions.
There certainly are long standing Samsung issues that span more then one generation of phones. The proximity sensor trashing the screen doesn't appear to exist at all. If anything it conserves screen life.
Auto brightness was always twitchy even on my S4+.
Auto brightness was never truly adaptive... and still isn't. Lol, all it does is give me a headache and waste resources.
The other thing is I always try to avoid using my phones in direct sunlight. Very rarely do I ever go past 65% brightness.
Direct sunlight+high ambient temperature+high power consumption can really overheat a phone fast.
Even worse...
Auto brightness on+charging+sunlight+accidental screen turn on that's not noticed, can fry a phone in a few minutes. Real easy to do in the car... been there.
Click to expand...
Click to collapse
Thanks, i never thought about that so it's a very valuable information.
Just in case if it can be useful :
A few years ago I found an app called Underburn which is a complete new approach about adaptive brightness.
https://play.google.com/store/apps/details?id=com.out386.underburn
Instead of adjusting the screen brightness from the ambient light, it set it according of the amount of white pixels displayed on screen to avoid binding you, and it doesn't care about sunlight.
The more white is displayed, the more it will dim the screen (by reducing the screen brightness, not by applying a filter ; even if there's also a setting for that if its too bright for you even at the minimum level) by the amount of your choosing.
It can play a role to save battery too somehow.
Nastrahl said:
Thanks, i never thought about that so it's a very valuable information.
Just in case if it can be useful :
A few years ago I found an app called Underburn which is a complete new approach about adaptive brightness.
https://play.google.com/store/apps/details?id=com.out386.underburn
Instead of adjusting the screen brightness from the ambient light, it set it according of the amount of white pixels displayed on screen to avoid binding you, and it doesn't care about sunlight.
The more white is displayed, the more it will dim the screen (by reducing the screen brightness, not by applying a filter ; even if there's also a setting for that if its too bright for you even at the minimum level) by the amount of your choosing.
It can play a role to save battery too somehow.
Click to expand...
Click to collapse
Thank you
I'll take a look at it. I'm running on dark mode but since it's Pie it's not native to all apps like Gmail which burns my eyes out.
*I'm playing with it. It will run on Pie. It takes some time to set up but definitely has potential.
Haven't been able to fairly gauge it's configured battery usage.