Hi, I changed the DPI from 240 on original CM10 to 480 or 320 (320 I think is much better) and the NHD+ is running much smoother and all the icons, fonts, look right.
If anyone interested try. With root explorer go to system, find build.prop, open it with text editor, change the density DPI from 240 to 320 save and exit, reboot and done. Or get a density changeling app from Google play.
Sent from my HD+
samomamo said:
Hi, I changed the DPI from 240 on original CM10 to 480 or 320 (320 I think is much better) and the NHD+ is running much smoother and all the icons, fonts, look right.
If anyone interested try. With root explorer go to system, find build.prop, open it with text editor, change the density DPI from 240 to 320 save and exit, reboot and done. Or get a density changeling app from Google play.
Sent from my HD+
Click to expand...
Click to collapse
Maybe that is why I never suffer any of the issues that others suffer. I have run at 320 since the first verygreen CM10/CM10.1's came out months ago. It is just the way I like it since my first tablet was a Galaxy Tab 7" and the icon and text sizes match that.
Sent from my Nook HD+ running CM10.1 on emmc.
samomamo said:
Hi, I changed the DPI from 240 on original CM10 to 480 or 320 (320 I think is much better) and the NHD+ is running much smoother and all the icons, fonts, look right.
If anyone interested try. With root explorer go to system, find build.prop, open it with text editor, change the density DPI from 240 to 320 save and exit, reboot and done. Or get a density changeling app from Google play.
Click to expand...
Click to collapse
Wow, after running on 240 for so long, changing to 320 makes everything seem magnified...like, so my grandma could read it. :laugh: Also less real-estate to work with.
I think i prefer 240, but thanks for the tip.
I guess a one third increase would look pretty big. I like the current size, but can appreciate others liking bigger. Not noticing the unsmooth issue with Nova, but DID notice it with the default launcher in CM 10.1 and also with stock 2.1 (even when using Nova).
rushless said:
I guess a one third increase would look pretty big. I like the current size, but can appreciate others liking bigger. Not noticing the unsmooth issue with Nova, but DID notice it with the default launcher in CM 10.1 and also with stock 2.1 (even when using Nova).
Click to expand...
Click to collapse
We are running omap4470 at the far end of it's capabilities, it seems. Same sort of issues are present in Kindle Fire HD 8.9 (also omap4470 chip with 1920x1200 panel).
There are no problems in stock launcher on Nook HD that has same 4470 chip, but much smaller 1440x900 panel.
It's a lot more pixels to push around, I noticed it on the HD+ as soon as I picked it up compared to the HD.
Usually even overclocking the CPU has little effect, but if we can oc the gpu and make it scalable it might actually make a difference.
I still need to learn more about omap chips, there doesn't appear to be a freq table like with msm chips, maybe I'm looking in the wrong places though. Can't even find any relevant commits on github, but again I'm probably looking in the wrong places.
Sent from my Galaxy Nexus using xda premium
Tegra 3 has the same issue, based on TF700 performance and Anandtech analysis. They actually found the 4470 more capable as far as cpu (this explains why HD+ is better with MAME) and for Flash and web browsing.
I prefer the HD+ with CM over the TF700 and stock Asus firmware. Seriously, and I am a picky person.
killersloth said:
It's a lot more pixels to push around, I noticed it on the HD+ as soon as I picked it up compared to the HD.
Usually even overclocking the CPU has little effect, but if we can oc the gpu and make it scalable it might actually make a difference.
I still need to learn more about omap chips, there doesn't appear to be a freq table like with msm chips, maybe I'm looking in the wrong places though. Can't even find any relevant commits on github, but again I'm probably looking in the wrong places.
Click to expand...
Click to collapse
it's in ach/arm/mach-omap2/opp4xxx_data.c, sadly a lot of them are running from a fixed clock so there's no easy way to actually bump them.
If we switch dpll_per clock for dpll_core for clocking bb2d and sgx cores, that should yield about 4% boost, that's about the easiest thing I see, though so far kernel does not want to agree with me about changing the parent clock
Anyone know if it is possible to change DPI on rooted stock?
jpisini said:
Anyone know if it is possible to change DPI on rooted stock?
Click to expand...
Click to collapse
On my HD I had ROM Toolbox I used that to edit DPI while on stock. When I reboot the device however was still the same. I would suggest a app from google play since you have root.
"dpi changer"
Sent from my Nexus 4 using xda app-developers app
jpisini said:
Anyone know if it is possible to change DPI on rooted stock?
Click to expand...
Click to collapse
Yes, look at my HD/HD+ stock tips thread linked in my signature (see item 7). You edit local.prop.
Sent from my Nook HD+ running CM10.1 on emmc.
doesn't changing DPI affect the ability to install certain market apps? I know on some phones it does...
blast0id said:
doesn't changing DPI affect the ability to install certain market apps? I know on some phones it does...
Click to expand...
Click to collapse
It certainly can, on my last tablet the dpi I liked made most apps incompatible. I would just grab them on my phone and then use titanium backup to make a copy for the tablet.
I gave 160dpi a try. Text gets *really* small.
If we use standard dpi's like 240, 320, 480 then go top settings/applications find the play store and clear the catch, then open play store and that's all it shouldn't be a problem.
Sent from my BN Nook HD using xda premium
thank you for this tips, I'm really liking the tablet at 300 dpi.
Be careful doing this on stock with apps like DPI Changer. My HD+ went into the boot loop and restored itself to factory, now I have to go through the hassle of rooting, redownloading all my apps and stuff, and setting everything up again.
Kevin43 said:
Be careful doing this on stock with apps like DPI Changer. My HD+ went into the boot loop and restored itself to factory, now I have to go through the hassle of rooting, redownloading all my apps and stuff, and setting everything up again.
Click to expand...
Click to collapse
Yes, I tell you how to do it safely on stock without reset in my HD/HD+ Stock tips thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
i set the hd up for 320. works great for flipboard and pulse. anybody try anything else that works in-between 240 and 320 that works well for the hd. im not to familiar with the standard numbers on the 7 inch tablet
Got an error while changing the DPI. It requires a root access mode. I am running CM11.
Related
I can't post this in development, as I do not have a superior ranking in XDA. I have figured out a build.prop tweak that will make your Kindle Fire with ICS look like a Nexus 7. I am running the CM9 based off of SGT7 ROM. This might not work the same as it did on the ROM I am using.
This will most likely work on other tablets, but I cannot guarantee it.
THIS WILL CHANGE SOME OF YOUR APPS TO THE PHONE VERSION.
**DISCLAIMER**
**I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE BASED ON YOUR ACTIONS**
Now that the standard things have been said, on to the fun!
REQUIREMENTS:
ROOTED KINDLE FIRE
ICS INSTALLED ON DEVICE
Process:
Install any app that can modify the build.prop file.
Find the setting for LCD_density and change it to 170 or 213. 213 is the Galaxy Nexus Official DPI, therefore it will not break app compatibility.
The smaller the number, the smaller every element will be, (I.e. the status bar) so 161 will be the smallest with the nexus 7 interface.
Reboot your device and you should be done!
Congratulations! You now have the look of JellyBean on your device!
If you would like to change back, just switch the LCD_density to 160 again.
Thanks:
twa_priv for his ROM
Hyperrunner for helping with DPI suggestions.
Jessical for widget suggestions in post #16
If you believe you need to be thanked for this, PM me.
Cool finding but it will break many app compatibility including the Play Store.
It didn't for me...
Switching to anything above 160 will make it look like the Nexus 7. Im using it at the moment at 161, and haven't lost any compatibility.
Dont you need something like button savior?
martimat000 said:
I can't post this in development, as I do not have a superior ranking in XDA. I have figured out a build.prop tweak that will make your Kindle Fire with ICS look like a Nexus 7. I am running the CM9 based off of SGT7 ROM. This might not work the same as it did on the ROM I am using.
This will most likely work on other tablets, but I cannot guarantee it.
THIS WILL CHANGE SOME OF YOUR APPS TO THE PHONE VERSION.
**DISCLAIMER**
**I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE BASED ON YOUR ACTIONS**
Now that the standard things have been said, on to the fun!
REQUIREMENTS:
ROOTED KINDLE FIRE
ICS INSTALLED ON DEVICE
Process:
Install any app that can modify the build.prop file.
Find the setting for LCD_density and change it to 170.
Reboot your device and you should be done!
Congratulations! You now have the look of JellyBean on your device!
If you would like to change back, just switch the LCD_density to 160 again.
Thanks:
twa_priv for his ROM
If you believe you need to be thanked for this, PM me.
Click to expand...
Click to collapse
You need button saviour. Otherwise you will have to restart every time you want to switch apps.
Sent from a thingymajig that sends things.
Not true
It you go to Settings>System>Conbined Bar, you have to check Navigation Bar, and you don't need anything like Button Savior.
Screenshots in attachments.
Ok if you want the official DPI for the Galaxy Nexus it is 213 and it doesnt break app compatibility since it is a official DPI, it looks nicer than 170.
Thanks! I'll try that!
200 or 220 look sharper than 213
Sent from my Amazon Kindle Fire using xda app-developers app
The point in 213 is that it won't break app compatibility.
martimat000 said:
Screenshots in attachments.
Click to expand...
Click to collapse
Looks verry nice.
martimat000 said:
The point in 213 is that it won't break app compatibility.
Click to expand...
Click to collapse
NBA Jam is not compatible with this mode
I set it to 170, otherwise I couldn't get the navigation option, but the status bar is huge. I guess that's something fixed in 4.1?
Jessical said:
I set it to 170, otherwise I couldn't get the navigation option, but the status bar is huge. I guess that's something fixed in 4.1?
Click to expand...
Click to collapse
I guess, the smaller you set the DPI, the smaller the elements get. How did you get those Widgets?
martimat000 said:
I guess, the smaller you set the DPI, the smaller the elements get. How did you get those Widgets?
Click to expand...
Click to collapse
Hmm, well. I dunno.
As for the widgets, I used Desktop VisualizeR and hooked it with the doubleTwist playlist and Play Books shortcuts. And set it to use the best quality so my images wouldn't be blurred when resized.
martimat000 said:
I can't post this in development, as I do not have a superior ranking in XDA. I have figured out a build.prop tweak that will make your Kindle Fire with ICS look like a Nexus 7. I am running the CM9 based off of SGT7 ROM. This might not work the same as it did on the ROM I am using.
This will most likely work on other tablets, but I cannot guarantee it.
THIS WILL CHANGE SOME OF YOUR APPS TO THE PHONE VERSION.
**DISCLAIMER**
**I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE BASED ON YOUR ACTIONS**
Now that the standard things have been said, on to the fun!
REQUIREMENTS:
ROOTED KINDLE FIRE
ICS INSTALLED ON DEVICE
Process:
Install any app that can modify the build.prop file.
Find the setting for LCD_density and change it to 170 or 213. 213 is the Galaxy Nexus Official DPI, therefore it will not break app compatibility.
Reboot your device and you should be done!
Congratulations! You now have the look of JellyBean on your device!
If you would like to change back, just switch the LCD_density to 160 again.
Thanks:
twa_priv for his ROM
Hyperrunner for helping with DPI suggestions.
If you believe you need to be thanked for this, PM me.
Click to expand...
Click to collapse
Thanks for this tip, 170dpi looks great on my Fire using twa_priv's ROM.
Sent from my Amazon Kindle Fire using xda app-developers app
Hey guys, just want to let you know that I found an app that will do this. It's called LCD Density Modder. It will change the DPI for you.
Hi there,
is there a way to get the Tablet UI without changing the DPI? I just changed it to 160 and eveything is really, really small Too small for my taste. So I was wondering if there is a way to get the Tablet UI without shrinking everything down?
Janzomaster said:
Hi there,
is there a way to get the Tablet UI without changing the DPI? I just changed it to 160 and eveything is really, really small Too small for my taste. So I was wondering if there is a way to get the Tablet UI without shrinking everything down?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1780970
But I didn't tried it yet.
Team EOS's nightly ROM's have a toggle for changing the systembar setup (from phatblet to tablet), but this doesn't activate system-wide tablet UI.
Are you rooted. I am running the latest AOKP and it has Tablet UI baked in.
Sent from my Nexus 7 using xda app-developers app
I use Paranoid Android which allows you to use tablet ui with a dpi of your choice.
I use 190.
*Sent from N7*
You can apply barrmullio's tabletUI code changes on any deodexed rom in the Dev section using my tool the autopatcher.
The tool works on CM10, AOKP and AOSP, and their derivative roms. It can be run on any PC, OSX, Linux or Windows. There is a GUI for Windows, but OSX and LInux will need to enter ONE command on the command-line.
I own a Nexus 7, so I added a bunch of the most useful code changes for our device to the tool.
No dpi ot build.prop edits needed, no market issues at all.
Curious about text size. I'm not rooted and think text on many apps is way small. If changing to 160 makes it smaller, can I assume changing it to 240 makes it bigger? Moon Phase Pro, and Amazon Appstore are 2 in particular that I find difficult to read.
Everything is much larger on my 5" screen Galaxy Player.
tcat007 said:
Curious about text size. I'm not rooted and think text on many apps is way small. If changing to 160 makes it smaller, can I assume changing it to 240 makes it bigger? Moon Phase Pro, and Amazon Appstore are 2 in particular that I find difficult to read.
Everything is much larger on my 5" screen Galaxy Player.
Click to expand...
Click to collapse
yeap. they will be bigger but I think a lot bigger, since stock dpi is 213.
Thanks a lot guys! I used Barmullios mod linked by Glimmling, doing just what I want.
The note was made for 240 dpi, and yet Samsung insist on making it 320dpi and giving us massive icons. I mines 240dpi via build change but it comes at a compromise.
Has anyone managed to get everything working fine at 240dpi or know of a ROM that supports it?
Sent from my GT-N7100 using xda premium
Right now no ROM officially supports it sahilaurora tried asking mike1986 if he will adding 240 dpi but it seems his rom is totally stock.
Omega doesnt offer it too...
You can try cm10 if port if you want
Right now all touchwiz roms will have compromises
Jamal Ahmed said:
Right now no ROM officially supports it sahilaurora tried asking mike1986 if he will adding 240 dpi but it seems his rom is totally stock.
Omega doesnt offer it too...
You can try cm10 if port if you want
Right now all touchwiz roms will have compromises
Click to expand...
Click to collapse
I hope for a ParanoidAndroid version by imilka as on the Note1 soon. See link Note1 http://forum.xda-developers.com/showthread.php?t=1797698.
Hmm...maybe I´m wrong, but it shouldn´t be any problem to change your DPI to 240 DPI using ROM Toolbox (or a similar app). TouchWiz wouldn´t stand this procedure, but you can use Apex or Nova instead without a problem.
And it wouldn´t be the first time that someone asks for providing a 240 DPI compatible version of S-Note It has always worked in the past, so why shouldn´t it work with the Note II?!
I´m not rooted yet (just having a test device), so I can´t try it out...but maybe someone here on the board sacrifieces some minutes to check it out^^
gee2012 said:
I hope for a ParanoidAndroid version by imilka as on the Note1 soon. See link Note1 http://forum.xda-developers.com/showthread.php?t=1797698.
Click to expand...
Click to collapse
We really hope...
I used that ROM alot back when i used Note 1 awesome. but it was already stable enough
In any case, any paranoid android/CM we will be getting on Note 2 will be unofficial as CM team has dropped support for exynos devices
240 works, however you get FC on the keyboard (which is perfect for the Note II) And the camera is all small, so is the dialer.
S-Notes is fine. So if you repalce the dialer,camera app and the keyboard you are fine to use 240 to 200 DPI. But is it worth it loosing the stock keyboard and camera? No..
Losing the stock keyboard is fine IMO, as there are loads of really good alternatives... apart from the fact handwriting with the SPen relies on it. For me that's no big deal, it's a gimmick anyway, but it could be a killer for others.
Hi all,
I've been trying really hard to adapt the stock GNote2 software for 240dpi but to no avail.
Basically the issue is the keyboard which crashes at 240dpi. It works anywhere from 320 down to 270 dpi (280-270 dpi is already nicer than 320 dpi, but it's definitely 240 dpi that we want ) but with a lower DPI it crashes.
What I am saying is that I think all the "button too small" issues can be fixed. For instance I have more or less successfully resized the Samsung keyboard for 280 DPI. All the other apps should be no problem: camera, e-mail...
But with the Samsung Keyboard crashing whatever I do I am stuck. Even when I resized the buttons for 240 DPI. I don't know what to do with that.
Something nice would be to "fake" the system DPI so that the Samsung keyboard still thinks it is at 320 DPI, but there seems no way to do that easilly (i.e. no source code hacking). Paranoid/Android does something like that with their "Per App Dpi" but I am not sure that we would reuse their code on Stock Samsung apps... They suggest that it is tied to CM.
Mmmm... Maybe the note 10.1 apps work with 240dpi... Worth a try
Can someone get this apps and installd it on the note?
- f3w1n -
Continuing on my previous post...
It sees the Samsung keyboard crashes because below 270dpi Android switches to "tablet mode". Application would not be made for it crash.
I don't know if there is any way around that? I guess Android uses the screen resolution to compute the --supposed-- size of the screen and then choose between tablet (big screen) and phone (small screen) modes.
NexusCrawler said:
Continuing on my previous post...
It sees the Samsung keyboard crashes because below 270dpi Android switches to "tablet mode". Application would not be made for it crash.
I don't know if there is any way around that? I guess Android uses the screen resolution to compute the --supposed-- size of the screen and then choose between tablet (big screen) and phone (small screen) modes.
Click to expand...
Click to collapse
Thats why i said to use note 10.1 apps.
- f3w1n -
f3w1n said:
Thats why i said to use note 10.1 apps.
Click to expand...
Click to collapse
Not sure what would be the result, do you have the Note 10.1 apps at hand?
Anyway, I have found the following thread which suggests that we could hardcode the DPI for specific applications: http://forum.xda-developers.com/showthread.php?t=1903519
If we could just force the Samsung keyboard to behave as if we were at 320 DPI, always and whatever the system settings, that would be perfect in my opinion...
I dont have it, but the keyboard can be stracted from the jb ota leaked or try the ics keyboard from any of the note 10.1 roms
- f3w1n -
Hendrickson said:
240 works, however you get FC on the keyboard (which is perfect for the Note II) And the camera is all small, so is the dialer.
S-Notes is fine. So if you repalce the dialer,camera app and the keyboard you are fine to use 240 to 200 DPI. But is it worth it loosing the stock keyboard and camera? No..
Click to expand...
Click to collapse
I'm fine with those compromises, so what's the easiest way for me to switch to 240? Never messed with dpi changes...
I'm sure I saw a comment on a thread here (screenshot thread, perhaps) from somebody running 189DPI... I'd love to hear more about that.
I'm running 240DPI at the moment and for me, with a few quirks, it's fine. I dislike the Samsung keyboard so changed that to Swype on day-one of owning the Note 2. So really all I'm left with is the odd graphical problem or quirk (such as the comedy-looking dialer) which is fine by me.
Can someone using 240 dpi post some screenshots of their icons please
Sent from my GT-N7100 using Tapatalk 2
I have a running 240 DPI rom with fixed camera app and touchwiz. Its got a few set backs for example not spen touchwiz detection. And no samsung keyboard, instead I installed swiftkey.
I might release it soon...
What's the easiest way to change dpi? I'm already rooted and want to try 270 since you guys says that's the lowest we can run without problems.
Brgds... /Tubgirl
Sent from my GT-N7100 via Tapatalk 2
Why we go for 240?its better?
Sent from my GT-N7100 using Tapatalk 2
Tubgirl said:
What's the easiest way to change dpi? I'm already rooted and want to try 270 since you guys says that's the lowest we can run without problems.
Brgds... /Tubgirl
Sent from my GT-N7100 via Tapatalk 2
Click to expand...
Click to collapse
Edit build.prop and reboot or install any dpi changer app
Sent from my GT-N7100 using xda app-developers app
Hi, i'm planning to buy the S4 this weekend..
I see i allready can root the device.. Is it also possible to change to 240dpi? Or is it to early
Greetings
I tried to switch to 240 dpi, but got ui errors after a reboot?
probably, but not for a little while. wait until all the hacks are released, and enjoy it for awhile first. lol
240 dpi is optimal for s3 , as s4 comes with 4xx dpi by default, id suggest you to change it to 320 dpi which would be optimal
I read somewhere that the S4 comes at 320dpi just like the S3.
type R-blood
Hi bala-gamer is it you who did the 240/180dpi modded apps for SGS3? If so I cant wait to do it for SGS4 I was very satisfied with your work and with the amount information displayed on SGS3 HD display on 240dpi...
You can always use another launcher which works on 240 dpi and use an others keyboard i guess .
No I tried all of the "best" launchers on SGS3 and ended with touch wiz...and bala modified problematic apps to work...
Help me to understand what is the discussion here.
DPI? Isn't that a print value?
BoneXDA said:
Help me to understand what is the discussion here.
DPI? Isn't that a print value?
Click to expand...
Click to collapse
DPI = printing
PPI = displaying
DPI=PPI moreless
but both means same = resolution of viewing doesn't matter the way
Actionx1 said:
I read somewhere that the S4 comes at 320dpi just like the S3.
type R-blood
Click to expand...
Click to collapse
I don't think there is even a hint of truth to that. Its like 441 dpi
Provide a link if you've got one. . .
sharkeecz said:
DPI = printing
PPI = displaying
DPI=PPI moreless
but both means same = resolution of viewing doesn't matter the way
Click to expand...
Click to collapse
But what is the point of changing it?
Icons and everything are displayed smaller so there will fit more info on the screen.
rauschkugl said:
Icons and everything are displayed smaller so there will fit more info on the screen.
Click to expand...
Click to collapse
yes, this is the reason for somebody who need it
I have tried
LCD Density Modder Pro - hangs on boot
A build.prop editor - boots fine, but dpi looks exactly the same. When I go back into the app, it says 480 dpi... as if I didn't change it
Xposed - hangs on boot
Anything that works?
3473 said:
I have tried
LCD Density Modder Pro - hangs on boot
A build.prop editor - boots fine, but dpi looks exactly the same. When I go back into the app, it says 480 dpi... as if I didn't change it
Xposed - hangs on boot
Anything that works?
Click to expand...
Click to collapse
same here, any infos?
ah ok i've got it.
my problem was that i added a line on the end of the build.prop -> i had to edit the one that was already there.
I used rom toolbox from the play store and changed mine to 320dpi and it's worked fine for the last 24hrs...
Sent from my GT-I9505 using xda premium
jongilluley said:
I used rom toolbox from the play store and changed mine to 320dpi and it's worked fine for the last 24hrs...
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
what line did you change?
zincsnow said:
what line did you change?
Click to expand...
Click to collapse
Within rom toolbox go to build prop editor and click the search icon and enter lcd. It should return a few lines but one will be lcd. Density at 420. Just click that one and change to 320 and reboot...
Need to be rooted as well.
Sent from my GT-I9505 using xda premium
rauschkugl said:
Icons and everything are displayed smaller so there will fit more info on the screen.
Click to expand...
Click to collapse
So how does going from a pixel density of 441 pixels per inch to fewer PPI (I've seem people talking about 240, 320, etc.) make things take up less room?
If an icon was 441 pixels wide, it'd take up an inch of screen space at native resolution. Change screen to 240 pixels per inch, and now that same icon takes up almost two inches.
Wouldn't you want to change to some number bigger than 441 pixels per inch to fit more on the screen? What am I missing?
For those not in the know, DPI setting can be changed on Android devices so that you can basically fit more on the screen. I must warn you that sometimes some apps might not show up in play store as your device is treated like a tablet (for example) - although I personally never had a problem resulting from this.
To change it you need to edit ro.sf.lcd_density=420 line in the build.prop file that is located in the system folder. As long as you can get to that file you can use any text editor to change the line
The default is 420, I changed it to 320 and you can see the results in the attached screes shot. Don't forget to restart the phone for changes to take effect.
Oh you live dangerously.
Mine is at 360 and it's the best for me .
For other people; you can also change it without having to root by using adb.
Holy crap do you guys have Superman vision? I'm in my 20's and I almost had to squint for the 420 density lol.
Mine is currently set to 480, the default for the G2 which has the same physical dimensions for the LCD.
badenglishihave said:
Holy crap do you guys have Superman vision? I'm in my 20's and I almost had to squint for the 420 density lol.
Mine is currently set to 480, the default for the G2 which has the same physical dimensions for the LCD.
Click to expand...
Click to collapse
You made yours BIGGER? Oh man that's crazy. Making the don't bigger wasn't working out for you?
I get "could not save file" tried with ES and build Prop editor, the file has r/w enabled to.
dannydogg said:
I get "could not save file" tried with ES and build Prop editor, the file has r/w enabled to.
Click to expand...
Click to collapse
Try using Root Explorer. I've run into issues using anything other than that for things like this.
I'm just glad Google added official support for 420. Looks great with all apps.
480
Sent from my Nexus 5X using Tapatalk
I use 320 on my N5x as well. I accidentally set it to 220 since that was what I used on my N4 and I didn't realize the resolution was different. I would say 220 is at the bottom end of what I would consider to be usable. It basically fits what would normally be on a 8" tablet on a 5" phone.
bblzd said:
I'm just glad Google added official support for 420. Looks great with all apps.
Click to expand...
Click to collapse
Agreed. At 420dpi I have no desire to make it smaller.
I settled on 440 and changed font size to large. 480 made the status bar too big imo. Some of my older apps have too tiny text for my aging 40+ year old eyes :sly:
420pi seems to be pretty solid for me, I truly wouldn't want it any smaller or larger than what it is at.
I use Nova Launcher to set icon size to 145% and system settings to set font size to large. Looks just right to me. Out of the box both icons and font sizer were too small and uncomfortable. Years ago I was an iPhone user and I'm sure I still have some of the DNA, lol. I fill my homescreens with icons - hate wasted space.
jbdan said:
I settled on 440 and changed font size to large. 480 made the status bar too big imo. Some of my older apps have too tiny text for my aging 40+ year old eyes :sly:
Click to expand...
Click to collapse
I also think 440 is the best size. I'll probably need to resize all of my ROMs I flash. But it's not too much or too little.
I don't want to root my phone, but I definitely want to change my DPI a little
Rado_vr6 said:
I don't want to root my phone, but I definitely want to change my DPI a little
Click to expand...
Click to collapse
You don't have to root to change dpi. I used adb. There are a lot of guides out there. It's very simple imo. Google "how to change dpi without root" good luck!
jbdan said:
You don't have to root to change dpi. I used adb. There are a lot of guides out there. It's very simple imo. Google "how to change dpi without root" good luck!
Click to expand...
Click to collapse
Forgot all about that method. Using it now good sir
Does the build.prop method make all apps behave properly? I tried using the adb method, but I had a few apps which didn't handle it properly (not the least of which was the Play store).
440. That matches roughly to the same estate as Galaxy S4 - just a tad bigger (as I expected when upgraded 5.0" to 5.2")
I was psyched when my Nexus 5X arrived and I saw that the stock DPI was 420. For the past two years, I've been changing the DPI on my Nexus 5 from 480 to 420...