Develop Bugs

[INFO][HOWTO] Official Galaxy Nexus LCD Density Modding Thread

***REQUIRES ROOT***
This thread will serve as a discussion for modifying the LCD Density of the Samsung Glaxy Nexus. Stock density is 320 dpi, and the preferred modded density is 240 dpi. Please feel free to discuss lcd density, and notify me of anything you want added to the list.
Why modify the lcd density of your phone? Simple answer: more screen real estate.
1. How to modify you lcd density
Note: You can always go back to 320 dpi at any time by following these same steps and putting 320 back in for 240!
240 dpi is the recommended modded dpi for the Galaxy Nexus. You can however set it to whatever you want. Just know that many dpi's will cause the on screen buttons to disappear, and even possibly cause the launcher to crash. In both cases you can use the adb method to restore to 240 or 320.
241 dpi is also a good number to try. It fixes the problems some apps have when running at 240 dpi. Credit goes to g33k3r. However it will cause market incompatibilities. Read #6 to fix this.
246 will fix the contact widget, and quick contact, but it will use the old style contact info which shows a large contact image above their info, not small and to the side. Credit goes to maddler.
250 dpi OR 260 dpi OR 280 dpi are also good values if you would like a smaller than stock value, but 240 is too small for you.
Method 1 (Using an app):
Download LCD Density Modder (Free) / LCD Density Modder Pro from market. Set density to 240 or 241, apply, then reboot. There are multiple different apps that can change your dpi, but this app is guaranteed to work on the Galaxy Nexus.
Method 2 (Modify a file):
Using Root File Explorer or a similar program, modify /system/build.prop file (must mount /system as r/w).
Replace:
ro.sf.lcd_density=320
With:
ro.sf.lcd_density=240
Save and reboot.
Method 3 (Using adb):
adb pull /system/build.prop C:/build.prop
In build.prop, replace:
ro.sf.lcd_density=320
With:
ro.sf.lcd_density=240
adb remount
adb push C:/build.prop /system/build.prop
Reboot phone.
2. Apps where UI is different on 240 dpi (for better or worse, ui elements have been rearranged, but none are broken)
Launcher: Home screen icons are still 4x4 and squished into the center of the screen. App drawer and Widget drawer do not fill. There is a mod that fixes this in this thread: FIX HERE
Market: Now has 2 columns instead of one when listing apps.
Gmail: Quick access icons have been romved from the bottom and placed on the top. Only first two icons are visible, other are collapsed into the drop down menu.
People: Contact info now has a two column layout: a small icon of contact on left (static) with all of the contact info as a scrolling pane on the right (no visible divider). Favorite contact icons are much smaller.
3. Apps where UI is broken, but still useable
Sports Tracker: Some interface items dont stretch to fill the screen.
ADW /ADW Ex Launcher: There is a blue line and a menu icon above the homescreen at all times.
Speedtest.net: App shows up centered on screen, not filling whole screen.
Kindle: It still works but the text is now centered in the middle and there is a large amount of paddling around it.
4. Apps where UI is completely broken
Music: App displays incorrectly at 240 dpi. Run at 241 to fix this
5. Android UI glitches
Sometimes when selecting text the menu bar on the top of the screen will have a weird blue streak across it.
Stock ICS keyboard the popup when you press a key seems like it gets clipped off a little on the bottom.
Clicking the picture of a contact either from the people app, or from a 1x1 contact widget you no longer get the quick access popup, instead it is now the person's contact picture blown up to full screen and half cut off on the right side.
6. Market apps incompatable with device (according to market)
None that I know of. Since 240 dpi is a standard dpi for most android phones, I don't envision very many apps being incompabile. If you find an app that the market say is incompatible, you can try setting your density back to 320 temporarily in order to download it.
For those with market issues on a non-standard dpi (241, 250, 260, 280 etc.), try this:
1. Boot your phone into 320 or 240 dpi mode (depending on which kind of compatibility you want).
2. Find the Market app under manage apps. Click uninstall updates, clear data, clear cache.
3. Find Market Updater under manage apps and click Disable.
4. Open Market and accept terms of service.
5. Change dpi back to 241 and reboot.
Alternatively, LCD Density Modder Pro has the ability to download and install a modded market apk to fix market compatibility issues.
Click to expand...
Click to collapse
7. Apps that crash (with possible workarounds)
Youtube: Will crash on start. Open from landscape mode! Youtube will not crash if openened in landscape mode. You can also open youtube links from the browser and other apps just fine.
8. Before and After Photos (320 dpi on left, 240 dpi on right):
***CLICK ANY SCREENSHOT TO VIEW FULL SIZE!***
Settings:
People:
Contact Info (note that the bottom bar has merged into the top bar):
Android Market:

***RESERVED***

can you provide a screenshot?
like a before/after pic.

I think this is crazy.
The stock DPI is amazing.
Get an SGSII if you want an old-school resolution or have bad eyes.
My stock DPI is absolutely beautiful...

ericshmerick said:
I think this is crazy.
The stock DPI is amazing.
Get an SGSII if you want an old-school resolution or have bad eyes.
My stock DPI is absolutely beautiful...
Click to expand...
Click to collapse
You are completely missing the point. On Android when you change the DPI, you are essentially telling android the size at which to "scale" all objects on the screen. Notice how the Galaxy Nexus has a 720p screen yet you can only fit 4x4 icons on the desktop like the Galaxy S2? Well that is because the 320 dpi is telling android to scale those things bigger. Setting it to 240 dpi will make everything smaller and give you more screen "real estate". The resolution is still 720p.
You mention having bad eyes, but when you lower the dpi you actually need GOOD eyes because everything is smaller and harder to read if you have bad eyes.
paOol said:
can you provide a screenshot?
like a before/after pic.
Click to expand...
Click to collapse
I am going to post some screenshots later today.

YouTube crashes on launch for me when set to 240 DPI. I have not performed a wipe, though I have tried wiping the settings and cache for the app.

LadFromWales85 said:
YouTube crashes on launch for me when set to 240 DPI. I have not performed a wipe, though I have tried wiping the settings and cache for the app.
Click to expand...
Click to collapse
Ah yes, thanks for reminding me. YT crashes for me as well, however if you have the widget you can click one of the videos and it will open that video. You can search for videos from there, but you cant access the home page for some reason.
EDIT: It turns out if you open youtube in landscape mode it will work!

Well thx for the Tip with the density. But however...When I start DPI Changer I get an error "Unable to read configuration file"
Any ideas?
Sent from my Galaxy Nexus using My Thumb...

Kizura said:
Well thx for the Tip with the density. But however...When I start DPI Changer I get an error "Unable to read configuration file"
Any ideas?
Sent from my Galaxy Nexus using My Thumb...
Click to expand...
Click to collapse
Are you rooted? This requires root.

for sure iam rooted...it was the first thing i have done... and i have ARHD Custom rom installed.
Sent from my Galaxy Nexus using xda premium

Kizura said:
for sure iam rooted...it was the first thing i have done... and i have ARHD Custom rom installed.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Do you have Root File Explorer? You can use the second method i listed to change the build.prop file. You can also use adb to pull the file locally, edit it, and push it back to the phone.

Oh ok then I will do it manually
I will report back soon ...I hope xD
Sent from my Galaxy Nexus
Edit: Ok this is more awesome as it was on my DHD !!!
Really thank you for that great Tip and the Help

Kizura said:
Oh ok then I will do it manually
I will report back soon ...I hope xD
Sent from my Galaxy Nexus
Edit: Ok this is more awesome as it was on my DHD !!!
Really thank you for that great Tip and the Help
Click to expand...
Click to collapse
Awesome. Make sure to check out my modified home screen launcher to get the full effect:
http://forum.xda-developers.com/showthread.php?t=1390935
Also, if you find any apps that don't display properly or something else is wrong with them (when running in 240 dpi), please post back in this thread to help inform others.

Mhh I use adb launcher... but on top of the screen is now a blue horizontal line with the three dots for options on the right side....
Will your mod take care of this? I hope you know what I mean...
Sent from my Galaxy Nexus

Kizura said:
Mhh I use adb launcher... but on top of the screen is now a blue horizontal line with the three dots for options on the right side....
Will your mod take care of this? I hope you know what I mean...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I have ADW Ex launcher and i see that as well. It is the default titlebar and menu system for apps in ICS. Did you experience this when in 320 dpi as well or only in 240? I haven't tested it in 320.
And no, my mod only affects the stock launcher so it will not fix your problem.

No with 320 dpi that line doesn't appear its there since I have 240 Dpi...
Tested your Launcher replacement...
Great Work
But as you said it will not fix this "line affect" in adw
Maybe in a future update in adw launcher it will be fixed.
Sent from my Galaxy Nexus

I added photos to the main post now. Click on any photo to view the original size image!

Awesome, really cool. Trying it out today to see if I like it.
Another noticed bug - if you have a contact on your home screen (single icon version), which normally pops up the quick box for the contact, this now just seems to pop up their display picture and nothing else.

I see what you mean about the contact. It also happens when in the people app and you click their picture. I added it to the first post. thanks.

I thought changing the DPI would enable the ICS for tablets UI?

Density Change - Root/build.prop method

Gents,
I wasn't impressed with the display density on my G4. Appears to have been developed for the legally blind. So I attempted the ADB method and realized (like everyone else) there were a lot of glitches. Snapchat/WhatsApp picture cropping was massively zoomed etc.
So I rooted my device. All went well, everything else root works perfect. However attempting to use Texroider results in the Density being changed (according to the app) but nothing happening after a reboot. It looks identical.
So i attempted to edit the build.prop manually. Again editing the ro.sf.lcd_density and saving, after a reboot it still reflects the value I set (540/560) yet their is no visual change.
For some odd reason my device isn't reflecting the changes. Using the ADB method the device was showing the changes, albeit with the graphical/app glitches.
Anyone have ideas I'm stumped.
Cheers

open adb and type this in to it.
adb shell wm size reset
adb reboot
Then you can change dpi in build.prop file.

You need to the command mentioned here to reset the adb dpi changes you made as you set it to default instead of turning it off.
THOUGH afterwards I'd just stick with textdroider rather than modding your build.prop when finished.
TIP: Use App Settings with Xposed to set your Camera app to stock 640, as it removes the option to save internally or to SD and picks what it wants. Also there's some graphical glitches with some stock apps at lower DPI that you can fix on a per-app basis.
Also... For some reason Google Maps really hates when I change DPI on it and gives me blue rendering artifacts everywhere so I had to change it to stock.

Appreciate the help, unfortunately it had no effect. Obviously it is doing something as Swiftkey goes into massive zoom mode, but my launcher (ADW) and everything else remains the same size.

Yea, I would have thought resetting DPI with ADB, then using Textdroid would work. Could it be something in the cache needing cleared?
Maybe you might need to backup everything up, then reflash a kdz file then use Textdroid.

Changing lcd density (DPI) problem

I'm facing an issue when changing lcd density (DPI) using build.prop editor, some widgets which was working on OP1 CM 11,12,13, are not displayed fine now. also Play store has some resolution issues, like recommended developer icon !
I tried different resolutions (380,400,420,460) all with the same results.
Any clues ?

Don't change DPI globally, that's problem-prone. Instead, install Xposed with module "App settings" and change DPI only for those apps where you want it. (Another advantage is that you even additionally have more flexible options, like changing text size or using the app's tablet UI etc.)

zorro_tmh said:
I'm facing an issue when changing lcd density (DPI) using build.prop editor, some widgets which was working on OP1 CM 11,12,13, are not displayed fine now. also Play store has some resolution issues, like recommended developer icon !
I tried different resolutions (380,400,420,460) all with the same results.
Any clues ?
Click to expand...
Click to collapse
hasenbein196601 said:
Don't change DPI globally, that's problem-prone. Instead, install Xposed with module "App settings" and change DPI only for those apps where you want it. (Another advantage is that you even additionally have more flexible options, like changing text size or using the app's tablet UI etc.)
Click to expand...
Click to collapse
I changed it globally with the app "Le DPI Changer" to 360 and don't have any problems in any app.

440 is great..

i have set the dpi to 380 and have problems in the following apps:
twitter: pictures in tweets have corrupted thumbnails
whatsapp: when you want to crop a picture, it is zoomed in very much and you cannot zoom out so you can only crop 10% of an image
imgur: corrupted thumbnnails too
music player (poweramp) cover art in player notification is zoomed
i think oxygen os handles dpi differently, as i couldnt even find dpi setting in build.prop
i hope someone can fix this bc i would like to stay on oxygen until cm ports etc have dash charging

As I said: No global DPI, but Xposed module "App settings". Then you avoid any problems.

~MaX~ said:
i have set the dpi to 380 and have problems in the following apps:
twitter: pictures in tweets have corrupted thumbnails
whatsapp: when you want to crop a picture, it is zoomed in very much and you cannot zoom out so you can only crop 10% of an image
imgur: corrupted thumbnnails too
music player (poweramp) cover art in player notification is zoomed
i think oxygen os handles dpi differently, as i couldnt even find dpi setting in build.prop
i hope someone can fix this bc i would like to stay on oxygen until cm ports etc have dash charging
Click to expand...
Click to collapse
Hmm from the four apps you mentioned I only use WhatsApp, and I just tested out the cropping of a selfie, normal picture and a gallery picture, it works fine for me.
I'm on 360dpi.

Does anyone know the stock dpi value?

numbere said:
Does anyone know the stock dpi value?
Click to expand...
Click to collapse
480
Sent from my ONEPLUS A3003 using Tapatalk

I'm noticing font is pretty big in comparison to another 1080p device I have in my possession. It's DPI is set at 420 and what I'd consider perfect.

crysen said:
I changed it globally with the app "Le DPI Changer" to 360 and don't have any problems in any app.
Click to expand...
Click to collapse
Which method in the app did you use? I moved the DPI slider in the app, applied it, rebooted, but nothing changed...
Sent from my ONEPLUS A3000 using Tapatalk

rickyx32 said:
Which method in the app did you use? I moved the DPI slider in the app, applied it, rebooted, but nothing changed...
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Oh right, forgot to mention, use the other method, the slider also didn't work for me.

Users with issues,
try this method:
Create a file called local.prop in the root/data folder with this text in it:
qemu.sf.lcd_density=xxx
xxx = your dpi value
Permissions of that file should be:
rw-r-r--
Reboot.
I did not test it yet on OxygenOS as my device is not unlocked, nor rooted yet.

AcmE85 said:
Users with issues,
try this method:
Create a file called local.prop in the root/data folder with this text in it:
qemu.sf.lcd_density=xxx
xxx = your dpi value
Permissions of that file should be:
rw-r-r--
Reboot.
I did not test it yet on OxygenOS as my device is not unlocked, nor rooted yet.
Click to expand...
Click to collapse
That file already exists on mine and already has the desired DPI but it's not having any effect...

rickyx32 said:
That file already exists on mine and already has the desired DPI but it's not having any effect...
Click to expand...
Click to collapse
Use the Le dpi changer from google play, set dpi value and hit build.prop button. Accept it and reboot.
OP3 by TT

i tried to change dpi with ledpi and now my build.prop file is empty and broken. can someone upload build.prop from latest oxygen os please?
EDIT: default.prop in root can be used as a new build.prop in case u get the same problem as me, no need for upload

Anyone know where I can change DPI manually? I can't find the code in the build.prop. I don't want to rely on whack apps or toolkits...
Sent from my ONEPLUS A3000 using Tapatalk

rickyx32 said:
Anyone know where I can change DPI manually? I can't find the code in the build.prop. I don't want to rely on whack apps or toolkits...
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
it doesn't exist on builb.prop of OP3, I added it manually.
Code:
ro.sf.lcd_density=400

crysen said:
Hmm from the four apps you mentioned I only use WhatsApp, and I just tested out the cropping of a selfie, normal picture and a gallery picture, it works fine for me.
I'm on 360dpi.
Click to expand...
Click to collapse
i always had the cropping problem with WhatsApp using custom dpi. try to set a new profile picture. always zoomed and no chance zooming out. you have to change the dpi back to 480 to change your profile picture, but otherwise i have had no problems with 380 dpi.

My only qualm about this phone was the abnormally large text and padding in various apps, 440 dpi is a perfect adjustment, haven't seen any graphical glitches as of yet.

Camera Doesn't Work (Related to DPI Changing)

So i am running into a very strange issue that i haven't been able to find much information on. I am running the latest OOS (3.1.2) rooted, i had changed the DPI a few days ago using build prop editor and everything seemed to be working just fine, except my camera, it suddenly would freeze when a picture is taken, crash, and not produce a picture, and sometimes the picture would be just green.
Here is what iv'e tried:
removed the line from build prop editor and rebooted to get to stock DPI
changed the DPI to stock with the toolkit, then back to a different DPI, then back to stock.
removed the camera app cache
factory reset the phone
Strangely enough the camera in HDR mode appears to work just fine, but it doesn't appear to work in any other mode (including video).

Using the camera with flash always turned on in pretty much any mode seems to also work.

Atlantisman said:
So i am running into a very strange issue that i haven't been able to find much information on. I am running the latest OOS (3.1.2) rooted, i had changed the DPI a few days ago using build prop editor and everything seemed to be working just fine, except my camera, it suddenly would freeze when a picture is taken, crash, and not produce a picture, and sometimes the picture would be just green.
Here is what iv'e tried:
removed the line from build prop editor and rebooted to get to stock DPI
changed the DPI to stock with the toolkit, then back to a different DPI, then back to stock.
removed the camera app cache
factory reset the phone
Strangely enough the camera in HDR mode appears to work just fine, but it doesn't appear to work in any other mode (including video).
Click to expand...
Click to collapse
I posted about this issue a few days ago http://forum.xda-developers.com/oneplus-3/help/weird-camera-bug-t3404660

mr.shme said:
I posted about this issue a few days ago http://forum.xda-developers.com/oneplus-3/help/weird-camera-bug-t3404660
Click to expand...
Click to collapse
Sorry, didn't notice that.
I flashed back to bone stock OOS 3.1.2 and everything seems to be working now... I will attempted to change the DPI again via the toolkit.

I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.

That's why I always say that global DPI change is not a good idea, period.
Much better and additionally more flexible is using the Xposed module "App Settings" where you can run every app at an individual DPI setting and tweak some more things (e. g. having an app run with its tablet UI).

I had the same issue on OOS 3.1.3 rooted and DPI changed.
I enabled RAW mode and it fixed the issue.

crumble6 said:
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
Click to expand...
Click to collapse
What DPI value did you set it to? No issues with camera, icons, widgets, etc?

jiznon said:
What DPI value did you set it to? No issues with camera, icons, widgets, etc?
Click to expand...
Click to collapse
400. No issues at all except that when I use "large text" captions in snapchat they display fine on my screen but the text is much smaller and out of position on my friends' phones. Literally not a single other problem with any app I've tried though. I've heard 380 works good too. Tempted to try it but tbh I'm happy at 400 for now.

crumble6 said:
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
Click to expand...
Click to collapse
crumble6 said:
400. No issues at all except that when I use "large text" captions in snapchat they display fine on my screen but the text is much smaller and out of position on my friends' phones. Literally not a single other problem with any app I've tried though. I've heard 380 works good too. Tempted to try it but tbh I'm happy at 400 for now.
Click to expand...
Click to collapse
Thanks for the quick reply. So far my experience has been frustrating.
1) Changed DPI to 400 via build.prop edit. Resulted in camera issues. Could not reset DPI or change to any other value. Had to reflash OOS 3.1.3 to fix.
2) Did some research. Heard a OP3 toolkit here on xda could change DPI without issue (I believe it just uses the adb method) . Used it to change to 400. Camera is fine, but I experience wonky sizing issues with widgets, icons on notification banners, twitter photo previews, and a few other little text size issues. Tried using the toolkit to return to default DPI but it simply doesn't change anything.
3) Per your account of this app, I tried it but it us unable to make any change. Looks like I may have to reflash AGAIN, and attempt the Le DPI Changer again.
Bah.

jiznon said:
Thanks for the quick reply. So far my experience has been frustrating.
1) Changed DPI to 400 via build.prop edit. Resulted in camera issues. Could not reset DPI or change to any other value. Had to reflash OOS 3.1.3 to fix.
2) Did some research. Heard a OP3 toolkit here on xda could change DPI without issue (I believe it just uses the adb method) . Used it to change to 400. Camera is fine, but I experience wonky sizong issues with widgets, icons on notification banners, and a few other little text size issues. Tried using the toolkit to return to default DPI but it simply doesn't change anything.
3) Per your account of this app, I tried it but it us unable to make any change. Looks like I may have to reflash AGAIN, and attempt the Le DPI Changer again.
Bah.
Click to expand...
Click to collapse
Sorry, I should have mentioned. I am using Nova launcher and have changed the grid size of the desktop to 11 x 7. Things will probably behave weird if you are using the oneplus launcher.

crumble6 said:
Sorry, I should have mentioned. I am using Nova launcher and have changed the grid size of the desktop to 11 x 7. Things will probably behave weird if you are using the oneplus launcher.
Click to expand...
Click to collapse
No worries. I am also using Nova Launcher with custom grid size. Only issues on my desktop is wonky icon size with Chronus widget.

jiznon said:
No worries. I am also using Nova Launcher with custom grid size. Only issues on my desktop is wonky icon size with Chronus widget.
Click to expand...
Click to collapse
I find enabling widget overlap in Nova and then playing around with resizing widgets I can usually get them looking right in the end.

I had already posted this here but it seemed like Nobody besides me had this problem.
http://forum.xda-developers.com/oneplus-3/help/camera-issues-root-t3409764
I'm glad this issue is getting attention!

running 340 dpi, works fine for me. did it with le dpi changer

Running 290 all good using le dpi changer ?
Sent from my ONEPLUS3

I'm starting to wonder there is a magic DPI number that doesn't break the camera!! Time to test!

I found this solution on the oneplus 3 reddit. Camera works perfectly and there are no weird icons!
https://www.reddit.com/r/oneplus/comments/4satgq/changing_op3_dpi_using_buildprop_without_breaking/
Basically use qemu.sf.lcd_density=xxx instead of ro.sf.lcd_density=xxx in your build.prop!
I'm using 420 and all is awesome now!!
Huge thanks to this guy for posting the solution!!

ro.sf.lcd_density=400 in build.prop works just fine on my device running stock OOS 3.2.1.
Only manual mode is slightly misaligned inside the camera app.
Trying qemu.sf.lcd_density=400 gives me the same result btw.
I never had issues with green photos in HQ or other weird behaviour.
Running dpi 400 via manual build.prop edit since day one
and only had to repeat this after each ota.

New dpi via adb?

Hi
I'm trying to change dpi in adb. Adb finds the device but when I'm typing "adb shell wm density 380" it doesn't work.
Anyone knows why?
Thx in advance

Try going into developer options and enable the security setting to on.

What is the default dpi for mi max 3?

jutley said:
What is the default dpi for mi max 3?
Click to expand...
Click to collapse
Should be 480

Lasse58 said:
Hi
I'm trying to change dpi in adb. Adb finds the device but when I'm typing "adb shell wm density 380" it doesn't work.
Anyone knows why?
Thx in advance
Click to expand...
Click to collapse
I think Xiaomi controlled the dpi using another variable, its called persistent density or something like that.. hence changing the normal density variable wont have any impact
Sent from my ONEPLUS A6000 using Tapatalk

You can change the DPI in MIUI by going to Settings > Additional settings > Accessibilty > Display size

barro32 said:
You can change the DPI in MIUI by going to Settings > Additional settings > Accessibilty > Display size
Click to expand...
Click to collapse
The smallest display dpi is "small"... its still too large for me haha... i think without root, there is no other way
Sent from my ONEPLUS A6000 using Tapatalk

Are USB debugging & USB debugging (Security settings) both enabled?
If I recall correctly, enabling USB debugging (Security settings) is a bit tricky.

https://forum.xda-developers.com/mi-mix-2/how-to/guide-changing-min-width-dpi-miui-9-t3736218
this can be helpful for you. My dpi is now 290. If you go higher google keyboard change tablet mode.

I was able to change it using Activity Launcher using the tutorial below:
http://en.miui.com/thread-1093064-1-1.html

Default dpi is huge even at the smallest setting. I am using 320 and it's perfect, can see a lot of content without being too small
Just make sure Developer options has USB debugging (Security settings) enabled and use adb shell wm density 320
Big difference. Would be a waste to not see more content on such a big screen but also understand some people's eye sight may not be as good so they prefer bigger objects
320 vs Small setting

I used this tool to change dpi:
https://github.com/Saki-EU/XiaomiADBFastbootTools

zed011 said:
Default dpi is huge even at the smallest setting. I am using 320 and it's perfect, can see a lot of content without being too small
Just make sure Developer options has USB debugging (Security settings) enabled and use adb shell wm density 320
Big difference. Would be a waste to not see more content on such a big screen but also understand some people's eye sight may not be as good so they prefer bigger objects
320 vs Small setting
Click to expand...
Click to collapse
tried this. but it doesnt seem to work. none of the layout is changing.

yup changing dpi without root is tricky. u need to enable security usb debugging. u need to use vpn apps.

got usb debugging on.
whats vpn tools?
anyway guys, thanks much. yea i have noticed that there are two options for usb debugging. look passed the other one.
now its working.

I just upgraded from Max 2 to Max 3... LOVE that i can change the DPI without rooting... had no trouble with either phone doing this. With the Max 2 i had it at 360, but with the Max 3 i'm trying 290....i may go up to 320 just because i need my glasses to see things like the battery % lol . No clue why Xiaomi didn't drop it below 400 out of the box but thrilled i can do it easily.

Smoked33 said:
I just upgraded from Max 2 to Max 3... LOVE that i can change the DPI without rooting... had no trouble with either phone doing this. With the Max 2 i had it at 360, but with the Max 3 i'm trying 290....i may go up to 320 just because i need my glasses to see things like the battery % lol . No clue why Xiaomi didn't drop it below 400 out of the box but thrilled i can do it easily.
Click to expand...
Click to collapse
I use Font size 80%, Display size Custom (289), Smallest width 597 dp.
597 or 289dpi is the smallest dpi you can set before tablet mode is enabled in portrait mode.
If you rotate your phone watching a youtube video in full screen tablet mode is already enabled so the notification drawer is opened by swiping down on the left half side of the screen otherwise nothing will happen.
Setting Smallest width value is the easiest way to change dpi in the latest android versions.
Setting it to 596, 598 and 599 won't do anything.
It will either default back down to 595 or jump to 600 because it must represent a whole number in dpi.
It is crazy that pretty much ALL phones comes pre-configured out of the box at factory state with a dpi so large you can barely fit two words across the screen..really...I don't think anyone have this bad eyesight, if so then you need to get new glasses or lenses.
There are high index lenses out there that go to 1.9 and even beyond 2 if you really want to pay a lot if your prescription is crazy high to be able to enjoy a thin and light pair of glasses.
Like what is the purpose of getting a phone this big if you gonna have it display just as little as your old phone with third the screen size..isn't that why you wanted a bigger phone in the first place to get more screen estate, at least that's what I wanted..

SUPERUSER said:
It is crazy that pretty much ALL phones comes pre-configured out of the box at factory state with a dpi so large you can barely fit two words across the screen..really...I don't think anyone have this bad eyesight, if so then you need to get new glasses or lenses.
There are high index lenses out there that go to 1.9 and even beyond 2 if you really want to pay a lot if your prescription is crazy high to be able to enjoy a thin and light pair of glasses.
Like what is the purpose of getting a phone this big if you gonna have it display just as little as your old phone with third the screen size..isn't that why you wanted a bigger phone in the first place to get more screen estate, at least that's what I wanted..
Click to expand...
Click to collapse
I can't agree with you more. Just thankful it's so easy to change
On a side note...and i'm not sure it's related because I didnt' try before changing the dpi(i use the adb method)... my TSN app won't stream any channels. It gives me an error... i'm not sure if that's the DPI setting that caused it? Only app that doesn't work right. I'm going to have to play with that when i'm home from work as it worked on my Max 2 set at 360 no problems and the only main difference i can tell with the 2 phones is the version of Android.
Edit: nevermind it wasn't the DPI setting... i allowed TSN GO to work in full screen mode and that did it.
Love the phone!