Database Users

[Q] LCD Density Changer not working on JMEv4

LCD Density Changer is not giving me the options to set it as default density. I'm guessing it has something to do with Busybox as I cannot update my Busybox. Anyone else having this issue or know how I can fix it?
EDIT: Fixed it please using Titanium backup

i noticed that i was having issues on my tab as well, so i decided to delete the app even though i have the latest Busybox.

use root explorer to open /system/build.prop
find lcd densitry and change it to whatever you like
remount, reboot and enjoy

I just hit the problems button in titanium and it fixed whatever was wrong cuz it gave me the density setting back

Sounds crazy, but build.prop edits not persisting through hard reboot.

I know this will sound crazy, but when I edit the build.prop file with root explorer to change the LCD density, then after a hard reboot the nook reverts to default settings. As in, I change the LCD setting to ANYTHING, and after a hard reboot the nook ALWAYS boots to 161 LCD density.
Soft reboots will retain my build.prop edits.
My just flashed the most recent nightly, had the same problems on the previous nightly.
I tried copying the build.prop file to my SD-card, then editing it, then deleting the one in the system folder, then moving the new/edited build.prop file into the system folder. This did not work as well.
Frankly I'm stumped.
Anyone else have any ideas?

Make sure you mount /system/ r/w in root explorer... somtimes people forget and just mount / as r/w but that doesn't work.

DizzyDen said:
Make sure you mount /system/ r/w in root explorer... somtimes people forget and just mount / as r/w but that doesn't work.
Click to expand...
Click to collapse
Thanks for the quick reply, but I am only mounting /system/ as r/w. The file IS being changed, the actual change to the LCD density setting is there and persists. The nook just ignores it and loads 161.
EDIT:
I just tried adb pulling build.prop, changing the LCD density in notepad++, and adb pushing it back to /system. It still hard reboots to LCD density 161 no matter what I change it to.
EDIT2:
Here's an even crazier thing. When I adb pull the build.prop and open it, the LCD density setting says what I changed it to, but it's like the nook is disregarding that setting and defaulting to 161.
EDIT3:
Here's a link to my build.prop file and a logcat if anyone smarter than I can find anything wrong. http://dl.dropbox.com/u/20309200/build.prop http://dl.dropbox.com/u/20309200/logcat.txt

DPI Change

Guys I heard by changing the DPI of Oxygen OS reduces lag..
It even improves the laggy camera app..
Never heard before..
If yes best way to change DPI & how much wil be better?

Root, then install le dpi changer.

It's just "ro.sf.lcd_density" property in build.prop file.
No need to install all kind of special apps. Just edit the file (root needed for editing system file) and reboot.
I found ro.sf.lcd_density=400 to be good enough zoom out,
so more stuff can fit on screen but still things are readable.

Use adb command from your PC: " adb shell wm density XXX" where xxx is your desired dpi. This can be done on rooted or non rooted devices.
I currently use 240 dpi but you can try different ones to find the right one that suits you.
Sent from my ONE A2005 using Tapatalk

[Guide][Init.d script]Set resolution and dpi at boot

First of all you need root and init d support.
Second i will not take responsibility if something happens to you're phone.
I tried screen shift for a long time, but it kept disabling the set at boot and i got sick of it. Now im using 1600x900 with 360dpi with init d script and could not be happier that it works perfectly.
1. Download the file.
2. Open your preferred file manager with root priviliges.
3. Browse to your download folder and search the file.
4. Remove the txt extension from the file by renaming it.
4. Open the file with text editor and change the resolution and dpi to what you want.
5. Copy or cut the file into /etc/init.d
6. Reboot your phone and boom! You have you're desired resolution and dpi set at boot.
Stock 1900x1080 480dpi file attached.
You can change the values with text editor if you wan't different resolution and dpi.
1600x900 360dpi setting file also included.

Eh?
Code:
adb shell wm density “INSERT_DPI” && adb reboot

SpiritBreak3r said:
Eh?
Code:
adb shell wm density “INSERT_DPI” && adb reboot
Click to expand...
Click to collapse
What about the resolution?
I think that that only changes dpi.
I want more performance with lower res.

Fatsodonkey said:
What about the resolution?
I think that that only changes dpi.
I want more performance with lower res.
Click to expand...
Click to collapse
Code:
wm size "resolution"
wm size reset
wm density "DPI"
wm density reset

Does that also work with every boot?
I thought earlier that it just changed the value and after boot it would not stick.
Maybe i should not make guides since im a bit nooby with this. I just thought that it would make life easier for people like me.
I will just add the adb commands to it and call it a day.

Change to build.prop not having any effect

I'm pretty confused... I'm running Cataclysm with regular root (not systemless) and I've modified the build.prop (shows the modified value even after reboot) to change my screen dpi but upon reboot my dpi stays unchanged. Any ideas? I've tried to change the dpi through the adb method and that works but it shows some odd behavior in play store (some icons being too large, etc.) that other people say don't occur if you modify build.prop.

bgymn2000 said:
I'm pretty confused... I'm running Cataclysm with regular root (not systemless) and I've modified the build.prop (shows the modified value even after reboot) to change my screen dpi but upon reboot my dpi stays unchanged. Any ideas? I've tried to change the dpi through the adb method and that works but it shows some odd behavior in play store (some icons being too large, etc.) that other people say don't occur if you modify build.prop.
Click to expand...
Click to collapse
I'm running cataclysm as well. Changing the build prop works fine for me. Maybe it's the file manager application? I've had it happen to me when I first got my 6p and tried using root explorer. Also, make sure that you are actually saving the new build.prop and the values change before doing a FULL reboot

I had this exact problem on stock. I ended up downloading one of those DPI changer apps on the play store and it worked.. I have changed bp many times in the past. Don't know what was happening.
Sent from my Nexus 6P using Tapatalk

I tried dpi changers and build.prop editor apps and nothing works. I can change the model name and see the change reflected in the "about phone" section of settings so I know that the build.prop is being successfully edited. It just seems like my phone refuses to read the lcd_density line.

An update in case someone else runs into this problem. I can get the desired proper scaling if I change the build.prop value and use adb shell wm density with the same value in the build.prop. This fixes the scaling annoyances that I see from using adb shell wm density only to make the dpi smaller. I'm guessing the reason I can't use build.prop only to change the dpi is because I first tried to change the dpi using adb. For some reason that must trigger something and both places have to be changed.