[BUG]: Optimiser Stops Working
Checked for duplicates?
- [X] This issue is not a duplicate
Does it also happen in the desktop version?
- [ ] This bug does not occur in the latest version of Anki
What are the steps to reproduce this bug?
I tried optimising my parameters for one of my decks which works fine. I don't save the settings, go back, do a review card, and try optimising once again.
Expected behaviour
I should be able to optimise my parameters.
Actual behaviour
The optimiser shows FSRS parameters are already optimal.
Debug info
AnkiDroid Version = 2.18beta1 (c12b398c216dc2a2c2e2c98709c92132d19d105c)
Backend Version = 0.1.38-anki24.04.1 (24.04.1 ccd9ca1a8309b80bcb50ddc5d99c7ce63440bce9)
Android Version = 11 (SDK 30)
ProductFlavor = full
Manufacturer = realme
Model = RMX2193
Hardware = mt6768
Webview User Agent = Mozilla/5.0 (Linux; Android 11; RMX2193 Build/RP1A.200720.011; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/123.0.6312.121 Mobile Safari/537.36
ACRA UUID = cf265e01-9693-407f-984d-61ddf9698fac
FSRS Enabled = true
Crash Reports Enabled = true
(Optional) Anything else you want to share?
No response
Research
- [X] I am reporting a bug specific to AnkiDroid (Android app)
- [X] I have checked the manual and the FAQ and could not find a solution to my issue
- [ ] (Optional) I have confirmed the issue is not resolved in the latest alpha release (instructions)
Here's the recording of what I was doing: Youtube
Note: I reported this in FSRS's github repo originally.
We don't do anything different from Anki desktop on that screen, so I believe that's an upstream issue.
To ease the reproduction, exporting the deck with the scheduling information and deck presets would help
We don't do anything different from Anki desktop on that screen, so I believe that's an upstream issue.
Yes that is what I believe. I only opened this because Sherlock asked me to do so.
To ease the reproduction, exporting the deck with the scheduling information and deck presets would help
Can you check here? You need to change the date which I mentioned there.
This was (most probably) an issue with FSRS Optimiser. I'm closing this thus.