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.
Related
it was trying to build a newer version of a watchface. Android Studio upgraded to Version 2.2.
Since that, I have the problem, that the handheld-APK doesn't seem to have the wear-APK inside. If I install it via the play store (as a beta-release), I can see the app, which is for configuration, but the watchface is not pushed to the watch.
If I build the wear-APK alone, it is about 3 MB, the handheld one about 3.2 MB.
I googled a lot but only found one similar article here, but without a solution, only that it might be a bug in AS.
My watchface doesn't have a Activity, as I only use the service.
Can anyone help? Thanks!
This is what is in the wear-manifest:
<uses-feature android:name="android.hardware.type.watch" />
<uses-permission android:name="com.google.android.permission.PROVIDE_BACKGROUND" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
and this in the mobile-manifest:
<uses-permission android:name="com.google.android.permission.PROVIDE_BACKGROUND" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.INTERNET" />
I'm uploading an App to Google Play and there is about 2321 devices not compatibles with it. In order to test it I have setted all uses permissions to false (except openGl, for Maps V2). I'm using a lot of permissions but, for example, as far as I know Sony ST21 (http://www.gsmarena.com/sony_xperia_tipo-4718.php) has all my required features.
This are my required permissions (from Google Play):
android.hardware.CAMERA
android.hardware.camera.AUTOFOCUS
android.hardware.LOCATION
android.hardware.location.GPS
android.hardware.location.NETWORK
android.hardware.TOUCHSCREEN
And this are my permission inside Manifest:
<permission android:name="com.zonaapp.flamencomovil.permission.MAPS_RECEIVE"
android:protectionLevel="signature" />
<uses-feature android:glEsVersion="0x00020000" android:required="true" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="com.google.android.providers.gsf.permission.READ_GSERVICES" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="com.zonaapp.flamencomovil.permission.MAPS_RECEIVE" />
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
Whats wrong with my Manifest Configuration?
Check your min and max SDK version, those 2321 devices not compatibles with it may goes out of of your min & max sdk version.
So, provide min SDK version as below as and instead of max SDK or target SDK version provide latest android version.
Then it will cover lots of devices.
This has nothing to do with your permissions, you need to check the value of minSdkVersion in your manifest file. If it is very high, then many devices running older versions of Android won't support your app.
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!
I'm having trouble getting my app to install on a tablet through the market. Note I'm not using Honeycomb as the app is primarily for a phone. Previousdly I was using level 7 but now changed it to level 10 (2.3.3) to support xlargeScreens. The app installs on my tablet via adb and works great but its not possible to install through the market.
I've read several posts on SO and thought my manifest is correct after adding the supports-screen property.
Here are the most important parts of my manifest:
<uses-sdk android:minSdkVersion="7" />
<supports-screens
android:anyDensity="true"
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:xlargeScreens="true" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.MODIFY_PHONE_STATE" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
Any idea where I'm going wrong?
Thanks in advance.
it's probably your android.permission.MODIFY_PHONE_STATE.
check this official issue that is specific to 2.3+
http://code.google.com/p/android/issues/detail?id=15031
The MODIFY_PHONE_STATE permission was marked as "for system use only" in Android 2.3.
While this was never intended for developers and publicly endorsed by Google, there are hundreds of apps in the marketplace using it. Unfortunately, a seemingly innocent checking by the Android folks has now crippled many popular apps for Android 2.3+.
This is an ENHANCEMENT request that you:
1. Restore the MODIFY_PHONE_STATE permission for Android 2.3.x
2. Create a proper Telephony API for Android 2.3+ (at which time you can remove the MODIFY_PHONE_STATE permission)
If the problem is related to MODIFY_PHONE_STATE
Maybe you can try:
<uses-feature android:name="android.hardware.telephony" android:required="false" />
Never try this, but you can check.
By the way, here you have the information regarding Market-Filtering
Market Filtering
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