Develop Reference

Android app failure of execution in some devices

In an application that I recently uploaded at Google Play there are reports of some users that the application can not even executed. In particular it is reported that this happens at
Samsung S4
LG Nexus 4
Sony Xperia Z2
Samsung Note 1 (N7000) (ANDROID 4.1.2)
The permissions of the app are
<uses-permission android:name="android.permission.WRITE_INTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.STORAGE" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
and
<uses-sdk
android:minSdkVersion="14"
android:targetSdkVersion="22" />
A possible code incompatibility maybe is on the file functions since the application checks for a particular folder to exist every time that it executes and try to create it if it is not exist. However, since I do not have access at that devices, I can not be sure of anything.
So the question is:
Is there any particular restrictions on that devices concerning the permissions of the application? What could be the problems in the code that creates this problematic behaviour?
Thank you in advance for any hints or advices.

The problem was at the third line of the MainActivity where I declared that the application will appear in landscape mode...
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
For a reason I do not understand that line created a memory overflow in some devices and the application was instantly crashed. I manage to find the faulty code by try and error when I created a Nexus 5 API 22 x86 virtual device and reproduce this situation.
The solution was to remove the above faulty line and type
android:screenOrientation="landscape"
in the AndroidManifest.xml file.

android app force closing in release mode

I have finished developing an Android app. I'm using android studio. Everything is working fine when I normally run the app in debug mode on my device. Not even an exception.
But when I followed Google's guidelines on creating the signed release version of my app and installed it in my device, the app is force closing as soon as I launch it.
I just can't figure out a way to locate what the problem is. I created the release version using the "Generate signed apk" option in the Android studio IDE. Then I copied it in my device and installed the app. And then when I run, it just stops working immediately.
I don't know what more info should I give here because I just can't infer the cause of this issue.
Please help. What can be the possible reasons behind such problems.? And how can I find them?
EDIT:
Everytime I unlock the device, it is displaying the dialog "MyApp has stopped working". There's nothing in the logcat. I have no idea why this might be happening. My app uses these permissions:
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />
<permission
android:name="com.mypackagename.permission.C2D_MESSAGE"
android:protectionLevel="signature" />
<uses-permission android:name="com.mypackagename.permission.C2D_MESSAGE" />

I solved the issue on my own.
First of all, you can use a tool named "monitor", present in the android sdk tools to debug your release version. This tool shows everything that happens in your device.
I used the tool and found out that the problem occurred because I had enabled proguard in my app and forgot to add rules for third party libraries used in my app.
So all those who might be facing this problem, check your proguard file and make sure you've added the required rules for all third party libraries as well.

app works on development google-play store show device incompatible

I'm developing a android app. While developing I tested it on Moto E os-4.4.4. It works properly. But after deployment playstore shows your device is incompatible with this version. It shows compatible with many other devices running same os version.
I found some similar questions I tried there answers but nothing seems to work for me.
Any help is appreciated.
Here's my manifest file
<uses-sdk
android:minSdkVersion="7"
android:targetSdkVersion="19" />
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"
android:maxSdkVersion="18"
/>
<uses-permission android:name="android.permission.GET_ACCOUNTS"/>
<uses-permission android:name="android.permission.CAMERA"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
Not only moto e, its showing incompatible with over 1000 devices. The external libraries I've used are apptentive,flurry,facebook and actionbarshelock.

Android 4.4 is version 19. By setting a max SDK version, you're telling it not to allow install on any version over 18. So it won't consider your device compatible. Remove that max sdk version. Even google no longer checks this on the device beyond version 2.0.1.

There was some problem with google-playstore. It got solved after playstore update and now it's compatible with my device as it should be.

Android App is incompatible on a lot of devices

I am the developer of a rather popular game published on Android Play Store. Until just the latest version, most devices, if not all, were able to download and enjoy this game. However with this latest version, a lot of older devices (~2 years old?) have started seeing the game as "incompatible" with their device.
I diffed the manifest files of the two versions, and the only difference that pops up is the change to android:versionName, android:versionCode.
I related thread suggested that this might be because the APK might be too big for the devices. While it is true that we do have the APK sitting at ~49 mb, it only grew from 48.66 -> 48.68 this version, so I find it hard to believe that this is the reason.
The list of incompatible devices is quite extensive but here are some of the standouts..
galaxy nexus
samsung galaxy tab 10.1 
Samsung Galaxy Tab 7.7
eeepad asus transformer tf101
Motorola XOOM
Acer Iconia Tab A700
This list is directly from our (former?) customers, but I have verified this on a Galaxy tab 10.1, and Transformer. Tab 2 and Nexus 7 are able to see it, if that helps.
Update: These devices are shown as compatible in the developer console.
Have there been any recent changes in the way these things are decided? Is there any service which tells us why the app is said to be incompatible?
The permissions section of my app is below
<permission android:name="com.nubee.japanlife.permission.C2D_MESSAGE" android:protectionLevel="signature"/>
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />
<uses-permission android:name="com.nubee.japanlife.permission.C2D_MESSAGE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.READ_PHONE_STATE"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.READ_SMS" />
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.WRITE_SMS" />
<uses-permission android:name="android.permission.SEND_SMS" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.GET_TASKS" />
<uses-permission android:name="com.android.vending.BILLING" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="android.permission.MANAGE_ACCOUNTS" />
<uses-sdk android:minSdkVersion="7" android:targetSdkVersion="7"/>

As I can see you have lots of permissions in your application which in most devices / tablets won't let you to install it via Play Store. Depending on what is actually doing your application and in what kind of device (phone / tablet) it will be used in most cases you should consider using for example :
<uses-feature
android:name="android.hardware.telephony"
android:required="false" />
First of all it's just an example! I am doing that in one of my apps where I am letting the user call certain numbers, that's why I need TELEPHONY permission, but it's not neccessary for my app. That's why I am using use_feature with required=false.
Hope this helps you!

application requires feature(s) not available on your device

I have an Android application on Android Market, but some users are complaining about an error shown when the installation starts, just after the download:
One of them sent me a video of this error showing up, and I could see that this error is not caused by the application, but probably in the verification of permission/features process.
As far as I know, this error is just happening on Motorola Droid/Milestone devices running Eclair, it doesn't happen with Froyo. Unfortunately, I don't have access to any device like this one in order to run logcat and check what's going on.
Here are my permission/features on AndroidManifest.xml:
<uses-feature android:name="android.hardware.camera" />
<uses-feature android:name="android.hardware.location" />
<uses-feature android:name="android.hardware.telephony" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.FLASHLIGHT" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.ACCESS_GPS" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

I finally found out what's happening by getting a Droid device and running logcat:
E/PackageManager( 1280): Package com.mycompany.myapp requires unavailable feature android.hardware.telephony; failing!
Motorola Droid devices running Eclair are not able to install applications that declare
<uses-feature android:name="android.hardware.telephony" />
in their manifest. It's very strange, though, because the Android Market should hide it from these devices. This is probably a bug caused by the changes made to the Eclair by Motorola, since it doesn't happen with other devices running Eclair, neither with the same Droid running Froyo.

According to the docs:
Android Market attempts to discover an application's implied feature
requirements by examining other elements declared in the manifest
file, specifically, <uses-permission> elements.
Given that, have you tried removing the uses-feature tags? Since those are implied by the uses-permissions tags, and you aren't using the "android:required" attribute.

The device say " this feature is not available in this device " when I'm installing an app downloaded from play store and i have to give it permission