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.
CM12.1 support DPI adjustment natively (if you see some apps still show bigger font, then try modify the build.prop to same value, this may help.)
========================
B320/B322 update screwed up below DPI adjustment. Thanks @medwatt testing, see #45 for details. For values like 240 or 260, the phone is completely blank, and if you do 'adb shell logcat *:E', you can see the resource not found error all over the place.
========================
Edit on July 3, 2015:
On Lollipop B309, the ro.sf.lcd_density is in build.prop already and set to 320, we can change it to smaller value: (make a backup first)
Code:
ro.sf.lcd_density=240
you can use any number between 240 to 320. Save then reboot. (Thanks @ArkAngel06 point out this entry still works)
Then everything is working fine. No expose needed and didn't see any big problem so far.
One problem we noticed is stock 'Browser' app FC, pls use your favorate 3rd party browser instead. (The one i currently use is boat browser)
========================
Following is original post for JellyBean 4.3
===Normal disclaims applies, be careful and know how to use adb to restore /system/build.prop before you try this=============
You phone may brick if this file got corrupted.
ROOT is required to change the LCD density.
Today trying to play around the DPI of display, and noticed the stock value is 320:
Code:
getprop | grep dens
[ro.sf.lcd_density]: [320]
But our 720p display native DPI is 240. That's why all the stuff display so big??
Anyway, I backed up /system/build.prop, and play a little bit.
I recommend simply use Root Browser with "RB Text Editor" to do the task. Other DPI changer app may work and convenient, but it is more risky and may do some change unknown to the phone. Due to lack of backup/restore recovery right now, I prefer manually editing the file myself.
Adding following to the end of /system/build.prop.
Code:
ro.sf.lcd_density=264
For some different varies like Consumer Cellular version, or MT2L05 version, you can try following if above doesn't work:
qemu.sf.lcd_density=264
Not sure it is a bug or what, when I use ES file explorer to edit the file, If I select edit mode right after open the file, it won't scroll to the end of file. I have to scroll to the end first in view mode, then select edit mode. Anyway, Root Browser editor works without any problem.
Following is some test result:
Code:
______________ System UI________ Settings__________ Gallery
180__________force close
200______________ok____________ force close______ force close
220______________ok____________ force close______ force close
240(native)______ok____________ force close______ force close
260______________ok____________ force close______ force close
264______________ok________________ ok____________force close
280______________ok________________ ok____________force close
320(stock)______ ok________________ ok________________ ok
Also, for all DPI less than 320, the stock lock screen shortcut is not displayed properly.
I think I will stick with 280 (update, now I am using 264) for a few days and see if I found more problems. And it should be easy to find an alternative gallery app.
The smaller font and everything actually make the display more clear and sharp
PS. I know there is font size in display settings, but the DPI change will make system zoom everything based on this new display density.
Thanks aragon257 and others feedback, some info from below is collected from the replies. Thanks.
MORE INFO/UPDATE:
. There is Exposed framework modules (like app settings) to do per app DPI settings. Please see end of this post for more info.
. The app force closing caused by lower DPI is purely software (view layout arrangement) issue, so lowering DPI will not do any harm to hardware.
. List of Apps that Force Close. I list them from higher DPI to lower DPI, The apps that crashes in higher DPI will also crash in lower DPI.
DPI 264 or 280: Currently I am using 264.
Lock Screen: No crash here. The app short cut moved to center of the circle, and requires less distance swipe to unlock.
Gallery (Also affecting camera since it start Gallery when you view pictures)
Alternative: "Galleray KK" and "Camera KK" from play store works pretty good, though it is Ads supported.
DPI 240:
Settings
Phone app when receiving calls.
Use Xposed Framework
OK, set DPI to 240 in build.prop, I need use Xposed module "App Settings" to set following App DPI to higher value to make the phone fully work:
Code:
Gallery(com.android.gallery3d): 297 (dp: 320x480)
Phone(com.android.phone): 264
Settings(com.android.settings): 264
SystemUI(com.android.systemui): 264
This number is set to lowest possible value, of course you can set to 320, then related apps will be bigger.
Please see attachment for some screenshot: (Left is stock 320 DPI, right is 264 DPI)
Thanks for doing all the research here
Use xposed and install app settings. Use it to give those apps that crash the default DPI. Just tried working great. And thanks about the tip of adb build.prop backing up.
Running at 240 DPI here.
Edit: Play store wouldn't download anything until I cleared the cache.
Edit again: Actually viewing images and trying to use the camera causes the gallery to crash... Ill fix it
FINAL Edit: Installed the kitkat camera and gallery. I had to unisntall the old gallery first. This works for me
Great, that xposed module is pretty cool, but for now I must resist as we don't have recovery yet
BTW, I have updated first post to correct the System UI FC number, it is 180, not 220. ie, DPI can be as low as 200 and the phone is still usable. So, native 240 is a pretty safe value.
Also, the "Huawei home" FC start showing up from 220 and below, though I am using Nova launcher.
Cheers.
I was having problems with incoming calls crashing the phone app. So back to 320, but using App Settings to change my downloaded apps to 240
Admired by this thread:
http://forum.xda-developers.com/galaxy-nexus/general/info-official-galaxy-nexus-lcd-density-t1392089
Call me bored, today I have tried more DPIs, and found 264 is the lowest number that Settings is working. Since the crashing is just cause by GUI view arrangement issue, nothing to do with hardware etc. So I will stick with 264 for now.
For the past few days with settings 280, I only noticed gallery is the problem. I didn't try too much widget/apps. Everything else I tried works pretty good.
Please refresh my memory, is lowering the DPI making the image smaller? If so, im interested.
yes, everything (font,icon,layout)will be smaller. but image actually maybe different story. try and see yourself!
so what apps are better in tablet mode for me to try?
Bobvark said:
so what apps are better in tablet mode for me to try?
Click to expand...
Click to collapse
I didn't use any particular tablet mode etc stuff, the lower DPI gives me more space asset, thats all.
xordos said:
I didn't use any particular tablet mode etc stuff, the lower DPI gives me more space asset, thats all.
Click to expand...
Click to collapse
ok, so Chrome, gmail, what would be good DPI for those? I'm a little worried about f'n up my phone and don't just want to do trial and error.
Is 240 the standard you all are using?
Bobvark said:
ok, so Chrome, gmail, what would be good DPI for those? I'm a little worried about f'n up my phone and don't just want to do trial and error.
Is 240 the standard you all are using?
Click to expand...
Click to collapse
264 or 280 should be safer. 240 the settings app wont work.
Added some screenshot to the 1st post.
I wanna mess with this later
aragon257 said:
I was having problems with incoming calls crashing the phone app. So back to 320, but using App Settings to change my downloaded apps to 240
Click to expand...
Click to collapse
ok, now with a twrp backup taken, I installed xposed and now i got exact same problem. 240 is really sweet dpi, even the lock screen layout is good.
I tried complete delete phone.apk, and contacts.apk, but looks like not easy to find a good replacement. other dialer app from play store still requires these two apks. And i checked my other phone 4.3 rom, they force close. will continue to the search.
Have you tried it with the xposed programs? I know it worked for gallery but not sure for settings.
oncouch1 said:
Have you tried it with the xposed programs? I know it worked for gallery but not sure for settings.
Click to expand...
Click to collapse
Thanks. Didn't try gallery with app settings module yet. For 240 dpi, call out/in problem is what I am focused on right now.
Was trying app settings with 240, I set phone dialer etc. at stock setting but forgot had face lock so when I restarted, crash due to camera (what a [email protected]!) Thank you guys for TWRP so I could restore! . On vacation and no PC to try and adb to modify build.prop.
Sent from my MT2L03 using XDA Free mobile app
xordos said:
Thanks. Didn't try gallery with app settings module yet. For 240 dpi, call out/in problem is what I am focused on right now.
Click to expand...
Click to collapse
yes, with exposed module, at 240 dpi, gallery/camera works fine, settings also worked, only phone app still FC. so now i am at 264, and use exposed to fix gallery.
Silly question, app settings didn't work on dialer?
oncouch1 said:
Silly question, app settings didn't work on dialer?
Click to expand...
Click to collapse
when calls come in, phone apps FC when dpi is 240 ( and app settings use 320 for com.android.phone)
EDIT:
OK, Maybe this defeat the purpose, set SystemUI to 264 resolve the incoming call problem. The incoming call crashed the phone app because the StatusBar trying to get a phone icon resource but failed.
To summary, In build.prop DPI set to 240, I need use Xposed "App Settings" to set following App DPI to higher value to make the phone fully work:
Code:
Gallery(com.android.gallery3d): 297
Phone(com.android.phone): 264
Settings(com.android.settings): 264
SystemUI(com.android.systemui): 264
This number is set to lowest possible value, of course you can set to 320, then related apps will be bigger.
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
Now that we have root and kernel adiutor, we might be able to change the dpi to the screen dpi with it.
Has already someone changed this?
According to the dpi calculator:
https://www.sven.de/dpi/
We should have ~197 dpi, but there is 280 in the build.prop
Actually how many dpi does our watch have?
I set the calculator above to 2.3 so the result reads 1,63x1,63 display.
But other calculators are different...
Change it for whole android is not perfect. Try instead the Xposed module app settings to change dpi for specific apps.