Difference between dencity and resolution? - XDA-developer encyclopedia

How are these different
If we change dencity of android phone so is resolution will be the same?

Resolution of a display is the total number of pixels that the display contains.
The actual hardware density is constant, but the density that is presented to the software can be changed.
If a program needs to display something that needs to look a certain height, and the reported display density is 160 ppi, the program will use 16 pixels, but if the reported density is 200, that tells the program that the pixels are smaller, and it will use 20 pixels to present the same object. However, since the resolution is unchanged, the object will actually look bigger.
I hope that clears it up for you.

Thnkss a lot

And changing Density is certainly usefull for new High Resolution Devices that Cant Operate old apps fullscreen...

Changing means it should be kept to high,so that every object looks smaller and really becomes to look like high quality.:thumbup:

Related

Getting the size of CF.NET Fonts?

I'm trying to get my .net application to look better on VGA screens. I see that the VGA device automatically uses larger fonts, so my 9 Point font is no longer 9 pixels high.
How do I determine (programatically) how tall the font is actually going to be? Do I have to run graphics.MeasureString() against it?

Any way to change the size of the statusbar without changing lcd density

I really like the way my system looks with a higher density setting.
Unfortunately some things look better bigger or just don't look good at all / don't work at all in lower density settings.
Is there a way to size down specific UI elements in specific the statusbar?

Programs in weird resolution...

I changed my lcd density to 190. Some programs adjust to it just fine, other programs look like they are squeezed to one side. Is there anyway to make those other programs "adjust" their resolution to fill up the screen properly instead of being crammed up in a corner?

Resolution effed up?

I change my resolution to 1920 x 1080 and all it does is change the size of the fonts, it becomes unreadable the tiles and basicaally the whole metroui remains the SAME size , its like windows its not adjusting the resolution properly, anyone else with this problem_ i have to use lousy 1360x768
Sounds like a DPI issue...
fed44 said:
Sounds like a DPI issue...
Click to expand...
Click to collapse
your on the ball today!

Softkeybar height

I know the nexus10 has a 2560x1600 Resolution but that includes the Softkeybar (Home, Back, Options) which we cant hide. We need the "real" usabable resolution so we dont get on trouble with image cropping etc.
Does anybody know exactly how high the Softkeybar on the Nexus10 is or what the "real" usable Resolution for the Nexus10 is? I googled already but cant find any usefull information.
Would be great to hear something from you guys.
Best regards
Philipp
Just a thought... take a screenshot. If it's less than 1600px high... minus the amount from 1600.
all screenshots i can find are 2560x1600. So that doesnt really help
I think it's 42dip.
for xxhdpi the ratio is about 1:3... So that would be about 126px (42px x 3).
EDIT:
Yep, this should help:
http://stackoverflow.com/questions/8168329/android-screen-sizes-in-pixels-for-ldpi-mdpi-hpdi
Kryten2k35 said:
I think it's 42dip.
for xxhdpi the ratio is about 1:3... So that would be about 126px (42px x 3).
EDIT:
Yep, this should help:
hm that confuses me. I measured it in photoshop on a 2560x1600 Screen shot and it was 96px. But i wanted to make sure so i hoped for some official info about that.
The DP stuff will be important when choosing sizes for UI Elementes but isnt relevant for the whole "whats resolution to work for" problem.
Isnt there any official Info about how many pixel of the screen height (in landscape mode) i loose to the Softkeybar?
Click to expand...
Click to collapse
mitsubstanz said:
Kryten2k35 said:
I think it's 42dip.
for xxhdpi the ratio is about 1:3... So that would be about 126px (42px x 3).
EDIT:
Yep, this should help:
hm that confuses me. I measured it in photoshop on a 2560x1600 Screen shot and it was 96px. But i wanted to make sure so i hoped for some official info about that.
The DP stuff will be important when choosing sizes for UI Elementes but isnt relevant for the whole "whats resolution to work for" problem.
Isnt there any official Info about how many pixel of the screen height (in landscape mode) i loose to the Softkeybar?
Click to expand...
Click to collapse
This guide has some of the basic info for density calculations.
http://developer.android.com/guide/practices/screens_support.html
The value will be different depending on the device's current screen density, but below are the default calculations for the Nexus 10:
The navigation bar height is defined in framework-res as 48dp.
The device's screen density is defined in build.prop as 320.
The density ratio (screen density / android default density of 160) is 2.
48 * 2 = 96px so your measurement in photoshop is right.
You can also visually check using Settings > Developer options > Input subsection > Pointer location
Click to expand...
Click to collapse
I just come back to say yeah it was 48dp. I had changed mine using AOKP to 42dp.
The above post is good info.
I don`t use navigation bar or the notififcation bar.
On aokp roms i hide them with gmd gesture control. Very easy to navigate with gestures and have the whole screen real-estate to apps.

Categories

Resources