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
Related
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
so i just flashed the AmeriCanAndroid rom and everything is running smoothly. the only issue is that the screen is very small. like the notification bar is so small i can hardly see it. the lock screen is a little bigger then a US stamp. i searched the original thread but there are over 1500 pages and the search function yeilded no results . so how do i fix the screen size?
The very first page of ACA thread says
"-Starting with 080111 and later, users can edit /sdcard/android/startup.txt prior to booting to adjust LCD_DENSITY, GPS_ZONE, and DATA_SIZE (data.img)
(ie: the default lcd_density of ACA is 167. Edit the lcd_density= value to 240 to get standard sized icons and fonts)"
The part you're looking for is to change the value to 240.
I do agree, its a plague to look through that thread and search ain't no help if you don't search right
RE: Wrong Section
Hi...please put this in the questions and answers section...iron fist will be on you ...here are some solutions I found by simply using the search:
You can increase the density (sort of like changing monitor resolution) on your screen by simply changing the build.prop file. This gives you more viewing area on your screen. The build.prop file contains many user variables that are editable and one of them is the LCD Density. The lower the number, the higher the resolution. The default value is 240, but by simply changing it to 200, you can increase the resolution and see more emails in your email app, more app listings in the market, more room for widget alignment, crisper graphics, and much more!
PERMANENT ROOT SOLUTION:
now that we can do perm root, you can permanently change this by modifying your build.prop file located /system/build.prop. look for ro.sf.lcd_density and modify the number and save and reboot.
Recommended value is 200, though many users like 190. If you are unsure what you like, please try TEST MODE shown below!
Please be sure to download Spare Parts from the Market, and disable Compatibility Mode in the app. This will fix many, many apps from not displaying full-screen, however there are some apps that will not re-size.
This works really well if you pair it with something like Launcher Pro or ADW.Launcher, where you have control over rows/columns and resizing widgets.
Easiest Method -- Go to Market and download one of the LCD Density apps. Search "LCD Density."
Phone-Only Method:
You can use Root Explorer, or any text editor like notepad++ or text edit.
1. Open a File Manager and locate /system/build.prop
2. Make sure "/system" is mounted as R/W (in Root Explorer, click the Mount R/W button at the top.)
2A. MAKE A BACKUP!
3. Open and Edit the file.
4. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
5. Save the file.
6. Exit and Reboot!
If you use a separate text editor, just copy the file to your SDCard, edit it there, and move it back and overwrite the original. I recommend backing up the original just-in-case.
ADB Method:
at the cmd prompt:
1. adb pull /system/build.prop
2. Go to SDK / Tools folder and open build.prop in a text editor (recommend WORDPAD for Windows).
3. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
4. Save & Exit
5. go back to cmd prompt and type: adb shell mount -o remount,rw /dev/block/mmcblk0p25 /system
6. type: adb push build.prop /system/
7. exit and reboot phone!
hope this helps you out
Or if that doesn't work, go to spare parts and uncheck "compatibility mode" then reboot phone
Pansi SMS screen size issue
I am using american android 2.3.7.
I have installed Pansi SMS application for messaging but some how it is not coming on the fullscreen of HD2. It is just capturing upper middle part of the screen Neither am i able to open the settings of Pansi SMS. Even the windows key is not working to open its setting.
How can i resolve this.
Is there any other SMS app as good as PANSI ?
I tried to change the Japanese font for HDX(the default one is so ugly)like what I did on other android devices before but I failed.
My HDX is already rooted and get SuperSU and RootExplorer installed, but I cannot mount r/w system/fonts folder so the fonts pasting failed, however other folders in /system can be mounted r/w without any problems.
Could anyone tell me the reason?
Maybe you could try and use some other browser for mounting r/w?
Sent from beneath my cloak of magic
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