I just noticed the past couple weeks that my light sensor does not read out less than 90 lux, even in total darkness. For reference, a totally dark room should read out at 0 lux. This affects any auto-brightness settings and apps.
I could almost swear that I tested this when I first got the phone, it did work correctly. So I was wondering first if anyone else has seen it happening to them, or if you could please test it.
The best way I've found to test is to use AndroSensor from the market. Also, just as additional info, I've tried this with an Otterbox Defender and with a naked phone, with the same results. Phone has never been dropped or wet and the proximity sensor works fine. I'm running stock ROM rooted.
Many thanks...
I can't help but I can say a few people have been having problems with there sensor... I had to replace my phone today because of it not working...
Sent from my EVO using xda premium
Slappy_G said:
I just noticed the past couple weeks that my light sensor does not read out less than 90 lux, even in total darkness. For reference, a totally dark room should read out at 0 lux. This affects any auto-brightness settings and apps.
I could almost swear that I tested this when I first got the phone, it did work correctly. So I was wondering first if anyone else has seen it happening to them, or if you could please test it.
The best way I've found to test is to use AndroSensor from the market. Also, just as additional info, I've tried this with an Otterbox Defender and with a naked phone, with the same results. Phone has never been dropped or wet and the proximity sensor works fine. I'm running stock ROM rooted.
Many thanks...
Click to expand...
Click to collapse
mine dont go less than 90 either???
Getting the same thing..
I'm curious, does anyone else that's getting the 90 lux reading also have light bleed from the home button? If you're getting a 0, do you have light bleed? Maybe something with how the glass is glue on?
I think we all are? Maybe the reason why the auto-brightness is so sensitive.
Just tested it... Mine stays at 90 to no matter what... Does not move in light or dark... I don't think the program is utilizing out sensor right??? Also my proximity sensor goes from 3.5in to 0 no matter how far or close I am... There is no in between???
Sent from my EVO using xda premium
Same here. No light bleed...
Check Me Out On The Google Play Store!!!
Sent From My HTC Evo 4G LTE, On The Now Network From Sprint!
I'm getting the same reading of 90 lux and if I put it up to light it moves higher ... You think this can be fixed when we get kernel source?
Sent from my LTEeeeeevoo using xda premium
NissanNick said:
Just tested it... Mine stays at 90 to no matter what... Does not move in light or dark... I don't think the program is utilizing out sensor right??? Also my proximity sensor goes from 3.5in to 0 no matter how far or close I am... There is no in between???
Sent from my EVO using xda premium
Click to expand...
Click to collapse
This is as designed - the proximity sensors either read out "something is up against the phone" or not. So they all have only 2 values, zero and something else.
goffmj said:
Getting the same thing..
I'm curious, does anyone else that's getting the 90 lux reading also have light bleed from the home button? If you're getting a 0, do you have light bleed? Maybe something with how the glass is glue on?
Click to expand...
Click to collapse
No light bleed that I can see, and I used to have an Evo 4G, so I know what it used to look like on that device. I'm tempted to try a factory reset, but have not unlocked the bootloader yet, so no way to make a nandroid. Ugh.
Bump-bump-bumpity-doo...
Anyone else seeing their light sensor truly zeroing out? For now, I've reinstalled my purchased copy of Lux Auto Brightness and set it to use the camera as the light sensor, which does the trick, but only checks when the screen is first turned on.
Related
My girlfriend got an Evo today and the soft keys will not light up at all. They flash when the screen turns on but will not come on at all afterwards. I did a factory reset and still nothing. Is this a known software issue or should we just take it back in?
Mine only turned on when I completely covered up the light sensor. I didn't get a chance to play with it much since I already put the invisible shield and put it to sleep until tomorrow but try that, they should at least turn on and you'll know if it's defective or not.
Sent from my Evo3D Shooter.
mine stay on the whole time the screen it on..... I would take it back..
Racer Of All said:
Mine only turned on when I completely covered up the light sensor. I didn't get a chance to play with it much since I already put the invisible shield and put it to sleep until tomorrow but try that, they should at least turn on and you'll know if it's defective or not.
Sent from my Evo3D Shooter.
Click to expand...
Click to collapse
Thanks it does come on when I cover the light sensor. Hopefully a software update will fix this. Since other people's are coming on without issue would it be a good idea to take it in anyway?
mine only come in in low light ie light sensor covered as well. i do believe this is the way they are intended to function. why would you need the soft keys lit up in full light? them staying lit constantly would just drain the battery quicker. i would say your device is working properly and there is no need to worry.
^^^^^^^^this^^^^^^^^^
sent from my Evo LTE, usually.
Zacisblack said:
My girlfriend got an Evo today and the soft keys will not light up at all. They flash when the screen turns on but will not come on at all afterwards. I did a factory reset and still nothing. Is this a known software issue or should we just take it back in?
Click to expand...
Click to collapse
They are light sensitive.
via HTC EVO 4G LTE.
I've seen reports that the light sensor can be picky if it's covered by a screen protector
Lol. Check your Google wallet...
Sent from my Galaxy Nexus
I was very excited by the Smart Stay feature of SGSIII but after a few days, experience, my opinion is that it does not work. I set the timeout to 15 sec. The eye flashes in the notification bar but most of the time screen is turned off. I tried staring directly at the front camera. Tried various positions too but no result. And all this is done in a normal lit room. Then I tried removing my specs and then it seems to work. Since I can't do much without them, so no fixed observation. Can anybody help?
do you wear glasses?
defia said:
do you wear glasses?
Click to expand...
Click to collapse
Yes
Mine works even with glasses on
Toadeh said:
Mine works even with glasses on
Click to expand...
Click to collapse
Any particular setting? Or particular angle at which you keep your phone? Mine for sure does not work. The eye flashes but then the screen is also turned off.
I have the same issue too. Does anyone know the issue and how to overcome it? Thanks
I get mixed results with it. It works under ideal conditions but I had to extend the dim period to use it in everyday use.
The icon appears to show that the phone is checking for a face and not confirming it saw one. I see it flash even when looking from an angle where I'm definitely out of the camera frame.
defia said:
do you wear glasses?
Click to expand...
Click to collapse
Me and a friend we bought s3 and both of us having an issue with smart stay !It works after you open the device for the 15-30 minutes and after that nothing,after the eye appears the screen goes off!We are not wearing glasses!!So any idea what cause that?A possible bug of it?Or any future update will fix it?
you guys running on XXfl2 or whatever it is?
smart stay works really well for me, never has an issue, even at acute angles
It never works for me.
Then again... I'm way to ugly for my phone to stay with me.
Smartphone's R getting to smart I guess.
Works great for me too...
Samsung already stated they are working on improving the feature as it is not yet capable of handling some light conditions, and most glasses.
Sent from my DROIDX
Works fine for me with glasses, as long as the phone's front camera is pointing right at me.
The flashing eye means its searching for a face; the only indication that it has recognised you is that the screen doesn't turn off.
Same issue!
Yup, facing the same problem. Keep staring at the screen for hours for the damn thing to work. But it just wont. I have tried with my glasses off. Got the same result. The eye appears on the screen twice. The first time it dims the screen, the second time it shuts it off. I have tried different angles, but have finally resigned to my fate, unless XDA/Sammy figure it out!
not working for me 2
I am not wearing any glasses but it simply dont wok tried to change the angels but no luck ... hope it need improvement. This was the main reason to purchase the s3 but....
Mine works quite well, feels like its abit of a battery drain though.
Sent from my GT-I9300 using XDA
For anyone having issues this might be worth a shout.
http://www.redmondpie.com/iseeyou-b...-older-devices-running-android-2.3-or-higher/
Sent from my Galaxy Nexus using Tapatalk 2
It needs to be a nice distance from your face to pick up your eyes, light is an issue too.
Its a nice feature that has some obvious issues on a 1.X MP camera.
Sent from my GT-I9300 using xda premium
ronak47 said:
For anyone having issues this might be worth a shout.
http://www.redmondpie.com/iseeyou-b...-older-devices-running-android-2.3-or-higher/
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Samsung patented this feature so i guess the app dev is in a bit of danger unless he is not really rich.
Other apps wont be as good either, as smart stay was made with this hardware in mind (namely the camera). Others will have to bend and shape to fit multiple cameras, making detection algorithms not as strong.
Sent from my GT-I9300 using xda premium
*** YOU MUST BE ROOTED TO USE THIS APP ****
This app will recalibrate a worn or dirty proximity sensor. If your screen does not turn on after a call, then your prox sensor either needs to be recalibrated or is burnt out.
Usage:
1) Open the app. If your screen does not turn on after a call, it should report the word "NEAR."
2) Increase PS2_CANC (High Threshold) until it reports "FAR." Go one or two values past where it first changes.
3) Cover and uncover your proximity sensor and verify that it reports NEAR and FAR correctly.
4) If you want the values to be set on boot check the box.
5) Post the values that work best for you along with the ROM you're using in this thread. Hopefully we can use them to find better default values.
If any combination of low threshold and high threshold does not make your proximity sensor function as it should, then it is most likely burnt out and you need to warranty your phone.
Get it at:
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator
This app was inspired by DHD proximity sensor calibrator by leppie:
http://forum.xda-developers.com/showthread.php?t=951858
Source:
https://github.com/Chad0989/Rezound-Prox-Sensor-Calibrator
Neat. Low 13, high 51 is the crossover point for my phone.
Works great, Chad. Mine was on the edge, so to speak. It worked sometimes, and didn't others. Bumping high up to about 54 and it's working great.
the defaults worked well for me. What does the low threshold do though? Changing it doesn't affect the responsiveness.
65 for the high works pretty well for the distance it should be when holding to your ear, but being more sensitive (detecting near when my hand was farther from the sensor) at the defaults also works.
This is great. Exactly what we needed. Thanks man
Had to set the high on mine down to 14 just to get "near" to show. Tested on a call and it works perfectly now. Thank you Chad. I'm using the global firmware and it never worked correctly after the ruu.
Low 12, high 53 works the best for me. thank you chad!!!!!!!!!!!!
Okay, this is pretty incredible. Thanks, Chad, invaluable fix for my poor Rezound's post-call-black-screen bug.
chad0989 said:
*** YOU MUST BE ROOTED TO USE THIS APP ****
This app will recalibrate a worn or dirty proximity sensor. If your screen does not turn on after a call, then your prox sensor either needs to be recalibrated or is burnt out.
Usage:
1) Open the app. If your screen does not turn on after a call, it should report the word "NEAR."
2) Increase PS2_CANC (High Threshold) until it reports "FAR." Go one or two values past where it first changes.
3) Cover and uncover your proximity sensor and verify that it reports NEAR and FAR correctly.
4) If you want the values to be set on boot check the box.
5) Post the values that work best for you in this thread. Hopefully we can use them to find better default values.
If any combination of low threshold and high threshold does not make your proximity sensor function as it should, then it is most likely burnt out and you need to warranty your phone.
Get it at:
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator
This app was inspired by DHD proximity sensor calibrator by leppie:
http://forum.xda-developers.com/showthread.php?t=951858
Source:
https://github.com/Chad0989/Rezound-Prox-Sensor-Calibrator
Click to expand...
Click to collapse
Default settings work for me as well.
You are the best!
Sent from my HTC Rezound using xda app-developers app
Gotta say, this is a pretty awesome tool. I've been trying to use this app called "Wave Control" that uses the proximity sensor to control media players and have just had absolutely no luck until now.
Couldn't tell if my sensor was just worn, dirty, or burnt out. With this app, it was reading "Far" constantly, but after some messing around, I finally got it to register again. Oddly enough, the values working best for me right now are:
Low Threshold: 5
High Threshold: 36..
Not sure what this means, but I'm just glad it's working still. Thanks for all the work you do, Chad. You're invaluable to the Rezound community.
Sent from my HTC Rezound using Tapatalk 2
14 and 29 for me
Hoping this will work for me. CM9 light sensor hardly turns my screen off when in calls, so it would seem I'm collecting too much light. Was getting pretty angry at it when it dials numbers with my cheek.
Thanks for this.
4 and 15 for mine
Sent from my Rezound using xda app-developers app
THANK YOU.
I bought my Rezound off eBay so I had no idea if it was normal for the screen to be so glitchy during calls. I had to press the power button to turn the screen on during calls if I needed to use to dial pad or even hang up. I'm so glad I saw this app because it's all fixed!
I had to set my settings to Low: 22 / High: 86....not sure if that's good or bad, but the screen now turns itself on when I pull the phone away from my cheek instead of me having to do it myself so it's all I care about.
what were the default values again?
darienms1986 said:
what were the default values again?
Click to expand...
Click to collapse
Mine defaulted to 12/51.
Sent from my ADR6425LVW using Tapatalk 2
darienms1986 said:
what were the default values again?
Click to expand...
Click to collapse
It appears to be different for every device. There is some sort of in-built automatic calibration in the kernel but it seems to not work very well.
chad0989 said:
It appears to be different for every device. There is some sort of in-built automatic calibration in the kernel but it seems to not work very well.
Click to expand...
Click to collapse
Ok just trying to set mine back to default. No big deal. The settings are working great that i posted. Thank you so much for all your hard work. I love this phone and you keep making it better
Sent from my Rezound using xda app-developers app
mine is 2/36.
and how did you guys find out the low threshold value？that value seems to affect nothing even if i set it higher than the high threshold value.
Sent from my ADR6425LVW using Tapatalk 2
darienms1986 said:
Ok just trying to set mine back to default. No big deal. The settings are working great that i posted. Thank you so much for all your hard work. I love this phone and you keep making it better
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
Uncheck set on boot and reboot?
Sent from my ADR6425LVW using Tapatalk 2
Basically, out with my daughter at the beach today and dropped my phone in the only tiny shallow pool of water around!
It was in there for about a second at most, coz I grabbed it out SUPER fast, gave it a shake, blew all over it, wiped it down on my nice dry top I had on etc.
2 big nasty gashes in the screen, but luckily I had a screen protector on!
But, they were really nasty looking things and just couldn't pluck up the courage to take off the screen protector until I got home, as I was 100% convinced screen was gonna have at least a couple nasty scratched bits etc.
However, got home, took off protector...PHEW, screen was still in perfect condition, so was the bodywork/chassis as I had a case mate on it.
Everything seems fine with the phone, apart from to the left of where it says 'htc' the is a constant red light that stays on no mater what.
I think this is the proximity sensor?
Any ideas how I can get this light to go off and stay off??
Really guys, ANY help would be sooooo much appreciated.
Thanks
Matt
Yes, on the right of the htc bezel is the proximity sensor. Even if your daughter dropped the phone, I don't think this affected the sensor. Does it stay on even if you turn the phone off? If not then I am sure some app is using it.
/\/\ said:
Yes, on the right of the htc bezel is the proximity sensor. Even if your daughter dropped the phone, I don't think this affected the sensor. Does it stay on even if you turn the phone off? If not then I am sure some app is using it.
Click to expand...
Click to collapse
On the LEFT side of the htc bezel there is a red light that stays on, but if I turn the phone off, then the light goes off.
It's only happened since I dropped it in water today.
Any ideas?
Matt
But it sounds really weird that a damage could cause it. Seriously. Please ensure there is no app running in the background which reads data from the proximity sensor. One time I was using some app, don't remember the name, never mind. It had an option to make use of the proximity sensor. Even if I turned it off, the proximity sensor was on all the time. Disabling the app/uninstalling it fixed my problem.
/\/\ said:
But it sounds really weird that a damage could cause it. Seriously. Please ensure there is no app running in the background which reads data from the proximity sensor. One time I was using some app, don't remember the name, never mind. It had an option to make use of the proximity sensor. Even if I turned it off, the proximity sensor was on all the time. Disabling the app/uninstalling it fixed my problem.
Click to expand...
Click to collapse
I know what you mean, the app is Called Viber and some users used to experience that using that app.
I've never used Viber and have checked all other apps. No result.
I downloaded Elixr 2 from the market and ran the Proximity Test.
Don't know What it means, but here is a screenshot of the result:
jpg images
Any more really is super appreciated.
thanks.
Matt
Just wait until you make a phone call, then you're whole world is going to go upside down.... with my proximity sensor on my X+ I grabbed an app called Rezound Proximity sensor adjust the PS1_CANC (Low_Threshold) value. My X+ is set to 95
hope this helps you.
Lloir said:
Just wait until you make a phone call, then you're whole world is going to go upside down.... with my proximity sensor on my X+ I grabbed an app called Rezound Proximity sensor adjust the PS1_CANC (Low_Threshold) value. My X+ is set to 95
hope this helps you.
Click to expand...
Click to collapse
Thanks for the help.....will try that now.
Nice to see a fellow welsh dude helping out!:good:
Matt
matthew33 said:
Thanks for the help.....will try that now.
Nice to see a fellow welsh dude helping out!:good:
Matt
Click to expand...
Click to collapse
Oh by the way you'll need root. Set it then reboot dude. Not many welsh on here haha.
Lloir said:
Oh by the way you'll need root. Set it then reboot dude. Not many welsh on here haha.
Click to expand...
Click to collapse
Done that and rebooted.
Proximity sensor still permanently on, here are some screenshots of sensor info....god knows what it means....
click image upload
matthew33 said:
Done that and rebooted.
Proximity sensor still permanently on, here are some screenshots of sensor info....god knows what it means....
Click to expand...
Click to collapse
You need to finetune the rezound app...if not then you are S.O.L
Lloir said:
You need to finetune the rezound app...if not then you are S.O.L
Click to expand...
Click to collapse
When I make or receive calls, the screen acts perfectly as it should.
Goes dark when it's at my ear, the lights up when I pull it away from my ear, just the damn proximity light is on all the time draining my battery.
Anyway to turn it off?
image hosting site
Matt
Is there anyway to turn off the proximity sensor light in the build prop?
Matt
matthew33 said:
Is there anyway to turn off the proximity sensor light in the build prop?
Matt
Click to expand...
Click to collapse
nope, do you use the other sensors?
you can rename or nuke the following file, note that the rotation/prox/light sensors will be toasted after
adb shell
su
rm system/lib/hw/sensors.enrc2b.so
or to move it replace the rm to mv so do this mv system/lib/hw/sensors.enrc2b.so system/lib/hw/sensors.enrc2b.so.old
Lloir said:
nope, do you use the other sensors?
you can rename or nuke the following file, note that the rotation/prox/light sensors will be toasted after
adb shell
su
rm system/lib/hw/sensors.enrc2b.so
or to move it replace the rm to mv so do this mv system/lib/hw/sensors.enrc2b.so system/lib/hw/sensors.enrc2b.so.old
Click to expand...
Click to collapse
That should stop my light staying on?
matthew33 said:
That should stop my light staying on?
Click to expand...
Click to collapse
it should in theory...
matthew33 said:
That should stop my light staying on?
Click to expand...
Click to collapse
if it doesn't then you might have to disable it in the kernel, if you know how to do that. I would do that, but zero time sorry...
There is a root led app I know a bout
Well i am calling it a possible fix as i am still testing it. I am talking about the full brightness issue that many others are facing too. The issue was the brightness would still vary automatically depending on the ambient light even when the auto brightness was switched off. So when you are in a dark room even if you wanted you could not turn the brightness to 100%. Initially when i just bought the phone for few days i felt the screen looked a little less brighter compared to how it looked in the showroom, so when i searched for it found out that so many of them out there have the same issue. You can just test it by switching off the auto brightness and keeping the brightness to 100% in a dark room and when you project a flash light or some light source on the sensor next to the ear piece the screen would get brighter and when you take off that light the screen would again become a little dimmer. I for a second thought it could be some kind of feature as well. But what ever that was i dint like it as could not pump up the brightness in a dark room to its full capacity even if i wanted it. And thats such a shame for such a beautiful display.
So i first wanted to flash some custom ROMs and see if that makes any difference. First i flashed a custom rom from the S6E android development section but the issue still persisted and after a day's observation i again flashed a ROM today from the s-6--s-6-edge-unified-development thread and after flashing the ROM i went in to settings-accessibility-vision-colour adjustment and switched it on, since then the brightness varied just once right after the colour adjustment was switched on but now i am continuously able to pop up the brightness to 100% even in the low light area and seems like the issue has been fixed !! I have been observing it for the last 3 to 4 hours.
So who ever has this issue can try this out and let me know if it worked. I would not say the ROM installation is a must, first try turning on the colour adjustment under settings-accessibility-vision-colour adjustment and if it doesnt work then try flashing the ROM and again doing the colour adjustment and let me know if it worked for you !! But after what ever changes you make do a reboot and give it an hour or so.
EDIT : As i was still testing it unfortunately the bug showed up again so i finally decided to flash an S6 ROM ( Not S6 edge) on to my S6E and to my surprise the issue was solved !! Now i can confirm that its just a software bug and hopefully samsung will fix it !! If any one wants to try flashing a flat S6 ROM let me know i will leave a link here with the kernel to be flashed. Hopefully this helped !!
I will test it..thanks for this
Can somebody confirm this as a possible solution to the bug?
Sent from my SM-G920F using XDA Free mobile app
the problem stills persists
LuanTeles said:
the problem stills persists
Click to expand...
Click to collapse
Ok so unfortunately samsung still has to work to solve it. I start to think it's really a serious issue if after 2 months there is still no solution. Samsung addressed the issue about the toggles desappeared almost immediately because it was probably really easy to solve...
Sent from my SM-G920F using XDA Free mobile app
I'm surprised not everyone is using lux. Just get the app and be done with it..
Oliv3 said:
I'm surprised not everyone is using lux. Just get the app and be done with it..
Click to expand...
Click to collapse
I tried with that also. Doesn't solve the issue unfortunately
Sent from my SM-G920F using XDA Free mobile app
What about reset or Odin stock.
Oliv3 said:
What about reset or Odin stock.
Click to expand...
Click to collapse
Unfortunately doesn't solve it as well
Sent from my SM-G920F using XDA Free mobile app
Must be a feature then, or some other reason Sammy did this.
On a side note, why worry about this? It's not a practical issue, is it?
Oliv3 said:
I'm surprised not everyone is using lux. Just get the app and be done with it..
Click to expand...
Click to collapse
I'm surprise so many people still recommend Lux app when it is useless for this issue. The issue is that the phone always has some autobrightness turned on even when we set it to be off. Even when you set Max brightness in Lux app, it's still only Max what the phone will do without Lux. Therefore, for those that want super bright all the time, Lux is useless.
Sent from my SM-G925T
nyknight77 said:
I'm surprise so many people still recommend Lux app when it is useless for this issue. The issue is that the phone always has some autobrightness turned on even when we set it to be off. Even when you set Max brightness in Lux app, it's still only Max what the phone will do without Lux. Therefore, for those that want super bright all the time, Lux is useless.
Sent from my SM-G925T
Click to expand...
Click to collapse
I'm "surprised" people still cry about impractical problems, just so they can have something to whine about.
This isn't widespread knowledge, I didn't even know this even existed.
Oliv3 said:
Must be a feature then, or some other reason Sammy did this.
On a side note, why worry about this? It's not a practical issue, is it?
Click to expand...
Click to collapse
Let's say that it is a really annoying issue in darken places because the brightness is too low. Try to compare the s6 edge with any other phone (s6 flat for example) and you will see how the issue is annoying! It is surely not a feature because the s6 flat doesn't do that. Moreover samsung admitted it is an issue (I have spoken with them several times), the funny thing is that after 2 months it is not solved yet.
Sent from my SM-G920F using XDA Free mobile app
I put some thing called velis auto brightness on and once set up seemed to solve it for me .
before always seemed to dark indoors
Sent from my SM-G925F using Tapatalk
mercuryzzz said:
Let's say that it is a really annoying issue in darken places because the brightness is too low. Try to compare the s6 edge with any other phone (s6 flat for example) and you will see how the issue is annoying! It is surely not a feature because the s6 flat doesn't do that. Moreover samsung admitted it is an issue (I have spoken with them several times), the funny thing is that after 2 months it is not solved yet.
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
What? That's not the problem OP is talking about? Brightness too low in dark places? No one has this problem, and if they did, a 3rd party app like lux would have fixed the issue.
Lux does not fix the issue. Many tried. I tried. I set Max brightness using Lux and its not as bright as it could be. You could try for yourself, turn off auto brightness, manually set Max brightness in both settings and Lux, go to a dark place and shine a flashlight on the light sensor. Screen will become brighter.
Then you'll understand that Max brightness does not work with setting and with Lux. Then you'll be enlightened... but then you can also choose not to try this and go on with your life as ignorance is bliss. When something doesn't work, most people call it a bug while some people choose to call it a feature
Sent from my SM-G925T
I thought the extra boost to brightness was a feature and helped battery?
Set to a certain maximum, on bright light situations (outside in sunlight, maglight on sensor) the display will boost to an unnatural brightness to aid visibility. On return to inside light levels the phone returns to normal.
Sent from my SM-G925F using Tapatalk
Oliv3 said:
What? That's not the problem OP is talking about? Brightness too low in dark places? No one has this problem, and if they did, a 3rd party app like lux would have fixed the issue.
Click to expand...
Click to collapse
It's not a feature its a bug. Every s6 edge has this issue . Maybe not everyone realized as you for example but it's for all s6 edge.
You can see it clearly comparing in a dark place a s6 flat and a s6 edge. The flat is way brighter than the edge so this is clearly a bug
Sent from my SM-G920F using XDA Free mobile app
Oliv3 said:
I'm "surprised" people still cry about impractical problems, just so they can have something to whine about.
This isn't widespread knowledge, I didn't even know this even existed.
Click to expand...
Click to collapse
Impractical? I always thought being able to control my screens brightness was fairly practical!
Surely the point of manual brightness is to be able to control it manually?
Oliv3 said:
Must be a feature then, or some other reason Sammy did this.
On a side note, why worry about this? It's not a practical issue, is it?
Click to expand...
Click to collapse
I also think this is more of a "feature" then a bug.
It originally was a bug before the maintenance update because the screen would not dim to 50% brightness before timing out completely. Unless the screen was in the (what im calling) super bright mode.
Since the maintenance update the screen will now dim to 50% before timing out altogether.
But we still see the screen go into super bright mode in very well lit areas (ie direct sun) When i look at the screen in this mode though i notice the colors dont look real. Which leads me to believe that this is more of a feature to ramp up the screens brightness when you are in situations that might make the screen hard to see (ie direct sunlight)