Related
This is a two part question. What screen brightness do you usually leave your phone at? I leave mine on what seems to be 0 (see next paragraph for explanation) and my screen still always uses around 60-70% of my battery. I don't understand how it can use that much without the backlight on.
Next question - When adjusting the screen brightness and the slider is all the way to the left is that 0? I'm asking because every widget out there when set to 0 is a a few times brighter than when I manually move the slider all the way to the left. Also, after using a widget to toggle to 0 and I check in the display settings, the slider isn't all the way to the left.
So I'm wondering what is true 0? What the widgets set it to or with the slider all the way to the left? Could the slider being all the way to the left actually be hurting my battery life?
No zero on the slider is technically not zero. You can confirm this checking your brightness sysfs file. You have to decompile framework and adjust some numbers. We can take it down to true zero or slightly above which would be much dimmer.
I did this for the atrix. Im surprised it hasnt been done yet for the nexus.
I know it is not actually 0 because if it was I wouldn't be able to see anything on the screen.
Is there anyone that has insight on my questions though?
I dont understand your question. Zero is not true zero unless we mod the framework. So your backlight is not "off". I dont know why youre getting so much drain.
But we should mod this anyway. Use root explorer and go to sys/devices/omapdss/display0/a6e8aa0 and open the brightnesd file. Note that value with your slider at zero and you will see a reading of 30 (0-255). So we can lower that down to maybe 5-10 and zero on the slider will be much dimmer = battery saving.
I have a similar problem. The max brightness is piercing and the min brightness is just a tiny bit too dim.
I have tried used root explorer to change the maximum brightness from 255 to 100 hoping that the slider may be more granular after. For some reason however I cannot update the max brightness file. I have ensured that it is r/w mounted and tried changing the permissions too. It says that the changes have been made and the original backed up. When I reopen the file it hasn't changed.
BTW, my 'brightness' file is at 10 when placed at the minimum brightness.
Try the newest AOKP.
Brightness controls.
I actually have NEVER used auto brightness...even back in my OG days.
And my X days.
Even when custom auto-brightness options were around I ignored them.
I'd simply keep it at around %20 of the default lowest value.
BUT...this is slightly annoying when you step into the sun and can't see anything.
With the newest AOKP you can even set the amount of brightness changes.
I set up four values.
I've mine set up for a pitch black room to lowest.
Average room to my previous 20%ish.
Bright (sunny) to 100/255
SUPER sunny to 240/255.
I didn't notice any added drain today.
But this was my first test.
I think this feature was actually kanged from CM9, but I'm not certain.
So far I have resisted the temptation to get flash happy and I am on stock 4.0.2 but rooted. Do I have any options without changing ROM?
aidanbree said:
I have a similar problem. The max brightness is piercing and the min brightness is just a tiny bit too dim.
I have tried used root explorer to change the maximum brightness from 255 to 100 hoping that the slider may be more granular after. For some reason however I cannot update the max brightness file. I have ensured that it is r/w mounted and tried changing the permissions too. It says that the changes have been made and the original backed up. When I reopen the file it hasn't changed.
BTW, my 'brightness' file is at 10 when placed at the minimum brightness.
Click to expand...
Click to collapse
We cant change that brightness file with root explorer, even mounted, unless we mod the driver first. It will likely just revert right back to its previous value.
However it is possible i bet to edit the driver. Would be a cool project. You could also try to echo your desired value in terminal. ie echo 255 > brightness. But you prob will get the same result as using root explorer.
Maybe ill look at the driver with my limited skills heh. Or the alternative is to mod the framework which is def possible to fix this, and easier. We did exactly this on the atrix. And the sgs2 had it done too.
Edit: i think i found the code for your granular request. Check lines 30 or so.
https://github.com/ogdobber/android...0/include/linux/platform_data/panel-s6e8aa0.h
Still would be easier to do in framework instead.
Hello Guys!!
Have anybody missed AUTO BRIGHTNESS feature in SIII MINI because lack of Ambient Light Sensor,
If yes, the don't worry. I have an easy solution for Auto Brightness, Yes you can use Auto Brightness on Galaxy SIII MiNi:victory:
NO ROOT REQUIRED
Download and install These two app from following links:-
Lux Auto Brightness
Tasker
After Installing these apps follow these steps:-
Lux Auto Brightness:-
Go to Lux settings
Tap on Sample Collection
Tap on Select light reading source
Select Camera
Then get back to main settings menu
Tap on Mopdify linked samples
Tap on Luma TAB
Tap on ADD, set brightness (yello bar) to 4% Luma value to 1 and press ADD
Add 3 more links with these values= 35%-70|100%-80|50%-120|
Exit Lux
Tasker:
Open Tasker, tap on Plus Gign(+) on main screen
Tap on Event
Select Display in Event Category
Select Display On in Display Event
A blank screen will appear, do nothing just press BACK Button
TAP on New Task +
Enter Name to task or just tap on tick
A blank screen will Appear, tap on Plus Sign (+)
Select Plugin from action category
Select Lux Plug-in
Tap on Edit Button
Scroll Down and Tick in front of Refresh Backlight brightness? Under Force
Press Done, then press back and back again
Exit Tasker
Thats all work to do, now your dvice have Auto Brightness feature:silly:
To test, just press power button and lock the screen and then cover front camera with finger and press power button again, screen will Light up wait 1-2 seconds, Screen brightness will reduce, remove finger, lock unlock screen and brightness will resume to normal.
I have tested this for full day on my L9 and got no any battery drainage.
You can modify Linked Samples Values to your comfort zone for batter sample values you can also search other XDA forums.
Guys try it and let me know how you feel
if you got any issue please post, I'll try to solve it (Coz m also new to TASKER & LUX so may be it will take little bit time to Solve:fingers-crossed
EDIT: You can uncheck "Presistent notification" in general settings of Lux Auto Brightness, If you think it is draining your phone's battery. This will also disable the annoying Lux icon from notification.
HIT THANKS IF I DESERVE IT
why tasker?
gdjindal said:
Hello Guys!!
Have anybody missed AUTO BRIGHTNESS feature in SIII MINI because lack of Ambient Light Sensor,
If yes, the don't worry. I have an easy solution for Auto Brightness, Yes you can use Auto Brightness on Galaxy SIII MiNi:victory:
NO ROOT REQUIRED
Download and install These two app from following links:-
Lux Auto Brightness
Tasker
After Installing these apps follow these steps:-
Lux Auto Brightness:-
Go to Lux settings
Tap on Sample Collection
Tap on Select light reading source
Select Camera
Then get back to main settings menu
Tap on Mopdify linked samples
Tap on Luma TAB
Tap on ADD, set brightness (yello bar) to 4% Luma value to 1 and press ADD
Add 3 more links with these values= 35%-70|100%-80|50%-120|
Exit Lux
Tasker:
Open Tasker, tap on Plus Gign(+) on main screen
Tap on Event
Select Display in Event Category
Select Display On in Display Event
A blank screen will appear, do nothing just press BACK Button
TAP on New Task +
Enter Name to task or just tap on tick
A blank screen will Appear, tap on Plus Sign (+)
Select Plugin from action category
Select Lux Plug-in
Tap on Edit Button
Scroll Down and Tick in front of Refresh Backlight brightness? Under Force
Press Done, then press back and back again
Exit Tasker
Thats all work to do, now your dvice have Auto Brightness feature:silly:
To test, just press power button and lock the screen and then cover front camera with finger and press power button again, screen will Light up wait 1-2 seconds, Screen brightness will reduce, remove finger, lock unlock screen and brightness will resume to normal.
I have tested this for full day on my L9 and got no any battery drainage.
You can modify Linked Samples Values to your comfort zone for batter sample values you can also search other XDA forums.
Guys try it and let me know how you feel
if you got any issue please post, I'll try to solve it (Coz m also new to TASKER & LUX so may be it will take little bit time to Solve:fingers-crossed
EDIT: You can uncheck "Presistent notification" in general settings of Lux Auto Brightness, If you think it is draining your phone's battery. This will also disable the annoying Lux icon from notification.
HIT THANKS IF I DESERVE IT
Click to expand...
Click to collapse
hello friend
i could not get the point of installing the Tasker additionally.
i am using only Lux and it is enough i think.
so whats the reason of tasker here?? thamx..
scaliskano said:
hello friend
i could not get the point of installing the Tasker additionally.
i am using only Lux and it is enough i think.
so whats the reason of tasker here?? thamx..
Click to expand...
Click to collapse
Hello scalikano,
Good Question .
i am using tasker coz if we use only lux, then it will run periodically in background for light reading. running lux periodically will drain battery and one more reason for using tasker is sometimes androids default task killing system kills lux service, so than lux will stop working until you restart it, tasker helps to keep it alive, so when ever you turn your phones display on tasker and lux will adjust screen brightness to its best....:highfive:
thanx for the update ..friend.
it is a good solution.
i dont have that problem battery draining or task killer issue.
i use lux on wake-up mode (lux only works when u unlock ur screen) n ignore lux in the task killer..thats another solution..thanx
scaliskano said:
thanx for the update ..friend.
it is a good solution.
i dont have that problem battery draining or task killer issue.
i use lux on wake-up mode (lux only works when u unlock ur screen) n ignore lux in the task killer..thats another solution..thanx
Click to expand...
Click to collapse
+1 same here. Though, I'm trying to understand how to use Lux properly, I mean: in a sunny day, outside, I need the brightness at 80%/100%, else I can't see anything on screen. At night time, viceversa, low brightness.
Now: I can set these low/top values, but, what can I do for average Luma values? Am I clear?
first adjust lux on-wake mode with settings wizard in setup.
then go to sample collection select camera and front camera and check ''ignore 0 lux settings''
in general setting, offscreen button backlight should be ON.
fade brightness changes checked,
jitter control checked
manual call brightness checked
persistent notification checked
and widget opens dashboard checked.
now put lux widget on your homescreen.when u click on widget lux dashboard will be open.
in the middle of the dashboard u will see a circle with yellow line to link brightness value to luma value
just press link button to fix ur brightness to that luma value.
it means according to changing environmental brightness u can adjust the brightness value by dragging line forward or back and make a link that luma value and after several times of linking it automatically comes to that brightness u had linked before.
so, no need to add one by one the values in luma.
i use lux like this way.
it is so simple.just link some values e.g. in the room at night light, in the noon outside,
sorry for my bad english i tried to explain in detailed as can as i do.
TY, I'll try your settings! :highfive:
EDIT: why Offscreen button backlight ON? I mean, it keeps softkeys always on, while, to save battery, I always keep them disabled.. uhm?
scaliskano said:
first adjust lux on-wake mode with settings wizard in setup.
then go to sample collection select camera and front camera and check ''ignore 0 lux settings''
in general setting, offscreen button backlight should be ON.
fade brightness changes checked,
jitter control checked
manual call brightness checked
persistent notification checked
and widget opens dashboard checked.
now put lux widget on your homescreen.when u click on widget lux dashboard will be open.
in the middle of the dashboard u will see a circle with yellow line to link brightness value to luma value
just press link button to fix ur brightness to that luma value.
it means according to changing environmental brightness u can adjust the brightness value by dragging line forward or back and make a link that luma value and after several times of linking it automatically comes to that brightness u had linked before.
so, no need to add one by one the values in luma.
i use lux like this way.
it is so simple.just link some values e.g. in the room at night light, in the noon outside,
sorry for my bad english i tried to explain in detailed as can as i do.
Click to expand...
Click to collapse
no it does not mean sofkeys always on.
it means when u are on lockscreen lux will work after u press menu button when on slide or pattern or other lockscreen mode.
otherwise after locking ur screen, brightness will not be increased by lux if u dont check that option and u are not able to see pattern to unlock under sun light.
scaliskano said:
no it does not mean sofkeys always on.
it means when u are on lockscreen lux will work after u press menu button when on slide or pattern or other lockscreen mode.
otherwise after locking ur screen, brightness will not be increased by lux if u dont check that option and u are not able to see pattern to unlock under sun light.
Click to expand...
Click to collapse
Okay, I see, but, actually, if I enable it, it keeps softkeys on, or that happens only to me? That's why I disabled it.
in phone /settings /lockscreen/ adjust it to 6 seconds...no problem.
softkeys will be turned off after 6 seconds and it will not effect lux working
scaliskano said:
in phone /settings /lockscreen/ adjust it to 6 seconds...no problem.
softkeys will be turned off after 6 seconds and it will not effect lux working
Click to expand...
Click to collapse
I've adjusted it to 5 sec (no way to set it at 6 -- ?), yet, softkeys would not switch off, and stay on all the time.. what do I do wrong?
sorry for mistake way...
settings-display-more settings-touch key light duration..6 seconds is there but i just gave it as an example.it does not matter u can turn it ''always off''
---------- Post added at 11:32 PM ---------- Previous post was at 11:29 PM ----------
u can try different ways..lux will work on lockscreen mode if selected in lux settings.
no worry..just play with ur phone.
scaliskano said:
sorry for mistake way...
settings-display-more settings-touch key light duration..6 seconds is there but i just gave it as an example.it does not matter u can turn it ''always off''
---------- Post added at 11:32 PM ---------- Previous post was at 11:29 PM ----------
u can try different ways..lux will work on lockscreen mode if selected in lux settings.
no worry..just play with ur phone.
Click to expand...
Click to collapse
Thank you, pal
Deleted
itsfozzy said:
deleted
Click to expand...
Click to collapse
As you said.. give it a go! I downloaded it for my gt-I8190, it uses front camera as light sensor, it works, I like it.
If so, follow scaliskano's steps. :good:
In the paid version of lux you can use the front camera as a lightsensor. Works like a charm for me. There's a thread dedicated on this subject. Don't have it at hand, just search for it.
Sent from my GT-I8190 using Tapatalk 4 Beta
Hi,
I just installed the ROM OpenSEMC-U CM 10.1 RC2 on my Sony Xperia S and it seems to be working just fine except for one little thing :
The led bar for the buttons lights up every time I touch the screen whereas it only lit up when hitting the buttons on the offical ROMs.
I already searched the forum and some advised to look for an xposed module that would do this.
I didn't find any.
Do you have a solution ?
I you only have a few information on how it's handled in the system, I could try to build the xposed module myself but I don't know where to find the part of the system handling this functionnality.
I would have posted this in the right development forum but I don't have the rights because I juste created my accout...
Thanks.
Regards.
Up !
Does anyone have an idea ?
Thanks.
I've come across some posts about the sys files controlling the leds :
I've seen you can change the lightning behaviour by changing values affected to the virtual files /sys/class/leds/button-backlight/ ...
The problem is that there are several values I can change and I couldn't find any documentation. For example, I wonder if the file trigger cannot be set to a value for which it only lights up when the buttons are touched and not every time the screen is touched.
Regards.
nrdev said:
I've come across some posts about the sys files controlling the leds :
I've seen you can change the lightning behaviour by changing values affected to the .
The problem is that there are several values I can change and I couldn't find any documentation. For example, I wonder if the file trigger cannot be set to a value for which it only lights up when the buttons are touched and not every time the screen is touched.
Regards.
Click to expand...
Click to collapse
i have been facing a problem,i have installed "OpenSEMC-mr2-alpha2"
when i control my brightness the illumination bar light remain full
but in stock ROM when i reduce my brightness the intensity of that illumination bar light also decreases .
it is very annoying if you are doing something in night with low brightness and the illumination bar light is full.
please help
and how to get over these
virtual files /sys/class/leds/button-backlight/ ..
any app use to explore or in cmd prompt
deepanshunamdeo said:
i have been facing a problem,i have installed "OpenSEMC-mr2-alpha2"
when i control my brightness the illumination bar light remain full
but in stock ROM when i reduce my brightness the intensity of that illumination bar light also decreases .
it is very annoying if you are doing something in night with low brightness and the illumination bar light is full.
please help
and how to get over these
virtual files /sys/class/leds/button-backlight/ ..
any app use to explore or in cmd prompt
Click to expand...
Click to collapse
If we can figure out which parameter to change, we can then write into thoses virtual files in the hw-config script file, which sets the parameters right on startup.
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: