Problems wih minSdkVersion 1.5

前端 未结 3 1165
别那么骄傲
别那么骄傲 2021-02-06 11:38

we have a problem related to the manifest file and the property \"android:minSdkVersion\". The issue is: If our platform is 2.0 and we use the property \"android:minSdkVersio

3条回答
  •  情歌与酒
    2021-02-06 11:48

    I assume you're specifying different assets for different screen densities using directories like res/drawable-mdpi, res/drawable-hdpi and so on?

    Android 1.6 (API level 4) was the first version of the SDK to support multiple screen densities, so it knows the significance of these directory names and so can successfully select the correct drawable from your res folders for the particular device it's running on.

    However, if you run an application developed in this way on an Android 1.5 device (API level 3), then the framework does not know that it should only use the medium DPI resources (as there are no Android 1.5 devices released with anything other than medium DPI screens (AFAIK)). So in this case, the framework can end up choosing seemingly randomly from all the available resource in your APK, whether they're intended for high density screens or medium density screens, or whatever.

    However, I haven't seen the reverse happening that you are, i.e. a 2.0 device appears to select drawables for, or assumes, a different screen density.

    I would make sure your res directory layout is correct, and that you're using density-independent measurements in each of your layouts as appropriate.

    But if you want to support multiple screen resolutions and densities and support Android 1.5 devices in a single APK, then I don't believe it's possible.

提交回复
热议问题