Android SDK too old for F-Droid (and most Android apps)

Bug Reports
1

REPRODUCIBILITY: 100%
OS VERSION: 4.6.0.15
HARDWARE: Jolla C (yes, the old Jolla C, not the C2)
UI LANGUAGE: German
REGRESSION: don’t know

DESCRIPTION:

I’m trying to install F-Droid from the Jolla Store on my Jolla C (bought recently). However, there is an error message telling that Andorid SDK 24 was needed and my phone had only Android SDK 19. After that, the F-Droid store seems to be installed (according to Jolla Store), but it doesn’t show up on the phone. I can uninstall and reinstall it from the Jolla Store with the same result.

PRECONDITIONS:

After receiving the Jolla C, I

  1. did a factory reset,
  2. installed all OS updates up to 4.6, and
  3. installed Android AppSupport from the Jolla Store.

STEPS TO REPRODUCE:

See Preconditions and Description above.

EXPECTED RESULT:

I’ve expected that after updating the phone to SFOS 4.6, the AppSupport would be on par with Android 11, i. e. Android SDK 30.

ACTUAL RESULT:

While installing F-Droid, the error message says that my phone is on SDK level 19 and thus F-Droid can’t be installed.

MODIFICATIONS:

Just installed a few additional basic Jolla apps.

ADDITIONAL INFORMATION:

2

Should you mean Jolla C it means it is not supported anymore.
The answer is forget.

3

No; the Tablet, Jolla C (1) and Xperia X are stuck on AAS 4.4 - and also out of support on SFOS. These are ancient devices.

1 Like
4

Thank’s for the immediate responses. I didn’t expect that Jolla C is stuck on an ancient Android level. I know that support for Jolla C ended with SFOS 4.6 last year. But I really expected that SFOS updates also increase the Android level of AppSupport.

5

That only happened from new AAS, on the XA2 and onwards.
The Android version is/was clearly documented.

I guess technically the Jolla C is on the licensed Aliendalvik thing, and actual AAS is a better remake which Jolla themselves control fully.

6

For the old Systems there is F-Droid Legacy. It runs on my Jolla 1 (JP-1301) Phone.

2 Likes
7

Thank you for the hint, @explit! Is F-Droid Legacy the same as F-Droid Classic?

Now I’ve got F-Droid Classic on the phone, but initially, it couldn’t load any package indexes out-of-the box; the error message is “Error getting index file” – even if I only select the package source “F-Droid Classic”.

This was a problem with the CA trust list, which I could fix by installing the Let’s Encrypt root certificate with the help of Root cert problems on AppSupport 4.4.4 - #2 by ugeuder. Most package sources were usable then, except “F-Droid Archive” (app crashes because archive seems to be to big) and “F-Droid” itself, which uses another root CA (HARICA TLS ECC Root CA 2021). I could have inserted that other root in the same way as with Let’s Encrypt, but I thought, I should get the complete bunch of relevant root certificates at once. Indeed, I found a solution for this: Update root CA certificates for legacy Android AppSupport system - #2 by Chwinterhoch5.

1 Like