Related
***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?
Hello everyone,
I am trying to use an app to adjust the resolution (or DPI) to simulate a 720p screen. However, my phone simply will not change its resolution no matter what I do. I have used the app "LCD Resolution" as well as another similar app. What I have done is to change the dpi setting in the app from 240 to 160. Then I click apply and it says I need to reboot. After reboot however, the setting has been reset to 240 again.
Can anyone tell me how to simulate a 720p screen on the Epic 4g Touch? I am using the CyanogenMod alpha 4 and I want to get as close to the experience of a Galaxy Nexus or Galaxy S3 as possible.
Could someone please help me?
Thanks so much.
Try Rom Toolbox in the market, I believe that's what most people here are using. Should be under build.prop tweaks set it to 160 and reboot.
https://play.google.com/store/apps/...wxLDMsImNvbS5qcnVtbXkubGliZXJ0eS50b29sYm94Il0.
If you have the root explorer app you can go to the build.prop located in system yourself and change the lcd density value yourself (you have to scroll down a bit). Make sure you mount as Read/Write so you actually change it instead of just viewing it.
Also a side note, you're not changing the resolution, only the density of the pixels packed. The resolution can't be changed on this device, nor any of the current Android devices for that matter.
The only one that worked for me was lcd resolution (root), by wemobs labs. I tried a few others, but they didn't change anything.
Sent from my Galaxy Nexus using XDA
If you like a tighter crisp viewing experience, I can confirm that adjusting DPI down to 540 is stable.
I use Texdroider DPI, works with 5.1 :good:
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
WARNING: Be careful, setting too low can bootloop your phone
It's your phone, your responsibility.
Could you maybe upload some screenshots to see how it looks. Im a little worried about getting a bootloop
Sent from my VS986 using XDA Free mobile app
Screenshots
I am experiencing no side effect or lag with DPI change.
On a side note-
There are several Nandroid backup options available, I use online Nandroid Backup w Nandroid Manager
Does this require root>?
wrichards2009 said:
Does this require root>?
Click to expand...
Click to collapse
Yes.
By stable, do you mean LG camera works too!? I tried 520 over the weekend and it kept FC, didn't think there was a sweet spot!
@540 camera works great. I haven't taken it down to 520.
Good feedback thanks
Ok, so I did this like I have on any other device by adjusting the build.prop with root explorer and I entered 540. And now I am in a boot loop.. any suggestions?
2 hours later.. had to flash stock firmware.
This is mine at 580. 540 starts to make things a little too small for these old eyes.
JacRyan said:
Screenshots
I am experiencing no side effect or lag with DPI change.
Click to expand...
Click to collapse
Even shortcuts on the lockscreen?
fr4nk1yn said:
Even shortcuts on the lockscreen?
Click to expand...
Click to collapse
I dont use shortcuts on my lockscreen.
Enabled 5 to test. All sized and working correctly.
Unable to screenshot lockscreen but no issues
JacRyan said:
I dont use shortcuts on my lockscreen.
Enabled 5 to test. All sized and working correctly.
Unable to screenshot lockscreen but no issues
Click to expand...
Click to collapse
thanks. The adb method causes weirdness like blank shorcuts. I may have to break down and root.
540 working great thanks
The only issue I have with 540 is you can no longer switch between saving to the MicroSD card vs internal in the LG camera app.
For the record
If you want to change to 540dpi I would without a doubt use Kernel auditor or Es File Manager. If you edit your build prop with Root Explorer you will boot loop! Root Explorer opens the G3/G4 build prop in a TRuncated mode because the file is too large and when you save that file it will only save the available truncated portion, BE CAREFUL AND PAY ATTENTION. Setting to 540 dpi will not effect anything on your device, all other posts and problems are due to other issues. Please read and save yourself the KDZ flash time, friends.
Thank you
It doesn't require root.
Enable developer mode, and usb debugging.
Use Minimal adb and fastboot
open the folder
shift right click open command prompt from there
type adb shell wm density 540
This works on any device without root
I did 540 dpi today and I have to say I really like it. Everything is a bit smaller now, it has more like a tablet feel rather than a phone. But you get quite a bit more content on the screen, and for myself it's the perfect balance between readability and usability.
endleesss said:
It doesn't require root.
Enable developer mode, and usb debugging.
Use Minimal adb and fastboot
open the folder
shift right click open command prompt from there
type adb shell wm density 540
This works on any device without root
Click to expand...
Click to collapse
Yup this is how I do it. Lowering the DPI was one of the main reasons why I wanted root. Now I don't even care about root. I love the LG software and tweaks so there is not much I would change. I do like some XPOSED Status bar tweaks to do center clock and hide some of the million icons (alarm, nfc, location, vpn, 4G/3G, Cellular strength, WiFi etc.). LG goes overboard with icons man. I just want a 4G/3G+Signal & Battery OR WiFi & Battery. 2 icons max. Plus a clock of course... an option for a Center clock would be awesome.
There is a big difference changing dpi with adb shell wm density vs texdroider_dpi app. For me at least, when i change dpi with adb shell, some apps don't work right, like:
ebay: the menu that shows your profile pic and links to home watching, etc is screwed up
amazon: product pics, when you enlarge, you can't zoom in & out, can only see the top left corner
tinycam: on a single camera view, the video feed is zoome in about 10x
with textdroider, all of those apps work properly. Did anyone else experience this?
I have done 530 with adb command, but not with texdroider, is it safe to change to 530 with texdroider?
They should both be the same output. Although not all density settings are equal. Some settings cause weird issues like what you posted. I think I use 540 and don't experience anything weird.
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.
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.