IzzyOnDroid listing

[IzzySoft]

Checklist

• [X] I have used the search function for OPEN issues to see if someone else has already submitted the same feature request.
• [X] I have also used the search function for CLOSED issues to see if the feature was already implemented and is just waiting to be released, or if the feature was rejected.
• [X] I will describe the problem with as much detail as possible.
• [X] This request contains only one single feature, not a list of multiple (related) features.

App version

6.3.7

Where did you get the app from

Other

Problem you may be having, or feature you want

Your APK is listed at IzzyOnDroid, and also has the badge on its Readme – thanks! However, there's a problem: APK size is over 60 MB now, and the per-app size limit at IzzyOnDroid is 30 MB. So it no longer fits.

Suggested solution

Consider providing per-ABI builds. Native libs are stored (i.e. without compression) inside the APK. So just the native libs of the 2 x86 variants sum up to ~30 MB already. Sticking to a single ABI (e.g. arm64) would bring the size back below 30 MB.

Thanks in advance!

Screenshots / Drawings / Technical details

No response

[dyeray]

The app is already on the main f-droid repo. Does it make sense to stay on IzzyOnDroid too?

[IzzySoft]

Does it make sense to have it on Amazon then? Or on OpenApk? :wink: Depends on your point-of-view. There's a basic comparison at the top of our FAQ, maybe that helps you decide. But of course, if you say so we can remove it from IzzyOnDroid – the authors' wishes are respected.

[XilinJia]

The app is already on the main f-droid repo. Does it make sense to stay on IzzyOnDroid too?

As many people prefer IzzyOnDroid over the main F-droid, I respect their choice. To me, at least I like the promptness of a release apk gets on IzzyOnDroid. F-Droid tends to have a delay.

@IzzySoft , I will check about providing per-ABI builds. You only need arm64?

[XilinJia]

@IzzySoft , the listing on your site appears to have a mis-match of versions. I searched Podcini and it shows version 6.3.7 here https://apt.izzysoft.de/fdroid/index.php

Then I click on Details, and it shows 6.3.4: https://apt.izzysoft.de/fdroid/index/apk/ac.mdiq.podcini.R

How come?

[IzzySoft]

You only need arm64?

At least currently, IoD can only pick 1 APK – so yes, arm64 would be fine and sufficient.

Then I click on Details, and it shows 6.3.4

Sorry, I cannot reproduce. For me it shows 6.3.7 there as well:

Maybe a caching issue in your browser?

[XilinJia]

In deed it's a cached version (but why?). I clicked reload of the detailed page and got 6.3.7

[IzzySoft]

The wonders of technology :see_no_evil: But glad this one is resolved at least. Remains the sizy one. Please give me another ping once the arm64 APK is available. Thanks!

[XilinJia]

@IzzySoft I tried building a arm64 apk by adding a "splits" section in build.gradle, but wasn't successful. Do you have some advice on how to correctly do it?

[IzzySoft]

Unfortunately not, I'm no Android dev… But maybe a working example can help? Here's one from another Kotlin app using split APKs. Setting isUniversalApk = false should spit out separate APKs, if I understood that correctly. But no idea how to have both. I usually take sed to adjust it to the APK I need for the RB run…

[obfusk]

Setting isUniversalApk = false should spit out separate APKs, if I understood that correctly.

That setting enables generating a universal APK in addition to per-ABI APKs.

[IzzySoft]

Thanks Fay! So setting that to false just disables the "fat build" (aka UniversalApk with all ABIs), true enables it – and in both cases, per-ABI-APKs are produced as well? And if one wants the "fat build" only, isEnable = false would take care for that?

[obfusk]

See https://developer.android.com/build/configure-apk-splits#configure-abi-split

[XilinJia]

Thanks everyone for the help. The arm64 is uploaded.

[IzzySoft]

Thanks! As 6.4.0 was already pulled, the arm64 APK will be introduced here with the next release then:

ApkMatch: /free.*arm64/i

[XilinJia]

Thanks! As 6.4.0 was already pulled, the arm64 APK will be introduced here with the next release then:

ApkMatch: /free.*arm64/i

Sorry, can you be clearer? What should I do with: ApkMatch: /free.*arm64/i

[IzzySoft]

Apologies: that's the pattern the updater here uses to match the APK it should pull from your releases. It's a regular expression, matching the current arm64 APK you've just provided. So I named it here to show the relevant part of the file name that should be there even if you decide to slightly rename (which would not break the updater as long as that regex still matches, e.g. Podcini.R_free_release_6.4.0_arm64-v8a.apk (current) would match, Podcini.R_release_free_6.4.0_arm64-v8a.apk as well.

[linsui]

The apk url is changed and the reproducible build failed. Could you please keep the old url?

[XilinJia]

@linsui you mean free apk file name?

[linsui]

Yes.

[XilinJia]

OK, renamed for 6.5.1.

For future, as @IzzySoft can also accept, I will maintain the pattern as: Podcini.R_release_free_6.4.0 rather than Podcini.R_free_release_6.4.0.

[linsui]

Izzy only needs the arm64 apk and F-Droid only needs the universal apk.

[XilinJia]

OK, Podcini.R_release_free_6.4.0 pattern is the same as before for F-droid. Since Izzy accepts the pattern, it's better I keep some consistency.

[XilinJia]

@linsui , is there a way to have F-Droid not publish my preview or pre-releases? I noticed Izzy has skipped the previews.

[linsui]

We only check the git repo instead of github release. You can add a suffix, e.g., -beta to the tag name so that we can exclude them.

[XilinJia]

Hi @IzzySoft

I no longer update this project as mentioned in the Readme (7.3.5 is the last release). I started a new project Podcini.X that is the same as this one but with access to Youtube stripped off. Would you also list the new project?

[IzzySoft]

Can do, @XilinJia – just a few questions:

• Podcini.R is discontinued, so there won't be any more releases?
  (if so, we can disable the update checks here for the repo as well as for the RB builder)
• Podcini.X will be its successor? (if so, we'd mark it correspondingly to people can "follow over" – and then remove R after a decent overlap, say, 1..2 months)
• We'd pick the *free*arm64*.apk for IzzyOnDroid (as the "full" one would be too large)
• We'd also see that we can establish Podcini.X as RB

All of this correct – or does it need any adjustments?

[XilinJia]

Can do, @XilinJia – just a few questions:

• Podcini.R is discontinued, so there won't be any more releases? (if so, we can disable the update checks here for the repo as well as for the RB builder)

Right.

• Podcini.X will be its successor?

Not really. It's has a different focus.

(if so, we'd mark it correspondingly to people can "follow over" – and then remove R after a decent overlap, say, 1..2 months)

I guess mark it with "follow over" would be fine, but not sure. X installs independently from R as a separate app. Whether to remove R is your decision perhaps based on user interests or other factors. But X is not a replacement for R.

• We'd pick the *free*arm64*.apk for IzzyOnDroid (as the "full" one would be too large)

For that X is structured as same as R.

• We'd also see that we can establish Podcini.X as RB

RB -> reproducible build? You can do the same as with R.

All of this correct – or does it need any adjustments?

[IzzySoft]

so there won't be any more releases?

OK, so I'll disable update check for it (both, repo and rebuilder) – done.

I guess mark it with "follow over" would be fine, but not sure. X installs independently from R as a separate app.

That's clear as it has a separate packageName.

Whether to remove R is your decision perhaps based on user interests or other factors. But X is not a replacement for R.

R had Youtube stuff, right? So it will fail sooner or later anyway (marked it for removal in 4/2025 hence). I didn't name X "successor", but "alternative" then:

RB -> reproducible build? You can do the same as with R.

Thanks, succeeded – so X will start as RB right away.

All these changes will go live with the next sync around 7 pm UTC.