[TUT][GUIDE] [lower roms adaptive brightness level to match kernel brightness level! - Xperia Z Themes and Apps

okay guys, here i'll explain how to reduce adaptive brightness (minimum) to match manual brightness (minimal) when using a kernel that supports lower minimum brightness than stock. (in this case, Zombie Kernel for Xperia Z, which is, as far as i know at the moment of writing, the only kernel for xperia z which supports this)
Disclaimer:
Im not responsible for anything that might happen to you or your phone or anything else when following these instructions.
Reguirements:
-PC with Java installed
-Notepad++ installed (recommended)
-Advanced ApkTool
-a phone (obviously) running a kernel that supports lower brightness than stock
-some basic knowlegde
1. first of all, make a nandroid backup in case something goes wrong!
2. copy your framework-res.apk and SemcGenericUxpRes.apk from /system/framework/ and from /system/framework/SemcGenericUxpRes/ and copy it to the root of your internal sd.
3. now plug in your phone to pc and move the files into the 2-in folder inside the advancedapktool folder on your pc.
4a. run advanced apktool and install frameworks (option 1).
4b. run option 2 (decompile files) and select the framework-res.apk.
5. you should now have a framework-res.apk folder in the 3-out folder in the root of the advancedapktool folder, open it and navigate to advancedapktool/3-out/framework-res.apk/res/values/
you should see something like this
now open integers.xml in notepad++ and search for the following lines:
<integer name="config_screenBrightnessDim">20</integer>
<integer name="config_screenBrightnessDark">20</integer>
change the ''20'' in to ''6'' (6 is a little bit brighter than kernel minimum, but 5 is too dark and makes the screen flickering)
so it looks like this
6. then you can recompile using option 3 in advancedapktool and option 2 in the next menu where it asks you to sign the apk. hit y and wait till its done.
7. copy the newly created framework-res.apk file found in the 4-done folder to the root of your internal sdcard.
8. using file manager, move the file to tmp/ folder and set correct permissions (rw-r-r aka 644)
9. then move the file to /system/framework/ and hit overwrite. (some apps like rootbrowser will create framework-res -copy.apk so i like to use ''file manager'' instead)
10. reboot and enjoy!
NOTE: you can also add brightness steps to the framework, they are in the arrays.xml file.
that will only add more diffferent steps to the brightness and will not reduce any brightness at all.
so, its an optional step if you like go a bit further!
the lines to look for look like this
also note, that values may differ from rom to rom and kernel to kernel and device to device. fine-tuning may be needed but this write-up defines what applied to my specific case.
Credits:
 @BDFreak for the advanced apktool which prevents bootloop after decompiling/compiling.
 @Tommy-Geenexus for this awesome, fast and lean kernel which supports low backlight brightness
 @chiragkrishna for his guide which i used as a start guide dates from 2012 so pretty old but thanks to him i knew where to look for.
i am not a developer nor i have experience in theming or building apps or roms etc, and this decompiling was new for me too so i learned a bit and was fun. (was pretty simple though)
regards

Good stuff. I don't mind that 6 is brighter, the minimum brightness on zombie is too dark for me except on pitch blackness
Sent from my C6603 using Tapatalk

CosmicDan said:
Good stuff. I don't mind that 6 is brighter, the minimum brightness on zombie is too dark for me except on pitch blackness
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
So, do you use this also now?

langeveld024 said:
So, do you use this also now?
Click to expand...
Click to collapse
Not yet, today I will do my heatsink mod with before/after heat tests and photos and such, then ill mod the framework
Sent from my C6603 using Tapatalk

Hey mate, I decided not to use this as I tried out "Velis Auto Brightness" on Play Store (free) and it works really well, very customisable and easy to tune replacement for adaptive brightness. Downside is that it is obviously an extra service running in background, and if you want to manually adjust brightness then you have to use its own notification slider (firmware brightness slider is literally hijacked and has no effect).
I'm also running Dirty Unicorns 9.5 firmware at the moment rather than stock, which means I'm not even on Zombie anymore. Battery life and performance is impressive.
Sent from my Xperia Z using Tapatalk

CosmicDan said:
Hey mate, I decided not to use this as I tried out "Velis Auto Brightness" on Play Store (free) and it works really well, very customisable and easy to tune replacement for adaptive brightness. Downside is that it is obviously an extra service running in background, and if you want to manually adjust brightness then you have to use its own notification slider (firmware brightness slider is literally hijacked and has no effect).
I'm also running Dirty Unicorns 9.5 firmware at the moment rather than stock, which means I'm not even on Zombie anymore. Battery life and performance is impressive.
Sent from my Xperia Z using Tapatalk
Click to expand...
Click to collapse
Okay cool bro, I've already read that in zombie threat lol
Anyway if u need the framework-res.apk, I made if for existenz rom so if anyone is interested I can put it online :thumbup:

Related

Lower Auto-Brightness Settings for DEODEXED FROYO / GINGERBREAD Sense ROMs

Hi all,
I'm a LeeDroid HD user, and I've spent some time over the last few weeks tweaking the auto-brightness settings to maximise battery life. I've reached a point where I haven't found any problems with my settings for 4 or 5 days now, which I think is a pretty good test. It's on the low side under most light conditions, but I've tried to find a point where I can comfortably read the screen without holding it up to my face, and when outside, this includes wearing sunglasses.
Obviously screen brightness is a very personal thing, so you might not like where I've ended up. When you want to impress your friends with your awesome DHD, you can always override the auto setting and just crank up the brightness control manually
Sharing my settings is also not simple either, since it requires a mod to res-framework.apk, which is used for themes. So ... what I will do is show you a graph of my changes to so you can see what I'm doing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Left side of graph is a dark room, right side is the harsh West Australian sun)​
And make a flashable zip available for Lee's default ROM, with no themes installed (Base_LeeDroid_Lower_Auto_Brightness_Patch).
And another flashable zip to use if you've installed the "LeeDrOiD Notification power widget" from the LeeDroid HD OP (LeeDroid-PNW-Lower_Auto_Brightness_Patch).
And I've already had a request to make one for the "Stock 1.84" theme from here, so that's also attached (Stock_1.84-Lower_Auto_Brightness_Patch).
If you have another theme/mod installed, I think that flashing the above will wreck it ... be warned!
If you have a specific theme/mod you're using and want to try my settings, just send me a link to it and I'll cook up a flashable zip for it ... it doesn't take long. Alternatively if you know what you're doing, I can provide my arrays.xml file and you can do it yourself.
ALL files in this post are to be flashed with cwm 2.5.1.3 ... I haven't tested with any other version.
Even though I've tested all these patches myself, I'm not an expert at this, so PLEASE PLEASE PLEASE take a nandroid backup first in case I've done something fundamentally wrong.
If you don't like my settings, you can either restore your nandroid backup, or if it was a theme specific patch, you could just apply the theme again.
If it all goes pear-shaped ... I TAKE NO RESPONSIBILITY!
Hope somebody (other than myself) can benefit from my experimenting
If any themers want to incorporate my settings, it's just a change to arrays.xml inside framework-res.apk, nothing else. I'll also attach my arrays.xml (zipped), feel free to use it. As a courtesy, please credit me for the auto-brightness settings If you use them.
As mentioned above, if anyone would like to patch this on top of a specific theme/ROM you have already flashed, just ask and I can cook it up. If you feel like making it easier for me, all I need is framework-res.apk, so if you have a link to just download that, you'll get your patch quicker than if I have to download the entire theme
If anyone has arrived here from the LeeDroid thread, be aware that these are NEW versions of the files, as the ones in that thread were based on the wrong version (they were too low in the 40-90-160 range).
Cheers all, any feedback is appreciated
I have since put together a DIY guide on how to mod the auto-brightness settings inside framework-res.apk yourself. Thanks to those who contributed. Here's the guide!
This was all done on myWindows XP SP3 machine.
1. Download and install a recent Java Runtime Environment (JRE), if you don't already have one. I won't go through those steps, google it. If you're unsure, you can always come back to this step later if it's not working.
2. Download APK Manager from here: http://forum.xda-developers.com/showthread.php?t=695701 ... there's probably lots of good info in this thread if you have questions later about this tool.
3. Unzip the file wherever you want, mine is just on my desktop.
4. I was advised to replace the version of apktool.exe in the 'other' folder with an earlier version. I don't know if this is necessary, and I don't know what version I now have ... possibly 1.3. ** Multiple people have needed to downgrade to the older apktool.exe that I use, so I have attached it to this post. Just extract apktool.exe from the zip and place it in the 'other' folder, replacing the existing apktool.exe.
5. OK, now you should be ready to go! Grab your framework-res.apk either from your phone, or straight from the ROM you've flashed if you haven't applied any themes. framework-res.apk can be found in /system/framework.
6. Copy your framework-res.apk into the "place-apk-here-for-modding" folder.
7. Run script.bat. If you see a text menu pop up then all is good. If you get an error then you've done something wrong! Probably related to your JRE.
8. Choose Option 9 - Decompile apk. Wait until it finishes. Minimise this window now, we'll come back to it later.
9. Go into your projects folder, and you will have a new folder there called framework-res.apk, double click it.
10. Navigate to res/values
11. Open up arrays.xml in a text editor such as Notepad++. Using Windows built in notepad app could cause issues due to Windows -> Linux compatibility issues.
12. Scroll down to the section where it says "<integer-array name="config_autoBrightnessLevels">". This is the section that defines the steps of the ambient light sensor. You probably won't need to adjust these values for now.
13. The next section down should be "<integer-array name="config_autoBrightnessLcdBacklightValues">", this is where the tweaks really begin. The values here relate directly to how bright the screen is at the steps defined in the section above. Minimum value is 1, maximum value seems to be 249, but that could be incorrect. Would make more sense for it to be 255.
14. Change these values as you wish, but change them to the same thing in all these 3 sections - config_autoBrightnessLcdBacklightValues, config_autoBrightnessLcdBacklightValuesUp, config_autoBrightnessLcdBacklightValuesDown.
15. The next 2 sections - config_autoBrightnessButtonBacklightValues, and config_autoBrightnessKeyboardBacklightValues do the same thing, except for the hardware buttons, and keyboard buttons (if present) respectively. Adjust these if you wish.
16. Save the file.
17. Navigate back to the root of the APK Manager directory.
18. Return to your APK Manager window.
19. Choose option 11 - compile APK.
20. When prompted if this is a system APK, type y. Hit Enter.
21. When prompted if you want to copy additional files, type n. Hit Enter.
22. Choose option 22 - Set Current Project
23. Choose option 2 - unsignedframework-res.apk
24. Choose Option 5 - Zipalign apk
25. Choose Option 24 - Quit. On my script version you have to choose option 24 twice. I assume it's a bug on my version, hopefully you won't have to do the same thing.
26. Congrats! You now have a modded framework-res.apk!! You'll find it in the folder "place-apk-here-for-modding", with the new name "unsignedframework-res.apk". Copy it somewhere else (eg. desktop) and rename it to framework-res.apk.
*** If you know how to copy the modded file into a pre-existing flasheable zip, then by all means go for it. If not, continue following the steps below to create a flashable zip in the UOT Kitchen ***
27. Go to the UOT Kitchen - http://uot.dakra.lt/kitchen/ Hopefully it's not busy and it lets you in! If not, you'll have to wait.
28. Go to the file upload tab and upload your new framework-res.apk file.
29. If this is a FROYO ROM that you're modding, then that's it! If it's a GINGERBREAD ROM, then you also have to grab SystemUI.apk and com.htc.resources.apk from your ROM or phone and upload these also. SystemUI.apk can be found in /system/app and com.htc.resources.apk can be found in /system/framework
30. Go back to the Summary tab, then click "Submit Work to Kitchen".
31. When it's done, download the file, boot into cwm, ***DO A NANDROID BACKUP***, then flash your file!
If you've done it right, you're auto-brightness settings should be applied!
If you get stuck in a boot loop, or it just doesn't boot at all ... lucky you have a nandroid backup!
Please note that as this thread progresses, newer versions of the files get posted which makes these ones in the OP redundant. I'll leave them up for now just in case someone needs them, but in general, you'll want to dig deeper into the thread to get flashable files for newer versions of ROMS.
Excellent post.
I will take a look at your final arrays.xml, but I'm happy (so far) with the one I've cooked up with modified at the dimmer end of the scale.
Over the next day or so, I'm going to try and add extra steps (double) into the array, making a more linear or at least a smoother curve. As you said in Lee's thread, not sure if it's up to the build of the kernel.
Even if I can successfully add the extra values and flash, maybe I won't notice if its really working and the values are applied or they are just ignored by the ROM or kernel? What's the worst that can happen? Backup...........
Using the GPS Status & Lux Meter I was able to double check the phone light sensor invrements in:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
UpInTheAir said:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Click to expand...
Click to collapse
That looks right to me, I've not noticed any others in my testing
UpInTheAir said:
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Click to expand...
Click to collapse
Yep, I believe that's right. New drivers would need to be compiled into the kernel, and then the array modified accordingly. This is still something I'm not 100% sure on though, since their could also be a hardware limitation here.
UpInTheAir said:
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
Click to expand...
Click to collapse
The way it works is, if the light sensor returns a value of 10 (which is < 21), then it returns the first value of the array. If it's 40 ( 40 > 21 and 40 < 42) then it'll use the 2nd value ... and so on. that's why there's one extra value in the backlight values arrays than there is in the brightness level arrays, because it's the in betweens, plus less than the first value, plus greater than the last value.
Does that answer your question? Or did I mis-understand?
Thanks for the reply. Confirmed what I had thought.
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system. I run W7, so that's no an option right now. It still is a little beyond my scope of knowledge, but I'm learning bit by bit and also a lot of reading what others have said and researching Mr. Google.
Another useful app is Sensor List, which can graph the changes in lx, but the values are the same as above.
Looks like I'll be keeping this PC when I eventually upgrade so I can run Linux on it to play around...........
UpInTheAir said:
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system.
Click to expand...
Click to collapse
No need to de-compile it dude ... Lee publishes his kernel source code on github!
https://github.com/LeeDroid-/htc-kernel-ace
As for making changes and then re-compiling it ... I have no idea either
Thanks, will check it out and see if I can find out anything useful.
I don't really want to bother Lee as he's either quite busy or having some well deserved time 'off' before the official GB release.
It's not that big a deal to me (as you said, could be hardware limitation, so no chance anyway), but more of having a play, seeing where things are and what happens and why.
Hi mate,
Sorry, I'm late...
Great thread.
Just few questions:
The value I got (have ever seen) in my GPS status are: 10-40-90-160-220(5)?-640-10240
I have not seen these readings: 320, 1280 and 2600.
So, do I need to download and flash arrays.xml.zip first?
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
I had a thorough test on the one slopppy posted for me in LeeDrOid's thread. I works great except when the reading is at 40. At 40, the brightness is lowered to minimum. I know this as the button light has lit up. (My phone got 40-90-160 under fluorescent light, so if brightness is lowered to minimum at 40, it means it goes too low [for me].) Apart from this, everything works fine.
Sitting in the car under the sun, the brightness works well. Screen is readable even with sunglasses on. Walking out from the car, under direct sunlight, brightness still works fine.
Like what I said before, may be we should not be too particular about how it works under the sun as it maybe too bright an environment for our eyes to notice the difference.
So bro slopppy, what should I do now if I want to try them out now?
Regards!
So, do I need to download and flash arrays.xml.zip first?
Click to expand...
Click to collapse
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid but no themes/battery mods etc on top of it
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid and then installed the "Notification Power Widget" from the OP of the LeeDroid HD thread.
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
Click to expand...
Click to collapse
Yep, this is the one you should flash mate
works great except when the reading is at 40. At 40, the brightness is lowered to minimum.
Click to expand...
Click to collapse
I think that 40 isn't a value I come across in my daily life! haha ... I've only ever seen it when I mess around with the sensor to try and make it hit different readings. Couldn't hurt to up it a little I guess.
So bro slopppy, what should I do now if I want to try them out now?
Click to expand...
Click to collapse
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
slopppy said:
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
...
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
Click to expand...
Click to collapse
Thanks mate. Will do a thorough test again for this.
Value 40 is when I'm sitting at the corner and the phone facing away (opposite) the light. My eyes did not notice any much difference in brightness but my phone's sensor did.
Thanks more for the last sentence of your previous post... (maybe push it up a little to 8%-10%? frankly, me too not sure whether it will suit me more... my suggestion, 40 - 8-10%, 90 - 10-12% and 160 - 12-15%)
Edit: Oh, luckily I'm patient enough to wait for your reply this time...lol
Quick feedback for indoor test:
My personal opinion:
at 40, the brightness is a lowered to minimum and button light turn on, hence, a little too low.
at 90, didn't notice any difference in brightness. However, the button light turned off. So there must be an increment but not noticeable to my eyes. Still too low. (the one posted for me in LeeDrOid thread doesn't have this issue)
at 160, a little (really little only) too bright. Few percent reduction is better.
Will again update my feedback for outdoor test.
Regards!
HoneyHD Theme.
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
What about Kalagas theme...i would be very appriciate
Is this for Froyo only because i can't find arrays.xml inside GB framework-res.apk
Yes, sloppy should be a bit more specific, but in his defence, he does mention in the first post cwm recovery 2.5.1.3,...... relative only to LeeDrOiD Froyo.
Sent from my Desire HD using XDA App
Yep, good point, sorry about that. It's for Froyo SENSE ROMs only.
Anyone know how I can modify the title of the thread??
I'll get on to the requests now.
Cheers,
hamurabi1 said:
What about Kalagas theme...i would be very appriciate
Click to expand...
Click to collapse
Which version of Kalagas theme are you running? There seems to be a zillion of them
kennykenneth said:
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
Click to expand...
Click to collapse
Hi,
The framework-res.apk from Honey HD doesn't want to play ball. It gets a couple of errors when I decompile it, then totally flips out when I try to recompile it. It's an intense theme ... maybe he's doing some things which are incompatible with the way I'm going about my changes.
You could always see if the developer is nice enough to cook you up a version using my arrays.xml from the OP. He has other changes in his arrays.xml as well, so he would have to make sure he just uses the auto-brightness section.
Sorry mate!
slopppy said:
Which version of Kalagas theme are you running? There seems to be a zillion of them
Click to expand...
Click to collapse
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].
Thank you!
hamurabi1 said:
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].!
Click to expand...
Click to collapse
Here you mate
As stated in the OP, please do a nandroid backup first ... better safe than sorry ...

[GUIDE][FIX] Nvidia PRISM/smartdimmer - fix screen washout after watching videos

THE PROBLEM
To save battery while playing video Tegra intelligently decreases the backlight while increasing color brightness and contrast. Because it monitors on a frame by frame basis the changes are often unnoticable. You basically end up with the same displayed image using less backlight.
Unfortunately it seems to get stuck even after you leave the video and the changes are very noticeable as the changes were specific to the video frame you just left and not your homescreen.
This also may be the cause of some ghosting issues and for some it seems to eliminate any ghosting problems for them.
MANUAL FIX
(will reset at each reboot)
In terminal -
(You may need to type "su" and press enter before entering these commands)
To turn it off
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
To change how aggressive it is (untested)
echo "#" > /sys/devices/tegradc.0/smartdimmer/aggressiveness
Note: battery life while watching videos WILL decrease if you turn it off or decrease the aggresiveness
AUTOMATIC FIX
Trickster Mod
- has the ability to disable PRISM and set it to disable on boot.
N7scripts.rar
- A collection of scripts compiled by hamdir which, in conjunction with Script Manager (available in the market) will allow you to toggle smartdimmer/PRISM on and off at will.
- You can also use script manager to toggle it at boot if you want.
- Also includes a script to disable 3D scaling which may improve 3D gaming performance (untested)
Thanks to hamdir for his pack of scripts and for convincing me to make a new post for these fixes.
I may use this for other sysfs tweaks... mine for now.
Thanks. Easier to save and flash then manually entering in these values each time I crackflash.
If the T3 can increase the color saturation and gamma while decreasing backlight, wonder if we can increase the colors while leaving the backlight alone. All of the N7s I've played with have a dull washed out look with a warm tone for whites.
Sent from my Nexus 7 using xda premium
does flashing the .zip just delete the PRISM file? cuz when I manually enter the command after flashing it via CWM it doesn't allow me to any more.
"
ROM may flash stock recovery on boot? Fix?
No
.
.
.
.
.
Yes - Disable Recovery flash
.
.
.
+++ Go back +++
which reboots if you "go back" what is this?
-------------------------------------------------------------------------
How do you set up the script? I have script manager and the Scrip.rar saved onto my SD card. Thanks in advance!
player911 said:
Thanks. Easier to save and flash then manually entering in these values each time I crackflash.
If the T3 can increase the color saturation and gamma while decreasing backlight, wonder if we can increase the colors while leaving the backlight alone. All of the N7s I've played with have a dull washed out look with a warm tone for whites.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Messing with the kernel I haven't had any luck. You could ask Morfic. He might be able to make something happen.
Also prism increase color BRIGHTNESS for the most part (you said saturation). That's why the homescreen ends up looking washed out and bright and not oversaturated when PRISM fails to shut off.
Sent from my Nexus 7 using xda premium
sharp2G said:
does flashing the .zip just delete the PRISM file? cuz when I manually enter the command after flashing it via CWM it doesn't allow me to any more.
"
ROM may flash stock recovery on boot? Fix?
No
.
.
.
.
.
Yes - Disable Recovery flash
.
.
.
+++ Go back +++
which reboots if you "go back" what is this?
-------------------------------------------------------------------------
How do you set up the script? I have script manager and the Scrip.rar saved onto my SD card. Thanks in advance!
Click to expand...
Click to collapse
There's no prism file. These tweaks are changing a sysfs value. There's no file. The flashable zip adds an init.d file that runs the manual command at every boot.
In your case CWM is complaining about a file that flashes stock recovery on boot and overwrites CWM. These are completely different things. Let CWM "disable recovery flash" and you'll be good to go.
Sent from my Nexus 7 using xda premium
This is awesome. It definitely needs to be implemented in a ton of ROMs
so does flashing this decrease battery life when watching videos? im confused by op..
awesome post, thx!
yes this fix, completely get rid of the grey levels washout issues!!! and greatly improves the quality of the display, it will cost some battery life, but any boost to this average screen is welcome
now about ghosting it did reduce it a lot but sadly it didn't kill it, i still get the very random occasion of faint LCD ghosting
finally we really need to find out a way to fix the stupid low saturation, in particularly the greens are very low
google....these screen issues, lack of tablet UI and launcher rotation issues, makes want to smash it through the wall
Nice find. Hopefully Google/Nvidia/Asus will fix this in an update.
Thank you very much for this! While I don't own a Nexus 7, I *do* own an Asus TF700T and this problem also exists on it. On the TF700, this "mode" is active all of the time, no matter what you are doing and it is *very* noticeable and distracting, especially when watching videos (but it *is* noticeable everywhere else as well).
Disabling this "Feature" makes the problem go away. At the very least, you can enable/disable as needed now.
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
ever since i disabled this gamma destroying feature and my screen keeps getting better and better
starting to fall in love with it really
Riquelme10 said:
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
Click to expand...
Click to collapse
you didn't even enter the command line properly...
Sent from my Nexus 7
sharp2G said:
you didn't even enter the command line properly...
Sent from my Nexus 7
Click to expand...
Click to collapse
Care to post how it should be done then? Might be a little bit more helpful
Also, does this affect battery life overall? Or just while watching movies?
Riquelme10 said:
Hello from Germany,
my Nexus is unlocked and rooted
Terminal:
su
cd /sys/devices/tegradc.0/smartdimmer
./enable
"Permission denied"
change user rights:
chmod 744 enable
(old settings are 644)
./enable
./enable[1]: 1: not found
so where is my fault?
Click to expand...
Click to collapse
You do not "run" the "enable" file. You need to do this:
echo "0" > /sys/devices/tegradc.0/smartdimmer/enable
or
echo "0" > enable (if you are already in that dir).
That will disable the SMartDimmer "feature". Echoing a "1" will re-enable it. I have not noticed any battery life difference....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
espionage724 said:
Care to post how it should be done then? Might be a little bit more helpful
Also, does this affect battery life overall? Or just while watching movies?
Click to expand...
Click to collapse
yes its an LCD battery saving feature and so disabling it will definitely reduce battery life
choose between battery life or quality display
hamdir said:
yes its an LCD battery saving feature and so disabling it will definitely reduce battery life
choose between battery life or quality display
Click to expand...
Click to collapse
Yes as said in the OP smart dimmer analyzes the video frames and determines whether it can lower the backlight while increasing the color brightness and maintain almost the same image. Lower backlight = better battery life.
Sent from my Nexus 7 using xda premium
After I turned off the dimmer, the screen got a little brighter, so I manually turned down my normal 40% brightness to 30% brightness. So in the end I don't think I'm losing any battery life at all.
Ravynmagi said:
After I turned off the dimmer, the screen got a little brighter, so I manually turned down my normal 40% brightness to 30% brightness. So in the end I don't think I'm losing any battery life at all.
Click to expand...
Click to collapse
I agree - I think any battery life reduction will be *very* minor for most people... I certainly haven't noticed any difference...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

[MOD] Lower auto brightness v2.1

Lower auto brightness
After being disappointed by many apps, I did some research and found a nice guide to change each value of the native auto brightness.
As it took me some time to install what's needed, to manage to make the change and to find new values, I decided to share it for the laziest of you
This mod will changes the values on arrays.xml from
Code:
83
83
83
83
116
142
170
198
227
255
to
Code:
20
25
25
30
43
60
80
120
165
205
for the respective light sensor values
Code:
11
41
91
161
226
321
641
1281
2601
As you can see, I put some really lower values to make the greatest improvement in battery life.
If you are a little geek inside, I still recommend you to personalize the values yourself following chiragkrishna's guide.
Installation :
It only work for Project X v4.1 or Sabsa Prime v8.0 or v8.5
Download the zip for your rom and flash it via recovery
Download :
You can find the current version, older versions and changelog at
http://www.mediafire.com/?7aag2a70uuak6
Future improvements :
Different values to make it the most battery friendly without the screen being too dark ( your feedback will be helpful to adjust these new values )
I can make it for other roms if someone wants it.
Thank's
chiragkrishna for the original guide
alirez_sos and nikhil007mmus for their awesome roms
Lux Auto Brightness for making easier to find the brightness values.
As English is not my first language, there are probably many mistakes in my post. Please feel free to report them ( pm would be better ).
isn't there some way to adjust these values on the fly? as in from the phone itself?
You can do that with an app. I don't think it's possible to edit from the phone because the framework-res.apk has to be decoded and extracted in order to edit the values. I've never heard of a tool that can do that from the phone.
Sent from my HTC Incredible S using xda app-developers app
why app also? Android is linux-based, i should be able to edit some values in a file, restart some service and it should apply
But you have to decompile the apk, pretty sure you can't do it on the device
You can change the auto brightness values on the fly with viper vivo #justsayin
Sent from ViperVIVO
Switch between different framework-res which has each different values will surely be possible but again, each one will have to be prepared from a computer. Or if there is a way to decompile an apk from your phone, it will probably be too complicated to make that when you need it.
Seems like there's nothing you can't do with venom viper
Sent from my HTC Incredible S using xda app-developers app
farhadtarapore said:
isn't there some way to adjust these values on the fly? as in from the phone itself?
Click to expand...
Click to collapse
Changing these values on the fly is possible. ROM like AOKP has this feature built in its settings where you can define values on your own. But with Sense ROM, one needs to modify smali codes which is much complicated. But ROM like Virtuous Infinity has done it and you can select from a list of preset values from its Tweaks.
question
can we use it on sabsa prime 6.5 ???
danialnab said:
can we use it on sabsa prime 6.5 ???
Click to expand...
Click to collapse
Probably not, the apks used are likely to be different. But you could always try
danialnab said:
can we use it on sabsa prime 6.5 ???
Click to expand...
Click to collapse
A brief report: This thing works, better than i thought.
And Danialnab, this patch will not work on any other roms. it totally replace the framework apk witch was modified from the project X 4.1.
New version
v2.0 out!
Still only for ProjectX 4.1.
From last version : increased values for high light and decreased values for low light.
You can now find all versions on this mediafire folder : http://www.mediafire.com/?7aag2a70uuak6
v2.0 is very suitable for everyday indoor use. For outdoor (high light), it is little too dark.
I really like your mod, it saves a lot of battery usage when turn on the auto brightness.
botonic said:
v2.0 is very suitable for everyday indoor use. For outdoor (high light), it is little too dark.
I really like your mod, it saves a lot of battery usage when turn on the auto brightness.
Click to expand...
Click to collapse
It's most of the time fine outdoor as long as you have high contrast like black text on white background but I also find it too dark to watch pictures or things like that. For this purpose I keep an auto-brightness switch in quick settings so I can rapidly put a higher brightness when needed.
I can update the projectx version tonight to 2.1 which has a brighter brightest value
Sent from my vivo using xda app-developers app
pec0ra said:
It's most of the time fine outdoor as long as you have high contrast like black text on white background but I also find it too dark to watch pictures or things like that. For this purpose I keep an auto-brightness switch in quick settings so I can rapidly put a higher brightness when needed.
I can update the projectx version tonight to 2.1 which has a brighter brightest value
Sent from my vivo using xda app-developers app
Click to expand...
Click to collapse
That's a good idea. Thanks a lot for your great mod and suggestion. :good:
This tool is very good. I haven't tested on a bright sunny day, but so far it works well to adapt to most indoor/cloudy situations.
Sent from my HTC Incredible S using xda app-developers app
is there a way to uninstall this.
jonahmt21 said:
is there a way to uninstall this.
Click to expand...
Click to collapse
Yes, you just need to flash the "restore_default_values" zip for the version of your rom. You can find it in the same folder as the install zip
Thanks pec0ra for posting this thread and the link to the guide in the OP and thanks to chiragkrishna for the great guide.
I hope it's ok but I been using one of your zip files as the base for making my own auto-brightness mod, it works well and I'm still tweaking the final values I want.
I have changed array to the value below. I think it is best setting for all outdoor and indoor usage to me. Thank you very much pec0ra for your good mod.
Code:
20
20
25
33
43
60
100
165
200
228
I'm finally getting the brightness levels close to what I want.
I've ended up adjusting the sensor auto brightness levels as well as the LCD backlight values.
I noticed that there is 9 sensor levels but 10 backlight values, is there any reason why there is an extra value under the LCD backlight levels?

rooted can i lower brightness lower

the lowest brightness setting is still quite bright would like to decrease it more if possible and not too difficult
doitinthedirt said:
the lowest brightness setting is still quite bright would like to decrease it more if possible and not too difficult
Click to expand...
Click to collapse
1. Download and install Xposed Framework
2. Download and install GravityBox[KK] via Xposed (or if you're still on JellyBean then choose GravityBox[JB])
---a. Apply the GravityBox module and reboot
3. Open GravityBox and click on Display Tweaks (6th option down), then select "Brightness Settings".
4. Turn the switch to "On" and move the slider for "Minimum Brightness Level" down to 1.
5. Reboot to apply the changes.
Autobrightness won't take advantage of these changes but manual brightness will go very very dim now.
This worked for me so I hope this helps!
If you run into errors just quote this post and tell me what went wrong and I'll do my best to try to troubleshoot with you.
thank you are all of them available in the Play Store or do I get that stuff from somewhere else
doitinthedirt said:
thank you are all of them available in the Play Store or do I get that stuff from somewhere else
Click to expand...
Click to collapse
Sideload Xposed via the APK download:
http://repo.xposed.info/module/de.robv.android.xposed.installer
And GravityBox is installed through the Xposed installer, so after you install Xposed, open Xposed and select "Framework" then click "Install/Update" then reboot. Once the phone reboots go back into Xposed and select "Download". Find "GravityBox[KK]" and swipe from right to left to get to "Versions". From there select Download on the latest version (3.2.1 at the moment). Back out to the main screen of Xposed and select "Modules". Put a check in the box for GravityBox and then reboot. Now open GravityBox and continue with the steps to lower the brightness.
Lux will do it also. In the play store
There is an option in Xposed/Gravity Box KK/ Statusbar tweeks..to press on statusbar, slide left or right to control brightness..seems most simple, convenient way for me..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Check out "display brightness " on play store. Doesn't make it go dimmer than stock minimum.... But puts a highly customizable always on top slider on the screen. Anywhere around the edges and any size or color. A great way to manually control brightness and save some juice.
https://play.google.com/store/apps/details?id=com.googlecode.eyesfree.shades I downloaded this from the Play Store works very well a lot dimmer than the stock lowest setting takes it to completely black. saves on the battery
edit not sure it saves batt... may be just shading the brightness? will have to look into changing settings and see ifbatt gets better
I use Lux and its perfect for me. Make sure to disable the built in auto brightness if you use it. It has day and night profiles. I have my night profile set at -40% for 0lx and my day set to -10% for 0lx. I use dynamic mode but other modes work well too and use less sensor time.
search for a screen filter on google play.

Reduce minimum brightness

Hello, some one please guide me so i can reduce the min brightness in lollipop, even the lowest is too bright and hurts my eyes at night,
I want to change settings in the rom and dont want to use apps
Take a look at this thread: http://forum.xda-developers.com/showthread.php?t=2893061 is for KK but I think is almost the same for LP
DorianX said:
Take a look at this thread: http://forum.xda-developers.com/showthread.php?t=2893061 is for KK but I think is almost the same for LP
Click to expand...
Click to collapse
Thabks, i tried it already and searched all what i could get from google, still nothing works and most mods need custum kernel or patching service jar which is a bit of a head ache of steps
If i could mod build prop or a sys file
My other phones where already dim at low or i could mod their brightness throu build prop or lcd min value but none is possible on this phone
Gamer4Life said:
Hello, some one please guide me so i can reduce the min brightness in lollipop, even the lowest is too bright and hurts my eyes at night,
I want to change settings in the rom and dont want to use apps
Click to expand...
Click to collapse
#!/system/bin/sh
#night mode
echo 1 > /sys/class/leds/wled:backlight/max_current
Can be used as script or via terminal emulator
If you need more brightness change value after echo
My value>
1 for lowest
3 for normal
25 for max
Yenkazu said:
#!/system/bin/sh
#night mode
echo 1 > /sys/class/leds/wled:backlight/max_current
Can be used as script or via terminal emulator
If you need more brightness change value after echo
My value>
1 for lowest
3 for normal
25 for max
Click to expand...
Click to collapse
Explain little more please?
Okay, fir now i lowered the max current, now the display is really nice and dim how just how i like it
But max brightness is very low now, only if i could only changr thr min value
You can use apktool to decompile framework-res.apk and change the lcd backlight related numbers in /res/values/ files. The lowest setting that I can still see my screen was 2. The lowest manual setting changes but the adaptive brightness doesn't go to the new minimum. But sometimes the framework-res.apk doesn't rebuild properly and you need to restore with recovery and ADB.
Gamer4Life said:
Okay, fir now i lowered the max current, now the display is really nice and dim how just how i like it
But max brightness is very low now, only if i could only changr thr min value
Click to expand...
Click to collapse
Just change value to 25
But you need change this value every time each reboot.
Not a permanent, but a handy solution :3
For me, I made 3 script as widget (in small app), so I can change brightness value as I like.
Yenkazu said:
Just change value to 25
But you need change this value every time each reboot.
Not a permanent, but a handy solution :3
For me, I made 3 script as widget (in small app), so I can change brightness value as I like.
Click to expand...
Click to collapse
I will be grateful if you share with us how to make these shortcuts in small app menu.
Also which setting do you use for night?
For me i tried 3 and i like it. My eyes are very sensitive to light and will make them dry and bit sore

Categories

Resources