Problems wih minSdkVersion 1.5
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:minSdkVersion=3" (3 = sdk 1.5) the graphics get corrupted (In details, the application's resolution get reduced to a 2/3 part of the original size, this is, when the resolution should be 480x720, it becomes in a 320x480). This is happening on the Android emulator, and on the devices Droid/Milestone (Which are platforms 2.0). When we switch the property to "android:minSdkVersion=4" (4 = sdk 1.6) the problem gets solved, but when we want to put that version on platform 1.5, Android doesn't allow us to install it. It would help us to know any conflict regarding graphics within the 2.0 sdk, or any known problem around the "android:minSdkVersion" in the manifest.
Asked by: Brooke213 | Posted: 24-01-2022
If you specify
targetSdkVersion as well as
minSdkVersion your application will start to work correctly on all platforms.
So have an entry in your manifest like this:
<uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4"/>
This is covered in the Android API Levels page in the Android Developer documentation.Answered by: Julian548 | Posted: 25-02-2022
I assume you're specifying different assets for different screen densities using directories like
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.Answered by: Ada251 | Posted: 25-02-2022
Add this tag in your AndroidManifest.xml to support multiple screen densities.
Answered by: Emily541 | Posted: 25-02-2022
<supports-screens android:largeScreens="true" android:normalScreens="true" android:smallScreens="true" android:anyDensity="false" />
Android minSdkVersion and using classes introduced in higher level SDK
I was testing android minSDKVersion property and find a strange behavior- I put minSDKVersion=3 (1.5) and targetSDKVersion=4 (1.6) in androidManifest.xml file. For testing, I put following lines in onCreate method of launching activity - android.telephony.SmsManager sm = android.telephony.SmsManager.getDefault(); ArrayList<String> stringArray = sm.divideMessage("this is message"); T...
java - Titlebar shrinks when I specify a minSdkVersion in AndroidManifest.xml
I am trying to specify the minSDKVersion: <uses-sdk android:minSdkVersion="5" /> Whenever I add this line, my titlebar shrinks a little bit. Not sure why? When this line is not in my manifest, everything is fine. <?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" android:versionCode="1" andr...
android - Suppress AndroidManifest.xml minSdkVersion related warning
As recomended here http://developer.android.com/guide/practices/screens_support.html for compatibility reasons my AndroidManifest.xml contains this: <uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4"/> This generates warning in eclipse: Attribute minSdkV...
android - Setting minSdkVersion and available emulators?
Today I upgraded to SDK version 3.0 from 2.3.3. I have one question that has always puzzled me. My code is unchanged from when I built it with build target API level 7, so there are no API level methods called. I've now changed the Properties/build target to API level 11 but set the minSdkVersion to level 7 in the manifest. When I set up a run configuration under Eclipse, the only AVDs available to me are ...
sdk - Write to file depending on minSdkVersion - android
I have written a filewriter for my android application. It is to function on a Galaxy Tab, so my minSdkVersion has to be at least 4, so it will fill the screen. I originally started out with SdkVersion = 2 and at that point my filewriter worked perfectly. Changing the SdkVersion to 4 introduced the problem. My filewriter doesn't work anymore! The application runs fine, but a file doesn't get created. My .jav...
android - How to change the minSdkVersion of a project?
I have been building a project and testing it on the Android emulator. I realized that I set the minSdkVersion to 10. Now, I have a phone to test the program on, but its sdk version is 7. I tried to go into the manifest file, and change the sdk version to 7, but every time I run the program, it crashes. How can I rebuild or change the sdk version to a lower number (from 10 t...
android - Possible Market issues when increasing minSdkVersion
my app is currently compatible with Cupcake and up. That is: minSdkVersion is set to 3 in the manifest. For some technical reasons I am thinking about breaking compatibility with Cupcake, by setting minSdkVersion to 4. But I have quite a few existing users who either downloaded the lite version or purchased my app, and who are running Cupcake. What will happen to them on the Android Market? Will the...
android - Increasing minSdkVersion causes Out Of Memory errors
I developed my app with minSdkVersion set to 3, targetSdkVersion set to 8. My app is published, and runs on everything from Android 1.5 to 3.0 Though devices it will run on with anything older than 2.0 is always spotty, some it will and some it won't It works perfect on my Incredible, Android 2.2. It uses 5-8mb memory when running. However I decided I wanted to split it into two different a...
I wrote a program that worked perfectly until the market required me to add 'minSdkVersion'. Since I was using 2.3.3 capabilities I set it at 10,but then my program stopped being able to access files from the disk (all file access is false though it works without 'minSdkVersion'). Changing it to require API 1 fixed the functionality but now inadequate OS versions can download it. Should the 'minSdkVersion' be able to ch...
java - Why does changing the minSdkVersion of my application change the color of the text in my tabs?
Why does changing the minSdkVersion of my application change the color of the text in my tabs? Am I doing something wrong? I recreated the problem using the Hello Tab Widget. By adding <uses-sdk android:minSdkVersion="8" /> to the manifest, I get ugly tabs. If I don't want ugly tabs, do I have...
Still can't find your answer? Check out these communities...
Android Google Support | Android Community | Android Community (Facebook) | Dev.io Android