Is there an LCD Density app whose setting survives a reboot ?
I am enjoying setting it to 200, but it resets on reboot.
you can manually edit the build.prop file in the system folder.
There's a line for lcd density that looks something like:
edit ro.sf.lcd_density
use Root Explorer to access and edit it. then save and reboot.
Also there is Font Changer that keeps density after reboot.
What is the absolutely correct LCD density? What exactly is it anyway? I don't understand its difference from resolution.
rulevoid said:
What is the absolutely correct LCD density? What exactly is it anyway? I don't understand its difference from resolution.
Click to expand...
Click to collapse
169.3333
It is the density of pixels per inch. Use the physical size of the screen and resolution of the screen, and determine how many pixels are in a square inch.
The Nook Color is 1024 x 600 resolution, on ~7in screen.
http://thirdculture.com/joel/shumi/computer/hardware/ppicalc.html
My preferred method of permanent density change:
adb pull /system/build.prop
edit build.prop on PC text editor
enable r/w /system/
push build.prop back to /system/
ThrowingKs said:
169.3333
It is the density of pixels per inch. Use the physical size of the screen and resolution of the screen, and determine how many pixels are in a square inch.
The Nook Color is 1024 x 600 resolution, on ~7in screen.
http://thirdculture.com/joel/shumi/computer/hardware/ppicalc.html
My preferred method of permanent density change:
adb pull /system/build.prop
edit build.prop on PC text editor
enable r/w /system/
push build.prop back to /system/
Click to expand...
Click to collapse
You can also just do it through Root Explorer, right on the nook.
-Go into the system folder
-Change folder to RW
-Long press build.prop and choose 'Open in Text Editor"
-Find the line with LCD density and change to whatever
-Switch folder back to RO
-Reboot
-Enjoy!
If you don't want to do any of the manual editing, LCD Density Changer by Beansoft (in the Market) will keep your density after a reboot. It costs about $1.
philburkhardt said:
You can also just do it through Root Explorer, right on the nook.
-Go into the system folder
-Change folder to RW
-Long press build.prop and choose 'Open in Text Editor"
-Find the line with LCD density and change to whatever
-Switch folder back to RO
-Reboot
-Enjoy!
If you don't want to do any of the manual editing, LCD Density Changer by Beansoft (in the Market) will keep your density after a reboot. It costs about $1.
Click to expand...
Click to collapse
Unfortunately, there are two lines in build.prop with LCD density (x and y direction) - which one [or both] do you have to change?
docfreed said:
Unfortunately, there are two lines in build.prop with LCD density (x and y direction) - which one [or both] do you have to change?
Click to expand...
Click to collapse
Not sure what you are looking at. Mine is as follows:
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.allow.mock.location=0
ro.sf.lcd_density=160
ro.setupwizard.enable_bypass=1
Don't see anything about X and Y. There is:
ro.sf.hwrotation=270
...but I specified the LCD Density line.
EDIT: Btw, I am running CM7.
philburkhardt said:
Not sure what you are looking at. Mine is as follows:
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.allow.mock.location=0
ro.sf.lcd_density=160
ro.setupwizard.enable_bypass=1
Don't see anything about X and Y. There is:
ro.sf.hwrotation=270
...but I specified the LCD Density line.
EDIT: Btw, I am running CM7.
Click to expand...
Click to collapse
I'm seeing ro.sf.lcd_density.xdpi=169.3333 and ro.sf.lcd_density.ydpi=169.3333. I also see a line (looks commented out) that is # ro.sf.lcd_density=240. So I do not which one to change - is it p0ossible that # ro.sf.lcd_density=240 was left over from a previous ROM flash or use of LCD Density Changer (I used to use that app but trashed it because it would not hold density on reboot.
And thanks for the prompt response!
LCD Density Changer is available in the market.
If you go the build.prop method, notate out (using the # sign at the start of the line) the X/Y lines and use the lines from the poster's build.prop
Sent from my SAMSUNG-SGH-I897 using Tapatalk
docfreed said:
I'm seeing ro.sf.lcd_density.xdpi=169.3333 and ro.sf.lcd_density.ydpi=169.3333. I also see a line (looks commented out) that is # ro.sf.lcd_density=240. So I do not which one to change - is it p0ossible that # ro.sf.lcd_density=240 was left over from a previous ROM flash or use of LCD Density Changer (I used to use that app but trashed it because it would not hold density on reboot.
And thanks for the prompt response!
Click to expand...
Click to collapse
I would say it is a definite possibility. 240 is the density on my EVO. I don't know that is was ever associated with the nook.
Here is my build.prop from CM7 v21 (sorry, I had to zip it to attach). The LCD density is pretty straight forward.
Sounds like you may have a Frankenstein build.prop
philburkhardt said:
I would say it is a definite possibility. 240 is the density on my EVO. I don't know that is was ever associated with the nook.
Here is my build.prop from CM7 v21 (sorry, I had to zip it to attach). The LCD density is pretty straight forward.
Sounds like you may have a Frankenstein build.prop
Click to expand...
Click to collapse
Yeah, I see what you mean about a Frankenstein build.prop - mine's quite different (although my Nook is running smooth as silk - just running Eclair (rooted) with no special tweaks excepting that I applied a tweak for the screen sensitivity via ADB. The tweak (posted on NookDevs) did a fabulous job of making the notorious "corner sensitivity issues disappear. Hmmm! That could of changed build.prop. Anyway, I'm probably not going to screw with it now - I'll wait until a really stable CM7 or HC comes around.
Thanks for the help anyway.
docfreed said:
Unfortunately, there are two lines in build.prop with LCD density (x and y direction) - which one [or both] do you have to change?
Click to expand...
Click to collapse
Comment them both out. Using the # sign.
Then add ro.sf.lcd_density=169.3333 right under them.
hey,
after flashing this version the dpi (according to lcd density) is 240 instead of 265..tried few apps to change it back with no luck.
somebody know what to do?
tanks
genia.m said:
hey,
after flashing this version the dpi (according to lcd density) is 240 instead of 265..tried few apps to change it back with no luck.
somebody know what to do?
tanks
Click to expand...
Click to collapse
Default is 240 afaik...
Sent from my Xperia Neo V using xda app-developers app
480 x 854 pixels, 3.7 inches (~265 ppi pixel density)
http://www.gsmarena.com/sony_ericsson_xperia_neo_v-4122.php
and it's not just gsmarena it's my eyes too - everything looks samller
genia.m said:
480 x 854 pixels, 3.7 inches (~265 ppi pixel density)
http://www.gsmarena.com/sony_ericsson_xperia_neo_v-4122.php
and it's not just gsmarena it's my eyes too - everything looks samller
Click to expand...
Click to collapse
I suppose you've changed the font size maybe. Go to Settings > Display > Font Size > Normal.
you can edit the file /system/build.prop and change the lcd_density value.
To change the resoultion and to make the dialer take up the whole screen .. Just change the LCD density to 120 using build.pro editor or change the value of this line : ro.sf.lcd_density = 100 to 120 ....
This question is for rooted Moto E users only. Can you please check the build.prop file located at /system/ and check the value of "ro.sf.lcd_density" (located towards the lower end of the file)?
That's the default lcd density or dpi. If you are sure you have never modified that value, then I kindly request you to check the value because I have been playing around with the LCD density value a lot and thus I forgot the default value. :/
nilanko said:
This question is for rooted Moto E users only. Can you please check the build.prop file located at /system/ and check the value of "ro.sf.lcd_density" (located towards the lower end of the file)?
That's the default lcd density or dpi. If you are sure you have never modified that value, then I kindly request you to check the value because I have been playing around with the LCD density value a lot and thus I forgot the default value. :/
Click to expand...
Click to collapse
The default is 240
I just thought I would give everyone a warning about changing LCD density with "adb shell wm density XXX"
(only applies to us non-rooted users -- rooted users can edit build.prop on the fly)
If you change the density, and then decide to check out the other resolutions like 720p and 1080p, it will fully erase your set density and return to stock resolution, even if you change the resolution back to stock (WQHD)
I myself didnt know this. I thought it would keep the resolution and recalculate the density, or reduce / increase the density based on the difference between WQHD. This is not the case.
So for those who set a custom density, DONT CHANGE RESOLUTION!