API level 19 not supported for Wear apps? - android

Fresh start with Android Studio, I created a new Project and added checked both Phone and Tablet and Wear. I chose MinSDK 19 for mobile and 20 for Wear (there is no option here). As I try to compile and run this project on my phone (Running 4.4.4 API Level 19), it just fails with the error INSTALL_FAILED_OLDER_SDK.
I have tried all possible permutation-combinations of API levels for the Mobile/Wear projects but I can't get it either compile/run on the device.
Any thoughts?

you cannot put your app as SDK 20, that needs to go in your wear app, leave your main app at 19

Related

Android Studio Android Phone "Android Version" 9.0 with SDK API v22?

I'm a new Android developer using Android Studio. I've purchased a phone to test my app. My app runs SDK API 27 and higher (i.e., OS Oreo 8+).
My specific question is why does my Android version 9.0 phone have SDK API of 22 rather than SDK API 28?
I purchased a phone that says its running Android 9.0 (Settings->About Phone->Android version = 9.0)
According to wikipedia and other links Android 9 should have SDK APIs of 28.
When I connect the device to Android Studio with USB Developer Mode enabled, I get a red (!) error that Android 9T (minds(API 27) > deviceSdk(API 22))
Additionally, I cannot download my app from Google Play as google play also thinks the API level is too low.
Another interesting thing about the phone is that it won't let me upgrade to Android 10, which I thought it should be able to. When I click the Android 9.0, nothing happens, i.e. 10.0 isn't available.
Sorry! Because of my reputation, I can't comment. As #Mehran B said you may be scammed. First, find IMEI Number of your mobile from the settings. Then go to here
. Type your IMEI Number there and check info like Company Name, Model that matches with your physical device.
Hope helpful!

How to choose target API level when creating a new project in Android Studio?

I am new to android development and Android Studio. I also have a physical device which runs android version 5.0.1. When I try to debug an app from Android Studio on my device I don't get the behavior as in the emulator.
My project's target API level (when I create it) is always 23 (Android 6.0 Marshmallow). Although the minimum API level is 17 (Android 4.2 Jelly Bean) I want to know how to set the target API level on project creation. Is this possible with the current version of Android Studio (1.4.1)?
There is no way to choose the target API level using the New Project wizard in Android Studio currently (1.4.1). It should always be the latest version available anyway.
From http://developer.android.com/intl/es/training/basics/supporting-devices/platforms.html#sdk-versions:
To allow your app to take advantage of these changes and ensure that
your app fits the style of each user's device, you should set the
targetSdkVersion value to match the latest Android version available.
To modify it after project creation just edit the targetSdkVersion value in your build.gradle file.

Eclipse: keep getting "ERROR: Application requires API version 15. Device API version is 14 (Android 4.0.2)."

I've been testing an Android app on a device that had API version 15 installed. I now have to switch to a different device (a Samsung Galaxy Nexus, if it matters) that has version 14. Even though I changed "project build target" from Google APIs 15 to 14, I still get the following message when I try to execute the app on the new device:
ERROR: Application requires API version 15. Device API version is 14 (Android 4.0.2).
Cleaning all projects did not help. Restarting Eclipse did not help. I created a simple new test app with target=14 and it worked fine.
Why changes to the old project are not taking effect?
Thanks!
You have to change the minSdkVersion in your AndrodManifest.xml. See this post and the blog entry it is based on for details.

move to sdcard with minSdk=4 (Android1.6)

I want to add a new feature, move2SDcard available only on API8 (Android2.2) but making minSdkversion="4". So, I change the Android jar file loaded in eclipse by (project prop -> Android ) and select Android 2.2 Project compiles and runs.
Is this a good way to add new apis specific to new versions.
for minSdkversion you need to specify the minimal api level with which you app runs with no problems, in you case api level 8. If you say min sdk 4 that means that your app will be able to be installed on phone with api level 5 and in app with api level 5 I think your app would NOT be able to work correctly.
with Android 2.2 it goes minSdkversion="8" (API level 8) FROYO
here are some platform highlights http://developer.android.com/sdk/android-2.2-highlights.html
take a look to the statistics of the market and you will understand that most of the apps are above API 8 http://developer.android.com/resources/dashboard/platform-versions.html

How do I emulate a HoneyComb-compatible app on older emulators?

I began the process of making one of my apps Honeycomb-friendly.
I started by changing the project's target build to version 11, and edited to AndroidManifest.xml to use:
<uses-sdk android:minSdkVersion="5" android:targetSdkVersion="11" />
These are the only changes I made so far. I am able to test it perfectly on my Honeycomb tablet device.
However, I cannot get Eclipse to launch this app in an older emulator (e.g. version 9). Technically speaking, the app should run in older android versions, so what can I do to test this app for older devices?
Or am I doing something else wrong?
I'm by no means an expert on this front but setting the minSdkVersion different from the targetSdkVersion doesn't make the app automatically use a different API level based on the device. See this:
Android Min SDK Version vs. Target SDK Version
and this:
http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html
I suspect that because your application is using level 11 apis it won't run on a device that is of a previous API level.
This seems to be some sort of bug. When my 3.1 device is plugged into my PC, Eclipse/Android won't let me launch a new emulator that's < 3.0.
I worked around this by launching the emulator before I plug in my device, and then it has no problems deploying the app to both of the running devices.

Categories

Resources