diff --git a/docs/html/guide/topics/resources/providing-resources.jd b/docs/html/guide/topics/resources/providing-resources.jd index 7e2f8a0cea04d..1d6ab259c3551 100644 --- a/docs/html/guide/topics/resources/providing-resources.jd +++ b/docs/html/guide/topics/resources/providing-resources.jd @@ -450,8 +450,8 @@ application during runtime.
to match the device density.Added in API Level 4.
-There is thus a 4:3 scaling factor between each density, so a 9x9 bitmap - in ldpi is 12x12 in mdpi and 16x16 in hdpi.
+There is thus a 3:4:6 scaling ratio between the three densities, so a 9x9 bitmap + in ldpi is 12x12 in mdpi and 18x18 in hdpi.
When Android selects which resource files to use,
it handles screen density differently than the other qualifiers.
In step 1 of How Android finds the best
@@ -895,7 +895,7 @@ drawable-port-ldpi/
drawable-port-notouch-12key/
Exception: Screen pixel density is the one qualifier that is not
-eliminated due to a contradiction. Even though the screen density of the device is mdpi,
+eliminated due to a contradiction. Even though the screen density of the device is hdpi,
Exception: If the qualifier in question is screen pixel density,
-Android
-selects the option that most closely matches the device, and the selection process is complete.
-In general, Android prefers scaling down a larger original image to scaling up a smaller
+Android selects the option that most closely matches the device screen density.
+In general, Android prefers scaling down a larger original image to scaling up a smaller
original image. See Supporting Multiple
Screens.drawable-port-ldpi/ is not eliminated because every screen density is
considered to be a match at this point. More information is available in the Supporting Multiple
@@ -922,9 +922,8 @@ drawable-en-notouch-12key/
drawable-port-notouch-12key/