Related
Do xperia arc and arc S, have light sensor? If they do, why isn't there any option "auto brightnes" in Display settings? Is there any mod to enable "auto brightness"?
Sorry if any similar theme already exists, but I can't find search button (no kiding, dead serious)
SEK610i said:
Do xperia arc and arc S, have light sensor? If they do, why isn't there any option "auto brightnes" in Display settings? Is there any mod to enable "auto brightness"?
Sorry if any similar theme already exists, but I can't find search button (no kiding, dead serious)
Click to expand...
Click to collapse
It has a light sensor and its auto-brightness works very well.But the firmware does not provide its control option.
If you use a power widget style app (Extended Controls for example) you can choose auto brightness.
I notice my screen changing brightness depending on situation (and if I cover the sensor with my thumb).
You can changes the auto-brightness settings with different apps if you have root. I personally like the stock setting.
Greetz
Looks like XDA people have already made an app for this exact purpose!
(You need root)
https://play.google.com/store/apps/details?id=com.hatcyl.android.Disable_Auto_Brightness
I searched and found no info on dimming the camera's LED. I want to be able to use as a flashlight, but I don't want it so darn bright.
Still looking at different apps on the Play Store, but I think it would have to be some kind of hack for rooted phones, which I haven't done yet.
Any one have any ideas?
whipps said:
I searched and found no info on dimming the camera's LED. I want to be able to use as a flashlight, but I don't want it so darn bright.
Still looking at different apps on the Play Store, but I think it would have to be some kind of hack for rooted phones, which I haven't done yet.
Any one have any ideas?
Click to expand...
Click to collapse
I don't think it's possible. When you use it as a flashlight android apps have a setting called "torch" and that's it. There is no modification for adjusting brightness. Also, I looked in the /sys/class/leds/ directory for the camera led to be able to enter your own value for the brightness file, but nothing exists in there for the camera light. I personally like the bright led for a flashlight. If I don't want something super bright, I use a screen flashlight that just displays a white screen and boosts brightness to Max. I personally use a red screen though.
Sent from my SGH-T999 using Tapatalk 2
The tricky aspect of what you are talking about doing here is that the Linux kernel is your entire power management for the device. There might be a a root flashlight somewhere in the market that could accomplish this for you, otherwise it would take some adjusting at the kernel level... which again is your power control for hardware
Thank you guys for the help and info. It's not the end of the world if I can't do this, but now I know what to keep my eye out for.
The kernel is the key to over clock and under volt, so I understand that the kernel would have to support that.
Main concept is keyboard and bln backlight dont turn on to save battery. I have 2 solution both has own limitations.
I use cm10.1, but it should work with others. This is my first android mod, be sure you backup .
1st solution Liblight
Strengths
Key click timeout, turn off when you dont hit any key
Working with lcd brightness
Keyboard light and BLN light too
Weaknesses
It wont work with high birghtness
No customization ( you can only change light value for lcd birghtness)
install
Better backup /system/lib/hw/lights.n1.so
Simply install from recovery.
changelog
1.1 This version prevents to turn on button's light ( keyboard and navigation keys) when high light, it couldnt handle light changes.
disable hardware buttons light too
when power on, sensors always says 0, so wait 2x 1.1sec and power down lights, when need.
2.0, [17/06/2013] This version use normal lcd brightness, and it changes keyboard and navigation keys light with lcd. When lcd brights it turns off keyboard lights.
redesigned. I use lcd brightness idea from QWERTYled.apk
2nd solution Userspace
Strengths
Easy customization
You can use only apk.
Weaknesses
Not BLN support
No key click timeout
install
Install latest apk, optimal install keyboard-light-remove.zip from recovery.
Start app, and start sevice.
changelog
1.30+bubor1.0
credits
nonamerzz (queryled source)
Daniel Hillenbrand, Tanguy Pruvot, Adam77Root ( original liblight )
Cool beans man!
Sent from my cool and awesome SGH-I927 (Samsung Captivate Glide) using xda app-developers app! Awesome!
How does this work with the keyboard patch that ties the keyboard lights to the capacitive buttons on the screen? Are you using this with that mod? If so would it do the same to the capacitive buttons?
Sent from my SGH-i927 using xda premium
try this
jevan24 said:
How does this work with the keyboard patch that ties the keyboard lights to the capacitive buttons on the screen? Are you using this with that mod? If so would it do the same to the capacitive buttons?
Sent from my SGH-i927 using xda premium
Click to expand...
Click to collapse
Try this, I did the same with hardware buttons. Test BLN too.
I installed this on Liquid Chrome and seems to have shut off the key lights when not in use... Don't see any problems yet?
PeACe
Sent from my i927 TGG Liquid Smooth
I've found Nonamerzz's project. He made a userspace service to control keyboard light. ( http://forum.xda-developers.com/showthread.php?t=2032962 )
He sent me the source code, I've change files, but I'm testing other liblight at the moment, so feel free to try it.
You need to install apk and remove liblight keyboard control, you can found both attachment.
Hello.
Could You add setting of ambient light sensor to 2.0 version? I'm using automatic brighiness and lowered it to 0% in low and medium lights. Keyboard backlight is really needed for me only if ambient light is below 100 lux according to automatic brightness regulator, but I'm using 0% of backlight for all ambient light below 3000 lux, and so 2.0 version keeps lights on even if I can see keys w/o it (in medium light conditions).
Thank You.
S-trace said:
Hello.
Could You add setting of ambient light sensor to 2.0 version? I'm using automatic brighiness and lowered it to 0% in low and medium lights. Keyboard backlight is really needed for me only if ambient light is below 100 lux according to automatic brightness regulator, but I'm using 0% of backlight for all ambient light below 3000 lux, and so 2.0 version keeps lights on even if I can see keys w/o it (in medium light conditions).
Thank You.
Click to expand...
Click to collapse
I dont think I could make it in liblight. Please try qwertyled, I've updated APK.
new qwertyled
Just made some modification in qwertyled:
Settings where you can define the sensor value when to turn light.
[updated 9th July 2013 : Add delay, so keyboard not blinking when you use subway ]
bubor said:
Just made some modification in qwertyled:
Settings where you can define the sensor value when to turn light.
[updated 9th July 2013 : Add delay, so keyboard not blinking when you use subway ]
Click to expand...
Click to collapse
i use it in rootbox rom and now keyboard ligths works:laugh: now i can test other roms:good:
Is it possible to fix the broken landscape mode? If you open the keyboard it won't go back to portrait mode.
Also, thanks. The keyboard lights now work. Good job.
Sent from my SGH-I927 using XDA Premium 4 mobile app
LaizureBoy said:
Is it possible to fix the broken landscape mode? If you open the keyboard it won't go back to portrait mode.
Also, thanks. The keyboard lights now work. Good job.
Sent from my SGH-I927 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its nothing with light library.
QWERTYLED Works well on my OmniROM setup, but I don't care for the unremovable "Q" notification in the upper left. I am using the Xposed module NotifyClean to force-remove it, but I wish I could just turn it off and uninstall NotifyClean.
snarfies said:
QWERTYLED Works well on my OmniROM setup, but I don't care for the unremovable "Q" notification in the upper left. I am using the Xposed module NotifyClean to force-remove it, but I wish I could just turn it off and uninstall NotifyClean.
Click to expand...
Click to collapse
I've removed notification from this version: QWERTYLed-1.30+bubor1.0-notify.apk you can download from the first comment.
bug report^^
dear bubor,
seems this odd behaviour went unnoticed up to now.. when the screen is turned off while the keyboard is expanded, and the screen is turned on again, the keyboard is not lit until keyboard contracted and re-expanded.
Also, when screen is off, expanding the keyboard make the backlight turn on but not the screen - now when power button is pressed, screen turns on and keyboard backlight turns off :silly:
this is about the only problem I had so far, thx for coding it up.. maybe you want to put the source on github as well?
eMPee584 said:
dear bubor,
seems this odd behaviour went unnoticed up to now.. when the screen is turned off while the keyboard is expanded, and the screen is turned on again, the keyboard is not lit until keyboard contracted and re-expanded.
Also, when screen is off, expanding the keyboard make the backlight turn on but not the screen - now when power button is pressed, screen turns on and keyboard backlight turns off :silly:
this is about the only problem I had so far, thx for coding it up.. maybe you want to put the source on github as well?
Click to expand...
Click to collapse
apk or lib?
bubor said:
apk or lib?
Click to expand...
Click to collapse
qwertyled apk (1.30+bubor1.0)
btw is this the code you forked? https://github.com/nonamerz/QWERTYLed
could you put the modifications on your github?
eMPee584 said:
qwertyled apk (1.30+bubor1.0)
btw is this the code you forked? https://github.com/nonamerz/QWERTYLed
could you put the modifications on your github?
Click to expand...
Click to collapse
here you are : https://github.com/buborh/QWERTYLed
bubor said:
here you are : https://github.com/buborh/QWERTYLed
Click to expand...
Click to collapse
thx.. :good:
so basically no changes, just compile?
i have so no idea how to fix :cyclops:
Hi,
anyone experienced issues with brightness level on B112? i bought the phone used on ebay, and it came with this firmware
if the brightness is set at the middle, it looks like is set at minimum, and if i try to set it below middle, the screen goes totally black ( 0 visibility )...also if i set the screen on auto brightness, the second it is set, it goes blank screen ( the screen is working, just the brightness is so low you cannot see anything )
also, should i consider upgrading from B112 to a newer firmware? performance wise, i am very happy with B112, because comparing with B125 ( on my second ascend p6 ) it runs smoother, no lag in menu at all ( so far ). i also get in antutu 15200-15700 scores with B112.
any thoughts are welcome
Sacerdot said:
Hi,
anyone experienced issues with brightness level on B112? i bought the phone used on ebay, and it came with this firmware
if the brightness is set at the middle, it looks like is set at minimum, and if i try to set it below middle, the screen goes totally black ( 0 visibility )...also if i set the screen on auto brightness, the second it is set, it goes blank screen ( the screen is working, just the brightness is so low you cannot see anything )
also, should i consider upgrading from B112 to a newer firmware? performance wise, i am very happy with B112, because comparing with B125 ( on my second ascend p6 ) it runs smoother, no lag in menu at all ( so far ). i also get in antutu 15200-15700 scores with B112.
any thoughts are welcome
Click to expand...
Click to collapse
Hello,
Are you using the buttons at the pulldown menu or the phone settings menu to set the brightness ?
If it happens only when you are using the pulldown menu you can try the following (if you have a rooted phone) :
1.First of all, make a copy of build.prop and save it on your SD card !
2.Open build.prop (located in system folder in your device) with a root file explorer (like ES File Explorer on Google Play).
3.Look for this line "ro.config.disablesmbacklinght=true".
4.Replace "true" with "false".
5.Reboot the phone.
PS : You can save the changes in build.prop only if you mount your system like RW (see the ES File Explorer settings)
it happens all the time, doesn't matter how I get to screen brightness...it acts the same
Sacerdot said:
it happens all the time, doesn't matter how I get to screen brightness...it acts the same
Click to expand...
Click to collapse
Do you have the Smart Backlight option ON in the phone settings menu > Display ? Try to disable it !
It is possible that you have a preinstalled application like Screen Filter (by the last owner)? If yes, try to uninstall it !
Best regards,
vigitall said:
Do you have the Smart Backlight option ON in the phone settings menu > Display ? Try to disable it !
It is possible that you have a preinstalled application like Screen Filter (by the last owner)? If yes, try to uninstall it !
Best regards,
Click to expand...
Click to collapse
smart backlight is OFF
there is no app preinstalled, as i have factory reset the phone...no other funky app either
i was thinking maybe there is a system file that can be tweaked with, to edit a maximum and a minimum parameter for the brightness ...
Sacerdot said:
smart backlight is OFF
there is no app preinstalled, as i have factory reset the phone...no other funky app either
i was thinking maybe there is a system file that can be tweaked with, to edit a maximum and a minimum parameter for the brightness ...
Click to expand...
Click to collapse
You have the possibility to check if it is a software problem using Lux Dash application (do a search on Google Play).
"Lux is a third-party app that allows you to easily calibrate your phone’s brightness sensor".You could try it !
vigitall said:
You have the possibility to check if it is a software problem using Lux Dash application (do a search on Google Play).
"Lux is a third-party app that allows you to easily calibrate your phone’s brightness sensor".You could try it !
Click to expand...
Click to collapse
i tried Lux, and it works, but it does not have any calibrate function, it is a good alternative to default screen brightness tho...
I was hoping for a fix for the default ( built in ) screen brightness setup menu...anyway, this will do the trick for now
thanks
Hello Everyone,
I have a problem with my amami and I doubt I am the only one but for some reason people do hardly complain: the brightness even at lowest possible setting is still too bright.
I had this back when I had original FW and I am having the same issue with CM11 (latest nightlies). Using manual control or auto-brightness doesn't make much difference, i.e. in a totally dark room the ambient light sensor reports 0Lux and the screen is still too bright.
I found a workaround already (the ScreenFilter app that people recommend all over the internet) but it sucks because it heavily reduces the picture quality, i.e. visibly reduces contrast and especially the gray color resolution. And it also doesn't reduce power consumption like real brightness value change would do.
I looked around for possible solutions and there is a trick with writting a new value of current limit to Linux settings (some mA value between 0 and 20 to some max_current file in procfs). And this really helps but also impacts the maximum brightness, the screen is hardly ready in sun light with reduced current.
Is there a silver bullet? I am thinking about writing an app for that but it would require SU permissions and is kinda dirty to implement. Can anyone recommend a better solution?
have you tried the xposed Modul "minimum brightness" ?
Install Lux Brightness. from play store.
You can overboost it or make the screen so dark that you can't even see it.
Another great screen mod is Twilight which basically dims the screen red based on clock so it helps fall sleep faster when using phone before bed.
New Folder said:
Install Lux Brightness. from play store.
Click to expand...
Click to collapse
Yes, another vote for Lux. It lets you set brightness to negative levels, mine is usually around -50%. https://play.google.com/store/apps/details?id=com.vito.lux&hl=en
Vote for Lux here too.
Nothing comes close
camaro322hp said:
Yes, another vote for Lux. It lets you set brightness to negative levels, mine is usually around -50%. https://play.google.com/store/apps/details?id=com.vito.lux&hl=en
Click to expand...
Click to collapse
Thanks for the hint. I tried the Lite version and AFAICS it simply uses the same trick as ScreenFilter and other "sub-zero" regulators, putting an alpha overlay on top of the image stack.
You can identify this kludge easily by looking at the button areas, they don't get darker anymore. And you can see the black level not getting real black, i.e. the power consumption is not reduced.
However, Lux seems to be one of the better toys because of the plugin interface. Unfortunately there is no HW plugin for Sony devices but judging by the quick look at the Nexus-4 plugin (it's open source!!) it should be possible to adopt this method to Z1 as well. So, maybe when someone could eventually implement that.
xposed Modul "minimum brightness" works, i tested it for you. you can make the screen dim to complete black with your normal display brightness slider without grey or black overlay. it just sets down the minimum brightness level to 1 or 0 (default is 10 or 20), so it should also work with enabled auto brightness
chertVdetali said:
I looked around for possible solutions and there is a trick with writting a new value of current limit to Linux settings (some mA value between 0 and 20 to some max_current file in procfs). And this really helps but also impacts the maximum brightness, the screen is hardly ready in sun light with reduced current.
Click to expand...
Click to collapse
As far as i remember, /proc is only used to call upon information, not to set specific values. What you are looking for is placed within /sys.
To be precise in /sys/devices/leds-qpnp-ee125e00/leds/wled:backlight/. There you will find a file called max_current with which you can easily control the brightness and set it to a very low level. Note that this actually dims the screen and not just applies a filter like most apps do...
One drawback is that the value will change again after you restarted the device. I set up a little flow with Automate β that takes care of this for me. I find this solution a lot better than all the screen filter apps.
This is true for CyanogenMod 11 and GreatDevs Kernel. It might be different on Stock. I know that the path for my Nexus 7 is sys/class/leds/lcd-backlight.
I hope this helps you a little bit.
rob rich said:
xposed Modul "minimum brightness" works, i tested it for you. you can make the screen dim to complete black with your normal display brightness slider without grey or black overlay. it just sets down the minimum brightness level to 1 or 0 (default is 10 or 20), so it should also work with enabled auto brightness
Click to expand...
Click to collapse
I am wondering how you can claim that the result is complete black. Calling this black is like saying "TN monitors have good black values" (I know such people, they change their mind quickly when they see my Eizo with a VA panel at night).
No, seriously, the default was already 10 (see config.xml in cm11 repo) and the difference between 1 and 10 is hardly visible. It's still way too bright for work without eye strain in the darkness.
@Wooaarr: thanks, this is apparently the way to go, I just need to find time to configure it. And yes, of course, the file is in sysfs and not procfs (automated typing, when I grew up with Linux there was no sysfs out there ).
chertVdetali said:
I am wondering how you can claim that the result is complete black. Calling this black is like saying "TN monitors have good black values" (I know such people, they change their mind quickly when they see my Eizo with a VA panel at night).
No, seriously, the default was already 10 (see config.xml in cm11 repo) and the difference between 1 and 10 is hardly visible. It's still way too bright for work without eye strain in the darkness.
@Wooaarr: thanks, this is apparently the way to go, I just need to find time to configure it. And yes, of course, the file is in sysfs and not procfs (automated typing, when I grew up with Linux there was no sysfs out there ).
Click to expand...
Click to collapse
when i disable autobrightness and push the slider to the left my screen goes completely off, so you wanna say that screen off isnt black? funny
chertVdetali said:
Thanks for the hint. I tried the Lite version and AFAICS it simply uses the same trick as ScreenFilter and other "sub-zero" regulators, putting an alpha overlay on top of the image stack.
You can identify this kludge easily by looking at the button areas, they don't get darker anymore. And you can see the black level not getting real black, i.e. the power consumption is not reduced.
However, Lux seems to be one of the better toys because of the plugin interface. Unfortunately there is no HW plugin for Sony devices but judging by the quick look at the Nexus-4 plugin (it's open source!!) it should be possible to adopt this method to Z1 as well. So, maybe when someone could eventually implement that.
Click to expand...
Click to collapse
Interesting information, I did not know that. You are correct, the navigation buttons are brighter than the rest of the screen at negative values. I had noticed that before but didn't know why. Works well enough for me though.
rob rich said:
when i disable autobrightness and push the slider to the left my screen goes completely off, so you wanna say that screen off isnt black? funny
Click to expand...
Click to collapse
Well, you claim that it works for me because you tested it on your device. So... yeah, why not, I could say what you mentioned above just following the same logics. :silly: