sorry for the double post!!!
Hi all,
Is there any way to adjust the gamma of the screen for this device? It's too low for video playback using any of the usual players. Screen brightness on full. Black's still crushed.
Rehue and vitalplayer allow software brightness increase but neither are very smooth and it's still not as good as the correct gamma.
I saw one post on here about editing mdnie but couldn't figure it out, also tried ironmaster rom with stweaks, which usually allows gamma correction , but not it seems with this device. The whole 'screen' tab is missing in stweaks.
Any clues anyone? It's frustrating, the screen looks superb for anything other than video playback.
Related
I find the dimmest screen toggle still too bright. I find it embarrassing to use in dark public spaces.
Is there a way to dim the screen even more?
Download the screen filter app from the play store. Literally puts a filter effect on the screen to make it appear darker making it much easier to use in the dark.
Yes its possible to take the screen much lower, but we have to edit the framework. Nobody had done this mod yet for some reason.
CM9 has the ability to change the screen lowest settings built in
B97 said:
Download the screen filter app from the play store. Literally puts a filter effect on the screen to make it appear darker making it much easier to use in the dark.
Click to expand...
Click to collapse
+1. I use Screen Filter also, it's uber handy for reading at night when the light seems too bright. If you've got hardkeys like I had on my Desire, you can even turn them off.
i wrote a tutorial on how you can mod the frameworks apk. it's very easy and you can change the brightness levels to anything you want. here's the thread
screen filter only puts a transparent layer on the screen and messes with the colors. modding the frameworks will lower default brightness to any level you want. you can raise it too if you like.
Thanks for all the ideas. I went with the easiest one, Screen Filter.
AOKP also has an option to reduce screen brightness...
dynamicpda said:
Thanks for all the ideas. I went with the easiest one, Screen Filter.
Click to expand...
Click to collapse
Good man!
Sent from my GT-I9100 using XDA
neotekz said:
i wrote a tutorial on how you can mod the frameworks apk. it's very easy and you can change the brightness levels to anything you want. here's the thread
screen filter only puts a transparent layer on the screen and messes with the colors. modding the frameworks will lower default brightness to any level you want. you can raise it too if you like.
Click to expand...
Click to collapse
Great work, I've been wondering why nobody did this mod yet for the nexus. I made that same mod on my atrix, using the sgs2 thread as well. But I've been too lazy to do it for nexus.
The above mod is the best option. Screen filter doesn't achieve the same results. The above mod reduces power draw as well when on the lower brightness setting of 5 or so. Screen filter just hides the higher brightness but has same power draw.
RogerPodacter said:
Great work, I've been wondering why nobody did this mod yet for the nexus. I made that same mod on my atrix, using the sgs2 thread as well. But I've been too lazy to do it for nexus.
The above mod is the best option. Screen filter doesn't achieve the same results. The above mod reduces power draw as well when on the lower brightness setting of 5 or so. Screen filter just hides the higher brightness but has same power draw.
Click to expand...
Click to collapse
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.
fnf said:
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.
Click to expand...
Click to collapse
Agreed, GPU just isn't good enough. I hate the lag with the button glow animations on!
I use an app called root dim, it's really useful. Let's you use a brightness level of 1, which is really quite dim. Free, too.
Sent from my Galaxy Nexus using XDA App
Remoteconcern said:
Agreed, GPU just isn't good enough. I hate the lag with the button glow animations on!
I use an app called root dim, it's really useful. Let's you use a brightness level of 1, which is really quite dim. Free, too.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thanks for the tip, on the Galaxy Nexus it's possible to set the brightness to 0 by writing to /sys/class/backlight/*/brightness but the brightness is checked and reset to the minimum (default 10) every time the screen is turned on. I guess Root Dim works to the same effect so it runs as a system service. Still, it'd be an awesome addition for people who haven't bothered to mod.
fnf said:
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.
Click to expand...
Click to collapse
Screen filter may reduce power. But amoled screens save power with lower brightness. There is no difference between lcd vs led on this issue. And modifying the framework to bring min brightness down to 5 rather than 15 saves much more power than screen filter. Its no contest. This isn't different from lcd in this case.
---------- Post added at 03:20 PM ---------- Previous post was at 03:14 PM ----------
fnf said:
Thanks for the tip, on the Galaxy Nexus it's possible to set the brightness to 0 by writing to /sys/class/backlight/*/brightness but the brightness is checked and reset to the minimum (default 10) every time the screen is turned on. I guess Root Dim works to the same effect so it runs as a system service. Still, it'd be an awesome addition for people who haven't bothered to mod.
Click to expand...
Click to collapse
Yes we can write to that sysfs file, but it gets reset. The mod to the frameworks incorporates that backlight file so its now able to go down to 1, 2, 5, or whatever you want. It makes it now stock, so you are no longer capped at 10 (actually I think 15 is the cap I see). But that mod is just removing this cap and making it lower to whatever you want. Stock.
So no extra app is needed. No additional tweak. It now makes the stock brightness able to go down to 1 by itself whenever it needs.
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:
Hi...my problem is asa stated in the title... i tried in 2 video players (KMP & MX video players)...when adjusting the brightness within the app, nothing happens...but brightness can be adjusted via the status bar...does anyone have an idea what is wrong?
Hi all,
Is there any way to adjust the gamma of the screen for this device? It's too low for video playback using any of the usual players. Screen brightness on full. Black's still crushed.
Rehue and vitalplayer allow software brightness increase but neither are very smooth and it's still not as good as the correct gamma.
I saw one post on here about editing mdnie but couldn't figure it out, also tried ironmaster rom with stweaks, which usually allows gamma correction , but not it seems with this device. The whole 'screen' tab is missing in stweaks.
Any clues anyone? It's frustrating, the screen looks superb for anything other than video playback.
MY issue with the stock Rom, which has been bugging me for a while is that when I reduce the brightness to the minimum, the Contrast changes, or something of the sorts, this really annoys me and I would like to disable it. Can someone help me out? I really don't want to flash a custom ROM.
I think that's normal because of AMOLED display, I also noticed it on CM14.1
This is simply the way this particular screen works, can't be fixed with software.
You can only avoid it by not reducing brightness as much. According to "Lux" the color shift starts under 4% brightness.
Sent from my OnePlus 3 using Tapatalk
But why does the min brightness in mxplayer not have this issue?
Zeryth said:
But why does the min brightness in mxplayer not have this issue?
Click to expand...
Click to collapse
Because mx player doesn't set the brightness as low as you can set it manually using the brightness slider.
Select menu - display - settings - screen - untick "brightness". Now you can set your brightness manually to even lower using the brightness slider.
Other apps seem to work similarly (for example an third party brightness widget)... Not setting it to minimum... Like they don't recognize the "real" minimum brightness - which is lower. I don't have this "issue" on my tablet. Haven't looked much into it though.