Related
In this post I'd like to share a small bit of Android information with you. I've discovered it while looking around at the build.prop file and did some research on it, and it turns out to be a pretty cool and powerful feature. Of course, seeing as this requires root you can probably already guess that it involves some more-than-consumer level risk, so anything you do here is your responsibility. This is not a tweak for a fairly novice user. You will need some basic knowledge on command line terminal and how to copy/edit files. I will be assuming you know how to setup and run ADB, and how to execute it and work with it in command prompt.
What's this mod do? Basically it changes your resolution (not really, but for simplicity sake we'll say it does) to a higher pixel density. What this means is everything on your screen will look smaller as if you changed your resolution on your PC to a higher setting. Now obviously we don't want to increase this too much or it will make our screen look bad and be impossible to read things, so I recommend you stick with the settings I have and only tweak it if you're daring.
Now for setup:
1: You require root access for this to work, so make sure you have it prior to doing anything else.
2: Next you will need to get your build.prop file from the /system directory. An easy (and free) way to do this is to use Astro file manager. Open up Astro, navigate to /system/ and copy the build.prop file to the sdcard.
3: Hook the phone up to your PC and enter USB Mass Storage mode. Open the drive on your computer and copy the build.prop file to the desktop.
4: IMPORTANT: make a second copy of this file, and rename it to: build.prop.BAK - accept the change to filetype and leave it alone for now.
5: Open up build.prop using notepad. Once its open you'll see a whole ton of text assuming you have Word Wrap enabled. Press Control + F and type in "density" then press enter.
6: Close out the search menu and find the number "240" to the right of "density"
7: Change the number from 240 to 200. Save the file and close notepad. (Note - higher numbers means bigger text/objects, smaller numbers means smaller text/objects allowing you to fit more on the screen)
8: Put your phone back into PC Mode, and then enable USB Debugging in Settings->Applications->Development
9: At this point I assume you have ADB setup on your PC. Copy and paste the modified build.prop file into the folder with ADB, and then open up a command prompt, change directory to wherever you have ADB installed (ex: cd C:\adb\ ), and type in "adb devices" without the quotes to start ADB and make sure your device is configured properly
10: Now you must push the modified build.prop file to your sdcard. To do so type this in:
adb push build.prop /sdcard/build.prop
11: You should see the text indicating it successfully transferred the file. Now type in "adb shell" without quotes. You should see a $: appear. Once it does, type in "su" and it should change to a #: sign.
12: Now that you're in root access, you must mount /system as read/write to copy over the new build.prop file. To do so type this in exactly as it is, making sure to not skip any spaces or use wrong letters/characters:
mount -o remount,rw /dev/block/system /system
You should see the line repeated and that means it went ok. If you get anything else like an error, somethings not right with the text you entered. Go back and double check it.
13: Now we'll copy the file from the sdcard to the system directory to overwrite the old build.prop file:
cp /sdcard/build.prop /system/build.prop
Again, you should see the line repeat below to confirm it copied it successfully. You can now reboot the phone to make the changes happen (note: for a speedy reboot, simply type in "reboot" from the #: prompt, this will drop you out of root shell and do an automatic reboot of your phone pretty neat)
Once your phone is booted back up you should notice some pretty significant changes in appearance. Everything will look smaller much akin to the changes you see on your desktop PC when you increase the resolution from say 800x600 to 1600x1200. In case you want to change it back to the old look, simply re-trace your steps using the original build.prop file, with the pixel density set to 240 instead of 200.
Screenshots for comparison. Note how lines of text are fully exposed in the new screenshots compared to the old ones, where it has to scroll/cut off text in App names etc:
http://forum.androidcentral.com/motorola-x-roms-hacks/32035-how-resolution-tweak-req-root.html
Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/
I think that is pretty sweet bro!! Great finding
Sent from my PC36100 using Tapatalk
njfoses said:
Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/
Click to expand...
Click to collapse
Been using this for a few days now. It works great. They should have released the Evo with the higher resolution from the start.
Looks great in my opinion. I lowered just slightly to 220 and i used RootExplorer to just change the Build.prop file.
Shouldn't this be in general? This is like dpi in windows lol... not resolution
rawdikrik said:
Looks great in my opinion. I lowered just slightly to 220 and i used RootExplorer to just change the Build.prop file.
Click to expand...
Click to collapse
yeah, root explorer is fantastic. it even creates a backup for you after you edit the file.
The interesting part about this is, I made a thread about the density change back when the EVO first launched and nobody cared lol
Just changed to 200 with the aforementioned app, the only problem I have is the main status bar and most of the popup menus and stuff look like crap. Hoping we can find some higher resolution (or whatever) pieces to use. Might be because I'm using Manup's theme.
bdoople said:
Just changed to 200 with the aforementioned app, the only problem I have is the main status bar and most of the popup menus and stuff look like crap. Hoping we can find some higher resolution (or whatever) pieces to use. Might be because I'm using Manup's theme.
Click to expand...
Click to collapse
i noticed that too....so i just went to like 215. 200 was looking good though
ro.sf.LCD_Density=240
Is that the proper value to change in root explorer?
Right below it, there is another value of 160, that's why I ask. I'm on an Evo
Poor resolution has always bugged me. On such a big screen, that number of pixels really isn't enough. This will be a great mod, just don't wanna mess it up.
Thanks.
see there's an easier way to do everything, by that i mean there is an app for that, lol.
scottspa74 said:
ro.sf.LCD_Density=240
Is that the proper value to change in root explorer?
Right below it, there is another value of 160, that's why I ask. I'm on an Evo
Poor resolution has always bugged me. On such a big screen, that number of pixels really isn't enough. This will be a great mod, just don't wanna mess it up.
Thanks.
Click to expand...
Click to collapse
The line below it (With the value of 160) has a # in front of it as that is the default value if none specified. Change the 240 to 200 or 220 or 210 or 190 etc depending on your preferences. Again, appelflap has an awesome application to easily do this for you and it provides a boot monitor as well that will check to make sure you can see the screen, and if you can't it will revert back to default setting in case you mess something up. It costs approximately $1 and is well worth it.
On my evo I am using the app and I set mine to 180. Everything looks fine so far. I don't recommend using it with the sense launcher at this level though.
Sent from my PC36100 using XDA App
Appreciate all the feedback. When it comes to system tweaks like this, I've always preferred to do them manually. Makes it easier to keep track of changes, and, if you know what's goin on 'behind the scenes'. Even with winmo, I always would opt for tweaking via registry editor, rather than some blind, hands-off tweak app.
Thanks all, though.
Edit: ok, foot in mouth. So I opened root explorer, found build.prop, opened it clicked the mount R/O toggle, but can't seem to edit it no matter what. NVM, found editor
Also, I checked out the app on the market, looked at comments and saw lots of people say that density broke certain apps, and can't get back to normal, broken phones, blah blah blah
Anyone speak to this?
Exposes lame apps
Worked great on rooted EVO running CM6.2.
Need to increase the power of my bifocals now!
Also exposes lame apps that display set screen resolutions, such as WeatherChannel. Poopnoodles!
Very cool find, not one I will be keeping though. The taskbar icons get a bit blurry, and the widget/icon spacing looks ugly.
njfoses said:
Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/
Click to expand...
Click to collapse
Just tried that. Was able to make a few changes with no problems. As soon as I tried to go back to the stock settings my phone would no longer boot past the white EVO screen. Doing a restore now
And of course the restore isn't working properly for some reason. Argh.
yeah
Yeah, I read the thread by Appleflap, about his app, and it really sounds like there are a lot of issues from doing this (at this point), some of which cannot be recovered from. And at the very least, there are apps and icons that won't scale properly, and there's no fix for that but to find new ones (from the horses mouth).
Things to be worked out by some real sharp devs.
I'm not totally convinced that this makes things anything beyond just smaller. I've been testing this a various resolutions and am not sure it really adds any new pixels...aren't "pixels" more hardware related? If it were just a software thing wouldn't everyone do it?
Is there a way to change/increase resolution of tablet running the vegan 5.1?
I love the high resolution which comes with the gingerbread build?
Sent from my PC36100 using XDA App
Try LCD densitychanger from the market. Its free and doesnt survive a reboot, There is a paid version that will make it permanent. You can do a search of this forum and the instructions for changing it permanently manually are around.
rob_z11 said:
Is there a way to change/increase resolution of tablet running the vegan 5.1?
I love the high resolution which comes with the gingerbread build?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.
bittrix said:
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.
Click to expand...
Click to collapse
Thank you both for your help, and I think 120 is too small, and 140 did the trick for me which is the nice combination of the workspace and not too much strain on eyes.
I am sorry to report you Bittrix, but down in Florida temperature is gong to hit 60 and may be 68 tomorrow, so enjoy the cold weather in Canadian rockies
I use 120 for my tablet on all roms. I used 140 for awhile when starting to use lcd density, but eventually went to 120 because of app issues. 120 and 160 seem to nativly supported in android, and numbers in between its hit or miss as to whether they would work or not, even with compatibility turned on. (Some would only take up 3/4 of the screen instead of full or not open at all)
My build.prop does not have a line ro.sf.lcd_density=xxx and am running the latest Vegan build...
Any ideas?
EDIT: Added the line and no issues - just dont like it that small.. reverted back. Thanks
bittrix said:
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.
Click to expand...
Click to collapse
Moved to general
I think the this is pertinent to all Samsung ROMs, and I would like Devs to provide input on an aspect that affects the whole reason we buy the phone - in this case the Skyrocket.
This is about brightness/clarity changes that happen between ROMs. One MAIN reason that we buy the Samsung phones is the brilliance of the Super AMOLED screens. When custom ROMs are flashed, the screen brighness and clarity - yes, clarity which may itself be a psychological link to brightness - changes quite a bit.
Almost all ROMs do NOT mention if the dev ACTIVELY changed the brightness settings in framework-res. NO DISSIN ANYBODY here. So please this is not a negative. Or did the dev remove stock apks, files etc., that may or may not be linked to screen/display settings. I UNDERSTAND THAT THIS MAY BE DONE TO SAVE BATTERY. So no biggie there either.
ALSO, I know how to hack the brightness in framework-res, and also have apps that can do it for me.
It would be great if devs could indicate if brightness was hacked, because STOCK BRIGHTNESS/DISPLAY always looks so much more impressive. Much more impressive than any custom rom, BUT STOCK SUCKS otherwise. If it was not hacked then clearly settings are getting affected.
It would be really great if we could retain stock display quality in custom ROMs. Also, by indicating about brightness in Rom OP, this would give a heads up what to expect. Whether to hack myself, or use apk.
THANKS TO ALL DEVS, anyways for their super work that makes the phones so much better than manufacturer's want us to have !!
chappatti said:
I think the this is pertinent to all Samsung ROMs, and I would like Devs to provide input on an aspect that affects the whole reason we buy the phone - in this case the Skyrocket.
This is about brightness/clarity changes that happen between ROMs. One MAIN reason that we buy the Samsung phones is the brilliance of the Super AMOLED screens. When custom ROMs are flashed, the screen brighness and clarity - yes, clarity which may itself be a psychological link to brightness - changes quite a bit.
Almost all ROMs do NOT mention if the dev ACTIVELY changed the brightness settings in framework-res. NO DISSIN ANYBODY here. So please this is not a negative. Or did the dev remove stock apks, files etc., that may or may not be linked to screen/display settings. I UNDERSTAND THAT THIS MAY BE DONE TO SAVE BATTERY. So no biggie there either.
ALSO, I know how to hack the brightness in framework-res, and also have apps that can do it for me.
It would be great if devs could indicate if brightness was hacked, because STOCK BRIGHTNESS/DISPLAY always looks so much more impressive. Much more impressive than any custom rom, BUT STOCK SUCKS otherwise. If it was not hacked then clearly settings are getting affected.
It would be really great if we could retain stock display quality in custom ROMs. Also, by indicating about brightness in Rom OP, this would give a heads up what to expect. Whether to hack myself, or use apk.
THANKS TO ALL DEVS, anyways for their super work that makes the phones so much better than manufacturer's want us to have !!
Click to expand...
Click to collapse
how exactly do you hack the brightness? I'd love to play with this.
Sent from my SAMSUNG-SGH-I727 using xda premium
Shadeslayers said:
how exactly do you hack the brightness? I'd love to play with this.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Here are some spots to help you: I would try to make a tutorial but have not gotten arond to it since it is available in some places.
The first is very up-to-date:
http://forum.xda-developers.com/showthread.php?t=1377410
http://forum.xda-developers.com/showthread.php?t=1337722
This tutorial below is form a different forum posted originally by DRGilroy (at Team BAMF Forums). This particular post is not available and I have copied it from Google's cached version: BUT ALL CREDIT GOES TO DRGilroy:
[How To] Customize Auto Brightness
I've created my own Auto Brightness Mods for people to use and I thought I would help those out who are interested in creating their own.
I learned how to do it myself by searching and finding tutorials here and there in different posts and forums. Some of what I found was either not detailed enough or had incorrect instructions for the version of APK Manager I am using. So, most of what I'm going to do here is just reiterate what someone else has already written out there somewhere in the world wide web.
Tools:
APK-Manager v5.0.2 (versions earlier than 5.0 behave differently so instructions would be somewhat different if your attempting to use one of them)
Notead++
7-Zip
Instructions for Creating Your Own Custom Auto Brightness Levels:
Extract the file "framework-res.apk" from your favorite ROM. You can find it in /system/framework/
Copy the framework-res.apk file into the APK Manager directory "place-apk-here-for-modding"
Execute the Script.bat file in the root of the APK Manager directory
Type option "9" and press Enter to Decompile the framework-res.apk file
Leaving the Command Window open, with Notepad++ open the file "arrays.xml" found under "\projects\framework-res.apk\res\values"
Find and edit the following *values:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>94</item>
<item>94</item>
<item>94</item>
<item>94</item>
<item>143</item>
<item>143</item>
<item>171</item>
<item>199</item>
<item>227</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValuesUp">
<item>94</item>
<item>94</item>
<item>94</item>
<item>94</item>
<item>143</item>
<item>143</item>
<item>171</item>
<item>199</item>
<item>227</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValuesDown" >
<item>94</item>
<item>94</item>
<item>94</item>
<item>94</item>
<item>143</item>
<item>143</item>
<item>171</item>
<item>199</item>
<item>227</item>
<item>255</item>
Save your edits and close Notepad++
Reopen the Command Window and Type option "11", press Enter to Compile apk
When asked "Is this a system apk (y/n)" type "y" and press Enter
When asked "Aside from the signatures, would you like to copy... (y/n)" type "y" and press Enter
When prompted with "Press any key to continue . . .", Leaving the Command Window open, Navigate to the APK Manager directory "keep" and delete the file "resources.arsc"
Reopen the Command Window and now press any key to continue
Type option "22" and press Enter to Set current project
Select the newly compiled unsignedframework-res.apk file, it should be number 2, type "2" and press Enter
Take note of the "Current-App:" unsignedframework-res.apk should be shown on the upper right corner of the Command Window
Type option "5" and press Enter to Zipalign apk
At this point you can close the Command Window
Copy the file "unsignedframework-res.apk" from the APK Manager directory "place-apk-here-for-modding" and rename it to framework-res.apk
Congratulations, you now have a framework-res.apk that has your own custom Auto Brightness values!
Now what do you do with the framework-res.apk file?
There are a couple things you can do with the file.
You can use ADB to push your new framework-res.apk to the phone
You can create a flashable Zip using the UOT Kitchen website
You can use an existing flashable Zip that contains a framework-res.apk file and replace it with yours
I'll throw you a bone and you can use my flashable zip below, Yes, I'm just that nice!
bamf_forever_1.0.8_auto_brightness_1.0.zip
Brightness: 31, 31, 59, 87, 115, 143, 171, 199, 227, 255
MD5: A1360E982CE401E9302929D527BC3641
*Brightness Values Explained
The following numbers represent the light sensors steps for using brightness:
11, 41, 91, 161, 226, 321, 641, 1281, 2601
The following numbers are the stock values that I mod and they represent the level of brightness, lowest to highest in ten level steps:
94, 94, 94, 94, 143, 143, 171, 199, 227, 255
Example:
Light Sensor___Brightness
10---------------94
40---------------94
90---------------94
160--------------94
225--------------143
320--------------143
640--------------171
1280-------------199
2600-------------227
Higher------------255 = Max
You can use a free app on the Market called AndroSensor. It can provide you with the value of how much light the sensor is detecting.
In my testing, it appears to me that brightness values lower than 30 do not cause the backlight to dim any further. Also, when connected to a charger with battery charging, the light sensor doesn't go lower than 40 until the battery is fully charged, then it will lower to 10.
Then there is this http://forum.xda-developers.com/showpost.php?p=24437288&postcount=29
After all this there are free apps: I am using LogGraph.......
Good Luck !!
call me crazy but why bother. there are three options, I always just use dim to save battery, but occasionally ill go full bright when viewing a photo or something.
edgex said:
call me crazy but why bother. there are three options, I always just use dim to save battery, but occasionally ill go full bright when viewing a photo or something.
Click to expand...
Click to collapse
This phone has a great screen that clearly is the major selling point for it. Why ruin the screen under sub optimal conditions?
I am actually running mhx's full bloat stock ROM, and am loving the screen......... but I am restricted to this if I want the full visual experience. It is a little like buying HDTV for watching only 480p programming.
also automatic brightness when executed properly makes viewing under changing light conditions so much more smoother and pleasurable..
Well........that's just my opinion, not really complaining since a custom room is better than ATT cares to give us and I am thankful For that.
Is anyone else having issues with stock auto brightness? It's usually too dark until light is shining right on it, and then it is painfully bright. I am currently using Lux with manually linked samples to some degree of success.
Since I'm on my third Infinity due to build issues/defects, I'm wondering if this is something related.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
darkmuffin said:
Is anyone else having issues with stock auto brightness? It's usually too dark until light is shining right on it, and then it is painfully bright. I am currently using Lux with manually linked samples to some degree of success.
Since I'm on my third Infinity due to build issues/defects, I'm wondering if this is something related.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
I found a way to "tune" the auto-brightness (assuming you are rooted) - this has worked very well for me - hopefully it will be useful to you as well:
You'll want to edit the values in this file to tune the auto-brightness (in my case, it would always set brightness all of the way down when at home):
/system/etc/config/brightness/brightness_config_04.xml
There are separate config files for both with and without IPS+ enabled (I've only tuned the values with IPS+ disabled since I don't use IPS+ mode).
Here is my modified config file if you want to use these values as a starting point:
<?xml version="1.0" encoding="utf-8"?>
<!--
**
** Copyright 2009, The Android Open Source Project
**
** Licensed under the Apache License, Version 2.0 (the "License")
** you may not use this file except in compliance with the License.
** You may obtain a copy of the License at
**
** http://www.apache.org/licenses/LICENSE-2.0
**
** Unless required by applicable law or agreed to in writing, software
** distributed under the License is distributed on an "AS IS" BASIS,
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
** See the License for the specific language governing permissions and
** limitations under the License.
*/
-->
<brightnessconfig>
<!-- for auto brightness -->
<array name="autobrightness_SuperIpsOn">
<value>37</value>
<value>58</value>
<value>83</value>
<value>86</value>
<value>90</value>
<value>93</value>
<value>96</value>
<value>100</value>
<value>103</value>
<value>106</value>
<value>110</value>
<value>113</value>
<value>116</value>
<value>141</value>
<value>166</value>
<value>191</value>
<value>212</value>
<value>255</value>
</array>
<array name="autobrightness_SuperIpsOff">
<value>15</value>
<value>25</value>
<value>35</value>
<value>45</value>
<value>45</value>
<value>50</value>
<value>50</value>
<value>66</value>
<value>70</value>
<value>73</value>
<value>76</value>
<value>80</value>
<value>83</value>
<value>108</value>
<value>133</value>
<value>158</value>
<value>183</value>
<value>255</value>
</array>
<!-- for manual backlight -->
<item name="manual_backlight_SuperIpsOn_Max">255</item>
<item name="manual_backlight_SuperIpsOn_Min">37</item>
<item name="manual_backlight_SuperIpsOff_Max">161</item>
<item name="manual_backlight_SuperIpsOff_Min">5</item>
<!-- for manual backlight power consumption-->
<item name="config_enable_ManualBacklightPowerConsumption">1</item>
<item name="config_power_manualBacklightSetBrightPointA">45</item>
<item name="config_power_manualBacklightSetBrightPointB">55</item>
<item name="config_power_manualBacklightPwmBrightPointA">25</item>
<item name="config_power_manualBacklightPwmBrightPointB">26</item>
</brightnessconfig>
/ #
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Doing that resulted in my tablet hanging at boot. I forgot to mention that in Lux I used the Android Debug option to see what Android thought the actual ambient brightness was. It fluctuated like crazy. I think I might have ANOTHER defective device. I'm getting really tired of this.
Sorry to hear you had issues with this mod - just curious - what exactly did you do/change? Certainly, changing the values in this file should not cause a hang at boot. Did you change one value, two values, replace the entire file, etc?
You may be correct that you have yet another faulty unit - Asus QA is really bad (and seems to have gotten even worse with the TF700 if some of the threads here are any indication).
I do feel for you! I was pretty lucky with my first unit - just some minor light bleed that is only noticeable at boot-up...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Like this?
Well, I've never monitored the actual values being returned by the sensor itself, so I can't comment on that (yet).... I can say that the values that I've modified seem to make the auto-brightness work really well. You might even notice that I have the same value duplicated for more than one "brightness level" - simply because the value would "teeter" between the two while at work, so I do think that the sensor is very sensitive, at the least.
However, what you guys are reporting sure sounds a little different and may in fact be a hardware issue, as you've eluded to.
I'll install an app to read the sensor directly and report my findings.
Thanks.
EDIT: FYI - I just installed AndroSensor (monitors *all* sensors - pretty nice actually) and while my light sensor DOES go back and forth between 0 and 6 lux constantly while in my normal "sitting position", they are the only two values reported as long as I didn't change the lighting level. So, it definitely is very sensitive, but the problem that you guys are having sounds much more dramatic that what I'm seeing. Would you agree?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Thanks, jtrosky. Once I manually edited the file it seems to work. Before I just copypastad the code into the file, but when I manually just changed the values, it did work. Maybe you could have ROM developers include this tweak? I'm new to XDA and now sure how that would work.
EDIT: Does your autobrightness ever turn down on its own without turning off the screen? It's driving me crazy.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Actually, that's probably my bad - I should have mentioned not to copy and paste it - it seems that the forum "interpets" certain characters in that output and "hacks it up" a little. So, I can understand why copy and pasting could cause a hang at boot. I thought that there was a way to paste text as "code" so that it doesn't try to interpret the text, but I couldn't find that option for some reason....
Anyway, glad to hear that it's working better now. Good luck tuning it to your specific needs/environment!
By the way, I really don't understand why Asus doesn't allow you to "customize" these values - you should just be able to adjust the auto-brightness levels by moving the brightness slider while in autobrightness mode (kinda like iOS devices do it). Obviously, it can be done on the TF700... Oh well, maybe in a future update!
EDIT: Regarding the brightness level going down - I *think* that it will eventually lower the brightness automatically, but I think it takes much longer than than the brightness increases for some reason. Might be wrong about that though - maybe it doesn't ever go down (it should do that if it doesn't already though!)
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
I'm interested in trying this. i can get current lux value for different situations from androsensor. what's the best way to get current brightness values so i can log them and know what levels i want to put in?
There is no need for this.
When you feel the brightness is to high or low in a situation set the desired level and link it.
I have never "pre"-set any levels.
redheadplantguy said:
I'm interested in trying this. i can get current lux value for different situations from androsensor. what's the best way to get current brightness values so i can log them and know what levels i want to put in?
Click to expand...
Click to collapse
Are you trying to set the auto-brightness levels with the brightness_04.xml file (or whatever the name is) or with the "Lux" app from the Play store?
If you are just setting the levels in the .xml file, just start messing with levels - you'll quickly find levels that suit your needs - I posted a list of the levels I used earlier in this thread - just start with those and fine-tune as-needed....
With the TF700, there really is no need for the "Lux" app anymore if you are rooted. The number of different "levels" are already defined in the .xml file - you just need to adjust the brightness for the levels by editing the .xml file - it's really pretty simple. I've found that it works really well without the need of a third party app...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Is there also some way i can modify build.prop or something to lower minimum brightness on manual adjustment? often at night, i can't sleep. i like to use my tablet in the dark, and even minimum is far too bright for my eyes.
i DO LOVE the super ips+ display, however. i have seen friends with tablets that were impossible to see outside in sunlight.
but in a dark room, i need it down farther. thanks.
redheadplantguy said:
Is there also some way i can modify build.prop or something to lower minimum brightness on manual adjustment? often at night, i can't sleep. i like to use my tablet in the dark, and even minimum is far too bright for my eyes.
Click to expand...
Click to collapse
A quick check reveals that the brightness slider goes down to 10, but you can set the brightness manually down to 3 and still see something (below 3 it's completely black).
Type this into a root shell:
Code:
echo 3 > /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
_that said:
A quick check reveals that the brightness slider goes down to 10, but you can set the brightness manually down to 3 and still see something (below 3 it's completely black).
Type this into a root shell:
Code:
echo 3 > /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
Click to expand...
Click to collapse
thanks. I'm thinking of using Rom toolbox to make a script I can run when necessary.
is the "echo 3" part the number 3 setting? say I wanted minimum brightness at 5. would I change it to read " echo 5"?
redheadplantguy said:
thanks. I'm thinking of using Rom toolbox to make a script I can run when necessary.
is the "echo 3" part the number 3 setting? say I wanted minimum brightness at 5. would I change it to read " echo 5"?
Click to expand...
Click to collapse
Keep in mind that if you want to permanently lower the minimum (or maximum) brightness, you can do so by editing this file:
/etc/config/brightness/brightness_config_04.xml
In this file, you can set min/max brightness (for both manual and auto-brightness) as well as "tune" the auto-brightness levels.
So, you could, for example, make it so when it's completely dark that the brightness will automatically be lowered to it's lowest possible value (which is lower than the slider allows).
The file is commented pretty well. Just make *sure* that after saving this file, that the permissions are "rw-r--r--" or else you will freeze at boot-up (guess how I know that! )
EDIT: you will need to reboot after making any changes to this file (in order to make the changes take effect).
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Keep in mind that if you want to permanently lower the minimum (or maximum) brightness, you can do so by editing this file:
/etc/config/brightness/brightness_config_04.xml
In this file, you can set min/max brightness (for both manual and auto-brightness) as well as "tune" the auto-brightness levels.
So, you could, for example, make it so when it's completely dark that the brightness will automatically be lowered to it's lowest possible value (which is lower than the slider allows).
The file is commented pretty well. Just make *sure* that after saving this file, that the permissions are "rw-r--r--" or else you will freeze at boot-up (guess how I know that! )
EDIT: you will need to reboot after making any changes to this file (in order to make the changes take effect).
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
THANK YOU SO MUCH! YOUR AWESOME!
I ran the script with rom toolbox, went to bedroom and shut off lights, its perfect! i will be doing the permanent adjustment to it.
I think that reply was meant for @_that!
@sbdags and @_that are awesome - not me! I'm just a Unix system admin by trade - that's the only reason that I know anything about Android (since it's unix-like)!!
Anyway, glad that we could help you find a solution - please let us know how things work out or if you have any questions about the values in that file.
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Keep in mind that if you want to permanently lower the minimum (or maximum) brightness, you can do so by editing this file:
/etc/config/brightness/brightness_config_04.xml
In this file, you can set min/max brightness (for both manual and auto-brightness) as well as "tune" the auto-brightness levels.
Click to expand...
Click to collapse
Strange that the file says the minimum manual brightness is 5, but reading /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness at the minimum position of the slider yields 10. But the other 3 limits are exactly correct.
_that said:
Strange that the file says the minimum manual brightness is 5, but reading /sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness at the minimum position of the slider yields 10. But the other 3 limits are exactly correct.
Click to expand...
Click to collapse
I believe that I read somewhere that you *can* set the brightness to a lower value manually via this file than you can with the brightness slider...
I've never tried it personally though.
Can anyone confirm?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
redheadplantguy said:
Is there also some way i can modify build.prop or something to lower minimum brightness on manual adjustment? often at night, i can't sleep. i like to use my tablet in the dark, and even minimum is far too bright for my eyes.
i DO LOVE the super ips+ display, however. i have seen friends with tablets that were impossible to see outside in sunlight.
but in a dark room, i need it down farther. thanks.
Click to expand...
Click to collapse
Wow! You guys are waaay to technical for me. I only edit files when I need to. I just use an app called Screen Filter to filter the stock brightness levels down a bit. Its got a slider function for filtering light levels. Works great for night reading and night light functionality. Any stock setting can be filtered from 0 to 100%.
This is the tutorial:
0 - Download a file explorer and grant superuser permission (I personally use ES FILE EXPLORER).
1 - Locate this folder: /data/data/com.whatsapp/shared_prefs/
2 - Open the file "com.whatsapp_preferences.xml".
+ Mod image quality (jpg compression level ?)
Look for this line: <int name="image_quality" value="80" />
Change its value (80 by default) to whatever you want (a number between 1 to 99, you shouldn't use 0 or 100 I think).
RECOMMENDED VALUE: 90
Info: at 99 your photos won't have any compression (best quality), but the file size will be MUCH bigger (very close to the original size)
+ Mod image resolution
Look for this line: <int name="image_max_edge" value="1600" />
Change 1600 to the value you want, for example 3200 or 6400 (or bigger).
Info: I think this changes the maximum width allowed for an image. By default, if you want to send a 4K photo (for example) the sent image will be downsized to 1600px. Therefore if you want to send bigger photos change 1600 to 6400 or whatever.
++++
Results (try it by yourself too and tell me):
Here is a 3500x3500 photo, the original file: http://s1.postimg.org/o5rwefjm7/Screenshot_2015_09_16_16_36_20.png
And this is the sent image: http://s27.postimg.org/84yk2ooxv/Screenshot_2015_09_16_16_36_45.png
As you see it keeps the same resolution, you can also increase the quality to 99 to send photos with almost no compression, so the sent image and the original are almost the same, but I don't recommend that value because it takes longer to upload (if you have bad internet like me you won't want to increase the quality to 99), so you should try 90 (which I think is the best quality/compression level).
***
srry4myEnglish
Good tutorial, thanks
Enviado con mi Note 2 Lollipop
I tried it a long time ago, and the preferences defined in the receiver's phone acts as a bottleneck. Most likely that this is deliberately done by the developers to reduce the effect of local file modifications.
its not working.. i can't change the value, it comes to the default value after using whatsapp. Please help me
. . .
Thanks.....Nice for tutorial.....
send from SM-N910C
Nice tutorial.It really works
Sent from my Cyanogenmod10.1 Huawei Y210 0100
It does not work on my galaxy S6 MM
This is a nice tutorial. But will not work.
As the new version of whatsapp re-writes the file with original values on start.
So, to solve this, kill whatsapp. Now from any root file explorer, change the permission - remove the write privileges for all (440).
Then open whatsapp. Now the mod is applied only for that session of the app.
Also you might need to change the max image size. <int name="image_max_kbytes"value="8128"/> (I've put it as 8mb)
(PS Extra info-But you' think won't it make all the settings fixed and any setting change from within the app won't reflect. Don't worry whatsapp automatically changes the permission with write privileges (660)). Hence can't have the mod be permanent.
So Cheers.
thank you
How about video to gif...
Use this trick
I searched for this trick and i got a trick to do it.
send the picture by selecting documents
Any way to set dp in original quality?
Thanks!
Sent from my Nexus 6P using XDA Labs
dattafilthyd said:
This is a nice tutorial. But will not work.
As the new version of whatsapp re-writes the file with original values on start.
So, to solve this, kill whatsapp. Now from any root file explorer, change the permission - remove the write privileges for all (440).
Then open whatsapp. Now the mod is applied only for that session of the app.
Also you might need to change the max image size. <int name="image_max_kbytes"value="8128"/> (I've put it as 8mb)
(PS Extra info-But you' think won't it make all the settings fixed and any setting change from within the app won't reflect. Don't worry whatsapp automatically changes the permission with write privileges (660)). Hence can't have the mod be permanent.
So Cheers.
Click to expand...
Click to collapse
Latest version 2020 also same ? everytime need to edit ?
Thank you !
Seems to be working, but after each time the file on Samsung S7, because the file is overwritten...