签名的 .apk 未安装在 ARM11 (ARMv6) 设备上
当我通过 ADB 部署或安装在 /bin 中生成的 .apk 时，我正在开发的应用程序可以在 ARM11 (ARMv6) 设备上安装并正常运行，但是一旦我对 .apk 进行签名（使用 Eclipse 的“导出签名 apk 功能”），生成的 .apk 将无法安装在某些设备上。
通过记下它工作和不工作的设备所使用的处理器，再加上一些搜索和阅读，我发现该问题似乎适用于 ARM11 设备（即 ARMv6 处理器）。
我正在使用 Proguard，起初认为这是罪魁祸首，但后来我通过注释掉 project.properties 中的适用行绕过了任何 proguard 恶作剧 - 签名的 .apk 仍然无法安装那些 ARM 11 设备。
还注意到 ARM11 设备运行的 Android 版本不高于 2.2.1，尽管我没有任何运行 2.2.2 或更高版本的 ARM11 设备来验证 2.2.1 是否是问题的一部分。
我在项目中包含 2 个外部 jar，但 /bin apk 安装并运行的事实表明这些 jar 不是问题的一部分。
您可能拥有的任何知识，或者关于我应该如何寻找解决方案的指导 = 非常感谢！
An app I'm developing installs and runs fine on ARM11 (ARMv6) devices when I deploy via ADB or install the .apk that gets generated in /bin, however once I sign the .apk (using Eclipses 'export signed apk feature') the resultant .apk will not install on some devices.
By taking note of the processors used by devices for which it works and doesn't work, plus some searching and reading I've identified the problem seems to apply to ARM11 devices (i.e. ARMv6 processors).
I'm using Proguard, and at first assumed it was to blame, however I since bypassed any proguard shennanigans by commenting out the applicable line in project.properties - still the signed .apk won't install on those ARM 11 devices.
Have also noticed that the ARM11 devices are running Android versions no greater than 2.2.1, although I don't have any ARM11 devices running 2.2.2 or higher to verify if 2.2.1 is a part of the problem.
I'm including 2 external jars in the project, but the fact that the /bin apk installs and works suggests the jars aren't part of the problem.
Any knowledge you may have, or direction as to how I should hunt for a solution = much appreciated!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
把这个归咎于潜伏在 Mac+Eclipse+ADTv15+HTCwildfire 组合中某处的 GREMLINS。通过转动Mac＆amp;来解决关闭 HTC Wildfire，回家睡觉，然后第二天再次打开 Mac 和 HTC Wildfire 并再次尝试。
Putting this one down to GREMLINS lurking somewhere within the combo of Mac+Eclipse+ADTv15+HTCwildfire. Solved by turning the Mac & HTC Wildfire off, going home and getting some sleep, then turning the Mac and HTC Wildfire on again the next day and trying again.