有 AAC+所有 Android 手机上的支持都已修复吗?

发布于 2024-10-18 12:52:00 字数 1114 浏览 6 评论 0原文

对于存储在 Android 应用程序中的语音文件,我想从使用 MP3 编码的音频文件切换到使用 AAC+。这将使安装尺寸更小。

我遇到的一个问题是 Android 的 Froyo 版本中 AAC+ 支持被破坏: http://code.google.com/p/android/issues/详细?id=9308

后来修复了: https://android.googlesource.com/platform/frameworks/base/+/ 16263d9f8cc01392c2f3678b381ce897647c8c81

Pandora 常见问题解答显然确认了某些手机已通过无线方式更新,但警告其他手机:

为什么我在 Froyo 上遇到音频问题?

如果您已升级到 Froyo (Android 2.2),您在收听时可能会注意到音频质量问题 到潘多拉。 Android 团队已意识到 AAC+ 音频的此问题,并发布了修复程序,该修复程序 正在逐步在各种 Android 手机上推出。

目前,Sprint HTC EVO 和 Google Nexus One 已通过 OTA Android 操作系统更新, 合并此 AAC+ 音频修复。

如果您的手机与上述两款手机不同,请联系支持团队以获取您的手机信息 如果您对此问题还有任何疑问,请联系手机。

所有 Froyo 手机都已更新以包含此修复吗?或者是否有一些运营商/制造商不打扰?这在 Android 中很常见,因为他们声称测试更新成本太高。

我的 Flurry 指标显示 Android 2.2 为 33.2%,2.2.1 为 12.2%,2.2.2 为 0.1%。因此,如果修复仅涉及版本号更改,则不适用于大多数 Froyo 手机。

I'd like to switch from using MP3 encoded audio files to AAC+ for voice sound files stored inside an Android app. This will make the install size smaller.

A problem I encountered is that AAC+ support was broken in the Froyo release of Android:
http://code.google.com/p/android/issues/detail?id=9308

It was later fixed:
https://android.googlesource.com/platform/frameworks/base/+/16263d9f8cc01392c2f3678b381ce897647c8c81

The Pandora FAQ apparently confirmed some phones were updated over the air, but warned about other phones:

Why am I experiencing audio issues on Froyo?

If you have upgraded to Froyo (Android 2.2), you may notice audio-quality issues while listening
to Pandora. The Android team is aware of this issue with AAC+ audio and has released a fix, which
is gradually being rolled out on the various Android handsets.

Currently the Sprint HTC EVO and the Google Nexus One have OTA Android OS updates that
incorporate this AAC+ audio fix.

If you have a different handset than the two mentioned, please contact the support team for your
handset if you have any further questions about this issue.

Have all Froyo phones been updated to include this fix? Or are there some carriers/manufacturers not bothering? Such is very common with Android, as they claim testing updates is too expensive.

My Flurry metrics are showing Android 2.2 at 33.2%, 2.2.1 at 12.2%, 2.2.2 at 0.1%. So if the fix only came with a version number change, it isn't out to most Froyo phones.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

一个人的旅程 2024-10-25 12:52:00

根据该提交的时间,它可能已在 2.2.1 中修复。由于 2.2.1/2.2.2 中没有 SDK 级别更改,因此 Google 不会单独跟踪其与 2.2 的使用情况。截至 2011 年 7 月 5 日,Gingerbread 和 Honeycomb 占总安装量的 19.5%,而且它们都肯定有 AAC+ 修复。大多数制造商和运营商除了主要更新(操作系统升级)之外不会发布任何更新,因此我估计大约 25% 的设备都有此修复。您还可以尝试使用 Ogg Vorbis,因为对它的支持已内置所有版本和语音配置文件可能足以满足您计划使用它的目的。

Based on the time of that commit, it was probably fixed in 2.2.1. Since there is no SDK level change in 2.2.1/2.2.2, Google doesn't track its usage separately from 2.2. Gingerbread and Honeycomb make up 19.5% of total installs as of July 5, 2011, and they all have the AAC+ fix for sure. Most manufacturers and carriers don't release any updates other than major ones (OS upgrades), so I would estimate that approximately 25% of all devices have this fix. You could also try using Ogg Vorbis, as support for it is built into all versions and the voice profile may be sufficient for what you plan on using it for.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文