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.
Related
Hello I am new to Android Programming, I have a doubt, can I run and test all android applications that I am going to create on my HTC phone with ice cream sandwich. I am using android studio and I prefer to test apps on my HTC connecting via USB. My system is very slow while using an emulator it is very difficult to test on emulator
Also 'compile with' API means what, I understand minimum and target sdk in Eclipse..
Yes, you can use your physical device.
But the good practice is to create a range on AVDs from minimal to max Android versions, and to test your app (run tests if you have wrote them) in those AVDs.
Skipping this point will lead to some users dissatisfaction because your app can fail\crash on untested versions. Different Android versions do have some minor differencies in the API and libs behaviour.
I am currently trying to develop an app for Android platforms in FlashDevelop, using Adobe AIR, and for which I would like the minimum target OS to be Android 2.2.
I have no problems running the app on Android 4.0, however when I try to debug the app on Android 2.2 or 2.3 the app crashes.
Do I need to use an earlier AIR version (I am currently using AIR 3.4) to compile my app in order to be able to run on earlier Android versions?
No, not necessary, we have developed a similar configuration app for android, and it works on 2.3 on wards, but for 2.2 or earlier, check the technical specifications
Just wondering I have searched but I have not found an answer. My question is I installed the latest sdk 4.0 platform. I am testing with a Samsung Captivate which runs on 2.2. When I debug I get the error about them being on different platforms. My question I quess is probably stupid, But can I ever use the captivate to test my apps I build in platform 4.0 or must I stay at the 2.2 level? New to this....Can I update my phone or just test using the 2.2 platform.
You will only be able to test apps that your phone supports. You are able to target different versions of Android (in Eclipse, right mouse click on your project then edit the Project properties - target a lower version of the OS).
Bottom line, if you are writing apps that target a specific version (in your case you wrote something for 4.0) the device you use must support that version of the OS.
You can set the version you target, which will allow you to debug on your device.
We are seeing a problem with our company's application that has me very confused about the Android compatibility model.
Our app supports Android 2.1 and later. It is targeted for 2.2 and later. Our application manifest expresses this as follows:
<uses-sdk android:targetSdkVersion="8" android:minSdkVersion="7"></uses-sdk>
One of our customers is having a problem running our app on a Sprint Motorola XT603, Android 2.3.5.
The app is visible to them in the Market (as expected), yet when they try to run it, they get the following failure:
*'This app is incompatible with your Sprint Motorola XT603'.*
An interesting tidbit is that developer.android.com does not even list 2.3.5 as an Android version: http://developer.android.com/guide/appendix/api-levels.html.
From what I have read, I believe we are properly using the <uses-sdk> entry. We have successfully installed and run our app on later Android version (HoneyComb/3.0).
Is anyone familiar with 2.3.5 and why this compatibility issue exists?
Android 2.3 is actually available in its 2.3.7 version.
But 2.3.5 to 2.3.7 are just bug fixes and application updates (for example : voice and video chat in Google Talk in 2.3.4), nothing new for developers...
It would have been a nonsense to change API level... 2.3.3+ is API level 10.
On the other hand, if the android market allows them to install the application, this application is assumed compatible: do your customers use a custom ROM ?
I have problems to get my application available for some devices. So I decided to keep it simple and go back to the "Hello World" example project, and try to make that available for those devices. Unfortunately, no matter what I try, the market keeps filtering it for the good old Samsung Galaxy i7500 and the T-Mobile G1 (HTC).
Copy Protection is Off, the application is "Free" and available for all countries but Unpublished (I'm not trying to download it ... yet).
The Manifest file has:
<uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4"/>
The manifest really has no other filters (permissions, uses-.. or supports-...)
I'm using eclipse, Indigo on Ubuntu Linux (11.04)
SDK version r14
Problem existed also on Eclipse Helios, Android SDK version r10
The Market application info states:
This application is only available to devices with these features, as defined in your application manifest.
Screen layouts: SMALL NORMAL LARGE XLARGE
Required device features
android.hardware.touchscreen
This application is available to over 694 devices.
Unsupported devices (some examples) are:
HTC
G1 (trout)
Touch Viva (opal)
Samsung
Behold II (sgh-t939)
Galaxy (gt-i7500)
Moment (sph-m900)
Spica (spica)
At least the G1 and the i7500 have a touchscreen, so that can not be the problem.
The Hello World project is made in Eclipse, with File->New->Android Project , and then just add the line mentioned in 2) in the manifest file. Sign, upload to market, save, and check the Device Availability Dialog.
It worked fine until somewhere in september, after I used the Android SDK Manager in Eclipse to update to the latest release. Am I the only one with this problem? How can it be solved?
This is a bug going on. The same thing actually happened to me. I ended up renaming my package and uploading it to the market and then it worked. This may be a solution you can try.
It looks like those devices can't even have android market so don't worry
reference: https://www.google.com/support/androidmarket/bin/answer.py?hl=en&answer=1141080
android version must be over 1.5 and those cellphones are:
G1 android v1.1
gt-i7500 android v1.5
Touch Viva Windows Mobile
Behold II android v1.5
(sph-m900) android v1.5
...
"Device is running Android 1.5
At this time, the Android Market website is only compatible with devices running Android 1.6 or higher. If your device is running Android 1.5, we recommend contacting your carrier or device manufacturer to see if an update to a higher version of Android is available."