This has been addressed but there is no solution yet:
sockenklaus
I was more curious why ver .33 is no longer working
0.0.33 isn't working anymore because Jerboa's default instance (Lemmy.ml) has already been updated to 0.18 for testing purposes and trying to connect to a 0.18 instance causes Jerboa 0.0.34 and older to crash.
We are in a rather silly state where we can't use Jerboa 0.0.35 to log in to instances other than Lemmy.ml and can't use Jerboa 0.0.34 when we haven't been logged in before updating. 😬
Would you like to tell my your device, Android version and Jerboa version? I'm trying to collect performance reports and hoping to find any pattern for bad performance
Would you like to tell me the Android version of those two devices and the used Jerboa version?
I'm trying to collect performance reports hoping to find some kind of pattern
Thanks, what's your Jerboa version?
Could you please clarify what phone and which Android version you're using? This sounds like some compatibility problem.
There have been some reports of performance problems and compatibility problems with older phones or Android versions.
See here:
I think your reply doesn't apply to Jerboa. Sorting algorithms should be managed server side.
At the moment blurring is kinda buggy:
It uses a Jetpack Compose function that is only available for Android 12 of newer. On older phones it just gets ignored.
I wrote a fix for older phones that has to be approved by Dessalines.
This is a known problem and has been addressed on GitHub:
Über dieses Phänomen "Innenstädte sind nicht für Menschen konzipiert sondern für Konsum" hatte Böhmermann kürzlich eine gute Folge.
https://www.zdf.de/comedy/zdf-magazin-royale/zdf-magazin-royale-vom-14-april-2023-100.html