I have written an Android application that I am about to release, but I would like to have a 2.1 version with multitouch and a lower API version without. However, if I simply just use the minSDK setting, the 1.6+ version would show up in the market with the 2.1 version on 2.1 phones. Is there any way to release for a specific range of OS versions?
View 3 Replies
I'm developing one android application which needs to support Android OS 1.5, 1.6, and 2.0. I've three different .apk files for all three SDK. How can I upload three different .apk files on Android Market Place for single application? I would like to have all 3 versions available under one application name. is this possible? So, users with any SDK can use my application.
View 5 Replies View RelatedHow can I publish two versions of my app without changing the package name, so that users may upgrade to either version, one for Anroid 1.5 and one for Android 1.6 ? I want to offer new features requiring Android 1.6 as soon as possible, but not all users will have upgraded to Android 1.6.
View 2 Replies View RelatedWe are upgrading our application to add 2.0 support. I have read http://developer.android.com/guide/appendix/api-levels.html and the older blog post http://android-developers.blogspot.com/2009/04/backward-compatibility.... I want to avoid using reflection if possible. I have found that if I set my minSdkVersion="3" in the application manifest but in my build path in eclipse point to the Adroid 2.0 jar file I can compile with direct calls to 2.0 code (with the relevant code to ensure they are not invoked on <2.0 devices). My question is will people with pre 2.0 devices be able to see the application in the market place in this case? What are other people using for multi-targeting different API levels with the same package.
View 7 Replies View RelatedI am planning to have two versions of the same app available in the market - let's say "App-Lite" and "App-Advanced". They both almost the same core functionality, but App-Advanced has a bit more specific features, than the App-Lite has. Now I am thinking what would be the strategy of deploying those two apps in the market. The simple way is to provide different name space in AndroidManifest.xml for both apps, so "App-Lite" and "App-Advanced" would show up as two completely different applications and could be installed parallel on the same device. But I'm also thinking about another way of installing the App-Advanced version - like an upgrade to the App-Lite which might be already installed. To do this, I can just set the same name space for both app in AndroidManifest.xml, so after installing one app would replace the other one - I can do this from adb command line, but I'm not sure how android market would behave in this case. Will it show them as two different apps, will it show them as two different versions of the same app with the ability to upgrade from one version to another, or it just will not allow to publish two apps with the same name space? Is this scenario doable with Android Market?
View 3 Replies View RelatedWhats the best way to deploy several customized versions of a Android application? Currently I have a script to exchange the resource folder for getting a customized version of my app. It works great, but all custom versions still have the same package name in the AndroidManifest.xml. Therefore it is not possible to install two customized versions of the app at the same time.
View 3 Replies View RelatedI need to be able to easily create different "flavors" on an app, each with a unique package name so that they can coexist on the same device. Is there a simple way this can be done, which doesn't require manually updating all the imports and other references to the package name each time I change it?
View 4 Replies View RelatedWe're thinking about building light and paid versions of our app for the Market. But I am not clear what we need to do, or how to do it. (1) Do we definitely need the two versions to have different package names for the two builds ?It seems logical to do it that way, but I have not found a clear answer from Google to that question. Though I have found several people asking the same question. 2) Is there any support in Eclipse for building two similar apps with different package names from the same java and xml files ?In most of the IDEs I've used, it is a doddle to define multiple build targets for one project, but none of those mechanisms seem to be present here. And, the package name is embedded in every java file, as well as in many places in the manifest, leaving me without a tidy way to build to alternate package names.Is there a tidy way to build multiple version ? Or are we really going to end up copying the whole codebase and search-and-replacing the package name.
View 6 Replies View RelatedI would like to know if its possible to prevent my application from looking different every time I run it on a different android phone. For example, on stock 2.2, my seek bar (with default values and theme) has an orange color for the selected portion, whereas on a Samsung Galaxy S (with 2.1), it is green. Also the tab background is grey in stock 2.2, but blue in Galaxy S. On a similar note, my rating bar changes size too. I do not implement multiple screen resolutions and all my drawables are located in the "drawables" folder under "res". I donot specify a minimum sdk requirement.
View 5 Replies View RelatedThis is for an Android application but I'm broadening the question to Java as I don't know how this is usually implemented. Assuming you have a project that targets a specific SDK version. A new release of the SDK is backward incompatible and requires changing three lines in one class. How is this managed in Java without duplicating any code(or by duplicating the least amount)?
I don't want to create two projects for only 3 lines that are different. What I'm trying to achieve in the end is a single executable that'll work for both versions. In C/C++, you'd have a #define based on the version. How do I achieve the same thing in Java?
I have an app on Android Market right now with a minSdkVersion corresponding to Android 1.6. I'd like to make an update that is only visible to users of Android 2.2 and higher (there is a good reason for this, which I will explain below). So I have two questions:
- First, if I publish an update with a higher minSdkVersion than the one it replaces, will existing users still be able to see and download the old version if their device is not >= that minSdkVersion? - Secondly, if so, would it be possible to publish updates to that older version branch? Or would it become a fossil relic, but at least always there for downlevel users? Now for the background. My apps use a large amount of resource files-- about 15MB for the Lite version, and about 55 for the Full version. Prior to Android 2.2, it was not possible to install an app on the SD card, so my solution to this was to have the app contain the bare essentials, and simply download the other resources from my web servers at first-run. However, this means that I must maintain external infrastructure, and it's also a bad experience for users who must download the app, then start another download sequence (I already have had several complaints about this in my user comments). What I would like to do is to keep the app as it is for users with Android OS < 2.2. I'd like to publish an update that is only visible to users with Android OS >= 2.2 which packages everything into the app and allows it to be stored on the SD card. And I'd like to be able to perform maintenance on both versions as needed. Why can't I just do the update as described above to a single branch of the app? Because it would mean that users with Android OS < 2.2 would have to download a massive application to their internal memory, which could be a deal-breaker for devices with only 128MB or 256MB, which is shared with the OS. Since I already have paying customers, I don't think I can ethically create an update that would potentially consume most of a user's internal memory, when the version they purchased was only a couple MB.
I need my app to run on all Android versions, but the Contacts API changed in 2.0. In SDK 1.6 and earlier I use android.provider.Contacts to query the contacts DB, but this does not work in 2.0 Instead, for 2.0 I use android.provider.ContactsContract. This presents a problem: when I have code for ContactsContract, my app will not build for 1.6 and earlier. Do I need to have two separate versions of my app (one for <= 1.6 and one for 2.0 and later) or is there a way to avoid doing this?
View 1 Replies View RelatedI'm contemplating the idea of developing an application for the android. I have several years of experience developing web applications with Java and so figured it shouldn't be too hard to pickup a book and learn how to do it for the android platform. So far so good; that's why I love Java.
My question is in regards to how does the android development community go about testing their applications of the various android version and phones? I think I'm more concerned about the android version rather than the phones. I'm planning on getting the Sprint Evo 4G LTE coming out on Friday, so I'm obviously going to be able to develop and test for Android 4 and HTC Sense 4 (though I don't think that is as important right? Development is usually against the OS and not the UI manager, right?). But how would I go about testing against Gingerbread, Froyo, etc.? Do you guys keep a previous old phone (like my old HTC Evo 4G) and flash diferent roms in order to test the app against previous versions of android? Are there other solutions? If it's using an old phone, does this work off-network/service? I guess you could just dump the apk on the sd card and install as third party app and test it out. As long as the app doing require phone services or mobile data network (internet) you'd be fine if you have wifi access right?
I would like to make a single Android app for multiple Android versions (possibly every one of them)
My problem is that I want to check what is the version of Android the app is currently running on, and dynamically load a class which is version dependent. This part should be ok.
I just wonder how I can achieve that without compilation errors in my Eclipse project. I mean, the project is configured for a particular target (1.5, 2.1 ...), so if a class in my project is not compatible wich the selected target, it will result in errors.
Is there a way to export this classes even if they are not fit for the platform (I thought about a separated lib, but then again : how to compile theses classes into a lib without compilation pbs?) ? This should be ok since they won't be loaded until I ask them to after having checked Android version.
I am currently trying to make my app compliant with all screen sizes / api levels. I have this mostly working, however there is 1 issue i cannot resolve: Layouts in the "layout-hdpi" folder are used by and any phone on 1.5 (API level 3). - Which i dont want, i want API level 3 phones to use the "layout" folder. So to resolve this I added "-v4" onto the folder also, this works, the folder is no longer used by 1.5 phones. However, now the folder is also not used on API Level 6 phones, for example the droid. The droid only picks up the folder if i name the folder: "layout-hdpi-v6". (Also if i put "-v3" on a folder, the layout folder is not used by API level 4 phones) My understanding is that the -v<api level> qualifer allows you to exclude phones on an API level that is too low, so -v4 should mean that the folder will be used by all phones on API level 4 and above. I am finding a folder is only used for that specific API level. Has anybody else ran into this same issue? And does anybody know of any possible solutions?
View 3 Replies View RelatedAre there any viable approaches for creating multiple .APKs out of a single codebase? The apps may share the same code, but they could have different manifest files, different resources, or different external libraries (for example in an app with both free and paid versions, the free version could have a library for display ads). Ideally, this would be a single Eclipse project, with a way to specify which app to build/debug, and possibly a command line way to batch build everything.
View 16 Replies View RelatedI need advice on which app is the easiest and best phone-to-pc app. Like being able to control your computer with your phone, like a desktop controller. I found this app, Desktop Remote Free - Android app on AppBrain. I'm not quite sure how to use it?
View 2 Replies View RelatedI have a few scenarios where I guess I am not alone with. There is no easy solution but this has to be on top of the list I think.
1. Suppose you have an application that is compiled with 1.5 and is working fine even if started on a 1.6 device. But you now want to support other resolutions, so you need to compile with 1.6. Problem: If I recompile and publish the new apk, the 1.5 users want see my applications. Users already downloaded my application can not upgrade. (will there be a "new version" available shown to them in the market?)
2. Lets say your application works fine on 1.5 and 1.6 and you decided to publish your application twice with different package names. "MyApplication 1.5" and "MyApplication 1.6" for example. Problem: The user upgrading from a older version does not know that there is a new version, because you published a new Application. You can write it into the description and tell the user to download the 1.6 version but many users might not read that Settings from the other application are lost. Your downloads are split into two applications, so you might not make it into the top ranks that easy . You might even need to publish 4 applications if you have a light and a paid version.
3. Now 2.0 SDK is available and you want to add multi touch features or any other new stuff for all 2.0 users. Problem: The above problems are getting even worse. There is no way to easily upload multiple apks for the same application. Having to rename the package is also not making this better. Every time svn freaks out and marks everything as new. Sharing code between versions is difficult because of that.
I don't know if its just "3" (provider in Austria), but I still have not received an official update to 1.6. Testing on the real device is not possible with a 1.6 image if you don't want to root your phone and update the rom manually. 2.0 will be on some devices soon, so there is definitely a need to support all 3 versions. There should be a faster update cycle for the users or a slower update of new versions meaning bigger steps. or We get an easier way to support multiple versions. This also means we need a way to know how many actual devices with version 1.5 / 1.6 / 2.0 are already sold and/or upgraded. If i know that 1.5 is only on about 5% of the devices left, then I can just stop supporting that version and upgrade.
I can run my application on 1.5, 1.6 and 2.0 emulator and on a 1.5 device without any problems. But some of my users are reporting force close and strange menu entries (see the attachment) using 1.6 and higher version devices.
This screen should look like this:
http://www.taypo.com/blog/WindowsLiveWriter/TurkceKlavye0.7_6F1/settings_0.7_2.png
And the code that generates this screen is:
<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android">
<PreferenceCategory android:title="@string/general_settings">
<CheckBoxPreference android:title="@string/haptic_feedback" android:defaultValue="true"android:summary="@string/haptic_feedback_summary" android:key="vibrate"/>
<CheckBoxPreference android:title="@string/sound_feedback" android:defaultValue="false" android:summary="@string/sound_feedback_summary" android:key="sound" />
<CheckBoxPreference android:title="@string/auto_caps" android:defaultValue="true"
android:summary="@string/auto_caps_summary" android:key="auto_caps" />
</PreferenceCategory>
<PreferenceCategory android:title="@string/layout_settings">
<ListPreference android:title="@string/keyboard_layout" android:defaultValue="TRQ" android:key="kbd_layout" android:entries="@array/layout_names" android:entryValues="@array/layout_values" />
</PreferenceCategory>
</PreferenceScreen>
I want to use the same eclipse project to maintain only one source code (or two projects that refer to a generic project). My problem is that the names of the package have to be different on the market (eg: my.android.app.lite and my.android.app.pro). If the package names are differents, the generated java ressource files are differents (eg: my.android.app.lite.R.java and my.android.app.pro.R.java). So, the source files must point to differents R files according to the version (pro or lite) and I have to change all the import...
View 6 Replies View RelatedI have 3 android phones with different Os version. I can see all my apps, but one disappeared for more than a day and still can not see it.
View 3 Replies View RelatedAll I'm baffled as to how this Market works. I was expecting a different version of the Market by now but things still seem awry. Say I have two apps - one free, one paid. I release updates to both. The free one is at the top of the list, but the paid one is down in the depths of the list. That kind of sucks. Is this really how it works? Or is something temporarily broken.
View 6 Replies View RelatedI'm trying to figure out a way to programmatically determine if my build was built in debug mode vs. release mode. I'd like to hide some items in my settings screen if it's release. When I build my app in Eclipse I'm building by default in Debug mode. However, when I build the app using the command line, I build it in release mode and sign the app using the jarsigner tool.
I've tried using:
PackageInfo appInfo = manager.getPackageInfo("com.adobe.psmobile", PackageManager.GET_SIGNATURES);
to test if
appInfo.signatures[0].toCharsString()
matches my debug signature and that didn't seem to work.
I'm now trying to see if I can introspect the app's KeyStore, to match the default debug alias described here:
http://developer.android.com/guide/publishing/app-signing.html of "androiddebugkey"
but I haven't figured out how to retrieve the app's KeyStore yet.
I created an application which is displaying camera preview. When the application terminates I noticed that some processes are still running. Also if I try to run the original camera application it displays an error (obviously due to the active process which belongs to the custom application).
Does anyone know how to release all resources when application ends?
I created an application which uses camera and during the appplication execution the screen is always on.
In the onCreate() method I added the lock code...
But after the application termination the screen remains on all the time and if I run the camera application it encounters an error which obviously appears because the camera resources are not released.
Does anyone know how to release all resources on application termination?
I want to create a PRO version of my application for Android and was wondering how to structure my repository. For know I have a trunk and feature branches. I'd like to put a pro version in another branch but maybe there is a better way? For example, maybe I should create two branches - one for free version, the other for pro?
Pro version will have additional features and will be ads-free, so e.g. I don't want to include AdMob libraries in the pro version. Do you have any experience or suggestions as to what would be the best way to structure the repository in this case? I think I've found the best solution (for my app) in this thread:
http://groups.google.com/group/android-developers/browse_thread/thread/4ad3d67f735f16d7/948b4f9eee2490a3
The trick discussed there is about having another application that only serves the purpose of unlocking PRO functionality in the actual application. The unlocking app is paid in the market and the actual app merely checks for the existence of it on the device.
What is the best way to release two versions of an application? E.g. a free version with limited features, and a paid version with the full feature set. #ifdef would be the ideal way to do this, but Java doesn't support it. Could I do something like: try {import com.foo.myapplication.ExtraFeatures; } catch (Exception e) { // ignore it, this must be the free version}? I could manage with this kind of construct, although #ifdef really would be ideal.
View 10 Replies View RelatedI'm pretty new to Android, and I had some questions that I've had trouble getting answered via the web. I have done a few searches, but I'm not sure how to word my question, either. So I apologize if this has already been covered somewhere...but here it goes. I was wanting to know how the Android handles application versions/ updates. Specifically, does an update blow away my database? Is there a way to preserve the users' settings as well?
View 5 Replies View RelatedAfter finishing my android application development I used the command showing below to get private key, but it shows some errors such as "The Keystore was tampered with or password was in correct".
$ keytool -genkey -v -keystore DEBUG.keystore
-alias alias_name -keyalg RSA -keysize 2048 -validity 10000
Is my problem with DEBUG.keystore? Should I need to generate another keystore for public release?
I want to develop application that should support all version (latest and old) and it should adjust screen resolution (large,medium). I read document. There I found legacy application if I develop application in 1.6 there I am giving:
<uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4"/>
Is it good way to develop application and is it support 1.5 and 1.5+. Users able to find my application there market.