Develop Reference

Android Apps run well on android studio but not compatible in store

I've been developing with a device in android studio, and run well, no issue at all.
But after I released it in store, some devices including mine could not find it because it was incompatible.
Is there anyway to find out why my device isn't compatible in store?

you beat me by seconds to the answer except mine was wrong. :)
Well not exactly- what I was going to say is that Android Studio has great documentation and I remember reading about that when I first downloaded it.
If you want to run on older devices the best way to be sure is to download a VM that is the lowest possible supported version and test on that before dist.
All the best.

You must be setting your minSdkVersion higher than your device sdk version in build.gradle or setting supports-screens to the limited device in your manifest.
Apart from that if you are using some hardware permission which is not necessary then set required false in manifest.
e.g
<uses-feature
android:name="android.hardware.camera"
android:required="false" />

Unity Android plugin (connecting Thalmic devices) doesn't work on 6.0

I have an Unity game which use an Android Plugin. This plugin is used for connecting and sending the informations from thalmic bracelets to my Unity Game.
In this plugin there is a scanner for detecting the bracelet using Bluetooth. The scanner works on Android 4 but when I try it on Android 6.0, the scanner doesn't detect anything.
I don't know if you guys know what could cause this, I'm a little lost right now.
Thank you

This is likely permission problem. Things changed in Android 6.0 Marshmallow. Android permission is now asked during run-time.
This is a bug that is now fixed in Unity 5.4.0B15 to support Marshmallow.
Unity 5.4.0B15 Android Marshmallow - Fixed issues when querying for custom permissions.
Update to 5.4.0B15 or above in order to fix this problem.

android application running in simulator but not in mobile devices

Recently I've created one android application using eclipse and ran it using android virtual device manager. It ran successfully in the simulator, but whenever I am trying to install it in mobile device HTC Salsa (2.3 ginger bread) it is showing an error message and not proceeding. The error message is:
Parse Error: There is a problem parsing the package
As it was my first demo application in android so it will be very helpful if you will guide me in this.

Got the issue, it was happening because of the API version. I have the target version as 4.0.3 i.e, API 15 but ginger bread is of API 10. So I've modified the line <uses-sdk android:minSdkVersion="15" /> in manifest file to <uses-sdk android:minSdkVersion="10" />. Now it is working fine. Thanks for all of your help...

Try to "clean" then "rebuild" your project.

Why is our Android 2.2 application "incompatible" with Android 2.3.5

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 ?

What happens if we use/install 2.3 build in 2.2 device

I am working on application which should go into android 2.2(Froyo) and android 2.3(GingerBread) devices.
I have built application with android 2.3 SDK , and Installed the same application in 2.2(Froyo) and 2.3 (Ginger Bread) devices.
In both the devices application installed successfully and it is working properly.
I want to know if we install the higher version build into lower version devices is there any chances to face problems.
Till now I didn't found any issue with this.
I didn't used the MIN:SDK version field in the Manifest file.

If you want only users from version 2.2 and up to download your app, just make sure your minimum SDK version is 2.2 by putting this line in your AndroidManifest.xml:
<uses-sdk android:minSdkVersion="8" />
If you want an upper bound limit as well, you can add:
android:maxSdkVersion="10"
So users with Android SDK version 2.2 up to 2.3.3 will be able to install your app.
Regarding problems: If you're using a specific SDK API then just make sure to add an if clause around it to make sure you're on the right version. The best thing to do is change the target to 2.2 just to see if you have any compilation errors... Then you'd know what to change.
Then just fix the problems, change back to 2.3 and build.

If you don't specify the minimum sdk attribute in the manifest file users with 2.2 won't see your application on the market. It specifies that your application supports 2.2 so that users can see the app on the market.
Make sure any functionality that you use from 2.3 has an alternative functionality so that 2.2 users have the ability to actually use your application.

yes , u can find problem ,
try to install that app on android 1.6
it's about API version , there will be some APIs in your app doesn't supported in a lower API version