谷歌如何确保你的手机离不开它
7 分•作者: KinetiNode•大约 2 个月前
你好 HN，
我一直在大量研究 AOSP（Android 开源项目），我注意到的一点是，即使 Android 本身不需要，它对 Google 的依赖程度有多高。以下是我发现的所有内容：
1. **GPS（Google Play 服务）的强制集成** - 这本身就给高级用户带来了很多问题，因为没有它，几乎什么都无法正常工作。即使你使用 MicroG，仍然存在一些服务器端验证是它无法解决的。
2. **侧载限制** - 从 2026 年开始，Google 要求开发者提交政府 ID、支付费用并注册签名密钥才能通过侧载分发应用，这实际上阻止了在认证设备上独立分发软件。
3. **生态系统依赖** - 我认为这一点无需多言。
4. **应用根本无法工作** - 银行应用和任何使用 Play Integrity 的应用都会拒绝工作。
最让我愤怒的是，Google 竟然限制了未经验证开发者的开源应用。这在开源社区和 F-Droid 中引起了轩然大波，因此 Google（大约在 2025 年 12 月）提供了一个令人难以置信的选项。你需要点击构建号 7 次 - 点击“允许未经验证的软件包”，然后输入你的设备 PIN 码。之后，你必须等待 24 小时才能下载任何内容。
虽然你仍然可以通过 adb 下载，但这个变通方法似乎非常繁琐。如果不是开源社区发声，Google 甚至没有计划允许未经验证的软件包。
我已将此内容解释得非常易懂，没有使用任何社区特定的术语，以便任何人都能理解。
查看原文
Hello HN,<p>I've been playing around with AOSP alot and one thing i noticed is how much android depends on google even if Android itself doesnt need it. Here's everything i found out:<p>1. Forced Integration of GPS (google play services) - This single handedly causes alot of problem to power users because without it almost nothing works.. Even if you use MicroG there's still some server side verifications that it just cannot help with.<p>2. Sideloading Restrictions - Starting in 2026, Google requires developers to submit government IDs, pay fees, and register signing keys to distribute apps via sideloading, effectively blocking independent software distribution on certified devices.<p>3. Ecosystem dependence. I don't need to explain this one at all i think<p>4. Apps literally won't work. Banking apps and any app that uses play integrity will just refuse to work.<p>What made me the most furious was Google locking down opensource apps with unverified devs. This caused an uproar in the open source community and F-droid because of which google (around december 2025) made an option which is outrageous. You need to click the build number 7 times - click "allow unverified Packages" and then put your device pin. Then you have to wait 24 hours before anything can be downloaded at all.<p>Although you can still download via adb, The workaround seems very obstructive. Google didn't even plan to allow unverified packages until the open-source community said something.<p>I've made this extremely easy to understand without any community-specific wording so anyone can understand this.