pmaports VS play-services-plugins

For me, not until it gets VoLTE: https://gitlab.com/postmarketOS/pmaports/-/issues/1878

Looking into the reasoning for why I found that we actually decided against AppArmor in the end. You can see our current reasoning and options at https://gitlab.com/postmarketOS/pmaports/-/issues/1596

It stopped working some time ago, don't think anyone has properly debugged it yet: https://gitlab.com/postmarketOS/pmaports/-/issues/1667

You can track the progress in https://gitlab.com/postmarketOS/pmaports/-/issues/1505 Charging is probably fixed already but I did not test it yet.

As a follow up, spent some hours diving the problem and found this 2 year old open issue with the pinephone telephony stack: https://gitlab.com/postmarketOS/pmaports/-/issues/731

Android is basically open source at the bare minimum. To use Android in a meaningful way, you need Google Play Services, which are proprietary and have root privileges on most Android phones (allowing Google to collect a lot of private data easily). The only ROMs I know of which utilise Sandboxed Google Play Services are GrapheneOS and ProtonAOSP. microG exists on CalyxOS and /e/ OS, but it will never be as compatible as Google Play Services.

One problem with relying on emulation is that Google has moved a lot of functionality from the open source Android layer to Google Play Services, and they obviously wont publish that on someone else's platform.

https://developers.google.com/android/guides/overview

The main privacy concern with most Android devices is that they usually include Google Play Services.

Here's an overview: https://developers.google.com/android/guides/overview

Yeah, frustrating I know. I actually made a PR 5 months ago (based on another) to introduce the ability to add libraries if they don’t have it included in their POM. Our use case was that we used a web view with local JS files that we needed to attribute to.