Samuele Zappalà
Samuele Zappalà
I too experience many breakages. This happens, for examples, when windows get opened from other applications and/or when they get closed: the other windows in the desktop doesn't get retiled...
Last check, stuck at 89%.
> Without logs, this will be hard to diagnose? Are you willing to create them? (You'd need to install either adb-tools or android studio, the latter is usually more easy)...
I installed the apk, but the app didn't got stuck, so I don't have any stacktrace to give you 😅 I actually received the results this time, for the first...
To me it seems like the calendar created from Deck is a calendar without events but with tasks (that is, a CalDav entity with tasks but not calendar nor journal)....
It turned out that Deck calendars are read-only. Making them writeable would solve this.
To improve this we should create (or find one already created) a request to make them writeable and propose a way in which Deck could understand changes coming from outside...
Same issure after upgrading to 1.16 from F-Droid: yesterday everything worked, now no one of the games I play (GBA, NDS, SNES) starts because I get this error about libretro.
Do you mean that it was obvious that we had to wait for 1.16.1 and we didn't need to create an issue?
> Of course. Because In the current build of Github 1.16.1 the problem has been fixed, then the timeliness of updating in the f-droid is their responsibility. There it was...