ducklingone@lemmy.today to Selfhosted@lemmy.worldEnglish · 2 个月前Keep Android Open (Stop Google from limiting APK file usage)c.orgexternal-linkmessage-square162linkfedilinkarrow-up11.13Karrow-down18
arrow-up11.12Karrow-down1external-linkKeep Android Open (Stop Google from limiting APK file usage)c.orgducklingone@lemmy.today to Selfhosted@lemmy.worldEnglish · 2 个月前message-square162linkfedilink
minus-squaregarbage_world@lemmy.worlddeleted by creatorlinkfedilinkEnglisharrow-up1·2 个月前Yes. Most of those AOSP forks still use elements of android (google play services) for compatibility reasons.
minus-squarerealitaetsverlust@piefed.ziplinkfedilinkEnglisharrow-up1·2 个月前Graphene doesn’t, they got their own sandboxed google play services compatibility layer. Other OS - no idea tbh.
minus-squaregarbage_world@lemmy.worlddeleted by creatorlinkfedilinkEnglisharrow-up2·2 个月前It’s actually the opposite. GOS GPS are real GPS, most other AOSP distros use MicroG, which is reimplementation of GPS.
minus-squarerealitaetsverlust@piefed.ziplinkfedilinkEnglisharrow-up2·2 个月前It’s real GPS, but within a sandbox without additional permissions. https://grapheneos.org/usage#sandboxed-google-play
Yes. Most of those AOSP forks still use elements of android (google play services) for compatibility reasons.
Graphene doesn’t, they got their own sandboxed google play services compatibility layer. Other OS - no idea tbh.
It’s actually the opposite. GOS GPS are real GPS, most other AOSP distros use MicroG, which is reimplementation of GPS.
It’s real GPS, but within a sandbox without additional permissions. https://grapheneos.org/usage#sandboxed-google-play