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?

LCD Density Changer?

Has anyone been able to get any density changer apps working on their Nitro HD? I've tried all of the following, and none seem to work. It's possible there is a problem with my su access, so if anyone HAS gotten any of these to work, please let me know. That at least tells me I definitely have an su problem...
DPI Changer
LCD Resolution
LCDDensity
Root Tools

Never mind; my build.prop file was set to read only.

Excuse my ignorance, but what exactly are they for? Does the density changes only the size of text or everything including graphic become bigger/smaller?

[email protected] said:
Excuse my ignorance, but what exactly are they for? Does the density changes only the size of text or everything including graphic become bigger/smaller?
Click to expand...
Click to collapse
wondering the same thing as well.

aquariuz23 said:
wondering the same thing as well.
Click to expand...
Click to collapse
For the most part, yes. Decreasing the LCD Density is like increasing your desktop's resolution. Icons and text become smaller, though apps that are written to scale to any resolution will usually appear the same.

Hmmm...I do see some issues with current density, for instance the avatars in Talk don't stretch to fit the square.
So witch tool would you suggest?

I tried DPI Changer the other and couldn't get it to work, thanks for the heads-up about the build.prop!
The Nitro also already has the "Screen Optimization" util (Settings > Display > Screen Optimization) that resizes checked apps to the Nitro's display. It helped with a few games, but some games just won't work (like Asphalt 5)...But now with the Density changer, maybe I'll give it another try.

[email protected] said:
Hmmm...I do see some issues with current density, for instance the avatars in Talk don't stretch to fit the square.
So witch tool would you suggest?
Click to expand...
Click to collapse
Actually, I'm not sure any of the tools above would work; part of the problem I am sure is that the build.prop file was not only read only, but there wasn't an entry for the LCD Density - so if the apps work by simply retrieving and editing the property, they aren't going to work. I just edited the file directly with a text editor, saved, and restarted the phone. Some of the apps would then at least report the new value, but still didn't seem to successfully update it. I quit looking because I got the density I wanted (about 270, down from the native 320).
As for compatibility with other apps, if they don't quite look correct it is because they aren't written well, and a different density changing app isn't going to do you any good. Again, it's like changing the resolution on your computer - it doesn't matter how you change your resolution - once it's set it is what it is, and apps that don't accommodate it just aren't going to look good.
Namuna said:
I tried DPI Changer the other and couldn't get it to work, thanks for the heads-up about the build.prop!
The Nitro also already has the "Screen Optimization" util (Settings > Display > Screen Optimization) that resizes checked apps to the Nitro's display. It helped with a few games, but some games just won't work (like Asphalt 5)...But now with the Density changer, maybe I'll give it another try.
Click to expand...
Click to collapse
The Screen Optimization utility only seems to address apps that are written to a specific resolution - not pixel density. In this sense, the LCD Density is actually more like changing your computer's DPI - I didn't use that analogy first because more people are more familiar with changing a desktop's resolution. The fact is that LCD screens have a set resolution, and you cannot increase or decrease that resolution through software. The Nitro's extremely high resolution (1280x720) just isn't common enough in phones (most software would see it as a tablet) to be accounted for in all apps - particularly older ones. So, the screen optimization app that is built-in will automatically stretch apps to take up the entire 1280x720 pixels, even if the app only renders (for instance) 800x480 pixels .

Can't adjust resolution, please help

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

[Q] Changing LCD density and customizing the quick launch buttons

I have two questions for you guys about the G Pad 8.3:
1. The default LCD density on this thing is 320 which puts the UI into phone vs. tablet mode (no dual-pane view for Gmail, Email, etc.). The physical density is 273, though, which should activate the tablet (actually phablet) UI. I'm rooted and I've tried changing ro.sf.lcd_density through BuildProp Editor, but on each reboot it reverts to 320. Has anyone else successfully done this? What process (and LCD density value) did you use?
2. Is it possible to customize the quick launch buttons that are activated when you swipe up from the navigation bar? The default ones are Google, Voice Mate, and Quick Memo, and I'd like to change those last two if possible. I can't find anywhere in settings to change those, though.
Thanks much!

The screen density should be easily possible with apps like LCD Density, free on the Play Store (survives one reboot). Alternatively you can also change the dpi for every individual app, by installing the xposed module App Settings.
I don't know a way the quick launch shortcuts can be changed, although there are also apps in the Play Store as well that allow modifications to some extent.

True, I changed the density in build.prop, with editor, restart the tablet has gone a bit 'in bootloop, I rebooted again and everything is restored.
I tried to put 240.

Palux said:
True, I changed the density in build.prop, with editor, restart the tablet has gone a bit 'in bootloop, I rebooted again and everything is restored.
I tried to put 240.
Click to expand...
Click to collapse
Yeah, this tablet seems pretty resistant to changing the LCD density for some reason. Thanks for confirming!

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.