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.
Related
Modifying the LCD density of your screen will provide HUGE REACTIVITY GAIN to the tablet
We can also tweak Dalvik heapsize for large application
Both are editable using software but they're also properties on the build.prop :
- dalvik.vm.heapsize
- ro.sf.lcd_density
Does editing this properties is enough for the Folio follow or do we have to make much complex operations ?
I there, is this fix already implemented or has to be done manually?!?
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Click to expand...
Click to collapse
I dont understand what u mean.
ps: have u read my pm?
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Click to expand...
Click to collapse
density of 120 works quite fine here now.. with old market app, there was a problem with 120 but that seems resolved now with new market app..
and yes, somehow screen and browsing seems to work better? or is it just the bigger picture giving a nicer resolution of browsing?
All resolution are good. If you have a lot of items on the screen lower density is best.
But by using something like 180 you get a lot of visibility. Since i've developped a lot of complex widgets, it's my favorite one.
Using a density >120 will get you less data to manage on the screen and you can feel the gain ! i'm using multipicture and a lot of complexes widgets and there's not fillrate lag at all.
I was quite surprised with this benefits.
My purpose is that those options can really feet somes users needs. VM heap tricks like the one you found on cyanogen helps on huge application like PDF readers.
But even after editing those properties on the build.prop they are not taken into account. Maybe because of the previous installation i've done. So i'm looking to better understand how to override android properties.
I'm not sure how android handles non-default values for this property.
You should try with one of these:
120 (low-density)
160 (medium-density, Folio default)
240 (high density)
Depending on how this is handled, setting a density different than that may result in broken applications (depending on how the layouts are coded)
Using the LCD DEnsity application i confirm that all resolution are compatible with the folio
Maybe some application will have a bad behavior ! so we've to be able to change the density
metuskale said:
I there, is this fix already implemented or has to be done manually?!?
Click to expand...
Click to collapse
This is no fix, as there are no real issues with these things. Its only a matter of tweaking the folio to your best personal use. They have to be implemented manually.
Shouldn't the dalvik heapsize fix the sound problem with some avi files?
I'm using the foliomod 1.3d, foliowidget works, but some avi files arn't giving me sound
Hello, could someone tell me how the default value for the heapzize is, please? There is only 16, 24 and 32 to choose, but I read something about 64!? How can I choose this value or get back to default?
Thx
Tom
Edit: solved!
hi guys..
i have seen a few posts on the SGS side of things about resizing the dialer / camera etc... correctly when the LCD denisty is changed to a lower than standard figure..
is there a way of these apps "ignoring" the LCD density values set in the build.prop files?
just thinking.....
ta
nutmegy said:
hi guys..
i have seen a few posts on the SGS side of things about resizing the dialer / camera etc... correctly when the LCD denisty is changed to a lower than standard figure..
is there a way of these apps "ignoring" the LCD density values set in the build.prop files?
just thinking.....
ta
Click to expand...
Click to collapse
This ROM has a modified camera app for 200 dpi: http://forum.xda-developers.com/showthread.php?t=1149713
Just extract it from SkyROM and replace yours via adb or root explorer...
please help me i changed my s2 density to 200 now its not booting please super please help.
Hello
Can i change dpi stock 240. Someone have tested?
kvadde said:
Hello
Can i change dpi stock 240. Someone have tested?
Click to expand...
Click to collapse
A solid-state screen's DPI is a physical attribute, you cannot change it.
I believe OP is referring to the soft DPI settings in build.prop. You must root, then edit the ro.sf.lcd_density setting in build.prop. It's already 240 on CM, not sure about stock though.
Cat McGowan said:
A solid-state screen's DPI is a physical attribute, you cannot change it.
Click to expand...
Click to collapse
You are talking about PPI, not DPI
Stock DPI is also 240.
But why would you want to change that??
If some app is not displaying to your satisfaction, it's better not to modify build.prop, because it could lead to unexpected weird behaviors.
Better is to use the "Xposed Framework" with the module "App Settings"; there you can specify individual DPI settings for each app. The safer and more flexible solution! I use it without problems on all my devices.
Felimenta97 said:
You are talking about PPI, not DPI
Click to expand...
Click to collapse
You have it backwards.
kvadde said:
Hello
Can i change dpi stock 240. Someone have tested?
Click to expand...
Click to collapse
As you didn't specify whether you want this on stock firmware or an AOSP ROM, I'd suggest to try the PACman port to the XTZ, as it includes per-app DPI modifier. It's currently in nightlies and no fully stable release as of yet, but it's worth to try if you really need that feature.
DPI = Dots Per Inch
PPI = Pixels Per Inch
The reason we've started to use PPI instead of DPI is because of PenTile, since that technology yields more pixels than dots per inch (dots are shared between adjacent pixels). Both are properties of the hardware but by telling Android you have a different DPI you can scale the UI. This procedure will make graphical elements that makes use of their physical size on the display (rulers, printing tools, etc.) show up at incorrect sizes.
For example, if you have a virtual measurement tape, you'll need to multiply all values with the original DPI divided by the new DPI. So if you choose to change your tablets DPI to 120, making every UI element scale to half of the original size, you'd need to multiply every value by 240/120=2 for it to match up with the real world.
I hope this clears things up.
Shanliang- said:
As you didn't specify whether you want this on stock firmware or an AOSP ROM, I'd suggest to try the PACman port to the XTZ, as it includes per-app DPI modifier. It's currently in nightlies and no fully stable release as of yet, but it's worth to try if you really need that feature.
Click to expand...
Click to collapse
As I already said: No need to change firmware. Just install Xposed framework with App Settings module on rooted device, and you can freely modify DPI per app.
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!