Related
Hi all,
Is there any way to reduce screen brightness even lower than what we could do with built-in settings? Thanks.
Sent from my Transformer TF101 using Tapatalk
Wear sunglasses?
I'd love to know too. The screen is just a touch too bright in bed at night
jimbob1971 said:
Wear sunglasses?
I'd love to know too. The screen is just a touch too bright in bed at night
Click to expand...
Click to collapse
I'd like to know this too, I have it at the lowest setting usually and it's still a little bright, I don't even need to turn it up outdoors.
On my modded galaxy s, the darky rom come with an app called "screen filter", it enable you to get your screen WAY dimmer, may be worth a look for in honeycomb, nice for froyo/gingerbread, you even have it in the task menu... my 0.02cents
I noticed that i always have to set it to the max cause it cut down on the glaze. This screen is like a mirror during the day.
http://forum.xda-developers.com/showthread.php?t=731032
try that app (requires root)
AdjBrightness doesn't work. I'm running Modaco ROM HR3, which means it's rooted, but AdjBrightness keeps saying it requires root. Thanks anyway.
Sent from my Transformer TF101 using Tapatalk
Try "Brightness level" by curvefish. I can't guarantee it will work but it works on my g tablet?
Sent from my DROIDX using Tapatalk
I don't think any apps can make it dimmer, without rooting and system access. Brightness level widget doesnt make it any dimmer (it reports the brightness level as 8%, when the system brightness bar is all the way to the left, and when set to 0% in BLW the screen doesnt change).
One of the first things that I look for before buying any device is can the screen be set to a low enough brightness. Manufactures often overlook this in their quest to make screens as bright as possible, and in one case I ended up taping a piece of plastic over the screen of an Acer netbook as a filter to get the brightness down low enough to use in a dim room. In the case of the Transformer, I could not try before I bought, but the screen does go down pretty dim.
+1 for Screen Filter. I don't have a TF yet so I haven't tried it but it works great on my SGS and doesn't require root. I suspect it may not work as well on an LCD as on my SAMOLED screen on my phone since it doesn't actually reduce the backlight, but it's still worth a try.
Thanks, screen filter works!
OK guess in having my first problems? Today my capacitate buttons at the bottom of the phone have just started going out on there own. Literally while I'm typing this they have come on and went out like 5 times now. Is anyone else experiencing anything like this? Weird cause up until now I have had zero problems with my phone. Maybe a sensor having glitches?
Are you typing in landscape mode?
Sent from my MB865 using XDA App
No portrait ...right now they won't even come on? Like they all of a sudden have a mind of their own LoL
have you tried covering the light sensor by the speaker grill? The button lights are brightness sensitive, so by covering the sensor, they should turn on. Otherwise, I would guess there might be a problem with your auto brightness or the sensor itself. When I first got this coming from a captivate, I was confused since the captivate turned them on when you touched the screen.
Sent from my MB865 using XDA App
Yep tried the light sensor and a battery pull as well. Now they won't even light up? Not like its a killer dealbreaker for me or nothing. Just weird they all of a sudden went crazy?
Now that you mention it I've been experiencing the same issue with my atrix2. Its like the buttons have a mind if their own.
Sent from my MB865 using xda premium
Yeah, mine come on when they want to. Right now they are off.
Sent from my mAtrix2!!
All moto phones do this. The software for the light sensor is just REALLY bad, so there is really nothing we can do about it, unless a dev wants to help us out.
Well it really just started doing this today. But after playing aroung with the display settings I'm thinking the light sensor is either going bad or is bad. When I set it to auto brightness it gets dimmer then the lowest manual setting in a completely dark room. Oh well, like I said not a killer deal for me. Just never had one fail quickly like this.
try turning off auto brightness and see if they still do it
svtfmook said:
try turning off auto brightness and see if they still do it
Click to expand...
Click to collapse
I never use auto brightness its always set at about the lowest brightness on manual. I've played with it back and forth and think the light sensor is just acting up.
Wow, I hope that's not a widespread issue.
My A2 doesn't have that problem. It's quite new but I think it's my 4th now (I've lost count of how many times I've seen a dead pixel on that otherwise gorgeous screen) and I do remember the capacitive buttons' backlight doing weird things on my other Atrix(es). I can't remember if that was on my OG Atrix, or if it was on one of my A2s in a car and the lighting kept changing, or if it was an actual problem.
But anyways, the light sensor works pretty well for me on my current A2. I usually have it on auto-brightness.
Mine work perfectly on manual or auto.
Hey everyone,
Whenever I use automatic screen brightness the screen always seems to be very dark or on the lowest brightness setting.
Has anyone else noticed this or does anyone know of a fix for this?
Thanks
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Yes my screen is pretty dim when on auto. I just don't use that setting. Maybe others will have some comments.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I am using it all the time, except the night time.
It's working flawlessly to me during the day, for example: when i am in a room and i will enter the garden, or a brighter room.. works awesome
But the level of brightness is not good during the absolute dark, i just don't like the dim, because it's loosing lot's of contrast, so i am just sliding i little bit to make it brighter.
As i said, absolutely no problem during the day, sunrise, sunset... but the dim is not good for my eyes.
EDIT: i'm on .30 FW
My screen is also too dark on auto most of the time.
I must agree. Auto dimming isn't so good. I find it easier to just leave it full blast
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I must agree. Auto dimming isn't so good. I find it easier to just leave it full blast
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
We should decompile framework.res and change the values for the dim...
Looking for some free time for doing the work...
dark auto brighness
I have exactly the same problem. It's definitively too dark and not working at all. If I put a lamp (bright light) on it, it will brighten completely the screen but will not go back to normal when I take the light away. I have to restart to find back this too dark screen. Please note that the pad I tried when buying in the shop at the same problem, and a friend who bought another transformer pad has this problem as well. Hard or software?
Try the Lux Auto Brightness app here. You can fully customize your auto brightness levels. Works great for me.
When you are in an average lit room, it will be on the lowest possible brightness
When it is night time it almost goes to full.
Don't use auto brightness if it bothers you.
sometimes the auto brightness gets stuck in dark setting .what i do to fix this is i just set the bright manualy to high and this turns off the automatic brightness . then i just turn on the automatic brightness and it works.
carlosraf20 said:
sometimes the auto brightness gets stuck in dark setting .what i do to fix this is i just set the bright manualy to high and this turns off the automatic brightness . then i just turn on the automatic brightness and it works.
Click to expand...
Click to collapse
hmmm...i'll have to try that.
90% of the time i use my tablet in my living room...and no matter what time of day, wether the sun is coming in through the back window or i am just using the lights, auto brightness is always too dim for me (except at night...then it is fine) its not a huge deal since they have the slider in the notification window.
thanks
David Dee said:
Try the Lux Auto Brightness app here. You can fully customize your auto brightness levels. Works great for me.
Click to expand...
Click to collapse
Thank you, it a great solution
http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Title says it all. Its a very odd glitch. If i call someone, unless i quickly exit the phone app, my screen turns black but my call will continue. I cant turn the screen back on until the call is ended and i have to pull the battery. It happens regardless of what rom im on. Any help? Thanks in advance everyone
Sent from my SCH-I535 using Tapatalk 2
Have your cleaned your sensor in the front of your phone.
Sent from my SGS3 running Eclipse 2.1
No, what is/how do i do that?
Edit: I also have a ghost armor/ slick wrap sort of thing on the front of the phone. Is that the reason?
http://a248.e.akamai.net/origin-cdn...pfiles/photos/SW-GALS3-CFRED-3.jpg?1342082302
Sent from my SCH-I535 using Tapatalk 2
I would try removing that skin, it could be blocking the proximity sensor. I had the same problem on a galaxy nexus. I tried clearing phone app data, reboots, factory resets. In the end had to send it in on warranty because the sensor was bad.
Sent from my SCH-I535
Its weird though because the screen only turns off if the app i am running and xcan interact with is the phone application. If i use firefox or anything else while making the call everything is hunky dory.
Sent from my SCH-I535 using Tapatalk 2
GalaxyS3IsMeh said:
Its weird though because the screen only turns off if the app i am running and xcan interact with is the phone application. If i use firefox or anything else while making the call everything is hunky dory.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Try using an app that shows sensor readings. I like to use Elixir2 which has a sensor section. When viewing the proximity sensor readings, it should indicate "Far" when nothing is activating the sensor, and "Near" if you cover the sensor (with your finger or whatever). If it reads Near without you purposely tripping the sensor, your protector could be covering it or something else is wrong.
Sent from my SPH-D700 using xda app-developers app
bbelos said:
Try using an app that shows sensor readings. I like to use Elixir2 which has a sensor section. When viewing the proximity sensor readings, it should indicate "Far" when nothing is activating the sensor, and "Near" if you cover the sensor (with your finger or whatever). If it reads Near without you purposely tripping the sensor, your protector could be covering it or something else is wrong.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Yeah try this. Problem with my phone was intermittent, clearing the phone app data seemed to fix it but it always came back.
Just out of curiosity did you ever install an app called facebook contacts?
Sent from my SCH-I535
Not an app besides messenger and the actual fb app persay, but i did sync them to my contacts
Sent from my SCH-I535 using Tapatalk 2
The app was actually facebook contact sync. It's a third party app and I had originally thought it may of had something to do with the problem. That's why I asked.
I don't think it's a software problem because you said it happens on all of the roms you've tried. My nexus was stock and I did several factory resets, even waited for the jellybean update. Nothing I did was ever a permanent fix.
So I think either something is blocking the sensor i.e. dirt or the screen protector, or the sensor is bad.
Sent from my SCH-I535
My proximity sensor went bad after I replaced a screen lens by heating up and unglue technique. I turned it off in the phone app, and now it's fine, but for me it's very irritating that I have a high-end device which is somewhat broken, so I started researching what's wrong and how to fix.
It does work, I tested it by enabling hidden menu ( *#22745927 ) and then diagnostic mode ( *#0*# ) + click "Sensors". It does show proximity sensor at ADC 16 or more (I think it triggers at 15, so always on). When I bring the hand to the sensor, ADC goes to 100, so the sensor is somewhat working, but it always does sense something which isn't there, which is causing it to misfire. I have another good S3, and ADC value on it is 0 or 1 when nothing is in front of it, so my sensor could clearly be better.
I have no idea what ADC is, by the way
I have another broken front panel laying around, so I took the phone apart and replaced a sensor with the one from that panel. I did see a slight improvement, which is: ADB value went down to 11-12, so the sensor was not ALWAYS in triggered state, but clearly still no bueno.
What I'm going to do now is get a new item and try replacing with a new one. It's not overly expensive, like 10 bucks when shipped from china (search for "Front Facing Camera s3" on ebay). Should that be a success, I will post my results here.
I also am not sure if it is possible to recalibrate sensor to not trigger if ADC value is, say, below 20 and such. I would imagine there could be a configurable value. Somewhere this value of 15 is coming from, isn't it? So, idk, if some guru here is reading this post, maybe could advise where to go to configure it
Not to keep this thread alive or anything, but I gave my dad my old phone and he complained to me a few days later that the screen kept going off as well so I met him only to find out that he had the case on wrong and it was blocking the proximity sensor. He definitely is not cut out for a smart phone.
Sent from my SCH-I535 using xda app-developers app
galets said:
My proximity sensor went bad after I replaced a screen lens by heating up and unglue technique. I turned it off in the phone app, and now it's fine, but for me it's very irritating that I have a high-end device which is somewhat broken, so I started researching what's wrong and how to fix.
It does work, I tested it by enabling hidden menu ( *#22745927 ) and then diagnostic mode ( *#0*# ) + click "Sensors". It does show proximity sensor at ADC 16 or more (I think it triggers at 15, so always on). When I bring the hand to the sensor, ADC goes to 100, so the sensor is somewhat working, but it always does sense something which isn't there, which is causing it to misfire. I have another good S3, and ADC value on it is 0 or 1 when nothing is in front of it, so my sensor could clearly be better.
I have no idea what ADC is, by the way
I have another broken front panel laying around, so I took the phone apart and replaced a sensor with the one from that panel. I did see a slight improvement, which is: ADB value went down to 11-12, so the sensor was not ALWAYS in triggered state, but clearly still no bueno.
What I'm going to do now is get a new item and try replacing with a new one. It's not overly expensive, like 10 bucks when shipped from china (search for "Front Facing Camera s3" on ebay). Should that be a success, I will post my results here.
I also am not sure if it is possible to recalibrate sensor to not trigger if ADC value is, say, below 20 and such. I would imagine there could be a configurable value. Somewhere this value of 15 is coming from, isn't it? So, idk, if some guru here is reading this post, maybe could advise where to go to configure it
Click to expand...
Click to collapse
UPDATE: I bought a brand new sensor/camera block, and same issue there: minimum ADB is ~12. So, it's glass. It is possible that the sensor openings are either slightly shifted, or too dark.
Anyone knows how to configure the threshold value?
galets said:
UPDATE: I bought a brand new sensor/camera block, and same issue there: minimum ADB is ~12. So, it's glass. It is possible that the sensor openings are either slightly shifted, or too dark.
Anyone knows how to configure the threshold value?
Click to expand...
Click to collapse
You shouldnt have to go through all this man. You should get a new phone
Sent from my SCH-I535 using Tapatalk 2
Solved, yay!!!!!!
GalaxyS3IsMeh said:
You shouldnt have to go through all this man. You should get a new phone
Click to expand...
Click to collapse
Nope, I got it resolved!!!!!!!!
Here's how, with pictures: http://blog.galets.net/2013/01/fix-proximity-sensor-on-samsung-s-iii.html
Hey guys,
I'm using my new nexus 5 for about two days now and something seems to be wrong with auto brightness (at least) on my device. The phone makes the screen brighter just fine, but dimming it when it gets in a dark environment doesn't seem to work really well. Can someone give this a try please?
Just turn off the lights in a room and see if the screen adjusts correctly. On mine it doesn't.
Turning on and off auto brightness fixes the issue but as soon as the screen gets brighter again, the problem starts...
Thanks in advance
Gesendet von meinem Nexus 5 mit Tapatalk
Good spot, I seem to experience this as well ! Exactly as you say works fine until the brightness gets set higher then it wont ever fall back its as if it can never lower only increase brightness.... odd!
Did you give it a minute to adjust?
Since my Nexus 5 isn't here yet this is what I've observed on stock Android in the Galaxy Nexus and other phones:
While it should go down after some time it's pretty common for auto brightness not to dim down as soon as it gets darker. You don't want your brightness to jump up and down just because the lighting changes for a second. And since turning the brightness up is much more relevant than down it goes up almost instantly but before dimming back down it monitors the environment for a while.
When you turn auto brightness off and on again you force the sensor into a new reading so this should set the brightness to the correct level without delay.
But it wouldn't be the first time auto brightness was bugged on a phone.
The delay really annoyed me on my tablet running vanilla 4.2 so installed lux which works well. You set the brightness how you want it at a given light level and then it sets the brightness according to the ambient light each time you wake it up and holds that setting until the next time you wake it up... best of both worlds.
Sent from my Nexus 5 using xda app-developers app
You're right gokpog,it does work I just didn't give it time. It took around 10 seconds to change the backlight levels which is much longer than the nexus 4 which is why I didn't notice it. Hopefully there is a more sensitive curve in the future
Sent from my Nexus 5 using XDA Premium 4 mobile app
Yep this has been the case with stock android for a while. Feature or flaw you decide but it is what it is and is across the board no matter what device if its using stock android on it
Sent from my Galaxy Nexus using xda app-developers app
Well it doesn't seem to work as expected to me: go to a bright place, then to a very dark one. Yes it will dim a bit but not quite enough. Remain in the dark room and turn off auto brightness. Then turn it on again. The screen will get significantly darker than it was before
Gesendet von meinem Nexus 5 mit Tapatalk
brittonberkan said:
Well it doesn't seem to work as expected to me: go to a bright place, then to a very dark one. Yes it will dim a bit but not quite enough. Remain in the dark room and turn off auto brightness. Then turn it on again. The screen will get significantly darker than it was before
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
just swith screen off and then on again with power button to seee the difference
I'ts how stock android works..it only increase brightness but not decrease..
andQlimax said:
just swith screen off and then on again with power button to seee the difference
I'ts how stock android works..it only increase brightness but not decrease..
Click to expand...
Click to collapse
I have find too that the automatic brightness take time to decrease brightness, also increase, but the most annoying is that with the same level of light and without moving the phone, the brightness goes up and down erratically, without a reason, it didn't happen with any of my previous phones
I just installed this app today, I've had similar problems that weren't present on my N4. With this app running, when I turn the phone screen toward a light, it brightens, and back to face a darker place it dims almost immediately. To give me more battery life I've tuned the brightness curve to be a bit low, N5's auto seemed to be too bright for me overall anyway. Be sure to tinker with both the settings and advanced settings areas, by default the changes are sharp but you can make them fade instead. Fixed the problems I had at least.
https://play.google.com/store/apps/details?id=com.nnevod.loggraph
I have the same problem with my Nexus 5.
Additionally, since day one, I've noticed that the phone consistently auto adjusts the screen to be slightly brighter than necessary given the ambient light.
I just noticed this issue last night, or at least it's similar. I was reading in bed for a few hours and occasionally (maybe every 15 minutes) the screen would suddenly dim to about half brightness and then brighten back to where it was originally. It was driving me nutz. I've also had a few random reboots, though not while I was using it. I'd notice it on my table booting up. FYI, this is stock with the latest update, no root or unlocking, and still has plenty of free space in memory. I've only had it for about 4 days.