>If that fedAndroid distribution would really be worried about privacy, they'd be implementing I2P since the beginning. GrapheneOS will not bundle third party apps or network services. Download InviZible if you want I2P. The licenses for it makes it incompatible to be bundled anyways. >Which they haven't and now pretend it doesn't exist. So there's that. Type 'site:discuss.grapheneos.org i2p' on your favourite search engine.

Can you expand on the license issue? Are they not open soruce?

It is open source but it is GPLv3. GrapheneOS software is MIT licensed, upstream code is Apache 2.0. For an app to be bundled it would need to be licensed like such.

I see. Their license page is a huge mess.

I2P Software Licenses - I2P

I was talking about the InviZible app rather than I2P itself. I assume that it could be possible to make a new app doing it with the licenses, but again we wouldn't bundle other services or apps. Our only interest in third-party apps is if they can replace an OS component and we can reliably maintain our own changes to it. The keyboard and gallery apps are ones we are targeting for this atm.

The beauty of bundling something like Tor or I2P is that you can control the deamon's lifecycle at the OS level, allowing it to stay running forever.

Android operating systems do provide an always on and leak blocking VPN functionality per-profile. We close out many more VPN leaks than the stock OS does too. Providing the app is well designed it should continue to stay running. Orbot was known to be terrible with this (tons of bugs) and had crashes on our exploit mitigations. If it ever got a recommendation then it only would have been because there was little other options. The per-profile VPN helps segregate networks like this easily. You could run a VPN on a standard user and an anonymity network in the profile's Private Space and you can switch to both with ease.

Is the always-on policy just for VPNs or are there other exceptions? App developers constantly run into issues to keep things running. For instance, in Nostr, we would like to keep an always on connection with the user's chosen Inbox relays at all times, replacing the Push Notification stack (FCM/UnifiedPush) altogether. Though I am not sure if we were successful in keeping that service running at all times, from a regular app, yet.

I wouldn't know details without knowing more from your app. Check out the documentation on background tasks, or if you discussed it elsewhere with a different team member then what they said should be helpful to you.

Android Developers

Background tasks overview | Background work | Android Developers

but this always-on feature is designed for VPNs, yes. you can background apps using the method I sent above.