Android应用程序 "unsupported"再次设备(回答: Bluetooth permission issue)

Question

我在 SO 上看到了几个这样的问题，但对于我的具体情况没有好的答案。一位使用“AnydataVisual Land Prestige 7D– PRO7D”Android 平板电脑的用户问我为什么我的应用程序在 Google Play 上被列为他的设备“不受支持”。不知道为什么，也没有办法向 Google 询问此事。

我阅读了类似问题的其他回复，但它们不适用。根据设备规范( http://www.visual-land.com/107d.html ，向下滚动，单击“技术规范”选项卡)，它具有 Cortex-A9 1.6GHz CPU、1GB RAM、7 英寸 1024x600 屏幕、运行 Android 4.1 Jelly Bean、WiFi、摄像头、扬声器、耳机 socket 。虽然没有提及蓝牙，并且我的 list 要求蓝牙许可，但这不应排除该设备。用户侧加载了我的 APK，并且该应用程序没有任何问题。还有其他想法吗？下面是我的 AndroidManifest.xml 的相关 fragment :

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
      android:installLocation="auto"
      package="com.hyperionics.avar"
      android:versionCode="4040000"
      android:versionName="4.4.0">
<uses-sdk android:minSdkVersion="8"
          android:targetSdkVersion="19" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.INTERNET" />
<supports-screens
        android:xlargeScreens="true"
        android:largeScreens="true"
        android:normalScreens="true"
        android:smallScreens="true"
        android:anyDensity="true" />
<application android:label="@string/app_name"
             android:icon="@drawable/at_voice"
             android:name="com.hyperionics.avar.TtsApp"
        >
(...)

我还在应用程序中使用 JNI native 库，并为 ARM、ARM-V7、MIPS 和 Intel CPU 构建单独的软件包，据 Google 称，在其他 4518 设备上没有问题...

该应用程序是网页、文章、PDF 文件等的 TTS 阅读器。或者，如果我们无法弄清楚这一点，是否有人知道就此类问题联系 Google 的好方法？

格雷格

Answer 1

No mention of Bluetooth though, and my manifests asks for BLUETOOTH permission, but that should not exclude the device

是的，应该如此。

引用the documentation :

Some feature constants listed in the tables above were made available to applications after the corresponding API; for example, the android.hardware.bluetooth feature was added in Android 2.2 (API level 8), but the bluetooth API that it refers to was added in Android 2.0 (API level 5). Because of this, some apps were able to use the API before they had the ability to declare that they require the API via the system.

To prevent those apps from being made available unintentionally, Google Play assumes that certain hardware-related permissions indicate that the underlying hardware features are required by default. For instance, applications that use Bluetooth must request the BLUETOOTH permission in a element — for legacy apps, Google Play assumes that the permission declaration means that the underlying android.hardware.bluetooth feature is required by the application and sets up filtering based on that feature.

有a special section in the documentation关于为解决您的场景的蓝牙权限正确设置 list 。