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
Related
Hi all,
Just wondered if anyone had any joy with the LCD Density changer remembering your updated density after a reboot.
If I re-power the device, it always returns to the stock 240 despite me clicking "Save" at 180.
It's getting slightly frustrating as the reason I paid for the app was to avoid having to re-do it everytime.
Anyone had any success getting it to remember? I rooted via Z4root, so I'm not sure if it's related to this method of rooting?
Thanks in advance.
If not, can someone tell me a step by step guide on how to hard-edit the density? - Thanks!
You have to go to settings and select "Save density as system density", then go back and save again on main screen.
You see a message saying it was saved as system settings and well keep after reboot or something similar.
all the best,
Joao.
awsome
I just did the exact same thing, also using z4root Only I also pressed the physical menu button while inside the lcd density changer app --> settings --> set saved density as system density ..or something like that (I don't have my tab with me atm). I hope this was helpful
Cheers guys - sorted at last. Much appreciated.
Hope the Galaxy Tab gets some love with some custom ROMs soon. Seems the Advent Vega is getting all the attention at the moment when I feel that the Samsung, with a few tweaks and bloatware gone - could be even more impressive than it is now!
Cheers all!
also, be sure to choose the permanent root option in z4root, or else your root will disappear on reboot
Any good screenshots where you guys take advantage of a higher density on the tab? (Sorry if OT)
Mate - just edit the build.props file in the system folder using root explorer or whatever
I have mine set for 200 and theres no need to muck about with apps of any kind... literally, just change 2 letters and youre good to go:
1. Download and install Root Explorer from Android Market.
There are other file managers for root users available, but this is one I use and what the rest of this tutorial is based on.
2. Open Root Explorer on your Tab, scroll to the bottom, and tap the system folder.
3. Tap the Mount R/W button at the top of the screen to gain read-write access to the files.
4. Long press on the build.prop item in the list.
5. Select Open in Text Editor from the pop-up menu that will appear.
6. Locate the line that reads ro.sf.lcd_density = 240. Delete “240″ and input another value in its place.
7. Tap the Menu button on the Tab.
8. Tap Save & Exit from the toolbar that will appear on the bottom of the screen. A backup of the original build.prop will be created automatically.
9. Tap the Mount R/O button at the top of the screen to return to the previous read-only state.
10. Exit Root Explorer and reboot the Tab to see the changes.
11. Repeat steps 2-10 as needed. Set the density to 240 to go back to the stock DPI.
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
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
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.
Hey guys was just wondering if anyone can post a video with a changed DPI? I'm not routes and I heard it can be done without root but wanted to see what it looks like first would really appreciate it
syphern said:
Hey guys was just wondering if anyone can post a video with a changed DPI? I'm not routes and I heard it can be done without root but wanted to see what it looks like first would really appreciate it
Click to expand...
Click to collapse
Not sure where you heard it can be done without root. Because it simply can't. Without root you cannot modify system files.
Sent from my Nexus 6P using Tapatalk
It can be done without root but needs to be done using ADB on a PC.
On your PC while the phone is connected:
ADB shell
WM density 480 (or whatever you want for your device)
Restart your device to complete.
Just try it. U can easily go back to default. But i promise, u dont want :b
I am rooted on my Nexus 6P, although I cannot get it to change the dpi settings.
I tried using texdroider_dpi, tried the adb method and even went to /system/build.prop and changed it via ES File Explorer.
When I set the DPI to anything but 560 my SwiftKey Keyboard breaks but the overall screen density doesn't change.
The value I entered is still displayed in the build.prop though ..
I had it changed already, but when I updated to the latest security patch 2016 I had to reinstall my phone since I flamingod something I guess.
Went ahead with Heisenbergs guide and followed Step 11 (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) to get my phone back to work. Only thing not working now is the dpi change ..
Any help?
Are you mounting system as R/W and saving the build.prop after you change the value?
dastinger said:
Are you mounting system as R/W and saving the build.prop after you change the value?
Click to expand...
Click to collapse
I didn't specifially mount the system as R/W - but when I restart the device afterwards the change is still persistent.
Try using another File Explorer (Fx with the root add-on for example) and make the change with that one mounting as R/W before doing anything else.
dastinger said:
Try using another File Explorer (Fx with the root add-on for example) and make the change with that one mounting as R/W before doing anything else.
Click to expand...
Click to collapse
I love you. #nohomo
Thank you very much.
[emoji4]
No problem, mate.
clubtech said:
It can be done without root but needs to be done using ADB on a PC.
On your PC while the phone is connected:
ADB shell
WM density 480 (or whatever you want for your device)
Restart your device to complete.
Click to expand...
Click to collapse
I do this but my Swiftkey is broken and some image elements are huge.
Does anyone know why something like texdroider used to work perfectly scaling everything and now it does not?
Before this update, after flashing the SuperSU 2.66 my twrp would give me the warning my phone was not rooted. Now, I do not receive this warning.
Sent from my Nexus 6P using Tapatalk