Just upgraded my Xperia Z to Android Jelly Bean 4.2.2 :
I am curious to know if there is already Sony SDK support for Android 4.2.2 (API17) or 4.3 (API18) or if support is limited to 4.1.2 (API16) with which the Xperia was shipped?
Basically, I'm doing a bit of dev through eclipse and I only see the SDK entry in API16. Now that I've upgraded I'm worrying I'll see problems.
Question :
So, in Android SDK, can I enter Sony SDK in API17/API18 or will I need to simply wait for Sony to update the SDK?
(I have had a look, I just don't know if Sony are slow at this or if I'm missing something in the process; Sony SDK instructions are only for API16 and the entry only appears in API16 in Android SDK manager)
The current Sony Add-on SDK only supports API level 16 as you have noted. You will need to wait for an update if you want to use any new features of API 17 or 18. What kind of problems are you worried about? Your phone should still be backwards compatible with previous API levels so as long as you set android:targetSdkVersion="16" in your AndroidManifest.xml your app should run without issues.
Related
I would like to make an app for my Sony Smartwatch SW2.
As I have an Android 4.1.2 (API 16) phone (it does not support higher versions), I guess I must use Sony Add-on SDK 2.0.
But I am having a hard times finding this 2.0 version, as the older developer pages, although writing exactly about 2.0 version, give the link to the official pages where one can find the only the latest SDK v3.0.
But with SDK v3.0 the minimum supported Android is API 19.
Where can I find Sony Add-on SDK 2.0? Or did I misunderstand something?
You can download v3.0, all what you'll need for SW2 is the samples that can be founded on Android-sdk/add-ons/addon-sony_add-on_sdk_3_0-sony-19/samples/SmartExtensions/
Initially I installed "Sony Add-on SDK 3.0", but in Android Studio it has been installed under "Android 4.4.2 (API 19)".
My main concern is will the app work on SW2 + an old smartphone with "Android 4.1.2 (API 16)" - (no upgrade possible) - I guess not?
The very reason I bought SW2 instead of SW3 is that SW2 supports older Androids starting with 4.0, so I can use it with my Galaxy S2.
I need to test my Android app on a device running jelly bean 4.1.1, however in the SDK manager there is no 4.1.1 package available for download. The closest options are 4.1.2 and 4.0.3, choosing either of these results in my device not being detected.
Is there something I'm missing? Shouldn't 4.1.1 be available in the SDK manager?
The closest options are 4.1.2 and 4.0.3, choosing either of these results in my device not being detected.
I do not see 4.1.2 in the SDK Manager. I see Android 4.1, which is as it should be.
(though I do see some updates to that API level in the SDK that I will need to download when I am not on a conference WiFi network...)
Is there something I'm missing?
No.
Shouldn't 4.1.1 be available in the SDK manager?
No. The SDK Manager goes by API levels, not consumer-facing patch releases. Android 4.1 defined API Level 16, and neither 4.1.1 nor 4.1.2 created a new API level. From the standpoint of a developer, 4.1 and 4.1.1 and 4.1.2 should behave identically. If they don't, that's a bug.
I created a project to implement USB accessory. The accessory mode is supported for Google API level 10 which works on Android 2.3.4.
Now my project works on AVD which has target device as Google APIs level 10 but does not work if I change the target to 2.3.3 ( Since 2.3.4 target is not there on eclipse).
In short I want to run a project that uses Google API level 10, on an android phone. How to do this?
I tried copying the .apk file but that was of no use. I also tried to copy the complete project but this is also not working for me.
Please assist...
I guess the obvious answer (though not the one you're looking for, I suspect) is that you'll need to get a device that's running 2.3.4 or higher (my current RAZR MAXX is at 2.3.6). A device that's running a version lower than 2.3.4 can't be asked to run an app compiled for versions 2.3.4 and higher.
and this may (or may not) be helpful to clear things up as well:
Can't find android sdk 2.3.4 in SDK manager
Welcome to Stack!
You are right, USB accessory does not work with 2.3.3, only with 2.3.4 and up. (And it does only work on selected phones, of course.)
I have downloaded the Android SDK(which i think has no version, it is standard). After installing Android SDK, Android SDK Manager comes which by default selects 3 things to be downloaded (1)Android SDK tools(2)Android 4.0.3 (API 15) and the things under it like documentation, samples etc (3)Google USB driver But at present i am having book on Android 3, so should i deselect the second option i.e. Android 4.0.3 (API 15) and select all things under Android 3.0 (API 11) or keeping Android 4.0.3 will be OK for Android 3.I know there are tutorials for Android 4.0.3 on Web so why should i go for Android 3 because i find it easy through books and i got Android 3 here in my place and still no Android 4. So what should i do?
You can install everything. I would recommend to install the API level you want to develop for. But it doesn't hurt (but wastes disk space) to install everything.
Sidenote: Android 3.0 is for tablets, 2.x for older and 4.x for the latest Android Smartphone devices.
You should select the API level that you will target. For example, I am writing an application for API level 7 (Android 2.1.x), so I've got that version installed on my machine. Of course, you can have more than one API level installed, so it is safe to install any combination (for example 3.0.x and 4.0.4 simultaneously - see last paragraph for the reason).
Once you've got a few API levels installed, Eclipse will allow you to change the target API for your project to any of the versions you have installed. The same applies for the command-line project creation.
There is actually one good use-case for installing a version newer than the one you are targeting in addition to the one you use: testing. You can create an emulation environment for a newer version of the API to ensure that your application does not crash and burn when the API levels do not match. If we were to extend my above example, a sensible set of levels to install is 3.0.x, 3.2, and 4.0.4. You can target the initial release of Honeycomb (unless you need anything from the later versions), and test with both the latest Honeycomb and Ice Cream Sandwitch.
I want to build Android application. My target devices is tablets (not smartphones). Today exist only 3.* version of android OS, aimed for tablets. Is it normal if i begin build application for tablets in 3.* API? The tablets which will be release with android 4.0 (ice cream sandwich) can to run my application built on 3.0 API? Or me better to wait for 4.0 API if my target devices is tablets?
Generally, in which version of API to develop my app for tablets?
Thanks.
I'm pretty sure that the applications which run on Android 3.* will run on Android 4.* too, because there is no point of making and OS if the old application will not run and all the developers have to build their applications for the next version. So I suggest to build your application for Android 3.* if your target devices are tablets.
Android documentation says that all their SDK releases are forward friendly and that seems to be the case when using an emulator. I have an application that was written in 2.0, recently upgraded to 2.1 and we have some people in the office that have XOOM tablets (3.0) and we cant get it installed.
After some modifications to the manifest (suggested steps from droid dev portal) it still wont install on the XOOM at all.
If you are targeting tablets then i would start with 3.0. If there are features in 3.1 that you can't live without then have fun.