Asked  7 Months ago    Answers:  5   Viewed   52 times

When it comes to developing applications for Android, what is the difference between Min and Target SDK version? Eclipse won't let me create a new project unless Min and Target versions are the same!




An integer designating the minimum API Level required for the application to run. The Android system will prevent the user from installing the application if the system's API Level is lower than the value specified in this attribute. You should always declare this attribute.


An integer designating the API Level that the application is targetting.

With this attribute set, the application says that it is able to run on older versions (down to minSdkVersion), but was explicitly tested to work with the version specified here. Specifying this target version allows the platform to disable compatibility settings that are not required for the target version (which may otherwise be turned on in order to maintain forward-compatibility) or enable newer features that are not available to older applications. This does not mean that you can program different features for different versions of the platform—it simply informs the platform that you have tested against the target version and the platform should not perform any extra work to maintain forward-compatibility with the target version.

For more information refer this URL:

Tuesday, June 1, 2021
answered 7 Months ago

In android_sdktoolslib there's a batch-file called find_java.bat. It calls find_java.exe -s to find a list of potential Java locations. Running the exe file like this returns the error I've been seeing:

Failed to convert path to short DOS path: c:windowssystem32java.exe

-s stands for short. Running it without the -s causes find_java.exe to work, causing find_java.bat to work, causing everything else to work. So the fix was to edit find_java.bat, and remove the -s .

Thursday, August 5, 2021
answered 4 Months ago

Ok I found the solution

Turns out I had 2 ADB installed in different Paths and Android studio was getting one of them that was not the correctly configured. I also had not properly set up the udev rules.

Here are the step I took to get it fixed
1. Remove ADB that was installed manually
2. Modify the udev rules to add the devices (It turns out that both my Nexus 7 and Moto G were not Asus and Motorolla respectively but Google inc instead. I acquired the right Vendor ID code using "lsusb" It returns XXXX:YYYY the vendir iD is the XXXX
3. Add the location of the right adb to path ( /Sdk/platform-tools/)
4. Then rebooted all of the devices (computer and android devices) and it seems it worked.

Sorry for not giving out all the terminal lines that were entered, being novice with Ubuntu it may have been a lot more confusing than helping.

Hopefully it can help someone that is in the same situation.

Sunday, August 15, 2021
answered 4 Months ago

I have the same problem, and my solution is:

Right click on the project folder > Android tools > Clear Lint Markers

"Run Android Lint" makes some markers and the markers cause this error.

Tuesday, September 7, 2021
answered 3 Months ago

Check out this link and you will love it Eclipse-Fonts First you have to open eclipse, in help Menu, find "Install new Softwares" paste the below link in "Works with" text Box

and press Enter, in the below box you will see "Eclipse-fonts", now press the next buttons..... and you have done it. enter image description here After installation is finished, you will see A icon in toolbox and you can zoom in using Ctrl+ and Zoom out using Ctrl- enter image description here

I think this will help you.

Monday, November 8, 2021
Alexey Ferapontov
answered 3 Weeks ago
Only authorized users can answer the question. Please sign in first, or register a free account.
Not the answer you're looking for? Browse other questions tagged :