Instead of trying to infer the dp conversion factor from the screen’s density classification, you can simply query it directly: getWindowManager().getDefaultDisplay().getMetrics(metrics); float logicalDensity = metrics.density; logicalDensity will then contain the factor you need to multiply dp by to get physical pixel dimensions for the device screen. int px = (int) Math.ceil(dp * logicalDensity);
Here is my learning from the RnD I did on system settings app (immersive control panel). (see my other answer for a simple C++ API I created from this learning – https://stackoverflow.com/a/58066736/981766. A simpler method for single monitor setups, or if you want to change DPI of just the prmary monitor is given here – … Read more
The problem is no one, not even the OS, knows the exact physical dimensions of the screen. You’d need to know that in order to calculate the PPI. There’s a display setting in the control panel where the user can manually specify the PPI and by default it’s set to 96.
You don’t have to do that to support different densities. What you do is create different resources folders: res/values-ldpi/dimens.xml res/values-mdpi/dimens.xml res/values-hdpi/dimens.xml Then Android will decide which file to use. You can have something like: <!– in values-ldpi/dimens.xml –> <dimen name=”textSize”>25dip</dimen> and.. <!– in values-mdpi/dimens.xml –> <dimen name=”textSize”>20dip</dimen> etc. And you shouldn’t care about resolution… there … Read more
I guess that’s a good way to go. The only downside I can think of is the resource overhead on small scale devices and possible artifacts because of the downscaling. Actually at this year’s Google IO Chris Pruett recommended embedding only high resolution assets and let opengl handle the scaling.
Well, um, all I can say is “Welcome to the real world.” You get your screen dimensions passed to you via onSurfaceChanged, and yes, it is your job to figure out how to scale everything based on this data. That’s why they pay us the big bucks. 🙂 You will want to make sure your … Read more
You don’t have to have each image in all scales if it won’t be used. Make only the sizes you need and name them according to their width. For portrait full-device-width images, you need 320px wide at 1x and 2x, 375px wide at 2x and 414px wide at 3x. 4″ devices used “-568h” suffix for … Read more
For Different screen size, The following is a list of resource directories in an application that provides different layout designs for different screen sizes and different bitmap drawables for small, medium, high, and extra high density screens. res/layout/my_layout.xml // layout for normal screen size (“default”) res/layout-small/my_layout.xml // layout for small screen size res/layout-large/my_layout.xml // layout … Read more
Finally after 2 days of searching and testing, i finally managed to find out what’s the real issue here.. All those above coding will give correct resolution. But the most important this is that we need to mention the target SDK in the manifest file.. Otherwise it will give wrong result if the density is … Read more
According to Supporting High-Resolution Screens In Views, from the Apple docs: On devices with high-resolution screens, the imageNamed:, imageWithContentsOfFile:, and initWithContentsOfFile: methods automatically looks for a version of the requested image with the @2x modifier in its name. It if finds one, it loads that image instead. If you do not provide a high-resolution version … Read more