Who has changed their DPI?
What have you changed it to?
Have you encountered any issues?
vinokirk said:
Who has changed their DPI?
What have you changed it to?
Have you encountered any issues?
Click to expand...
Click to collapse
If you change DPI even without rooting Android Pay won't work
what's the stock DPI? 240 I hope
Changed mine as soon as I got it. Everything is too big with the default DPI so using 400 atm, I tried 360 but it changed into tablet mode.
Born<ICs;4924608 said:
what's the stock DPI? 240 I hope
Click to expand...
Click to collapse
Good luck reading the display at 240 dpi. The lowest I used on my Nexus 6 was 400 and that's on a bigger screen
Pilz said:
Good luck reading the display at 240 dpi. The lowest I used on my Nexus 6 was 400 and that's on a bigger screen
Click to expand...
Click to collapse
Oh sorry, don't have phone. 240 is stock font on my tablet so I don't know
Born<ICs;4924608 said:
Oh sorry, don't have phone. 240 is stock font on my tablet so I don't know
Click to expand...
Click to collapse
Well yeah on a tablet its a different story because the screen is a lot bigger. It's the DPI bkt a font which is how everything is scaled
I know nothing about changing dpi, but can it be done without root?
Sent from my Nexus 6P using Tapatalk
Davidinks said:
I know nothing about changing dpi, but can it be done without root?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes if you did a little research you would have found that answer.
You need to have ADB on your computer then run these commands:
adb devices (make sure it finds your phone and you allow it to connect by hitting ok on your phone when prompted)
adb shell
wm density xxx && reboot (the xxx refers to the new density you want. The 6P stock is probably at 560DPI)
Pilz said:
Yes if you did a little research you would have found that answer.
You need to have ADB on your computer then run these commands:
adb devices (make sure it finds your phone and you allow it to connect by hitting ok on your phone when prompted)
adb shell
wm density xxx && reboot (the xxx refers to the new density you want. The 6P stock is probably at 560DPI)
Click to expand...
Click to collapse
I found that by doing this, it caused some issues. Mainly, on my Nexus 6, it caused some image problems throughout the Play Store. But if I changed the DPI in the build.prop, those issue did not exist.
Stock is 560. I changed mine to 400 with no adverse affects. Although I immediately change the DPI on any device I use.
388 is the lowest you can go before tablet mode change.
And I changed mine without root with a simple adb command:
Adb shell wm density 388
Is there a tool that can change the DPI rather than us having to do the script?
I have my Nexus 6P connected to my PC with the short cable it came with and when I do ADB Devices it comes up with nothing at all. In Windows Devices it registers that it knows it is a Nexus 6P but i cannot browse to the files on the phone or anything So i am not certain why the phone is not showing up on the PC.
**Update**
Figured out why it was not showing up on my PC and I was able to get it working via the PC rather than using an app. Thanks folks
littleneutrino said:
Is there a tool that can change the DPI rather than us having to do the script?
I have my Nexus 6P connected to my PC with the short cable it came with and when I do ADB Devices it comes up with nothing at all. In Windows Devices it registers that it knows it is a Nexus 6P but i cannot browse to the files on the phone or anything So i am not certain why the phone is not showing up on the PC.
Click to expand...
Click to collapse
use https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=en
Thanks for the quick link but is there a tool that does not require root?
stuff said:
I found that by doing this, it caused some issues. Mainly, on my Nexus 6, it caused some image problems throughout the Play Store. But if I changed the DPI in the build.prop, those issue did not exist.
Click to expand...
Click to collapse
it does change it system wide and if I'm not mistaken that include the build prop as well. I used this on and the build prop edit on different occasions and never had any issues other than Android Pay not working with a custom DPI.
I have changed the DPI though build.prop and Google search is gone from the recents menu. I've tried flashing the factory image and a new rom and still can't get the bar to appear. I've used 380,400,420, 480 and I'm at 500 now.
osi13 said:
I have changed the DPI though build.prop and Google search is gone from the recents menu. I've tried flashing the factory image and a new rom and still can't get the bar to appear. I've used 380,400,420, 480 and I'm at 500 now.
Click to expand...
Click to collapse
Does it come back when you say the DPI to stock?
@Pilz will changing to other "stock" dpi, for example 480, allow android pa pay continue to function?
I've set the DPI to 440 using the ADB method and nothing seems to be broken so far.
Looks so much better than the default.
Not able to test Android Pay as it's not available in my country yet.
Related
I saw a post recently about changing lcd density higher will revert the launcher to Gingerbread looking launcher. I prefer to still have the HC launcher, but thought that a higher lcd density might make the fonts and widgets bigger. I've done this on my Nook Color running CM7, and I just love how it looks at 200. I'm just scared to mess around with the A500 right now without nandroid backup possible. Anybody brave enough to try to change their lcd density yet? Please post some screen shots if you did and at what lcd density you have set it. Thanks!
I changed it to 300 and I changed to 100.
At 100 it looked really great when going through browsers since it gave you a full view though the text was a bit small.
at 300 it looked like a phone with big icons and text
Keep in mind that the settings revert after you reboot
Shigster said:
I changed it to 300 and I changed to 100.
At 100 it looked really great when going through browsers since it gave you a full view though the text was a bit small.
at 300 it looked like a phone with big icons and text
Keep in mind that the settings revert after you reboot
Click to expand...
Click to collapse
How can we change the LCD Density? Is is possible on unrooted device?
modify build.prop... changing the ro.sf.lcd_density value
Sent from my A500 using Tapatalk
minotauri said:
modify build.prop... changing the ro.sf.lcd_density value
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
or you can use this app though it needs SU access
https://market.android.com/details?i...=search_result
tried 170 and 180 but no luck getting the gingerbread ui......
eliteone said:
tried 170 and 180 but no luck getting the gingerbread ui......
Click to expand...
Click to collapse
try 220, should be work
Shigster said:
Keep in mind that the settings revert after you reboot
Click to expand...
Click to collapse
Any idea why the change in settings won't stick after a reboot? It's not convenient to keep on changing the setting since every change also needs a reboot to take effect.
Shigster said:
or you can use this app though it needs SU access
https://market.android.com/details?i...=search_result
Click to expand...
Click to collapse
Can anybody else not click that link? Takes me to exactly the link shown, '...' and all.
Build.prop is overwritten on startup by those pesky iconia devs. Not sure if this can fixed or not, gotta find where it happens.
akkidy said:
Any idea why the change in settings won't stick after a reboot? It's not convenient to keep on changing the setting since every change also needs a reboot to take effect.
Click to expand...
Click to collapse
Changing to anything >200 caused it to fail on boot before it was rewritten. It just hung at the boot logo.
I managed to get in with adb and reset it, but I'd highly recommend against trying this.
_motley said:
Build.prop is overwritten on startup by those pesky iconia devs. Not sure if this can fixed or not, gotta find where it happens.
Click to expand...
Click to collapse
Ugh! I wouldn't bother changing it then, if that's the case. Just too much work rearranging widgets every reboot. Thanks for the information.
bricked 2 iconias this way before cwm was possible.
cant recommend lcd changing.
Whats the best solution or whats recommended?
Greetz
Hiarni
I ran at 120 for a while with very good success until i noticed that 90% of what was on the market wasn't compatible with my device. I had to change it back.
I used "LCD Resolution" which can set at boot and works pretty well.
Anyone know a way past the incompatible market stuff?
Well, from the looks of things, I set mine to "leave it the heck alone"
hiarni said:
Whats the best solution or whats recommended?
Greetz
Hiarni
Click to expand...
Click to collapse
ro.sf.lcd_density=200. This is the best
i think this is the simple way..instead messing with the non working 3rd party app
larrylong said:
ro.sf.lcd_density=200. This is the best
Click to expand...
Click to collapse
just copy the build.prop from your system folder to ur computer..open it in notepad 2
next press crtl+F and type density..
you will find to rows with density written in it..i guess its 75 and 76 row..
on the right side of the density it is showing 240 change it to 200...and 200 is very good...
make it 200 in both the rows..
save it..
copy it in ur sd card...open root explorer in ur device...copy that build.prop file from the sd card folder..
now on the right corner..mount it as R/W...and paste it in the system folder...overwrite and reboot...
ta da...
For those changing lcd density you have to re-apply your edits after each rom/nightly flash. This method prevents that by overriding lcd density by using a local.prop file in /data.
1) Restore stock lcd density in build.prop: either undo the manual edits you did, or reflash your rom .zip to restore the build.prop to stock
2) Get one of these files based on the density you liked to use: lcd-density-120 or lcd-density-132
3) Rename it to "local.prop" and save it in /data (the root of the /data folder) - if you're on your touchpad then use any file manager to do this, or download to pc and adb push to /data
4) Reboot
This should override the 160 lcd density in /system/build.prop and it will survive rom flashes and incremental updates with goo manager for my nightlies (until you wipe /data obviously). Of course you can reverse the changes by simply deleting the file and rebooting.
You are welcome to try to add other mods using this method but not all will work, and for some reason not all apps/games read local.prop.
The files I posted just contain
"qemu.sf.lcd_density=132" which overrides "ro.sf.lcd_density=132" in /system/build.prop.
You can reply to this thread with other mods that you found to be working.
nice! THanks!
thanks!
has anyone gotten the latest chrome to work work on non-standard dpi's though? Considering it is my most used app, it kinda stopped me from using a dpi other than 160.
hockey4life0099 said:
thanks!
has anyone gotten the latest chrome to work work on non-standard dpi's though? Considering it is my most used app, it kinda stopped me from using a dpi other than 160.
Click to expand...
Click to collapse
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
This is a nice mod, thanks.
murso74 said:
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
the iPad2 has actually the same resolution but noone ever mentioned it.
it's awesome how the resolution actually changes but causes a lot of different problems with i.e. folders.
murso74 said:
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
yeah, so ive been stuck on 160 for a week now and it's not as bad as i thought it would be. If there is ever a fix id be happy to try it though. Not sure why one version it would work great but on the next it would force close. Maybe the next official update will solve our problems.
Thanks, this definitely saves some time and comes in handy!
Works as it should. I just wish 132 and 120 didn't distort much of the cm9 interface.
Does this work for any build prop entry? I would like to override a ro.ril setting....would I just use qemu.ril, and how can I verify it's working?
Download Minimal ADB and Fastboot
Open ADB
Make sure you have USB debugging enabled on your device
enter this text
adb shell wm density 420 && adb reboot
replace 420 with your own DPI if you wish
Default DPI = 480
120 (LDPI)
160 (MDPI)
213 (TVDPI)
240 (HDPI)
360 (XHDPI)
480 (XXHDPI)
640(XXXHDPI)
Device will reboot and your new dpi will be set
UPDATE ROOT METHOD (FULLY FUNCTIONAL)
EDIT BUILD.PROP & add ro.sf.lcd_density=360
thanks!
maybe you should note that default density is 480
I would love to know what dpi you guys and other members are using. Anyone interested in sharing screenshots of different dpi on the opx?
primemonitor said:
I would love to know what dpi you guys and other members are using. Anyone interested in sharing screenshots of different dpi on the opx?
Click to expand...
Click to collapse
I'm loving 420, 480 is far to big and makes the screen feel small
Rossyyy said:
I'm loving 420, 480 is far to big and makes the screen feel small
Click to expand...
Click to collapse
Could you please share some screenshots too?
I am rocking 380
Can i set resolution through adb? I would like to set it to 1600x900
Rossyyy said:
I'm loving 420
Click to expand...
Click to collapse
Who doesn't
I'm good with 480, i don't think it's worth changing. But i wouldn't mind seeing some screenshot so i could have an idea of what it looks like
PoloB49 said:
Who doesn't
I'm good with 480, i don't think it's worth changing. But i wouldn't mind seeing some screenshot so i could have an idea of what it looks like
Click to expand...
Click to collapse
It is looking very good at 420 but swiftkey and contacts do not work properly anymore. Anyone else with this problem?
Vennesch said:
It is looking very good at 420 but swiftkey and contacts do not work properly anymore. Anyone else with this problem?
Click to expand...
Click to collapse
Swiftkey sadly has problems with different dpi settings since some months Although contacts look fine here on 420 dpi.
Vennesch said:
It is looking very good at 420 but swiftkey and contacts do not work properly anymore. Anyone else with this problem?
Click to expand...
Click to collapse
i have also problems with contacts and google play stores "recommended" icon
everything else ist working fine
using 440 dpi since 420 was too small and 480 too big
Rossyyy said:
Download Minimal ADB and Fastboot
Open ADB
Make sure you have USB debugging enabled on your device
enter this text
adb shell wm density 420 && adb reboot
replace 420 with your own DPI if you wish
Default DPI = 480
Device will reboot and your new dpi will be set
Click to expand...
Click to collapse
Nice tip - also works in terminal emulator if you aren't near a computer with adb (like me), although obviously you need to remove "adb shell" from the beginning of the command. I previously tried to change the density with build.prop and had sketchy results. This works well for me at 380 - plenty of space!!
kornnflake said:
Swiftkey sadly has problems with different dpi settings since some months Although contacts look fine here on 420 dpi.
Click to expand...
Click to collapse
If you really need the density working with swiftkey, just add this line in build.prop
Code:
ro.sf.lcd_density=your_ppi
https://vip.swiftkey.com/index.php?/topic/10116-swiftkey-and-custom-dpi-not-officially-supported/
Vennesch said:
It is looking very good at 420 but swiftkey and contacts do not work properly anymore. Anyone else with this problem?
Click to expand...
Click to collapse
Works fine.. I am on 380 and this is how it looks
kornnflake said:
Swiftkey sadly has problems with different dpi settings since some months Although contacts look fine here on 420 dpi.
Click to expand...
Click to collapse
On 380 both contacts and SwiftKey work fine
---------- Post added at 06:40 AM ---------- Previous post was at 06:37 AM ----------
ckret said:
i have also problems with contacts and google play stores "recommended" icon
everything else ist working fine
using 440 dpi since 420 was too small and 480 too big
Click to expand...
Click to collapse
No problems with play either
SpiritBreak3r said:
If you really need the density working with swiftkey, just add this line in build.prop
Code:
ro.sf.lcd_density=your_ppi
https://vip.swiftkey.com/index.php?/topic/10116-swiftkey-and-custom-dpi-not-officially-supported/
Click to expand...
Click to collapse
you need root for this
kornnflake said:
Swiftkey sadly has problems with different dpi settings since some months Although contacts look fine here on 420 dpi.
Click to expand...
Click to collapse
I use Fleksi, better than swiftkey in my opinion
primemonitor said:
Could you please share some screenshots too?
Click to expand...
Click to collapse
Here
Funk Wizard said:
Works fine.. I am on 380 and this is how it looks
Click to expand...
Click to collapse
Is that a One X, how did you get all the extra icons?
Funk Wizard said:
Works fine.. I am on 380 and this is how it looks
Click to expand...
Click to collapse
No issues here on 380 either.
ps: what's the fond in your swiftkey please
Anyone knows how to change the default DPI on the g4 without ROOT???
Plug in your device and make sure dev usb is on and ADB is installed. Open a command line and use:
Adb shell wm density *** (where *** is your prefered DPI)
it will change in real time. However, 400 is the smallest you can go with the stock G4 firmware before goofball stuff starts to happen with the camera app and whatnot.
MadGoat said:
Plug in your device and make sure dev usb is on and ADB is installed. Open a command line and use:
Adb shell wm density *** (where *** is your prefered DPI)
it will change in real time. However, 400 is the smallest you can go with the stock G4 firmware before goofball stuff starts to happen with the camera app and whatnot.
Click to expand...
Click to collapse
Thank it work for me
(PS: Default DPI is 480 ^^)
So what's the optimal dpi setting people are changing to?
400 is a very good choice. Similar to many other big screen phone displays.
I just switched to 400 DPI and everything looks a better, but I have visual glitches in Twitter (screenshot attached) and Snapchat. I tried rebooting and reinstalling the apps and got nothing fixed. Just curious if anyone has seen these and if there's any good idea how to address them.
birch25 said:
I just switched to 400 DPI and everything looks a better, but I have visual glitches in Twitter (screenshot attached) and Snapchat. I tried rebooting and reinstalling the apps and got nothing fixed. Just curious if anyone has seen these and if there's any good idea how to address them.
Click to expand...
Click to collapse
Yes. I just switched to 400 and see the same image error in Twitter. When clicking through to the full image everything is normal, but the main feed image is like your screenshot.
I haven't noticed anything else malfunctioning.
zzzfrzz said:
Yes. I just switched to 400 and see the same image error in Twitter. When clicking through to the full image everything is normal, but the main feed image is like your screenshot.
I haven't noticed anything else malfunctioning.
Click to expand...
Click to collapse
Yup,same on this end. Not the end of the world, but I use Twitter more than anything else, of course ?
birch25 said:
Yup,same on this end. Not the end of the world, but I use Twitter more than anything else, of course ?
Click to expand...
Click to collapse
It's hit and miss on apps. I did a soak on the G3 and they sent a soak with a different DPI and my banking app and a couple of others didn't work. I raised the devil with the app developers until I discovered the foreign DPI. I had to eat crow on that one.
Stock with Android 7.0
I am on stock rom with android 7 and have my DPI set to 320.
Everything works perfectly fine.
Hi all.
What is the minimum DPI for the G4 using stock LG software?
For the G3 it was 528. I see 540 mentioned here a bit so wondering if on G4 the lowest DPI is 540 or 528?
TIA
I'm using 538 at the moment. I read that it was the lowest possible.
530 was the lowest for me.
I use App Setting Xposed module to set non LG apps to lower values.
theKramer said:
Hi all.
What is the minimum DPI for the G4?
For the G3 it was 528. I see 540 mentioned here a bit so wondering if on G4 the lowest DPI is 540 or 528?
TIA
Click to expand...
Click to collapse
I use 520 since a while. See screenshot.
.
steadfasterX said:
I use 520 since a while. See screenshot. .
Click to expand...
Click to collapse
Hi.
I forgot to specify on stock LG software. I'm gonna wait a little while before unlocking the bootloader. Make sure everything is working as it should before destroying my warranty
WMaddler said:
530 was the lowest for me.
I use App Setting Xposed module to set non LG apps to lower values.
Click to expand...
Click to collapse
If I get issues with apps crashing, I can still change the DPI via ADB, can't I ? There's nothing that prevents that right?
theKramer said:
If I get issues with apps crashing, I can still change the DPI via ADB, can't I ? There's nothing that prevents that right?
Click to expand...
Click to collapse
Yes, you should able to.
What I usually do is setting LG apps DPI to default (640) or anything => 530 using App Settings xposed module, that would put you on the safe side.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
steadfasterX said:
I use 520 since a while. See screenshot.
.
Click to expand...
Click to collapse
Which app is that?
maddler said:
Yes, you should able to.
What I usually do is setting LG apps DPI to default (640) or anything => 530 using App Settings xposed module, that would put you on the safe side.
Click to expand...
Click to collapse
Not a bad idea that
maddler said:
Which app is that?
Click to expand...
Click to collapse
Screen Shift. Requires root of course. Can use per app profiles and let you choose the resolution as well..
.
theKramer said:
Not a bad idea that
Click to expand...
Click to collapse
I know
Been doing that on various devices/ROMS when I had issues with custom DPI
I have never tried Dpi changer like apps. I want to know that does it take phone to bootloop if there is something gone wrong?
xdaorxan said:
I have never tried Dpi changer like apps. I want to know that does it take phone to bootloop if there is something gone wrong?
Click to expand...
Click to collapse
So just as an FYI, the G4 goes down to 528 without issue.
I didnt go any lower since lower than 527 would cause SystemUI errors on the G3 on stock, so G4 is probably the same...
Why would you want to lower the DPI? To safe battery? Does it make any difference?
BrotherZero said:
Why would you want to lower the DPI? To safe battery? Does it make any difference?
Click to expand...
Click to collapse
It makes all elements in the screen smaller, so you can "fit" more into your screen.
Personally I find the text too big with the standard DPI, so I reduce the DPI to make everything smaller.
Its easy to change and only requires a restart to enable. One just needs to be sure to not go below 527, as that will give continuous errors related to SystemUI.
You need adb installed and then you run the following command from a command prompt, where ADB is located:
adb shell wm density 528 && adb reboot
You can change 528 to whatever you want (between 528 and 640) ...
theKramer said:
It makes all elements in the screen smaller, so you can "fit" more into your screen.
Personally I find the text too big with the standard DPI, so I reduce the DPI to make everything smaller.
Its easy to change and only requires a restart to enable. One just needs to be sure to not go below 527, as that will give continuous errors related to SystemUI.
You need adb installed and then you run the following command from a command prompt, where ADB is located:
adb shell wm density 528 && adb reboot
You can change 528 to whatever you want (between 528 and 640) ...
Click to expand...
Click to collapse
My only problem is the faulty app drawer button of the stock launcher, on custom dpi's...
steadfasterX said:
I use 520 since a while. See screenshot.
Click to expand...
Click to collapse
do you use that on custom ROM? or stock ? cuz stock will have all LG apps crashing ..
iiD4x said:
do you use that on custom room ? or stock ? cuz stock will have all LG apps crashing ..
Click to expand...
Click to collapse
Custom. RR
polfrank said:
My only problem is the faulty app drawer button of the stock launcher, on custom dpi's...
Click to expand...
Click to collapse
I use Nova launcher, so don't have that issue..