Hey
I have a build of this code with all the fixes. I’ll try and share it with you today.
The changes need a review to be publicly shareable, and it will take up to 7 days.
Happy to share an APK if someone’s in a hurry.
Hey, sorry if this has been discussed but I did not see anything scrolling through this thread or on GitHub but I was wondering if there was a setting to allow when Reviews are made available?
Bunpro has a feature similar to what I am talking about if anyone is aware of what I am talking about. It’s called “Review Queueing Timing”. Basically anything low SRS level follows the hourly review time but after it goes to days it allows those reviews to show up at 3 AM so you do not have to wait until a specific hour to do some reviews.
I attached images to show the setting in Bunpro for reference.
It has been handy in allowing me to do as much as I can when I can. Then not be totally affected by the days I cannot do reviews at my scheduled time and then have to wait a “day” to get them back on schedule of hours I want to have them appear. I am not trying to speedrun but it helps me maintain a decent learning speed.
I will gladly put in a request on GitHub but wanted to check if I am missing a setting first or something else I can do for it.
I believe this is already the case?
Review a subject and it will be available again in a given amount of hours, not days, so it may show up again at any given time of the day. To say it another way, reviews aren’t first available a specific time of the day, simply at the hour they are meant to be reviewed?
I think he means for the app to not tell you about it between certain hours. That could be useful if like me one lacks discipline to not check your phone at 4 in the morning when I should be sleeping.
I’m hesitant to suggest a fork but if the maintainer is overboard, that might be what you want to do. If you need help with a clever name I am willing to give it a shot.
So yes as it stands and Bunpro can be the same way. You do a review at 7 PM and then the review should be available at the same hour, 7 PM, a day from then or whatever depending on SRS level.
However if you miss the time you usually do it like at 7 PM and instead do it at 8 PM then it becomes available at 8 PM when its due next. Well lets say that day it comes due I cannot do it at 8 PM but can only fit time in to do reviews at 7 PM, that means I won’t be able to clear that review until my next free time after 8 PM when it comes due or anytime the following day. So now I prolonged the time I master that review.
Bunpro made a work around for that. Instead of making them due on the start of the hour that they are supposed to become available to review, you can change a setting to make them just become available instantly the day they are due (3 AM was chosen by Bunpro for reasons I do not know).
So now I can do that review at anytime of the day on the day it was due and not have to wait until 8 PM when it would normally become available or wait a extra day until I have time to do my reviews. This is probably more beneficial to speed runners but also people that maybe cannot commit to strict schedule to do reviews and do not have to wait to the exact hour they are do. So its a QoL kind of function.
However this does not change the review timings for things less than 24 hrs. So Beginner items still follow their 4, 8, 24 hour interval and after that then they follow the day to months intervals but just come due on the day rather than a set hour.
So yeah somewhat what AimForKoshien said and it would give people that are completionism or people who cannot have commit to regular schedule time to still be able to complete the reviews on the day it was originally going to be due. Idk, just something I enjoyed on Bunpro and wished was here and helped me from having a backlog of reviews, be able to do more reviews in one session, and satisfied my impatience of wanting to clear all my reviews.
AFAIR it’s a limitation of WK and it would be nice if, for “day spaced” items the timing would be “day” and not 24h (well, 23h exactly).
I asked about it in general: SRS timings... how to avoid everything piling up in the evening? and right now I’m dancing around to keep the schedule to the time it suits me the most with reviews, but it’s darn annoying instead of being able to do the “day reviews” whenere I would please on that particular day…
Yep I agree. Its worked really nicely for me on Bunpro. I do not feel rushed, I am more eager to do reviews knowing I can when I want, and this way I rarely have any carryover to following days.
It keeps me motivated to do reviews each day and prevents task paralysis, which I know this is all a me problem haha. Anyways I would gladly put in a request form on GitHub, just wanted to make sure I wasn’t missing something.
minor issue: tapping on a level progress bar for vocabulary only includes “vocabulary” and not “kana-only vocabulary” in the search results
True!
It seems like kana-only vocabulary have been presented as a whole distinct concept to the user. But I don’t think anyone cares if they are handling kana-only vocabulary or not?
I’ll simplify this a little.
Hello, sorry if this has been covered but I’m having a repeating review issue. I do the reviews, but the count of reviews doesn’t go down and if I start a new session I get the same terms again. I’ve tried forcing a manual sync and restarting the app but no luck. Also it seems like the number didn’t go down on the app so syncing to the server wouldn’t do anything. Thanks for any input
Hey folks,
Like many of you, I’ve been a happy Smouldering Durtles user for a long time, and huge credit goes to Joeni and the previous maintainers for building it. Unfortunately the project has been inactive for over a year: pull requests weren’t being merged and the Play Store version hasn’t been updated, which means recent bugs have gone unfixed. I tried to reach Joeni privately but haven’t been able to make contact.
Since I couldn’t contribute fixes to the original, I’ve forked the project to keep it alive for the community. It’s rebranded as Blazing Durtles so I’m not publishing under someone else’s name, but it’s the same app, fully open source, and you can find the fork on GitHub.
This first release fixes the issues we’ve been discussing here lately:
- App reinstall failing
- The “ribcage” issue
- Notifications now work again on recent Android versions (the app now properly requests notification permission, so you can get notified when new reviews are available)
- Updated to target Android 15, which Google now requires for Play Store updates. You don’t need Android 15, the app runs on the same Android versions as before.
Play Store link: Blazing Durtles
I’m actively accepting pull requests and bug reports, so if there’s something that’s been bothering you, please open an issue. And to be clear: if Joeni comes back and wants to resume maintenance, I’d be glad to contribute back or step aside. My only goal is that the app keeps working for everyone using it alongside WaniKani.
I am not super familiar with app development, but how does the API version affect backwards compatibility? It looks like only about 40% of Android-based phones currently support this version of Android, which seems too low to make it a minimum for new apps. (There do not seem to be enough sources to make the 40% number reliable, but from my experience a lot of people use phones that are 3-6 years old, which would fall outside of this window).
Actually, it is some sort of upper limit I’m changing here. But even the latest Android phones will work.
The minimum Android version supported is Android 5, released 12 years ago. This app covers 99.9% of the phones on the market.
Will this be going to a github release or a fdroid release? My android I use for this is degoogled.