Hmmm that definitely shouldn’t be happening…
Sorry for the late response, will raise this with one of my team members!
Hi!
I don’t know if this is the place for this, but I couldn’t find a thread just for the Android App.
I was wondering why the app doesn’t seem to send notifications when reviews are due even though the “due notification” setting is turned on in the app settings.
I know Android 13 is fussy about notifications, so I also made sure to allow notifications from bunpro in the settings of my phone.
Could it be because the “set daily notification” setting was set as off? Although, I didn’t receive any warning that turning it off would imply it turns the due notifications off as well. Sorry if this is a silly issue and I actually got something wrong on my part.
2 Likes
My membership seems to have been ended by someone, but I am pretty sure I had another ~8-10 days left. I was planning on finishing up the JLPT N5 grammar study. Unless I am mistaken, anything we can do about that? Thanks!
1 Like
I just sent you a DM about it.
1 Like
Deck was set to primary and were all new cards. Just blasting through the N5 vocab deck to start putting vocab into my Bunpro rotation.
The problem does seem to have fixed itself since I changed to the N4 deck, and I can’t replicate it myself anymore.
Maybe it has something to do with originally changing to the preferred review method during a study session originally? I’m afraid I don’t really know though.
1 Like
Hmmmm will take note of this.
Please let us know if you notice it again!
Lots has been changing with Decks over the past few months.
Thanks!
I have just turned holiday mode off a couple days ago and the reviews are no longer synced to the ‘hour’. If there are 10 reviews coming up at at a given hour, the reviews will not appear in the pile and they will show on the forecast for that hour until something like 40 minutes in the hour, and then they will show in the pile and disappear from the forecast.
That could have been the specific time I turned of holiday mode but I cant be too sure, but it means all my reviews are back most of the hour from when they should come up. I just tried putting it in vacation mode again for 20 minutes and turning of again right on the hour, but still the same issue
Imabi changed its domain, so all ressources linked to it are now giving 404 errors.
1 Like
- I’m not exactly sure if this is a bug or a missing feature, but it seems strange to me that a lot of example sentences have voice lines in the browser, but not in the Android App:
- This has probably been reported already, but I have the issue that the “Last Session” percentage in the home screen of the Android app just won’t show the correct percentage from my session no matter what. It is always a completely arbitrary number.
- This screenshot hasn’t been taken in the latest version of the Android app, but I noticed this glitch with the furigana on the right side. I unfortunately can’t confirm if this is still an issue.
2 Likes
I’m not sure if something changed with the algorithm, or these random N1 points are just set incorrectly, but twice now I’ve had reviews popping at 3AM for reviews I completed at around 7 or 8PM. Not sure if the interval is too long or too short but they should be coming back around at around 7PM
EDIT: I just paid attention, and it happened again, I completed the んばかりに review just now and the next interval is at 3AM instead of tomorrow at 7PM
2 Likes
I’m actually having exactly the same issue as @Slysoft
In addition to my comment above on the timings, for some reason I’m having a huge clump of reviews popping up at 3AM. while some ghost and occasional reviews pop up during the night at times, there should be no reason there is that many all at once, at the same hour at 3AM given fairly predicable nature of the review system. Its happened over a couple days now. The first time I thought I could have been a coincidence, but to happen again and then see Slysofts comment, I imagine there must be an issue going on here.
1 Like
@SteveB Thank you for reporting this. The code that was causing this has been rolled back. We are working on the ability to set your reviews to daily or hourly rounding and a subset of that code got pushed prematurely. It would have set some of your reviews to be due earlier in the day they are due on.
Your reviews going forward should be back to normal. Sorry for the confusion 
2 Likes
Thanks for letting me know and getting onto that issue. At this stage I still have the same issue showing up tomorrow, so I’m not sure when the change was implemented.
Worst case, whatever the code did clumped everything together in my SRS, and even with the removal of the code, everything in my SRS wont move back, so I will have have essentially all of my days worth of reviews that were coming up clumped into 3AM for the foreseeable future
1 Like
Replying to my own post, but…is this going to be fixed? It doesn’t happen on the website, and it doesn’t seem like it can be that hard to fix it…
2 Likes
Hey @adamdschneider
I got it fixed, it will be released with other small patches next week 
Sorry for the late reply 
and have a nice weekend
2 Likes
I have “fill in” for both the default vocab question type and in the deck settings. It works for N5/N4/N3 decks, but when I’m using the N2 deck I keep getting translating (Japanese → English) questions. I also tried to update “all current reviews” but nothing has changed.
I’m going by “general” order, and the words I have tested against have a lot of example sentences.
Is it a bug or N2 vocab deck is still in progress?
1 Like
I’m unfortunately not sure if this has been reported yet, but this bug has been very persistent for a few weeks now:
(the video has sound)
When you try to disable/enable Furigana, it sometimes plays the audio of multiple unrelated example sentences at the same time. I’m not sure if this is the only trigger, but it sure is irritating.
I got a minor typo/grammar correction.
Not sure if this is intentionally mimicking my 黒くする
, but if not, then just letting know that it should be “You need to conjugate する before すぎる” .
2 Likes
I’m not sure if this is a bug, but the weird escape character looking thing and the stray comma after “Casual:” seem like they aren’t supposed to be there
1 Like