[Android] List the app on F-Droid

[gengrill]

Otherwise, for wider distribution it might be cool to put it on https://f-droid.org.. a ton of people who tinker with stuff (myself included) try to avoid the Google dependencies on their Android, and I don't see anything preventing this app from working without it.

[VanceVagell]

Thanks for the idea. For now, people are welcome to check out the Android app code from this repo, compile it, and side load it on their phone.

[Jacques-Olivier-Farcy]

I'd like also to have this on F-Droid for sure

[shuvashish76]

Requested at F-Droid : https://gitlab.com/fdroid/rfp/-/issues/2913

[VanceVagell]

Unassigning from myself as I don't want to own the F-Droid store listing / update process / etc. But I do support it being posted on F-Droid (I see in the linked F-Droid issue they need my confirmation).

Please just be clear in the store listing that this is a non-official posting of the app maintained by the community, and link to the website and this GitHub.

Assigning to @shuvashish76 who seems to have kicked this off. Thank you!

[shuvashish76]

I don't want to own the F-Droid store listing / update process / etc. Please just be clear in the store listing that this is a non-official posting of the app maintained by the community, and link to the website and this GitHub.

Ok untill then can we distribute via IzzyOnDroid (the largest third-party F-Droid repo)? Ping @IzzySoft for the scanner report and inclusion possibility... (More details in this article: https://news.itsfoss.com/android-open-source-ham-radio/)

[IzzySoft]

Scanner report looks good, just a single finding:

SigningBlock blobs:
-------------------
0x504b4453 (DEPENDENCY_INFO_BLOCK; GOOGLE)

Easy to fix with a minor addition to your build.gradle:

android {
    dependenciesInfo {
        // Disables dependency metadata when building APKs.
        includeInApk = false
        // Disables dependency metadata when building Android App Bundles.
        includeInBundle = false
    }
}

For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains. More details can be found e.g. here: Ramping up security: additional APK checks are in place with the IzzyOnDroid repo.

For inclusion I'd need metadata (description and some graphics (icon, screenshots)), ideally in Fastlane structures (you could use the IzzyOnDroid Fastlane Documentation for orientation – or provide the metadata by other means if the former is not possible.