LCD Density Changer? - LG Nitro HD

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 .

Related

LCD Panels - Some Answers

Ok I have seen a lot of confusion over the months regarding the LCD Panel fitted to the Kaiser, I will attempt to answer most of these issues here.
Hardware: The kaiser series is fitted with a 2.8 inch 240x320 TFT LCD panel, which means that it 240 pixels wide by 320 pixels deep, the optimum density of this LCD panel is 143 Pixels per Inch.
Resolution: This refers to the screen resolution that the Operating System will use to display on the LCD panel, the 3 most common being 240x320, 320x428 and 320x480, the reason this is possible is that the OS is capable of fooling the display into using the fixed 240x320 panel to display more pixels, ( it does not really have more pixels, it just looks like it).
DPI: DPI or Dots Per Inch, also known as Density, and correctly known as PPI or Pixels Per Inch, this refers to the number of pixels the screen displays in a One Inch Square on the screen. As I noted above, the actual PPI of the LCD panel is 143 PPI, this is fixed by the hardware, and cannot really be changed, however since the LCD is software driven, it can be persuaded to look as if it is displaying more or less pixels in that same area.
Panel Type: This refers to the actual LCD panel fitted to your device, there are 3 types fitted to the Kaiser series, one manufactured by Sony, the other two by Topoly. While the 3 different types of panel are functionally identical, they differ at the electronic level. On Windows Mobile this difference can be detected by the OS, however on Android this is not possible, so the panel type must be set in the parameters passed to the kernel at boot time, either in default.txt when booting from SD, or hardcoded in the NBH when booting from Nand. Also there is no easy way of telling which panel type is fitted to any given Kaiser, since the panel type was chosen by HTC depending on price and availability and stock at the time of manufacture, so any model of Kaiser can have any of these types fitted.
The main problems encountered with the display are usually solved by changing the Panel Type, either by editing default.txt, or reflashing the correct NBH, ( note that you can also edit the kernel parameters of an NBH using a Hex Editor, however this would be a relatively advanced method, since an error could cause major issues).
Changing screen resolution and density: As noted above there are 3 main resolutions used, 240x320, 320x428 and 320x480. These easy to change either by editing default.txt, or flashing an NBH, depending on how you run Android, resolution is usually a personal choice. Density is not as easy to change, although Rogue Tools by Myn, (available in Market, and discussed here: http://forum.xda-developers.com/showthread.php?t=667581), is excellent for this purpose, there are various common PPI settings, and again mostly personal choice, a little experimentation with resolution and density will allow you to find what you prefer.
Hope this helps clear things up a little
Thanks for this, it helps alot!
vertical lines issue
just to add to the above: the vertical lines issue some have is related to choosing the wrong panel type. Chosing the correct one will solve the problem.
Wrong panel make errors display, ok! But Can it lead to additional consumption of the battery?
Dark-Side said:
Wrong panel make errors display, ok! But Can it lead to additional consumption of the battery?
Click to expand...
Click to collapse
I suspect it may, since display errors such as vertical streaks, pixel errors, colour issues etc are actually caused by a mismatch between the OS drivers and the actual physical electronics, and it's possible that the panel may demand more power than it would normally, I'd have to bench test this to be sure, but it's probably easier just to use the correct panel type setting.
The correct panel type should lead to a 'normal' demand on the battery.
zenity said:
I suspect it may, since display errors such as vertical streaks, pixel errors, colour issues etc are actually caused by a mismatch between the OS drivers and the actual physical electronics, and it's possible that the panel may demand more power than it would normally, I'd have to bench test this to be sure, but it's probably easier just to use the correct panel type setting.
The correct panel type should lead to a 'normal' demand on the battery.
Click to expand...
Click to collapse
I use panel 2... I go to use panel 3 to test this. panel 1 make for me pixel errors. I'll report here.
Thank you
EDIT: no difference between panel 2 or 3 on my kais130
Thanks! That helps a lot.
I havd a thought, which is to change a physical LCD panel for my kaiser, HVGA or VGA... Is that possible? I would look into some electronic files later...
i guess that our chip has max resolution only 320x240 so no higher resolution
but as I look in the pdadb.net there are some devices with higher resolution and same chipset as ours so perhaps it is possible
It is unlikely to be possible to use another panel, since there are a lot of differences with the interface, it's not just the chipset, but how it's wired, plus higher resolution panels may need extra address lines which are not present in our kaisers.
For those of you experimenting with LCD Density settings. You may wish to try the following density settings.
100
121
144
169
196
Remember, pixels are square, so the density settings should reflect this, also the extreme ends of this table are just that, extreme
zenity said:
For those of you experimenting with LCD Density settings. You may wish to try the following density settings.
100
121
144
169
196
Remember, pixels are square, so the density settings should reflect this, also the extreme ends of this table are just that, extreme
Click to expand...
Click to collapse
density 106 works very well with 240x320 if the build is designed for 320x480. I'm using that on the CyanogenMod port. Haven't tried it with other builds though. I did try 107 once with another build but that did not turn out very well.
106? that should really look a little blurry, but I think it depends on the resolution that the build was designed for, however I think I'd find it a little small personally, have you tried 100? it should look clearer than 106, although I have noticed that some people just prefer a certain density regardless of the actual mathematically 'correct' one.
zenity said:
...
Panel Type:....
.... On Windows Mobile this difference can be detected by the OS, however on Android this is not possible, ...
Click to expand...
Click to collapse
So how do I detect which panel in winmo?
I don't like the idea of just stabbing blindly in the dark and hoping I get it right.
Basically? Stab in the dark, there is no way in wm or android to know which type is fitted, type 2 seems most common, and is usually a 'safe' default, if the graphics/colours are wrong, you probably have type 1, if you have issues waking from sleep then you probably have type 3. So try panel 2 first.
Sent from my HTC Dream using Tapatalk
I'm running Android on my HTC Tilt and am using panel 2. I tried panel 1 and the colors were off so Panel 2 seems good.
But the problem I am having is that when I open up the dialer, it doesn't fit correctly on the screen, the bar which shows which numbers you have entered covers up the numbers 1,2,3 and the sides are cropped.
Everything else seems to be fine why is the dialer messed up?
Should I try changing density its at default right now.
I personally like to use 110, but every time I open detail application on Market, it gave me force close. Facebook for Android does that too (I mean FC) whenever I open detail message or upload picture from gallery.. I've tried 106, 104 and 100 and still having the same problem.. it's not happening when I use 120 for density, everything seems work properly normal.. is that common or I have to do something to fix that problem?
Thats not normal behaviour for market, although it has been known to be a little flakey on some builds, however this is unlikely to be related to lcd density, since density only affects the visual appearance of the screen, not the OS itself.
Which Panel?2 or 3?
Am using HTC Tytn II and recently i tried almost all Android builds(donut,eclair,froyo) on my device.panel 1 shows some pixel errors and panel 2 and 3 makes no big difference for me, both settings showing a white flash screen on wake up!
and panel 3 i feel little smudge,not sure.panel 2 wake up with white flash screen and follows by grains(just like noisy TV screen).All these for two seconds.after that TYTN II behave normally.Any body can help me please?
stajan said:
Am using HTC Tytn II and recently i tried almost all Android builds(donut,eclair,froyo) on my device.panel 1 shows some pixel errors and panel 2 and 3 makes no big difference for me, both settings showing a white flash screen on wake up!
and panel 3 i feel little smudge,not sure.panel 2 wake up with white flash screen and follows by grains(just like noisy TV screen).All these for two seconds.after that TYTN II behave normally.Any body can help me please?
Click to expand...
Click to collapse
As previously stated, panel 2 is the most common of all.
As for the white flash and grainy display, this is due to the fact that we have to "fake v-sync" in order to display anything on our screens. Remember, Android was not designed for our Kaisers, but developers got it to run, piece by little piece, really well on our devices. There will always be drawbacks to this as the hardware doesn't really meet the requirements of what Android was developed for.
If you want to see whats going on when you have a white screen or snow, slide the keyboard open and press "Fn-left softkey". this brings up a screen that shows you what Android is doing.
To return to the main screen, press "Fn-right softkey".
Hope this helps...

[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?

[How-To/Guide] Change your LCD Density Setting For More Screen Real Estate

I posted a similar guide for my Galaxy SII, so I figured I would share the love here. Hopefully this helps out a few folks who want to better utilize the amazing screen on the GSIII. I am manually copying this from my post in the now closed combined GSIII forums. Please feel free to comment and make suggestions and please "thank" if you appreciate the post!
General Info for Beginners:
The Galaxy SIII comes with a gorgeous 4.8 inch, 1280 x 720 (albeit pentile) screen. As great as the screen looks, I couldn't help but feel that there is a lot of "wasted space" at the existing resolution. The best example of this fact is the app drawers default 4 x 5 layout. In my opinion, things look much better when the the icons are a bit smaller and more tightly grouped. For those that feel the same way, there is a simple build.prop edit you can do to "trick" you phone to thinking it is set to a higher resolution
How-To Change the Density Setting:
To accomplish this, all you have to do is change the build.prop setting for "ro.sf.lcd_density". There are multiple programs out there that makes this much easier but I have found the best results with "ROM Toolbox". Feel free to buy the full version to support the dev but if all you are looking to do is change the density setting, the lite version will do just fine.
1. download and install "ROM Toolbox" from the Google Play Store
2. go to the "Performance" tab
3. click "build.prop tweaks"
4. change the "LCD Density" slider to whatever DPI you like
5. reboot
As mentioned, there are multiple programs out there but based on my personal experiences, DO NOT USE "LCD DENSITY MODDER" from the play store. This app is known to cause soft-bricks/bootloops. However, I have been told that LCD Density Modder CAN still help with the Play Store app issue, but you will have to buy the pro version for that feature. Thanks uber_mike! (more on that later)
What Setting to Choose:
This is matter of personal opinion so try out different setups and see what you like best. Remember, the lower you set the number, the smaller your icons/text will appear but will also give you more screen real estate. I suggest starting from about 280 or so and working your way down and find something you like.
You may also notice that text and icons appear less sharp when messing with these settings. Keep in mind that because you are not truly changing your screen resolution, the translation will not be perfect. Personally, given the natural sharpness of AMOLED screens, I think most people while not be bothered by this or even notice.
"Phone Mode" vs "Tablet Mode"
As some posters have reported, going to 240 dpi or below will result in Android thinking your device is a tablet. I have been running 240 for a few days now and I'm loving it. In my opinion, may apps look a lot better in Tablet mode but if there are certain phone only apps you MUST have, please keep this in mind.
Potential Issues and Workarounds:
You will inevitably run into some compatibility issues so here are few final thoughts
Which ROM to use?
TouchWiz-based Roms: All roms based on stock Samsung TW for the GSIII were written with only the native resolution in mind. This means that certain apps and aspects of the OS will not scale well with a higher resolution::
- TouchWiz UX Launcher: If you are dead-set on using the default TW launcher, this mod may not be for you. The proportions will look way off and because you cannot edit things like margin or grid layout, it is not fixable. Aftermarket launchers like Apex handle the conversion much better (more on that later)
- The Phone Dialer: The dialer looks like small box that fills up only a portion of the screen. To resolve, you can use an aftermarket dialer app like "exDialer" from the Play Store
- TW E-mail App: The TW e-mail app (not gmail) also doesn't scale well. You can flash the AOSP version of e-mail as a workaround
- Stock Camera App: You will notice some of the border coloring and margins doesn't scale very well but the functionality is still perfect
- Notification Bar: I have noticed the little lines in the pull-down become off-center after you adjust the dpi. Again, a minor annoyance which doesn't effect functionality
- Twitter:*You may have profile pictures show up in 2 different sizes (Thanks Msilvame!)
Some additional feedback from other posters(thanks mhtruth!) but note that I personally do not have all of these issues
*status bar quick toggles DON'T scroll (stuck with just the 1st 5)
*status bar "remove all (X)" missing (swiping still works)
* in call speaker boost doesn't work...(only stops you from hearing not the person on the other end)
* some apps go into tablet mode (ex. HBO GO)
AOSP ROMs: CM9 and AOKP handle the conversion a bit better. You won't run into the dialer or e-mail issue like with TW ROMs but there are still some bugs.
- Certain pictures of contacts may appear too zoomed in, i.e. messaging notification pictures or the favorites tab
- Other aspects of the OS may become hard to read when scaled down so much, i.e. lock screen add-on buttons, notification pull down buttons
- I recently had a chance to mess with some JB ROMs and found that the lockscreen slider/phone answer slider does not scale well and is oriented towards the right of the screen. Boo
The Play Store Doesn't Show All Apps? - This is the biggest pain in the a$$ when you mess with the lcd density settings. There is a bug in the play store that prevents you from seeing certain apps when you change the lcd settings away from default.
I have seen a few "hacked" versions of the vending.apk out there that makes the play store think you are always set to a stock dpi but for some reason, this only works for a little while. LCD Density Modder Pro has a feature where it can install a "fixed" Play Store app that can help with this issue also, but there is also a workaround.
Here are the steps to get the market working again:
1. Change LCD Density back to stock (320)
2. Reboot to take effect
3. Clear the data for the Google Play Store AND Google Services Framework
4. Open the Play Store app and you should see everything again
5. Change LCD density back to whatever you like.
6. Reboot
I know this is a bit cumbersome but it's the best solution for now. I haven't quite nailed down what triggers the market to "break" but hopefully you won't have to do this fix too often. In opinion, this small annoyance is worth it.
Also, one thing I noticed when using Rom Toolbox is that after you set your dpi to a lower setting using the "build.prop tweaks" menu, if you go back and try to set it to the stock 320, it will max out at 280 or so. Not sure why this is the case but to do this manually, go to "build.prop editor" instead and change the "ro.sf.lcd_density" to 320.
I have been told that setting your dpi to 240 will also help with Play Store issues, since 240 is a stock resolution on other devices (GSII comes to mind). Feel free to try this out, but the size of icons and fonts may be a bit too small for some tastes (thanks DutchDogg54 and chakra!)
Everything Looks Too "Stretched Out"? - Having an aftermarket launcher will help with this tremendously, as the TW launcher does not scale well at all. I personally use Apex Launcher and there are some settings you can change to make the proportions look better
1. Homescreen Settings: Change the Vertical and Horizontal margins to medium or large
2. Dock Settings: Same as above.
You may also want to mess with different homescreen grid configurations now that you have extra room. I have bumped up mine to 5 x 5 and it looks great.
Bumping up the font size can also help even things out. At 240 dpi, I put mine to "normal", but at stock I used "tiny" (thanks falconator!)
List of all the ICS compatible launchers that will work for this mod:
- Apex Launcher (my fave)
- Nova Launcher
- Go Launcher
- Atom Launcher (new!)
- Holo Launcher (new!)
And that's it. I hope this will help you out so that you won't have to go through all the trial and error I did. I promise you, after you do this, it will be impossible for you to go back to the stock resolution (everything looks HUGE)
Update: I have added some of my and mhtruth's screenshots for those who are interested. I also added a screenshot of HBO GO in tablet mode
My setup:
- 240 dpi (Tablet Mode)
- AOKP M6 R3, Black Exodus Theme
- Apex Launcher
- Homescreen: 6 x 5 grid, Horizontal Margin: Medium, Vertical Margin: Large
- Dock: Horizontal Margin: Large, Vertical Margin: Medium
- Font Size: "Normal"
Feel free to show off your own homescreen screenshots! I will update OP and add yours too!
I was just complaining about this to myself this morning. Thank you for sharing this. I'm definitely going to try messing with this.
Sent from my SGH-T999 using xda app-developers app
I find that ROM toolbox is kind of buggy on the GS3.
There use to be an app o the market that did this and it stuck on boot. I hate messing with build prop myself. Someone should whip up a new app.
-me being lazy lol
Sent from my SGH-T999 using xda app-developers app
Update:
Since 8/10 I have been running the AMAZING Paranoid Android ROM and I am in love with this. For anyone who liked the LCD Density Mod posted above, you should definitely check out this ROM. I got to experience it just a bit with my GSII and continue to be impressed with my GSIII.
I suggest you try "Phablet" Mode at first. The advantage to this ROM is that it allows you to individually adjust the density of each app separately as well as prevents market incompatibility issues. This is a MUST for people who like things at a setting other than 240.
Hope this helps!
Stuck in boot
after 3 hours of getting it rooted, i got the density app, i may of gotten the lcd density modder , i didnt know there was 2 kinds. but i put it to 200, rebooted and now i try to turn on and it goes to samsung logo but then just turns off again, what do i do?
Well, if it didnt back up your build.prop then the easiest thing would be to flash a rom.
Or if you have a nandroid restore just the system part.
Otherwise plug up to your computer and oull your build.prop, set it back to default and push it back to system.
Sent from my SGH-T999 using xda app-developers app
I'm running AOKP milestone 1 on my SGSIII, when I change my density I get screen flashes. Is this the incompatibility your talking about? I've tried different DPIs with the same result. I've used the density changer built into ROM control, as well as ROM toolbox, both with the same results. Any help is appreciated. Thanks.
Let me make a few notes:
First, stock ics touchwiz ROMs do not like anything lower than 240. This means any ROM that is touchwiz based off stock ics will result in boot loops.. trust me been there -.-
Secondly, don't waste your money on the LCD density mod app to fix the market. I've already fixed the market. Just flash my zip found [MOD][APP][UPDATE 3.10.10] 320DPI GoogleServicesFramework and google play and you should be golden. Don't have a custom recovery, then extract the files from the zip and use a root file browser to copy them to the system/app directory.
Oh and 240 isn't tablet mode. I'm currently at 210 and it's not tablet mode.. I don't remember what it was.
Sent from my SGH-T999 using Tapatalk 2
So..... Any recommendations on the screen flashing after changing the density?
elterible said:
I posted a similar guide for my Galaxy SII, so I figured I would share the love here. Hopefully this helps out a few folks who want to better utilize the amazing screen on the GSIII. I am manually copying this from my post in the now closed combined GSIII forums. Please feel free to comment and make suggestions and please "thank" if you appreciate the post!
General Info for Beginners:
The Galaxy SIII comes with a gorgeous 4.8 inch, 1280 x 720 (albeit pentile) screen. As great as the screen looks, I couldn't help but feel that there is a lot of "wasted space" at the existing resolution. The best example of this fact is the app drawers default 4 x 5 layout. In my opinion, things look much better when the the icons are a bit smaller and more tightly grouped. For those that feel the same way, there is a simple build.prop edit you can do to "trick" you phone to thinking it is set to a higher resolution
How-To Change the Density Setting:
To accomplish this, all you have to do is change the build.prop setting for "ro.sf.lcd_density". There are multiple programs out there that makes this much easier but I have found the best results with "ROM Toolbox". Feel free to buy the full version to support the dev but if all you are looking to do is change the density setting, the lite version will do just fine.
1. download and install "ROM Toolbox" from the Google Play Store
2. go to the "Performance" tab
3. click "build.prop tweaks"
4. change the "LCD Density" slider to whatever DPI you like
5. reboot
As mentioned, there are multiple programs out there but based on my personal experiences, DO NOT USE "LCD DENSITY MODDER" from the play store. This app is known to cause soft-bricks/bootloops. However, I have been told that LCD Density Modder CAN still help with the Play Store app issue, but you will have to buy the pro version for that feature. Thanks uber_mike! (more on that later)
What Setting to Choose:
This is matter of personal opinion so try out different setups and see what you like best. Remember, the lower you set the number, the smaller your icons/text will appear but will also give you more screen real estate. I suggest starting from about 280 or so and working your way down and find something you like.
You may also notice that text and icons appear less sharp when messing with these settings. Keep in mind that because you are not truly changing your screen resolution, the translation will not be perfect. Personally, given the natural sharpness of AMOLED screens, I think most people while not be bothered by this or even notice.
"Phone Mode" vs "Tablet Mode"
As some posters have reported, going to 240 dpi or below will result in Android thinking your device is a tablet. I have been running 240 for a few days now and I'm loving it. In my opinion, may apps look a lot better in Tablet mode but if there are certain phone only apps you MUST have, please keep this in mind.
Potential Issues and Workarounds:
You will inevitably run into some compatibility issues so here are few final thoughts
Which ROM to use?
TouchWiz-based Roms: All roms based on stock Samsung TW for the GSIII were written with only the native resolution in mind. This means that certain apps and aspects of the OS will not scale well with a higher resolution::
- TouchWiz UX Launcher: If you are dead-set on using the default TW launcher, this mod may not be for you. The proportions will look way off and because you cannot edit things like margin or grid layout, it is not fixable. Aftermarket launchers like Apex handle the conversion much better (more on that later)
- The Phone Dialer: The dialer looks like small box that fills up only a portion of the screen. To resolve, you can use an aftermarket dialer app like "exDialer" from the Play Store
- TW E-mail App: The TW e-mail app (not gmail) also doesn't scale well. You can flash the AOSP version of e-mail as a workaround
- Stock Camera App: You will notice some of the border coloring and margins doesn't scale very well but the functionality is still perfect
- Notification Bar: I have noticed the little lines in the pull-down become off-center after you adjust the dpi. Again, a minor annoyance which doesn't effect functionality
- Twitter:*You may have profile pictures show up in 2 different sizes (Thanks Msilvame!)
Some additional feedback from other posters(thanks mhtruth!) but note that I personally do not have all of these issues
*status bar quick toggles DON'T scroll (stuck with just the 1st 5)
*status bar "remove all (X)" missing (swiping still works)
* in call speaker boost doesn't work...(only stops you from hearing not the person on the other end)
* some apps go into tablet mode (ex. HBO GO)
AOSP ROMs: CM9 and AOKP handle the conversion a bit better. You won't run into the dialer or e-mail issue like with TW ROMs but there are still some bugs.
- Certain pictures of contacts may appear too zoomed in, i.e. messaging notification pictures or the favorites tab
- Other aspects of the OS may become hard to read when scaled down so much, i.e. lock screen add-on buttons, notification pull down buttons
- I recently had a chance to mess with some JB ROMs and found that the lockscreen slider/phone answer slider does not scale well and is oriented towards the right of the screen. Boo
The Play Store Doesn't Show All Apps? - This is the biggest pain in the a$$ when you mess with the lcd density settings. There is a bug in the play store that prevents you from seeing certain apps when you change the lcd settings away from default.
I have seen a few "hacked" versions of the vending.apk out there that makes the play store think you are always set to a stock dpi but for some reason, this only works for a little while. LCD Density Modder Pro has a feature where it can install a "fixed" Play Store app that can help with this issue also, but there is also a workaround.
Here are the steps to get the market working again:
1. Change LCD Density back to stock (320)
2. Reboot to take effect
3. Clear the data for the Google Play Store AND Google Services Framework
4. Open the Play Store app and you should see everything again
5. Change LCD density back to whatever you like.
6. Reboot
I know this is a bit cumbersome but it's the best solution for now. I haven't quite nailed down what triggers the market to "break" but hopefully you won't have to do this fix too often. In opinion, this small annoyance is worth it.
Also, one thing I noticed when using Rom Toolbox is that after you set your dpi to a lower setting using the "build.prop tweaks" menu, if you go back and try to set it to the stock 320, it will max out at 280 or so. Not sure why this is the case but to do this manually, go to "build.prop editor" instead and change the "ro.sf.lcd_density" to 320.
I have been told that setting your dpi to 240 will also help with Play Store issues, since 240 is a stock resolution on other devices (GSII comes to mind). Feel free to try this out, but the size of icons and fonts may be a bit too small for some tastes (thanks DutchDogg54 and chakra!)
Everything Looks Too "Stretched Out"? - Having an aftermarket launcher will help with this tremendously, as the TW launcher does not scale well at all. I personally use Apex Launcher and there are some settings you can change to make the proportions look better
1. Homescreen Settings: Change the Vertical and Horizontal margins to medium or large
2. Dock Settings: Same as above.
You may also want to mess with different homescreen grid configurations now that you have extra room. I have bumped up mine to 5 x 5 and it looks great.
Bumping up the font size can also help even things out. At 240 dpi, I put mine to "normal", but at stock I used "tiny" (thanks falconator!)
List of all the ICS compatible launchers that will work for this mod:
- Apex Launcher (my fave)
- Nova Launcher
- Go Launcher
- Atom Launcher (new!)
- Holo Launcher (new!)
And that's it. I hope this will help you out so that you won't have to go through all the trial and error I did. I promise you, after you do this, it will be impossible for you to go back to the stock resolution (everything looks HUGE)
Update: I have added some of my and mhtruth's screenshots for those who are interested. I also added a screenshot of HBO GO in tablet mode
My setup:
- 240 dpi (Tablet Mode)
- AOKP M6 R3, Black Exodus Theme
- Apex Launcher
- Homescreen: 6 x 5 grid, Horizontal Margin: Medium, Vertical Margin: Large
- Dock: Horizontal Margin: Large, Vertical Margin: Medium
- Font Size: "Normal"
Feel free to show off your own homescreen screenshots! I will update OP and add yours too!
Click to expand...
Click to collapse
Im running a stock rom on a Chinese phone (W9208) and i dont have LCD density...apps dont work either...is there hope for me?
rndm said:
Im running a stock rom on a Chinese phone (W9208) and i dont have LCD density...apps dont work either...is there hope for me?
Click to expand...
Click to collapse
I'm not too familiar with that model. pardon me if this is a stupid question but i'm assuming you mean "stock android"?
if so, then you're fine. download an app that will let you change the LCD density manually in the buildprop (i.e. Rom Toolbox). find the line "ro.sf.lcd_density" and change to whatever you like.
The tricky part here is to find the right number. I wrote this guide a while back for my Galaxy S3, which ran 320 dpi natively at it's 720p resolution. To achieve tablet mode (and retain compatibility with the Google Playstore), I changed it to 240. My current device (nexus 5) runs 1080p which has a stock dpi of 480. To achieve tablet mode, i changed to 320. Does this make sense? Again, it's tricky b/c i'm not sure what resolution your phone is
Well, i hope this helps, good luck!
elterible said:
I'm not too familiar with that model. pardon me if this is a stupid question but i'm assuming you mean "stock android"?
if so, then you're fine. download an app that will let you change the LCD density manually in the buildprop (i.e. Rom Toolbox). find the line "ro.sf.lcd_density" and change to whatever you like.
The tricky part here is to find the right number. I wrote this guide a while back for my Galaxy S3, which ran 320 dpi natively at it's 720p resolution. To achieve tablet mode (and retain compatibility with the Google Playstore), I changed it to 240. My current device (nexus 5) runs 1080p which has a stock dpi of 480. To achieve tablet mode, i changed to 320. Does this make sense? Again, it's tricky b/c i'm not sure what resolution your phone is
Well, i hope this helps, good luck!
Click to expand...
Click to collapse
I wish it was stock android:crying:
Star's (Chinese manufacturer) manipulation of android to copy Samsung's touchwiz.
my device is 720p and has a 6.4 inch screen...hence me wanting to change the dpi...not sure what the dpi currently is but the drop-down status bar toggles labels are squashed.
I rooted and installed loads of dpi apps and none worked. Then I looked for "ro.sf.lcd_density" and realised I don't have one in my build prop. Know any fixes?
rndm said:
I wish it was stock android:crying:
Star's (Chinese manufacturer) manipulation of android to copy Samsung's touchwiz.
my device is 720p and has a 6.4 inch screen...hence me wanting to change the dpi...not sure what the dpi currently is but the drop-down status bar toggles labels are squashed.
I rooted and installed loads of dpi apps and none worked. Then I looked for "ro.sf.lcd_density" and realised I don't have one in my build prop. Know any fixes?
Click to expand...
Click to collapse
you should be able to manually add in the line yourself.
but a word of warning, given that i have no experience with "Star" and no idea what version of android is on there, I would proceed with caution if you do that
since you have it rooted, is there any way you can flash a completely stock custom version of android on there? is there any development support for it here on XDA?
rndm said:
I wish it was stock android:crying:
Star's (Chinese manufacturer) manipulation of android to copy Samsung's touchwiz.
my device is 720p and has a 6.4 inch screen...hence me wanting to change the dpi...not sure what the dpi currently is but the drop-down status bar toggles labels are squashed.
I rooted and installed loads of dpi apps and none worked. Then I looked for "ro.sf.lcd_density" and realised I don't have one in my build prop. Know any fixes?
Click to expand...
Click to collapse
You can use "Build.prop Editor" app and add that entry yourself. That's least painful way.
Perseus71 said:
You can use "Build.prop Editor" app and add that entry yourself. That's least painful way.
Click to expand...
Click to collapse
Great didn't know I could do that, however i might leave it now...
I installed texdroider and I couldn't type any numbers in the dpi change box (probably because it directly edits the lcd density registry, which i didn't have)
Then after that I installed LCD density modder app which put my phone into a bootloop after setting 300dpi
So I assume even after adding the entry I wont have much room to play with anyway?
---------- Post added at 10:37 AM ---------- Previous post was at 10:35 AM ----------
elterible said:
you should be able to manually add in the line yourself.
but a word of warning, given that i have no experience with "Star" and no idea what version of android is on there, I would proceed with caution if you do that
since you have it rooted, is there any way you can flash a completely stock custom version of android on there? is there any development support for it here on XDA?
Click to expand...
Click to collapse
Tried searching Mediatek LCD desnsity change but to no avail. Thanks anyway.
rockyhas said:
after 3 hours of getting it rooted, i got the density app, i may of gotten the lcd density modder , i didnt know there was 2 kinds. but i put it to 200, rebooted and now i try to turn on and it goes to samsung logo but then just turns off again, what do i do?
Click to expand...
Click to collapse
As mentioned, there are multiple programs out there but based on my personal experiences, DO NOT USE "LCD DENSITY MODDER" from the play store. This app is known to cause soft-bricks/bootloops. However, I have been told that LCD Density Modder CAN still help with the Play Store app issue, but you will have to buy the pro version for that feature. Thanks uber_mike! (more on that later)
Click to expand...
Click to collapse
You're screwed. Do a reset.
I did the LCD changes through playstore i ddint see this thread and now my phone logo comes but black screen after hard rest nothing working help HTc Sensation xl

Changing your DPI Settings (No-Root)

Hi all, please see the below thread. Only sharing the info as this was posted on the Verizon N4 forum.
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Hope this helps...
As indicated below some touchwiz native apps are affected.
List of known affected applications by changing DPI settings:
S-View (for S-View covers -- slightly misaligned but functional)
Touchwiz Stock Dialer (slightly misaligned but functional -- other non-stock options exist such as Hangouts or ExDialer)
Fingerprint lockscreen (arrow pointing to finger print scanner off center)
Exchange email (stock Samsung Email)
Stock Camera App
Just FYI to get some easy download links:
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Enable USB debugging on yer phone
-> http://www.mediafire.com/download/a4hd8y0c1iakysk/Samsung-Usb-Driver-v1.5.49.0.exe
Samsung USB drivers you'll need installed
-> http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
ADB / Fastboot installer
navigate to C:\adb\ and then run the command they give in the thread
adb shell wm density 540
(not confirmation will be sent but your phone should prompt you to 'allow' your computer to send adb commands to it.).
Restart phone
DPI settings are now at 540. original DPI settings are 640 BTW
imnoob55 said:
Hi all, please see the below thread. Only sharing the info as this was posted on the Verizon N4 forum.
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Hope this helps...
Click to expand...
Click to collapse
I came across that thread a few hours ago. It's pretty neat to be able to drop the density and make more use of display space (could even drop it down to 384 and make it look more like a tablet), but it has its problems. Samsung apps (Dialer, camera, S Note, S-View, etc) will lose their screen alignment and/or only cover a portion of the screen when altering the density. Finding an alternate dialer was easy enough, but I'm having trouble finding a camera app similar to stock in quality, and was unsuccessful at replacing the S-View...
redphazon said:
I came across that thread a few hours ago. It's pretty neat to be able to drop the density and make more use of display space (could even drop it down to 384 and make it look more like a tablet), but it has its problems. Samsung apps (Dialer, camera, S Note, S-View, etc) will lose their screen alignment and/or only cover a portion of the screen when altering the density. Finding an alternate dialer was easy enough, but I'm having trouble finding a camera app similar to stock in quality, and was unsuccessful at replacing the S-View...
Click to expand...
Click to collapse
Yup unfortunately that is a side-effect of doing this. Only way to do it that I am aware of conventionally would be via xposed or loading in custom TW apps, both not possible. Hangout dialer works well, for this. TW stock browser is not affected. My S-Note is not affected either, too. Dialer and S-View are (not unusable, they just are not center-aligned any longer as their height/width are set on static widths rather than proportional % when Samsung set up the layout.) Maybe they'll change that in L.
BTW I use Nova for launcher and Hangouts as my dialer. I do use an s-view case, though, which is of course impacted.
imnoob55 said:
Yup unfortunately that is a side-effect of doing this. Only way to do it that I am aware of conventionally would be via xposed or loading in custom TW apps, both not possible. Hangout dialer works well, for this. TW stock browser is not affected. My S-Note is not affected either, too. Dialer and S-View are (not unusable, they just are not center-aligned any longer as their height/width are set on static widths rather than proportional % when Samsung set up the layout.) Maybe they'll change that in L.
BTW I use Nova for launcher and Hangouts as my dialer. I do use an s-view case, though, which is of course impacted.
Click to expand...
Click to collapse
I'm also using Nova Launcher. I did download ExDialer at first, but I went to Hangouts Dialer instead since ExDialer has a trial period and costs money.
S Note is largely unaffected yes, but when you open the camera for copying documents, the square used for aligning the camera with the document is off-center. It doesn't seem to hurt functionality in any way, though. Oddly enough, the camera when used in S Note is fullscreen...
As far as S-View goes, I'm thinking about removing the flip cover. S-View is nice, but I'm always trying to not get smudges on the cover screen on top of the phone display, so the cover is a little bit cumbersome to me when holding it. Seeing how much better the phone looks at a lower density makes me lean even closer to just getting rid of it. That leaves me with just the camera replacement...
Exchange email is also broken... when you reply to an email, the screen font is set to eleventybillion.
-----
Sent with my Galaxy Note 4
Can anyone confirm if this impacts the play store? Typically changing the dpi on the whole device would prevent the play store from downloading some apps.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
jfenton78 said:
Can anyone confirm if this impacts the play store? Typically changing the dpi on the whole device would prevent the play store from downloading some apps.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
I haven't seen any problems with the Play Store yet, though I haven't been installing much of anything, either. The few apps I've installed so far gave me no trouble.
Also, just found out that the stock camera has no problems with accurate button detection when the phone is turned sideways for landscape rotation, though it's still not fullscreen. You have to guess where the buttons are on the screen in portrait when the density is changed.
Couple of tips:
if you get an error about the device being offline make sure you've got the current ADB installed. The link provided for the adb and fastboot didn't work for me because the file didn't install. The program is just an auto run zip file. you can open with 7-zip and just extract the adb files.
also if you get an error about the device being unauthorized you must select no action on the windows pop up and always perform this action. the phone should then get a pop up with the RSA key number and ask you to authorize. hope this helps.
540 DPI is pretty nice.
I was okay with the dialer and lockscreen, but the camera made me go back to 640. In vertical shooting mode, the touch points for all the icons, including the shutter button, is misaligned and is very annoying. What a shame as 540 looked AWESOME.
cj00ta said:
Exchange email is also broken... when you reply to an email, the screen font is set to eleventybillion.
-----
Sent with my Galaxy Note 4
Click to expand...
Click to collapse
Thanks! Just added to the top thread under impacted apps
Does this effectively change the resolution? I'm curious if lowering the DPI would give positive improvement to high-end game performance. Can anyone shed some light here?
Conkrete said:
Does this effectively change the resolution? I'm curious if lowering the DPI would give positive improvement to high-end game performance. Can anyone shed some light here?
Click to expand...
Click to collapse
It doesn't change the resolution. What it changes is the drawing size of on-screen content which is directly from the 'dpi setting' of the phone.
It's a little complicated to explain but this is how it works;
The phone's default screen density (DPI) setting 640, this is done because that's how many dots per inch of the physical screen there is (a phone of similar screen size would have a similar dpi). This value is stored in your phone's build.prop and is read by numerous applications, it might not match exactly the 'real' dpi of the screen but its normally very close to it.
By changing it lower in dpi you're instructing to applications you actually have a smaller screen size, thus to fit content (i.e words not being HUGE on a small screen) content is drawn to that dpi setting you're providing in build.prop.
Now to go into why we have certain issues when changing the dpi.
This is basically due to how the app did its layout sizing (do I base content on "actual size" of the screen-size or do I base it on "actual density" of the screen density in build.prop? Most apps, since they're targeting to be used with dozens of devices of all sorts of different sizes, will be designed where the layout of content is dependent upon dpi. A layout would be I want a rectangular box on the bottom that has height 10px and width 100%, so that effectively means the width is based on the proportion of the screen size (the OS controls this, its just a matter of scaling). This is why you once had 5 items to show now has 8 items to show in a listbox. The size of the listbox in this case would be based on actual density while the content (text etc.) inside would be based on actual size (scaling I would think is limited to a min/max actual size for text).
Samsung can get away with this on their stock apps because in their mind when they build their roms they are only going to be used on that specific device. They're starting to go away from this, however, and are starting to make their layouts more typical that of a normal application. You have somewhat less control of the layout going from actual size to actual density.
*keep in mind you can actually set parameters for both. Such as if I wanted something to be 10% in width but only up to 2.5 inches in actual size this effectively means that it will scale until it reaches 2.5" and then scale no longer.
I hope that makes sense. Resolution really doesn't have a role at all in this, you're always at the same resolution (4K) and this is handled by the lower-level kernel and GPU firmware. I don't think there's a way to change this at the app layer but than again I have really no background in android development.
*please if anything comes off as inaccurate please point out, I am from a XAML/.NET development background and linux/unix embedded systems and really I focused on back-end/databases/services and not really front-endy stuff. This is how it is handled in XAML though and I have seen android uses the same principals.
imnoob55 said:
It doesn't change the resolution. What it changes is the drawing size of on-screen content which is directly from the 'dpi setting' of the phone.
It's a little complicated to explain but this is how it works;
The phone's default screen density (DPI) setting 640, this is done because that's how many dots per inch of the physical screen there is (a phone of similar screen size would have a similar dpi). This value is stored in your phone's build.prop and is read by numerous applications, it might not match exactly the 'real' dpi of the screen but its normally very close to it.
By changing it lower in dpi you're instructing to applications you actually have a smaller screen size, thus to fit content (i.e words not being HUGE on a small screen) content is drawn to that dpi setting you're providing in build.prop.
Now to go into why we have certain issues when changing the dpi.
This is basically due to how the app did its layout sizing (do I base content on "actual size" of the screen-size or do I base it on "actual density" of the screen density in build.prop? Most apps, since they're targeting to be used with dozens of devices of all sorts of different sizes, will be designed where the layout of content is dependent upon dpi. A layout would be I want a rectangular box on the bottom that has height 10px and width 100%, so that effectively means the width is based on the proportion of the screen size (the OS controls this, its just a matter of scaling). This is why you once had 5 items to show now has 8 items to show in a listbox. The size of the listbox in this case would be based on actual density while the content (text etc.) inside would be based on actual size (scaling I would think is limited to a min/max actual size for text).
Samsung can get away with this on their stock apps because in their mind when they build their roms they are only going to be used on that specific device. They're starting to go away from this, however, and are starting to make their layouts more typical that of a normal application. You have somewhat less control of the layout going from actual size to actual density.
*keep in mind you can actually set parameters for both. Such as if I wanted something to be 10% in width but only up to 2.5 inches in actual size this effectively means that it will scale until it reaches 2.5" and then scale no longer.
I hope that makes sense. Resolution really doesn't have a role at all in this, you're always at the same resolution (4K) and this is handled by the lower-level kernel and GPU firmware. I don't think there's a way to change this at the app layer but than again I have really no background in android development.
*please if anything comes off as inaccurate please point out, I am from a XAML/.NET development background and linux/unix embedded systems and really I focused on back-end/databases/services and not really front-endy stuff. This is how it is handled in XAML though and I have seen android uses the same principals.
Click to expand...
Click to collapse
Extremely helpful and great info. Possibly the best response I've received from XDA. Thank you for the info. I have found a couple root apps that claim to change resolution but I've been hoping to find a non-root alternative.

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!

Categories

Resources