In my new version when putting these permissions in Manifest, I had a reduction of compatibility with several devices, would I have some way to verify this or who does not support these permissions will be left out anyway? %pre%
___ ___ erkimt How to minimize the reduction of compatibiliade due to the use of permissions? ______ qstntxt ___
______ azszpr45473 ___
One of the reasons for this problem is that your app requires GPS (ACCESS_FINE_LOCATION) to accurately access location. That is, if a device does not have GPS, it is excluded from the compatibility list.
One solution is to use ACCESS_COARSE_LOCATION, which gets the location over the network. This form is less precise, but works for some applications (I do not know if this is your case).
Another way is to add the following to your %code% :
%pre%
Or:
%pre%
This informs that even your app needing GPS, you treat the situation for cases where there is not. Then, non-GPS devices can install your app.
Another detail that limits a lot of compatibility is the minimum version of Android ( %code% ) required to run the app. If the minimum version is very recent, you will probably delete many devices from the compatibility list.
For example, if the minimum version is API 14, Android 4.0, you can reach up to 90.4% of devices.
___
One of the reasons for this problem is that your app requires GPS (ACCESS_FINE_LOCATION) to accurately access location. That is, if a device does not have GPS, it is excluded from the compatibility list.
One solution is to use ACCESS_COARSE_LOCATION, which gets the location over the network. This form is less precise, but works for some applications (I do not know if this is your case).
Another way is to add the following to your %code% :
%pre%Or:
%pre%This informs that even your app needing GPS, you treat the situation for cases where there is not. Then, non-GPS devices can install your app.
Another detail that limits a lot of compatibility is the minimum version of Android ( %code% ) required to run the app. If the minimum version is very recent, you will probably delete many devices from the compatibility list.
For example, if the minimum version is API 14, Android 4.0, you can reach up to 90.4% of devices.
2
In my new version when putting these permissions in Manifest, I had a reduction of compatibility with several devices, would I have some way to verify this or who does not support these permissions will be left out anyway?
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
asked by anonymous 30.12.2014 / 00:46
1 answer
1
One of the reasons for this problem is that your app requires GPS (ACCESS_FINE_LOCATION) to accurately access location. That is, if a device does not have GPS, it is excluded from the compatibility list.
One solution is to use ACCESS_COARSE_LOCATION, which gets the location over the network. This form is less precise, but works for some applications (I do not know if this is your case).
Another way is to add the following to your AndroidManifest.xml :
<uses-feature android:name="android.hardware.location" android:required="false" />
Or:
<uses-feature android:name="android.hardware.location.gps" android:required="false" />
This informs that even your app needing GPS, you treat the situation for cases where there is not. Then, non-GPS devices can install your app.
Another detail that limits a lot of compatibility is the minimum version of Android ( android:minSdkVersion ) required to run the app. If the minimum version is very recent, you will probably delete many devices from the compatibility list.
For example, if the minimum version is API 14, Android 4.0, you can reach up to 90.4% of devices.
30.12.2014 / 02:46