I am using a Xiaomi Redmi Note 11S, running Android 13 (version 1.0.11.0.TKEEUXM). Since the release of F-Droid version 2.0.3, the GUI has become unusable. The icon is no longer transparent. It has a white background now. When the app is opened, the interface appears light in daylight-mode and dark in dark-mode. However, neither text nor images are displayed, so the app is no longer usable in this version. As a temporary workaround, I have downgraded to F-Droid version 1.23.2.
pictures please
Unfortunately that’s not possible because I’ve already downgraded it. Imagine the open app as a solid white or dark area.
that was after you updated, right? It needs to upgrade the database from 1.23 to 2.0, depending on repos used and device speed it takes a bit, how much did you wait? how many repos did you have?
on a fresh 2.0.3 install it does not work fine?
F-Droid worked fine since years. I’ve got only the repo of f-droid.org . Last version of F-Droid which worked well was 2.0.2. I updated to 2.0.3 last saturday. It crashed.
I read that F-Droid has launched a completely redesigned version 2.0. The interface has been rewritten using Kotlin Compose and includes support for features such as an optional “Material You” color scheme. This might be related to the issue I’m experiencing on my Xiaomi device. I also read that the best thing is to downgrade to version 1.23.2 which is exactly what I did.
Best thing would be for us to fix that crash ![]()
any chance you can update to 2.0.2 and grab an adb logcat when upgrading to 2.0.3 to see the crash?
/PS: we’ve fixed a lot of bugs introduced by Chinese OEMs but we don’t have devices to test during development
Please don’t be upset with me: I spent several hours over the weekend working with AI just to get F-Droid up and running again. It was quite a stressful process trying to narrow down the source of the error. I really don’t want to go through that again. I think I’ll just stick with an older version of F-Droid and wait until I get a new smartphone. My Redmi Note 11 s is already a little bit old.
there’s a way to test that does not break anything
and a chance to help the others that encounter this
You can install F-Droid Basic alongside your 1.23.2
either directly 2.0.3 (latest), take note if it works fine or not, grab a debug log if it crashes
or even test the update that failed for your, instal 2.0.2 then update to 2.0.3
you can select the version in the app page, expand Versions
grab a debug log if it crashes now
Just did the upgrade. I think I understand what @Tugboat reported: on first start the screen just stayed solid gray for an uncomfortable amount of time, likely while the app was updating the data. Once loaded subsequent starts are fine.
It didn’t take extremely long (definitely way less than a minute), but long enough that as a user you might start to suspect a broken app.
I guess showing some spinner or such, maybe with a small text note “Loading data…” (depending on what is actually happening) would help a lot here.