Does anyone know the dpi of the grab. Why do I hear its like 118? That's horrible, the galaxytabs doing is 196. Anyone know how to change the LCD density(dpi) PERMENANTLY even after reboot?
Edit your /system/build.prop and add the following line. Change 160 to what your want.
ro.sf.lcd_density = 160
If you are using adb
adb pull /system/build.prop
edit and make the change to build.prop and save
adb remount to mount the partition in r/w
adb push build.prop ./system/build.prop
adb shell reboot
mmathai77 said:
Does anyone know the dpi of the grab. Why do I hear its like 118? That's horrible, the galaxytabs doing is 196. Anyone know how to change the LCD density(dpi) PERMENANTLY even after reboot?
Click to expand...
Click to collapse
I'm not sure about the first part of your question but I changed the density at boot by adding this to my build.prop under Additional Build properties:
ro.sf.lcd_density=120
Looks much better now and now I have even more screen real estate
This is very interesting. I am sure a few people would like to see pictures of this.
There is an app that I use called LCD density changer, it allows you to change it, with a soft reboot. I am now using it with the stock TNT 1.0.1 build. I know there are hatred of the TNT interface, but I love it when I am working at my desk.
I am new here so I cannot link it. I would be happy to send it to someone who can.
RNSlate said:
There is an app that I use called LCD density changer, it allows you to change it, with a soft reboot. I am now using it with the stock TNT 1.0.1 build. I know there are hatred of the TNT interface, but I love it when I am working at my desk.
I am new here so I cannot link it. I would be happy to send it to someone who can.
Click to expand...
Click to collapse
Would you care to take a picture of your g-tab with the density set to normal and then set to a higher number so we can see the difference?
I'll post some shots, what is a good screen shot app?
atomb said:
I'll post some shots, what is a good screen shot app?
Click to expand...
Click to collapse
Hmmm... that might be difficult to explain on the g-tab because i believe you need root and you need to use the one from the SDK.
you can just take pictures with your phone or digital camera and upload them... im sure that would be enough to see the difference.
what does this do
I have root explore and can add it but what does it do.
i put that change in
no app needed with root explorer and adding that line.
atomb said:
I'm not sure about the first part of your question but I changed the density at boot by adding this to my build.prop under Additional Build properties:
ro.sf.lcd_density=120
Looks much better now and now I have even more screen real estate
Click to expand...
Click to collapse
I changed mine to 120 as well and I like it much better. More screen real estate and the status bar isn't so big now
slampana said:
I changed mine to 120 as well and I like it much better. More screen real estate and the status bar isn't so big now
Click to expand...
Click to collapse
The icons were way to small for me and messed up some of the scaling on some apps. I am still glad that the option is there!
Call me stoopid, but I can't figure out how to edit the build prop (or whatever it's called) file. I've found it, and can open it with ES File Explorer, but when I try to save it after making changes I get an error message and it cancel's out.
Any suggestions?
App root explorer is all u need.
Sent from my PC36100 using XDA App
Are there any Root Explorer apps that are free?
Im Assuming Stock is 160 cuz thats what lcd Density for Root Tells me. I Wouldnt go smaller then 140. 140 is good but anything smaller is waaay too tiny.
lostpilot28 said:
Call me stoopid, but I can't figure out how to edit the build prop (or whatever it's called) file. I've found it, and can open it with ES File Explorer, but when I try to save it after making changes I get an error message and it cancel's out.
Any suggestions?
Click to expand...
Click to collapse
You will need a program that allows you to mount directories as read and write. Otherwise it won't work. I am not sure of any free ones that are available.
Mine at 120 (my favorite)
Sorry I tried to just do a screen shot but every app I try just gives me blank black images.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry to resuscitate and old thread, but Yesterday, my G-Tablet somehow trashed it's android.database.sqlite, so my planned upgrade to the Official CM7 was forced.
CM7 is great, but the Icons, the Menu Bar, and pretty much everything look too big -- and I'm an old guy that (sometimes) wears reading glasses. It looks like the Android Tablet for Pre-K.
I know I previously changed ro.sf.lcd_density, but -- old guy thing again -- I can't remember what I set it to.
The comment associated with this file also says something about Market Working properly.
Suggestions? Will changing it really keep Market from working, or will it just look "non-optimized"?
Related
The keyboard on the Droid X has been released and modded to work on an EVO, and some other 2.1 devices.
I think it is a great KB, and will use it over the HTC KB, I like the space between each keys, the speed, and the multi-touch.
The KB looks simple and is very easy to type on, in fact it finally has the biggest feature I want on an android KB, it corrects commonly misspelled words, but does not display them, or suggest them. This feature is cool but IMO, adds clutter to typing. For example, when typing "heklo" on the the keyboard, it auto corrects it to "hello" without displaying words or suggesting them like on the HTC and Stock Android KB.
Now, the purpose of the post. The only thing that Would make this KB perfect for me is to change the background color behind the keys to a grey color, I provided an image with something that I would like using Paint.
I have never developed for android and have no idea how to do it, but if someone who knows how to do it, could simply open up the code of the app, and just change the background from white to a grey, that would be awesome.
Many people would prefer it IMO, and it is a better typing experience because the colors are different and the keys are more noticeable, making it easier to type more accurately.
I provided a screen shot to show what I was talking about, and the original .APK of the Droid X KB.
Any help is appreciated.
If someone could point me in the right direction in finding it, I would be more than happy too. I'm looking through it now, if i figure it out......... I will make a black one
Like I said I have no idea how to develop, but tried something out, maybe it can help you.
I use Astro (file explorer) and when I open it I click browse file.
click 5th option=res>drawable-land-hdpi>then down to keyboard_background.9
I copied that to my computer, edited the pic which was originally white, and then changed it to the grey I wanted, I then deleted the original file to the .APK and then copied the version I edited on their and tried to install it.
But when I went to install it, it says application can not be installed.
If someone could explain it to me, I know because I edited a key file in the app, It probobly won't work or install properly, but does the whole .apk have to be refinalized and ready to install with the change I made to install right?
mjz147 said:
Like I said I have no idea how to develop, but tried something out, maybe it can help you.
I use Astro (file explorer) and when I open it I click browse file.
click 5th option=res>drawable-land-hdpi>then down to keyboard_background.9
I copied that to my computer, edited the pic which was originally white, and then changed it to the grey I wanted, I then deleted the original file to the .APK and then copied the version I edited on their and tried to install it.
But when I went to install it, it says application can not be installed.
If someone could explain it to me, I know because I edited a key file in the app, It probobly won't work or install properly, but does the whole .apk have to be refinalized and ready to install with the change I made to install right?
Click to expand...
Click to collapse
You might just need to resign the .apk.. not 100% sure though, never did it.
How do you do that?
mjz147 said:
How do you do that?
Click to expand...
Click to collapse
Like I said I've never done it, but if I had to I would try this..
http://forum.ppcgeeks.com/showthread.php?p=1838214#post1838214
deleted post
REMOVED: See next post for progress!
deleted pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Black will be done, going to bed.
I NEED SOME ONE TO HELP WITH THE XML FILES!! Please..... any help would be appreciated. What I need- learn the xml documetns coding, and when that happens... I believe I will have the letters white
froyo support?
will this have froyo support?
saywhat4118 said:
will this have froyo support?
Click to expand...
Click to collapse
If I'm not mistaken, this keyboard FC on Froyo
I'll just post the apk. It's weird how the space button is having the shadow stretching thing going on...... maybe someone can lend a hand.
If you already have the multi touch keyboard installed- uninstall-then install this one-go to settings-then uncheck then recheck multi touch keyboard- change input method in text field
Thanks so much, its people like you that make this website what it is.
It's nothing. I realized, while texting someone, that the weird shadow is on the orginal keyboard too
Sent from my Evo 4g using XDA App
I've always used 209 on most my devices but with this enormous screen I think we could go much smaller. Usually changing the density messes with certain apps. Anyone have suggestions on the best settings that has worked for them on the TB?
Sent from my ADR6400L using XDA App
@youneek, i had tried both of the lcd density apps (paid and free ones) and neither of them works on the thunderbolt. quite disappointed because the first thing i wanted to do after rooting was to change that density.
*sigh*
hopefully the developers are working on it. i guess i need to go ahead and be pro-active and email them about it.
were you able to change it at all from the default 240?
defsquad said:
@youneek, i had tried both of the lcd density apps (paid and free ones) and neither of them works on the thunderbolt. quite disappointed because the first thing i wanted to do after rooting was to change that density.
*sigh*
hopefully the developers are working on it. i guess i need to go ahead and be pro-active and email them about it.
were you able to change it at all from the default 240?
Click to expand...
Click to collapse
pretty sure you have to be rooted to change the density? if you are not it won't.
second, I came from the evo, and I liked 185. Only app it messed up was speedtest.net, and even then it was just smaller with spaces around it. I use swype so it making the stock keyboard all tiny didn't matter to me.
You can manually edit your build.prop if you are rooted. I'm using 209 since widgets align perfect on LP when using extra columns. Might try to go one up and reboot while taking screen shots each time.
Sent from my ADR6400L using XDA App
I'm using 210 and it works well for me, haven't really had the urge to make it smaller as of yet.
Wow, 185 looks great. Just wish sense worked better for font overlapping.
Sent from my ADR6400L using XDA App
some screen caps of the different density for those wondering
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
240 stock
210
185
two_cents said:
some screen caps of the different density for those wondering
240 stock
210
185
Click to expand...
Click to collapse
Terrible screen to show the difference lol. 210 and 185 look the same with your setup. I guess I should do screenies of mine since it is insanely different because I use Launcher Pro and not the stock launcher. Aslo apps like facebook will look dramatically different between 210 and 185.
Not trying to slam you or anything, just explaining because someone is going to ask why they don't look different.
I like sense so that's what I use... The 185 chops off the icon names... 210 is ok but it breaks the flip in the clock... Posted just to give an idea... No offense taken
Sent from my ADR6400L using XDA App
two_cents said:
I like sense so that's what I use... The 185 chops off the icon names... 210 is ok but it breaks the flip in the clock... Posted just to give an idea... No offense taken
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
LOL I didn't even notice what it does to the sense clock. I guess if you want to keep Sense you will want to not use 185.
Although changing the LCD density on this phone is very different from the Evo that I came from. The density change on the TB only changes somethings, not everything, like it does on the evo.
The thing I noticed about not setting a device to its correct native ppi, is that you won't get sharp 1:1 pixels but blurred antialiased pixels instead. Which makes sense, doesn't it?
build.prop
Using root manage i did a search for build.prop to play around (back up naturally) with the LCD Denisty. During the search i fould 2 build.props. One located /data/data/com.android.browser/app_plugins/build.prop and the other /system/build.prop... Do I need to sync the two values of will changing /system/build.prop be sufficient?
Neo3D said:
The thing I noticed about not setting a device to its correct native ppi, is that you won't get sharp 1:1 pixels but blurred antialiased pixels instead. Which makes sense, doesn't it?
Click to expand...
Click to collapse
Yeah, you can say that would be the equivalent of setting a 1920x1200 resolution lcd monitor on your computer to 1900x1080 or something lower. The screen will obviously be blurry because it's not the native (optimal) resolution. It's not a good idea to do that on your computer, so I am not following why it would be on your phone.
I am looking for a way to change the screen dpi (also called density or resolution) from and have it stick during a reboot. The current 240dpi is just too big and 190 looks just right to me.
I have tried a couple apps from the market (LCD DENSITY and LCD DENSITY CHANGER) and both work, but do not stick after a reboot. When I had the HTC HD2 I know you could edit the build.prop or something similar and get it to stick, but don't know if this can be done on the Nexus or not.
Does anyone have any ideas? I've used search and surprisingly found very little pertaining to changing the density on the Nexus.
Thanks for your help!
method2madness said:
I am looking for a way to change the screen dpi (also called density or resolution) from and have it stick during a reboot. The current 240dpi is just too big and 190 looks just right to me.
I have tried a couple apps from the market (LCD DENSITY and LCD DENSITY CHANGER) and both work, but do not stick after a reboot. When I had the HTC HD2 I know you could edit the build.prop or something similar and get it to stick, but don't know if this can be done on the Nexus or not.
Does anyone have any ideas? I've used search and surprisingly found very little pertaining to changing the density on the Nexus.
Thanks for your help!
Click to expand...
Click to collapse
you can just edit your build.prop file. its in /system/build.prop/. i use root explorer. after changing it and saving it, all you do is reboot for it to take affect.
heres a screenshot of my build.prop file, the line you want to edit has the curser behind it. and a screenshot of my homescreen and icons with the number set to 230 instead of 240..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
method2madness said:
I am looking for a way to change the screen dpi (also called density or resolution) from and have it stick during a reboot. The current 240dpi is just too big and 190 looks just right to me.
I have tried a couple apps from the market (LCD DENSITY and LCD DENSITY CHANGER) and both work, but do not stick after a reboot. When I had the HTC HD2 I know you could edit the build.prop or something similar and get it to stick, but don't know if this can be done on the Nexus or not.
Does anyone have any ideas? I've used search and surprisingly found very little pertaining to changing the density on the Nexus.
Thanks for your help!
Click to expand...
Click to collapse
I also use the build.prop method, but I use 165
Sent from my Nexus S 4G
That did it! You're the man. Thanks a bunch!
bwcorvus said:
I also use the build.prop method, but I use 165
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Wow. And I thought 190 was small! You must have awesome eyes.
Use exactly 200. Its equals out a little over qhd resolutions. 960x560 or something. Someone else filled me in on his to do the math and I went from there. Trust me 200 is what you want. Anything smaller and text starts to become grainy. I worked out the math a few months ago in my epic.
sent from my Touchwiz'd Nexus S 4g
RushAOZ said:
Use exactly 200. Its equals out a little over qhd resolutions. 960x560 or something. Someone else filled me in on his to do the math and I went from there. Trust me 200 is what you want. Anything smaller and text starts to become grainy. I worked out the math a few months ago in my epic.
sent from my Touchwiz'd Nexus S 4g
Click to expand...
Click to collapse
Hmm. I'm using 190 as I type this and have no complaints whatsoever. Text is very crisp and the size is perfect. I changed the columns in Launcher Pro Plus to 6 and am loving life.
Oh yea. One thing. The market homescreen is a little messed up, but nothing to get in a tizzy over. I never stay on that screen very long anyway.
I tried dpi 200 and I liked it, but unfortunately lot of apps which I have installed is now not compatible
Is there anyway to fix it? Because I like 200 dpi and want to keep it, 240 is just too much for me.
Revin said:
I tried dpi 200 and I liked it, but unfortunately lot of apps which I have installed is now not compatible
Is there anyway to fix it? Because I like 200 dpi and want to keep it, 240 is just too much for me.
Click to expand...
Click to collapse
Download a program from the market called "LCD Density". It allows you to make a temporary dpi change that resets back to normal after a hard reboot. Just temporarily set your DPI to 240 with LCD Density (it will do a soft reboot to apply the setting), download and install what you want from the market, then just do a hard reboot and Viola.
Is it possible to modify the DPI of the system via build prop on the Nexus 5 like I have done in the past with my Samsung phones? Stock icons are always much to large for me and stock apps font to large.
HughesNet said:
Is it possible to modify the DPI of the system via build prop on the Nexus 5 like I have done in the past with my Samsung phones? Stock icons are always much to large for me and stock apps font to large.
Click to expand...
Click to collapse
Never mind. It would appear the answer is yes. Nice. 340dpi is looking nice.
dpi change
HughesNet said:
Never mind. It would appear the answer is yes. Nice. 340dpi is looking nice.
Click to expand...
Click to collapse
Did you just root stock 4.4? Or did you flash one of the built ones? And have you seen any bugs anywhere?
Thanks
Showme1 said:
Did you just root stock 4.4? Or did you flash one of the built ones? And have you seen any bugs anywhere?
Thanks
Click to expand...
Click to collapse
I've modified my buildprop too, with rooted stock rom. I just used RomToolbox Lite to modify my buildprop, but there are many other ways to do that. Haven't noticed any bugs.
Megiddo2000 said:
I've modified my buildprop too, with rooted stock rom. I just used RomToolbox Lite to modify my buildprop, but there are many other ways to do that. Haven't noticed any bugs.
Click to expand...
Click to collapse
Can you show screenshot?:laugh:
tuncan said:
Can you show screenshot?:laugh:
Click to expand...
Click to collapse
I would, but I'm too lazy to screenshot, connect to comp, and upload it. Sorry :silly:
If your device is rooted, it's a really simple procedure to test out your own dpi values. It's really just opening a buildprop editor, and popping in some new numbers.
If you're device isn't rooted, and you're on the fence about rooting, and dpi is influencing that, just root it. You won't regret it.
I've changed mine to 320 in the build.prop and it looks nice. A lot better than stock. The only bug I have noticed is when I am in an app and press the home button, it returns to the home screen and the keyboard pops up. Just to trouble shoot I returned to the stock DPI and it didn't do it anymore. But its a minor annoyance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5 using Tapatalk
Tried 380
Jacob030 said:
I've changed mine to 320 in the build.prop and it looks nice. A lot better than stock. The only bug I have noticed is when I am in an app and press the home button, it returns to the home screen and the keyboard pops up. Just to trouble shoot I returned to the stock DPI and it didn't do it anymore. But its a minor annoyance.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So I set it to 380 and I thought things were too small. Also my App list button was off center and couldn't be moved. What DPI settings would scale well with 480 ?
Thanks!
EDIT- I think 420 works great. It reduces the Icon sizes by just the right amount, but yields no extra screen space.
Interesting. At 320 you are essentially telling your phone that it's a 7" tablet.
If it was just fonts and not icons, there are system font settings you can turn down as well under Display or Accessibility. For icons, would otherwise need a custom launcher.
Jacob030 said:
I've changed mine to 320 in the build.prop and it looks nice. A lot better than stock. The only bug I have noticed is when I am in an app and press the home button, it returns to the home screen and the keyboard pops up. Just to trouble shoot I returned to the stock DPI and it didn't do it anymore. But its a minor annoyance.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same problem here
Sent from my Nexus 5 using xda app-developers app
You can just tap home again and the keyboard goes down or the minimize button. And if you use a different launcher of course it is a non issue. I may go slightly larger then 340. It is perfect for in my hands but a little hard to read text while in my car dock
is there any way to get small icons on nexus 5 kitkat ?
i dont quite like the big icons
Uses SS launcher or Nova.
Or you can use Power Toggles and put apps on the widget (icons end up small).
rak****.sherwoodian said:
is there any way to get small icons on nexus 5 kitkat ?
i dont quite like the big icons
Click to expand...
Click to collapse
You can edit your build.prop to change the dpi of the device.
By default it comes with 480 dpi set (but the screen has an actual value of 445)
I've found that a 445 value will change a lot on the device, everything will be more defined and much smaller, unfortunately this will reflect everywhere, even in the browser where things will tend to be a bit smaller. 460 seems to be a good compromise.
The line you'll need to search for in the build.prop is ro.sf.lcd_density=480
You will need root and something like ES file explorer in order to mount the system as RW to be able to edit that row and save the changes.
chk27 said:
You can edit your build.prop to change the dpi of the device.
By default it comes with 480 dpi set (but the screen has an actual value of 445)
I've found that a 445 value will change a lot on the device, everything will be more defined and much smaller, unfortunately this will reflect everywhere, even in the browser where things will tend to be a bit smaller. 460 seems to be a good compromise.
The line you'll need to search for in the build.prop is ro.sf.lcd_density=480
You will need root and something like ES file explorer in order to mount the system as RW to be able to edit that row and save the changes.
Click to expand...
Click to collapse
This worked perfectly fine! I did not like those giant icons!
I think 445 is the perfect value.
Thanks.
rak****.sherwoodian said:
is there any way to get small icons on nexus 5 kitkat ?
i dont quite like the big icons
Click to expand...
Click to collapse
Apex Launcher, Nova Launcher or Icon Changer from Google Play
e_rene said:
This worked perfectly fine! I did not like those giant icons!
I think 445 is the perfect value.
Thanks.
Click to expand...
Click to collapse
Yep. After seeing this thread I set mine to 445 and it looks/works just fine with all my apps.
smaller means bigger .... in terms of space !
I went full on for the small look with maximum real estate and tablet mode apps, set dpi to 240 and get 2 separate drop downs at the top and apps go dual pane like a bigger tablet , love this look so much more ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry guys for my noob question but where is build.prop located?
cybermonk said:
Sorry guys for my noob question but where is build.prop located?
Click to expand...
Click to collapse
/system
Sent from my Nexus 5 using Tapatalk
netsyd said:
/system
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How do I go about changing the build.prop
I open the file on the phone and use text editor but does not let me save the change.
Do you need to be rooted?
icrzymonkey said:
Do you need to be rooted?
Click to expand...
Click to collapse
Rooted = Yes.
I use the text editor that's built in to Root Explorer. I'm sure there's other ways/apps but I've been using root explorer for so long that I don't even think about other options anymore.
Sent from my Nexus 5 using Tapatalk
Rom toolbox works very easily too.
Sent from the jaws of my Hammerhead!
terminal 7 said:
I went full on for the small look with maximum real estate and tablet mode apps, set dpi to 240 and get 2 separate drop downs at the top and apps go dual pane like a bigger tablet , love this look so much more ..
Click to expand...
Click to collapse
Dang. I tried this same setting, but it didn't give me the double drop-down.
rak****.sherwoodian said:
is there any way to get small icons on nexus 5 kitkat ?
i dont quite like the big icons
Click to expand...
Click to collapse
KitKat launcher in market ..
build.prop
reisa said:
Dang. I tried this same setting, but it didn't give me the double drop-down.
Click to expand...
Click to collapse
What app are you using or are you manually editing the build.prop
May be the xposed framework and app settings module may give you the result .
Or download an app called ROM toolbox and use the editor in thee app.
Good luck .
Great tips OP. For some reason, my edits made from using root explorer would not stick and revert back to 480, even after hitting "save"
Fortunately I read more advice on trying rom toolbox and it seemed to save the build prop edit to 445. I agree, it looks perfect and has the insanely sharp feel that the HTC One had.
ggoomani said:
Great tips OP. For some reason, my edits made from using root explorer would not stick and revert back to 480, even after hitting "save"
Fortunately I read more advice on trying rom toolbox and it seemed to save the build prop edit to 445. I agree, it looks perfect and has the insanely sharp feel that the HTC One had.
Click to expand...
Click to collapse
Use ES file explorer, works
I use Textdroider from market for DPI changing. It's simple and requires a restart ... voilà
Sent from my Nexus 5 using xda app-developers app
ggoomani said:
Great tips OP. For some reason, my edits made from using root explorer would not stick and revert back to 480, even after hitting "save"
Fortunately I read more advice on trying rom toolbox and it seemed to save the build prop edit to 445. I agree, it looks perfect and has the insanely sharp feel that the HTC One had.
Click to expand...
Click to collapse
Before you edit the build.prop with root explorer... at the top of all of the files in /system, you will see a mount r/o and r/w... Click r/w then make the change. Save, exit, and reboot
Sent from my Nexus 5 using Tapatalk
please donot attempt to do it manually using text editor. rather if you have rom tool box installed you get a better interface option to tweak the build prop. you can even keep the backups.
for me
460 makes a perfect gamble 4 x 6 looks decent and will keep.