So i'm new to this changing DPI stuff.
What are the benefits/disadvantages of changing your DPI?
I know lowering it makes everything smaller, but there is a downside to everything.
Is performance decreased?
Is touch sensitivity effected?
etc
Also, lowering your DPI increases resolution, isn't that counter intuitive?
Less pixels in an area should have lower resolution...
Related
This option is available in cm7.2 RC5.7 under CM Settings>Display>Change Lcd Density and options are 105, 110, 115, 120, 125, 130, Custom (Dpi)
What I am wondering and I'm sure others are too, is what are the Advantages/Disadvantages of messing with this, are the effects highly noticeable and how far can you push it?
I currently have mine set at 150dpi and seems to me like the screen is more appealable and sharper text reading, or maybe its just my imagination
Certainly this config alters the height of letters, icons, pics, web, etc (as does in other OS).
Some are more comfortable with lower, others with higher. You should try some and see which one suits you more.
Fraser1978 said:
This option is available in cm7.2 RC5.7 under CM Settings>Display>Change Lcd Density and options are 105, 110, 115, 120, 125, 130, Custom (Dpi)
What I am wondering and I'm sure others are too, is what are the Advantages/Disadvantages of messing with this, are the effects highly noticeable and how far can you push it?
I currently have mine set at 150dpi and seems to me like the screen is more appealable and sharper text reading, or maybe its just my imagination
Click to expand...
Click to collapse
It's a TFT screen, you can't make more of it than there are crystals, just go with stock, it will look better and perform better. stock is 110.
lower value means more space on screen and higher value means less space
lower value will decrease quality higher value will increase quality
I will recommend keeping it default because you will not like both higher and lower
I had this burning desire to know whether the density of the lcd could affect the overall performance of our phones. The idea is similar to changing the resolution on your PC or laptop. The higher the resolution you choose, the more resources required to run the computer without lag or other undesirable outcomes from rendering the screen differently than if you choose a lower resolution. Sadly, when I did a quick search on XDA I didn't find any answer than to "try it yourself". So why not?
With each test I had the CPU over clocked to 1920 MHz (1.9 Ghz.)
The ROM is Cyanogenmod 10 (4.1.2) by camcory
AnTuTu Benchmark v3.0.3 was chosen as the sole benchmark application
Lcd density^ was changed in the build prop : ro.sf.lcd_density
Now, I have to add that this wasn't a formal test, but rather an attempt at real world numbers. Each lcd density change required a reboot after which I did not load any program besides 1) Set CPU and 2) Antutu benchmark. With that in mind however, I didn't clear any cache, memory, kill any other programs, or anything like that. Just reboot and run.
Here are the results to my tests :
The default density for this device is 240.
240 received a score of 6095
160 received a score of 5875 (The lowest this phone density can go*)
200 received a score of 6016 (This test received varying scores**)
300 received a score of 5967
320 received a score of 5885 (The highest this phone density can go*)
^ The lower the number, the smaller screen appearance. The higher the number, the large the screen appears.
*This is the end of the spectrum of safety in either direction. The lowest or highest I was willing to test it at
** 200 density was tested three times with varying scores : 6016, 5977, 5871. To my knowledge, I did not open any applications.
The bottom line
The highest scored density was always 240, the default density for this phone. A density that moved in either direction away from 240 on the number line meant a slight , or major drop in performance.
Pictures: 160 density on the left, 300+ on the right.
(Click thumbnails for picture)
Just a little insight here... While your efforts are appreciated, the fact is, those scores are so close, they can all be achieved without touching the LCD density at all. Other factors make the score fluctuate between 100-200 points. Our phone will always be at 480x800. Adjusting the LCD density is nothing more than a software hack to emulate the difference of using another resolution. Rather than make a comparison to changing the resolution on a computer, it should be more comparable to changing the text DPI (eg, 96 to 120, as Windows allows you to do quite easily). There are no more or no less pixels being rendered overall - it's just the size and positioning of each UI element that's being rendered differently. That said, real world performance won't make a difference. It should also be noted that running a benchmarking app is subjective. No real world difference is noticed between a score of 5500 or 6500. I've seen some high scores where there was constant lag, and lower scores where everything ran smooth. The kernel makes the biggest difference, and other various things like being deodexed, having APK's aligned, various RAM tweaks, minfree values, multitasking aggressiveness, etc - those make up the real world performance differences, and quite often, won't even be detected in benchmark results.
I've used a few different across my android devices (different meaning other than the stock value) but I still don't quite understand...
Higher Density = Higher or Lower quality?
Lower than Stock density = Lower quality at all?
I'm liking 400 but I'm not sure if it lowers quality or not.
If you can't see any quality degradation, then what's the problem?
Sent from my C6603 using XDA Premium HD app
Well I meant in home/settings apps really, i would hate to later play a higher end game or a movie and see the quality is poor
Movies or games should still be rendering at the resolution of the screen. The DPI doesn't change that. What it could (and most likely will) is adjust the size of UI elements (such as camera controls, video player controls, etc.). Depending on what firmware you're running, the different elements and apps may be able to adjust themselves based on the DPI by utilizing different images within the APKs (mdpi, hdpi, xhdpi, etc.).
Take a look at this link. It might help you out a little.
http://www.androidtablets.net/forum/android-tablet-usage-tips-tricks/9444-lcd-density-explained.html
Also, there are ROMs/MODs that allow for different apps to implement different DPIs on the device. Great examples of this are ParanoidAndroid ROMs and Xposed framework mods. These can give you the ability to adjust dpi by application, that way if there are any incompatibilities at a certain DPI, you can work around the issues.
I just upgraded from 5.0.1 to 5.1 and I've noticed that when I change my resolution from the factory default of 560 to say the native res of 493, the contact thumb nails are distorted. If I use the terminal command "wm dentity 560" to go BACK to 560, it fixes it. Normally I run 493 which is the native res for this screen.
5.0.1 does not have this issues, only 5.1.. I also tried other resolutions and I get this issue on everything but 560.
I'm using CleanROM 2.2 which is a stock based ROM.
Also I noticed pictures in some image browsing apps do not display correctly. They show as super zoomed in on one section and I an not zoom out. ES File Explorers image app does this but for example QuikPic does not.
If I go back to 5.0.1, all problems solved though.
Just wondering about other 5.1 users experiences with stuff like this.
493 is not the native DPI. PPI and DPI are NOT the same.
Just to echo what @akeller said, DPI is not linked to resolution. DPI is not the same as PPI. PPI (Pixels per Inch) are how many physical pixels are in an inch of your display. This obviously cannot be changed.
Lets say you have a 5" screen at HD resolution (1080p) and also a 10" screen at the same resolution. As you can imagine, you have the exact same amount of pixels on the display, but the display is bigger so the pixels are also bigger.
This means that assets on your screen (icons, buttons etc) will also be much bigger, so you are not taking advantage of a bigger screen as you can only fit the same amount of stuff on it. For this reason, DPI is used as a scaling method to make assets smaller, to fit more on the screen. There is no hard-and-fast rule as to what DPI to use. Generally, the bigger the display, the smaller the DPI should be to make bvetter use of it. OR, the lower the resolution, the smaller the DPI should be. There is no direct link to PPI and DPI.
After you run "wm density 493" also run just "wm density". Now you'll probably see that it reports two values, 560 and 493. The solution is to also edit build.prop (change 560 to 493).
I've always used ui tuner, and i've used 289 ppi for more screen estate. But a z3 runs a 1080 screen at 424 ppi. So we know the hardware in the z3c can that. But i can't set my dpi to 424 as it would make everything larger and not smaller. So i have to use negative ppi. So i go from 320 to 289. When i lower the ppi it makes things smaller which also means the hardware has to draw more content.
But how do you figure out the relation between these. How does 289 ppi on 720 resolution relate to 1080 at 424 ppi?
Does this even make sense to you ?
System and apps use both resolution and dpi values to determine screen size, so they can figure out how much space to dedicate for interface stuff (bars, etc).
size (inches) = resolution (pixels) / dpi (pixels / inch) = (resolution / dpi) inches
The bigger the screen size, the more “zoomed out” default/interface view a device usually has.
The pitiful thing with certain world wide web sites is they use this information to determine your screen size and decide zoom level, usually resulting in jackassilly bigass screen items and little onscreen content, sometimes further sabotaged with squatter behemoth search bars and dumbass Twitsh1t and Fakeb00k buttons.
In my honest opinion, this is kind of stupid. I prefer fully zoomed out classic desktop pages, I'll zoom in where required, thanks.
Cheers :laugh: