I've seen this tweak for other devices and decide to give it a try for my Nexus One. it works great. This is what I've done.
1) connect phone to computer (using USB or my "ADB over WIFI" app, I connected over Wifi)
2) "ADB pull /system/build.prop"
3) Edit build.prop file (make a backup first), find density and change "240" to something else (I've tested 200 and 220, and settled down on 220)
4) "ADB remount"
5) "ADB push build.prop /system/build.prop"
6) "ADB reboot"
and you will see the magic. Try all commands on the command prompt without quotes. You definitely need a rooted phone.
Have Fun!
What's the advantage of this?
You get more display resolution, I think.
Yes? I think there's already a thread about this.. and I think someone posted that some apps doesn't work well with other resolutions
I tried with root explorer, rebooted and now nexus one looks much cooler. There are some problems with apps, for instance, blow up shrunk but all the native apps seems to be fine
I think this is the thread I mean
http://forum.xda-developers.com/showthread.php?t=765639
I have my Nexus set to 180 but I used the LCD Density Changer app in the market. Its a lot safer than doing it manually through the build.prop
Yoshilover said:
I have my Nexus set to 180 but I used the LCD Density Changer app in the market. Its a lot safer than doing it manually through the build.prop
Click to expand...
Click to collapse
Safer???? That's exactly what that application does!
someone please post a screenshot (ddms) so we can see the actual resolution thats possible.
Unstable
My nexus one was unstable today, mostly non-google apps such as Luncher pro, I've changed it back to 240.
About safety, change density app will do the exact things in first post.
Related
I take inspiration from this post to enable init.d scripting on stock rom! I think it need be tested, but work fine for me!
Disclaimer: This may cause a bootloop! I'm not responsable for any brick or damage.
Enable init.d
What is it:
Enable init.d permit run "autorun at boot" scripts, you can put in that folder your scripts (eg. ram and net optimization, load custom modules, etc.) and that will executed during boot.
Prerequisites:
Busybox Installed;
Root Explorer or similar software, otherwise you can do it manually from terminal.
Open Root Explorer, go to /system/ and mount the filesystem as R/W.
go in /system/etc/ and create a folder called "init.d" (without quotes), then set permissions as rwxr-xr-x.
Edit the file /system/bin/clrbootcount.sh and add at bottom:
Code:
bb=/system/xbin/busybox
if [ -f $bb ]; then
/system/bin/logwrapper $bb run-parts /system/etc/init.d
else
for i in $(ls /system/etc/init.d/*); do
sh $1
done
fi
Put your init.d scripts (someone here) and set the permissions to rw-r--r--.
Remount the /system/ as R/O.
build.prop mods
What is it:
build.prop is the main configuration file, where you can find settings about the LCD Density, the market fingerprint, etc.
With this mod you will able too power up your Nook Tablet and have a snappier and faster device with a stock rom.
Prerequisites:
Root Explorer (or similar)
build.prop file
cold blood
Step 1: copy the attached file in your memory card (or internal storage)
Step 2: open Root Explorer, browse to /system folder and press the button "Mount R/W"
Step 3: rename your /system/build.prop as build.bak
Step 4: copy build.prop from your card to /system folder
Step 5: Long press on build.prop - permissions - set to Owner RW-Group R-Others R (or chmod 644 from shell)
Step 6: Remount the folder as R/O and reboot your device.
Another method is do the same with a terminal emulator or ADB. I don't tried yet but the commands shoud be good:
Step 1: on your pc open an adb shell or open your terminal emulator on the Nook;
Step 2: write
Code:
$ su
# mount -o rw,remount /system
cp /system/build.prop /system/build.bak
cp /sdcard/build.prop /system/build.prop
reboot
Well, your device now should be more snappier
Manual modification (ONLY FOR ADVANCED USERS)
Change sceen density (more HD feeling)
Code:
remove or comment [I][B]ro.sf.lcd_density.xxx=169.33333[/B][/I] and add [B][I]ro.sf.lcd_density=xxx (good values are from 140 to 180)[/I][/B]
Force launcher into memory:
Code:
ro.HOME_APP_ADJ=1
Save battery:
Code:
wifi.supplicant_scan_interval=180
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
Enhance performance:
Code:
debug.sf.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
ro.kernel.android.checkjni=0
dalvik.vm.lockprof.threshold=500
dalvik.vm.deoxopt-flags=m=y
windowsmgr.max_events_per_sec=150
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
Memory settings:
Code:
ro.FOREGROUND_APP_MEM=1536
ro.VISIBLE_APP_MEM=3072
ro.PERCEPTIBLE_APP_MEM=1024
ro.HEAVY_WEIGHT_APP_MEM=51200
ro.SECONDARY_SERVER_MEM=51200
ro.BACKUP_APP_MEM=53760
ro.HOME_APP_MEM=1024
ro.HIDDEN_APP_MEM=53760
ro.EMPTY_APP_MEM=64000
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=4
ro.PERCEPTIBLE_APP_ADJ=2
ro.HEAVY_WEIGHT_APP_ADJ=5
ro.SECONDARY_SERVER_ADJ=6
ro.BACKUP_APP_ADJ=7
ro.HOME_APP_ADJ=1
ro.HIDDEN_APP_MIN_ADJ=8
ro.EMPTY_APP_ADJ=15
ENFORCE_PROCESS_LIMIT=false
MAX_SERVICE_INACTIVITY=
MIN_HIDDEN_APPS=
MAX_HIDDEN_APPS=
CONTENT_APP_IDLE_OFFSET=
EMPTY_APP_IDLE_OFFSET=
MAX_ACTIVITIES=
ACTIVITY_INACTIVE_RESET_TIME=
Source
forgive my ignorance, but how can lowering the pixel density improve the screen output?
JoeM01 said:
forgive my ignorance, but how can lowering the pixel density improve the screen output?
Click to expand...
Click to collapse
If you set a lower pixel density your will have smaller text and icons, that mean you will see more informations in one page.
If you want bigger text, push it up!
Sorry please delte post. Where is the easy build prop file?
Sorry was on my nook and simple did not see it glaring at me at the bottom.
Couldn't be achieved also using lcdDensity from Market ?
Changing LCD density can make some games (Gameloft, I'm quite sure) not working. Just be careful.
Does anyone know the default wifi sleep policy, I want it to never sleep.
I would like to know because Im guessing that the wifi part is were you can change it since the advanced menu is missing under wifi settings
thanks
little8020 said:
Does anyone know the default wifi sleep policy, I want it to never sleep.
I would like to know because Im guessing that the wifi part is were you can change it since the advanced menu is missing under wifi settings
thanks
Click to expand...
Click to collapse
If you are rooted then you can access it under spare parts.
Sent from my Nook Tablet using Tapatalk
will changing lcd density allow greater access to apps on Market?
Can someone post what the modded build prop actually does? In another post it was SUPPOSED to allow greater access to market apps, but did absolutely nothing for me.
snailmale said:
will changing lcd density allow greater access to apps on Market?
Click to expand...
Click to collapse
yourbrokenoven said:
Can someone post what the modded build prop actually does? In another post it was SUPPOSED to allow greater access to market apps, but did absolutely nothing for me.
Click to expand...
Click to collapse
Huh??? LCD Density mean different text size.. How can be related to the Market????
This build.prop have good memory settings, less lags, hardware acceleration, etc.
You will have a snappier NT.
diamond_lover said:
Huh??? LCD Density mean different text size.. How can be related to the Market????
This build.prop have good memory settings, less lags, hardware acceleration, etc.
You will have a snappier NT.
Click to expand...
Click to collapse
If I recall correctly, the main reason given for why certain apps don't show up on the Market is because of the unusual DPI of the NT's screen (few apps would specifically support 169.333). As such, editing the LCD Density in build.prop to a more common value (e.g. 160) may open up access to more apps.
However, I can't try this till the next time i get my hands on my gf's NT. Anyone else able to try it out?
snailmale said:
However, I can't try this till the next time i get my hands on my gf's NT. Anyone else able to try it out?
Click to expand...
Click to collapse
I'm using the modified build.prop. What specific app would be a good test?
Some people who changed DPI from default on NC actually lost access to certain market apps. So far I'm not noticing a change (increase or decrease) in available apps either way.
camapghe said:
Changing LCD density can make some games (Gameloft, I'm quite sure) not working. Just be careful.
Click to expand...
Click to collapse
LCD density has to be 160 or 240 if you want all apps to work correctly. Those settings correspond to MDPI and HDPI which are standard android densities.
Sent from my BNTV250 using xda premium
Just a quick thought.
Could somebody edit this build.prop a little further so that it thinks its something like a galaxy tab (the smaller one)? I see a lot of people edit the device tahts reported for better compatibility with apps in Market. If the build.prop says it's a galaxy tab then hopefully it will show a lot more apps, currently a lot of apps don't show for the nook tablet but they should if build.pro says it's a galaxy tab or something similar
CelticWebSolutions said:
Just a quick thought.
Could somebody edit this build.prop a little further so that it thinks its something like a galaxy tab (the smaller one)? I see a lot of people edit the device tahts reported for better compatibility with apps in Market. If the build.prop says it's a galaxy tab then hopefully it will show a lot more apps, currently a lot of apps don't show for the nook tablet but they should if build.pro says it's a galaxy tab or something similar
Click to expand...
Click to collapse
One of the most important concerns that go into device spoofing is the hardware in the original device and the one that it is pretending to be. Differences in processor, gpu, etc. can cause significant problems when doing this.
CelticWebSolutions said:
Just a quick thought.
Could somebody edit this build.prop a little further so that it thinks its something like a galaxy tab (the smaller one)? I see a lot of people edit the device tahts reported for better compatibility with apps in Market. If the build.prop says it's a galaxy tab then hopefully it will show a lot more apps, currently a lot of apps don't show for the nook tablet but they should if build.pro says it's a galaxy tab or something similar
Click to expand...
Click to collapse
You can try use galaxy tab's ro.build.fingerprint.
I found this
sprint/SPH-P100/SPH-P100:2.3.4/GINGERBREAD/EF17:user/release-keys
Click to expand...
Click to collapse
but I don't tested yet.
Unfortunately that hasn't worked I am trying to installed friendcaster for facebook on my wifes tablet which I'm setting up for xmas for her. Lots of apps she uses are missing
Thank you for your suggestion though
could add comments on each parameter?
I want to use to use this prop file, and if i decide to just add only a portion of it, ie, add battery life section, can it be done?
Also, i noticed some of the addition isn't in the prop file.zip, like wifi.supplicat line? Maybe i just need to check my vision?
Can someone give a little background as to what exactly does it do? Is it similar to setting msconfig in windows so the os doesn't load as much stuff initially?
I did something dump today
I used LCD density modder pro on my rooted prime. I changed from 160 to 140 and when i rebooted using "save as system DPI (Reboot) the Ics launcher keeps crashing and i cant go back to it to change it back to 160.
What is the easiest way to accomplish this now? I can use ADB, but before i start messing around and make it worse, please give me the easiest instructions (not a beginner, but not super duper adv either).
Thanks
-- Resolved --
Relatively easy.. adb'd pull to pc and fixed build.prop and pushed back and all is good.
I also came accross this issue.
Im not so advanced at adb etc.
The way I did it was to email myself a link to LCD Density Modder in the market.
I could then click on the email in the notification bar and use the link to open the market.
You can then click open on the app and change the density back to 160.
Before we could and still can change DPI for the phone but now that xposed is not working, we can't change specific apps that need original stock DPI. I hope I can live with the original DPI settings lol
Brava27 said:
Before we could and still can change DPI for the phone but now that xposed is not working, we can't change specific apps that need original stock DPI. I hope I can live with the original DPI settings lol
Click to expand...
Click to collapse
Have you tried changing the DPI? I tried with textdroider and despite trying a few different values it didn't change. Textdroider reported the proper value but there was no change in anything.
you know you have to be rooted to change dpi, right?
if you are, do it in the build prop
wase4711 said:
you know you have to be rooted to change dpi, right?
if you are, do it in the build prop
Click to expand...
Click to collapse
Yes I know that and changing it in the build.prop is what textdroider does. I've done it with app and manually and it doesn't change anything.
so, when you save the new build.prop, and you open it again, it shows that your density settings are saved?
And, then after rebooting, the old density is back in the build prop?
I wont get my phone until later today, so I cant try it now, but that's strange..
wase4711 said:
so, when you save the new build.prop, and you open it again, it shows that your density settings are saved?
And, then after rebooting, the old density is back in the build prop?
I wont get my phone until later today, so I cant try it now, but that's strange..
Click to expand...
Click to collapse
Yes the new value shows after manual (and after textdroider) edit and save/reboot but the screen DPI doesn't actually change. The value is shown, but the screen is the same.
There are actually a few different values, the one that is 400 is the one I'd been changing. I wasn't sure what the two 640 values were and haven't changed them. Never seen a build.prop with multiple values. Didn't know if maybe those two values corresponded to the left and right edge screens since there are settings for them.
Have you found out any more info about this setting?
Has anyone tried running this via adb shell:
wm density 380 (or whatever density you want)
This worked fine without root on my Xperia phone. Just curious as I am thinking about getting this phone, but not setting density is a potential dealbreaker.
Alright so an update, it's the first 640 value that changes the DPI. The one under #system.prop for universal7420. I changed it to 580 and the attached pic is the result. I loaded google now launcher to test the scaling and it appropriately scales itself to use the whole screen whereas TW moved itself to the top left of the display. I guess the next challenge is to make TW properly scale.
I noticed that last night. I wonder what the other 2 dpi settings control?
adb works
I have successfully changed the DPI using adb on normal S6, though Play Store now believe it to be a tablet. Also, most of touchwiz hates it, not a big deal for most things, camera may be the biggest annoyance when its only taking up the upper right 60% of the screen.
Has anyone sucessfully changed the per app DPI, like you can with Paranoidandroid?
Look for "buil prop editor" on play store!! But the kamera and keybord looks like a#$
Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,
wikidavid said:
Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,
Click to expand...
Click to collapse
What are you doing? trying to pad your post count? Exact same reply in three different threads about DPI, as well as your other post in the same threads asking "dears to please not use the double post..." WTF?
schollianmj said:
What are you doing? trying to pad your post count? Exact same reply in three different threads about DPI, as well as your other post in the same threads asking "dears to please not use the double post..." WTF?
Click to expand...
Click to collapse
I'm just trying these things :
1) delete double post/overflow on the forum
2) give a solution anyway.
Don't be upset, there's no reason to... Have a nice day !
boosting1bar said:
Have you tried changing the DPI? I tried with textdroider and despite trying a few different values it didn't change. Textdroider reported the proper value but there was no change in anything.
Click to expand...
Click to collapse
I also tried the same thing with no results
Hi,
I changed my DPI successfully by changing the first occurrence of ro.sf.lcd_density from 640 to 540 in /system/build.prop using the built-in texteditor in root explorer (and rebooting afterwards ofcourse).
Then I noticed the camera didn't work properly anymore, so I created a fix for that (see this post).
Hope you'll get it to work, it seems the same to me as on earlier devices with as exception that the ro.sf.lcd_density occurs multiple times in the build.prop file.
Cheers,
Bane.
For testing different resolutions:
- have a functional adb
- enable USB debugging on device (developer options)
- connect device to your PC via USB cable. Then start a cmd in folder containing adb.exe. Type "adb devices" (without quotes) in the command prompt to check if adb recognizes the phone
- If is OK, type "adb shell wm density ZZZ" (no quotes) where "ZZZ" is the pixel density value you want to try (default is 640)
- no reboot needed, the change is on-the-fly
- check the programs (Samsung ones - dialler, calendar, camera, launcher, etc...)
- the change will disappear when you reboot your device.
per-app DPI...not; only with Xposed, when will be available.
Once you find the desired resolution it can be inserted in build.prop
Hi:
I am trying to run gscript on the watch. Unfortunately, it does not fit on the screen. I found someone who said that in order to run it, I need to "change dpi of your watch to smaller (like 180 or something, default is 240)", but gave no instructions on how to do that. Any ideas?
hallevison said:
Hi:
I am trying to run gscript on the watch. Unfortunately, it does not fit on the screen. I found someone who said that in order to run it, I need to "change dpi of your watch to smaller (like 180 or something, default is 240)", but gave no instructions on how to do that. Any ideas?
Click to expand...
Click to collapse
You can change your DPI by connecting your watch to a computer with debugging enabled, using ADB type:
adb shell wm density XXX where XXX is the density you wish to apply. Be warned, this setting does stick between reboots. (At least, it has for me.)
EDIT: I also found that 175 is a pretty good DPI for the G Watch. I installed Twilight on the watch so that after sunset, it's not killing my eyes in the dark and needed to set the DPI so I could use it.
yep, that worked. thanks. I will try it with gscript lite to see if that will work.
ShadowEO said:
You can change your DPI by connecting your watch to a computer with debugging enabled, using ADB type:
adb shell wm density XXX where XXX is the density you wish to apply. Be warned, this setting does stick between reboots. (At least, it has for me.)
EDIT: I also found that 175 is a pretty good DPI for the G Watch. I installed Twilight on the watch so that after sunset, it's not killing my eyes in the dark and needed to set the DPI so I could use it.
Click to expand...
Click to collapse
Can you post some pics on 175dpi?
Verstuurd vanaf mijn Nexus 5 met Tapatalk
I dont know what is wrong with OPPO ColorOS system engineer. Such a big screen phone, how can they delete the DISPLAY SIZE?
I even checked all the oppo phones, they are the same. Even VIVO phones.
And this makes the ColorOS UI very ugly.
but you can set it by ABD Code or developer options.
after you set it, you can see the difference with the orignal DPI settings (360). because the original one is really ugly.
better set as 420 or even bigger. personally I prefer 480 or 500.
but, questions coming. while restarting your phone. it will become like this. Damn.... I dont even know why it can be like this.
View attachment 4564870
Does anybody have a good way to set it please?
thanks a lot.
Since ColorOS is heavily modified by oppo, on current stage it's impossible to change it, and if u adjust the DPI higher than 360 you'll also noticed that the status bar will go crazy...
zhuyonsan said:
I dont know what is wrong with OPPO ColorOS system engineer. Such a big screen phone, how can they delete the DISPLAY SIZE?
I even checked all the oppo phones, they are the same. Even VIVO phones.
And this makes the ColorOS UI very ugly.
but you can set it by ABD Code or developer options.
after you set it, you can see the difference with the orignal DPI settings (360). because the original one is really ugly.
better set as 420 or even bigger. personally I prefer 480 or 500.
but, questions coming. while restarting your phone. it will become like this. Damn.... I dont even know why it can be like this.
View attachment 4564870
Does anybody have a good way to set it please?
thanks a lot.
Click to expand...
Click to collapse
No way to change it unfortunately. Apps like Youtube and Google Now look ridiculously magnified.
Display size
Highly disappointed .there is no option to set display size.everything looks so zoom out
@zhuyonsan how did you change DPI through ADB, when I tried it show me an error saying "Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS"
Thanks
karunch said:
@zhuyonsan how did you change DPI through ADB, when I tried it show me an error saying "Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS"
Thanks
Click to expand...
Click to collapse
Two ways of doing it.
1. Developer Options---Smallest width.
2.ADB: adb shell wm density XXX && adb reboot (XXX： the size which you wanna change)
@zhuyonsan That didn't work for me, see attached image
karunch said:
@zhuyonsan That didn't work for me, see attached image
Click to expand...
Click to collapse
adb shell
wm density 420
adb reboot
I'm getting the same java.lang.SecurityException: Must hold permission android.permission.WRITE_SECURE_SETTINGS error as Karunch when running the command 'wm density 420' inside the adb shell. Was there a fix for this?
solution
drazil22 said:
I'm getting the same java.lang.SecurityException: Must hold permission android.permission.WRITE_SECURE_SETTINGS error as Karunch when running the command 'wm density 420' inside the adb shell. Was there a fix for this?
Click to expand...
Click to collapse
it works, just remember to check "Disable Permission Monitoring" in Developer Options
i set at 480 dpi with nova launcher prime
Hope it hepls
allacciascarpa said:
it works, just remember to check "Disable Permission Monitoring" in Developer Options
i set at 480 dpi with nova launcher prime
Hope it hepls
Click to expand...
Click to collapse
And what about neon notifications? On different dpi it makes a strange display effect!
freccia said:
And what about neon notifications? On different dpi it makes a strange display effect!
Click to expand...
Click to collapse
Here everything works fine.
So, any way yet to get rid of those weird cutouts on status and nav bar once we change dpi yet?
freccia said:
And what about neon notifications? On different dpi it makes a strange display effect!
Click to expand...
Click to collapse
Allesa said:
So, any way yet to get rid of those weird cutouts on status and nav bar once we change dpi yet?
Click to expand...
Click to collapse
That's one more noise...
allacciascarpa said:
it works, just remember to check "Disable Permission Monitoring" in Developer Options
i set at 480 dpi with nova launcher prime
Hope it hepls
Click to expand...
Click to collapse
Thanks! it was that second setting that I was missing. Also your additional post mentioning you had no problems with the notification bar. I originally set the dpi at 420 but got the messed up notification bar. Changed it to 480 to match your post and the display bug fixed :good:. I guess 420 does not scale properly with the default dpi but 480 does.
Edit: ok I think I finally figured this out. you have to use a lower number like '360' to increase what's displayed on the screen. 'wm density 480' is the default value.
Don't let people confuse you in this thread. Basically the dpi can be changed in the "minimum width" parameter in the developer settings. However, Oppo is absolutely tyrannical in their allowance of the dev menu. The entire status bar turns a flashing orange warning that the developer mode will lead to phone issues. Setting the dpi from the dev menu results in NO status bar anomalies. Upon disabling the developer menu, all dpi changes are LOST. The other way to change the dpi is through adb. The command wm density does this. This produces the same change as the developer mode does. Great right, let's use adb to just change the dpi and not use the dev mode. Well the developer mode is required to be enabled to further enable USB debugging to even send adb commands in the first place. So upon disabling dev mode, all adb dpi changes are also reset. I also used the command wm density xx && reboot. When rebooted the corner of the top and bottom right side has a black anomalous overlay.
Of all tweaks I care about, a custom launcher is one, but dpi is the next. This phone is borderline unbearable.
xNiNELiVES said:
Don't let people confuse you in this thread. Basically the dpi can be changed in the "minimum width" parameter in the developer settings.
Of all tweaks I care about, a custom launcher is one, but dpi is the next. This phone is borderline unbearable.
Click to expand...
Click to collapse
Totally agree to this. I don't think we have any clean solution right now. ColorOS is such a terrible skin to work with and probably Oppo is not serious about this. The team wants to add new features, but ironically some of these important basic android features have gone for a toss.. Shame! Such a software experience is a bummer and I'm not gonna consider Oppo in future - I'm really frustrated.
Is there a way we can send a strong message to the team for this inclusion of this basic option?
Download MS Resolution changer from playsotre, you can change the resololution and the dpi without roor but you have to give the app a permission from adb in order to use the it.
1-Install the app from Playstore on your phone
2-Open it
3-Enable "usb debugging" in Developer Options.
4-Enable "Disable Permissions Monitoring" in Developer Options.
5-Conncet your phone to your pc with usb cable and run this command on adb:
"adb shell pm grant com.draco.smresolutionchanger android.permission.WRITE_SECURE_SETTINGS"
6-Go back to the app and change resolution and dpi, I have an Oppo F9 and the best parameters is resolution: 1080x2340 | dpi: 360
Here's some screenshots : drive.google.com/open?id=10RajURi6meQG6XtobTP3YpW3dWs3MHt4
It takes effect immediately after changing it to 450 BUT it gets reset to default after rebooting.
Change:
c:\minimal_adb_fastboot_1.4.3_portable>adb shell wm density 450
Before ADB Reboot:
c:\minimal_adb_fastboot_1.4.3_portable>adb shell wm density
Physical density: 480
Override density: 450
After ADB reboot:
c:\minimal_adb_fastboot_1.4.3_portable>adb shell wm density
Physical density: 480
Is there some user start script where I can put this setting so that it get's picked up each time I restart Oppo Find X6 Pro (on Android 13) ?? (or some other way to make it permanent (phone not rooted)).