(New) App Feedback
-
Version 3.1.1 of the app is live, with the following changes:
- Fix app startup/hanging issues
- Truncate text of part release titles with ellipses
- Fix arrow key navigation in reader
@Lake let me know if the button navigation is fixed
-
@chocolatkey said in (New) App Feedback:
@Lake let me know if the button navigation is fixed
It looks to be working well, thanks!
-
Hello, does the app not track reading process anymore? I logged in today only to discover that all the read chapters in my follow feed are marked unread, and the two chapters I read today remained unread as well!
-
@JannyMau said in (New) App Feedback:
Hello, does the app not track reading process anymore? I logged in today only to discover that all the read chapters in my follow feed are marked unread, and the two chapters I read today remained unread as well!
That's coming, it's just late. They posted elsewhere that there's 15 million records to transfer from the old site to the new one for last read pointers, and they're coming back in reverse chronological order over the next couple days.
-
Seems the app is tracking my progress with light novel chapters (ones I've newly read, the records have not come through yet) but manga chapters do not display any newly made reading progress, whether partially or completely read.
-
-
Part releases aren't currently properly hyperlinked on the home page. They're only given the class "link" but are missing the href target. This is happening to me on desktop firefox. Meanwhile in the calendar the whole thing only links to the series page.
Previous behaviour had the title of the release link to the series page and the "part #" linked directly to the part (when released).
It's minor, but it's a downgrade in usability to me.E: same behaviour on mobile firefox (android).
-
On a Pixel 6A and probably on some other devices, the first line of text on each page is partly covered by the phone's front camera and cannot be scrolled vertically. I can see the letters behind the camera if I slide the page right or left as if I were turning the page, so it's a minor annoyance, it just feels clunky.
Edit: It got fixed, or fixed itself, in the last hour. I can't repro anymore.
-
@eggnog said in (New) App Feedback:
On a Pixel 6A and probably on some other devices, the first line of text on each page is partly covered by the phone's front camera and cannot be scrolled vertically. I can see the letters behind the camera if I slide the page right or left as if I were turning the page, so it's a minor annoyance, it just feels clunky.
You should be able to increase the vertical margins to move the text below the camera.
-
@eggnog If you encounter this again, please let me know.
-
Unfortunately version 3 is mostly unusable due to it hiding the navigation bar. This needs to be optional or disabled entirely as it prohibits navigation without messing up ones reading position. I can work around the problem by plugging in a keyboard and mouse to get some functionality back but that is not very portable.
-
@DandyGnome could you please let me know what OS and device you're on ?
Regardless of device, reading mode, or novel/manga, a tap on the middle of the screen will reveal the reader UI and system bars.
You can adjust the size of the middle tap area in Settings > Advanced Reader Settings > Page control regions (it's the blue area) -
@chocolatkey
It is a rooted LG G5 running Android 7.0. In both version 3.1.0 and 3.1.1 tapping the center area brings up the reader UI (which does include a back button that I have been using since the update when I don't have external devices connected) but does not reveal the system bars. Those require swiping and swiping up from the bottom usually touches the reading progress bar (revealed before the swipe or not) changing the progress. Swiping down from the top is safer but requires the use of a second hand making it clunky.Note I am comfortable using a terminal or editing preference files if there is a way of disabling immersive mode via those methods.
-
@DandyGnome ok thanks for the details. If I remember correctly, Android's behavior for immersive UI controls is a bit different before Android 10, so it may have something to do with that. I haven't tested the app on a version before Android 12 in a while, so there could very well be a bug. I'll try to get a bugfix deployed soon.
Regarding your interest in trying to edit config or use the terminal, the logic for this embedded in the app code. Since you're rooted there's probably some way to force disable hiding of the navbars for an app, but I've never tried that before -
@chocolatkey
Thanks, I have been researching the possibility of force disabling immersive mode and may eventually figure that out. And yes if I remember my research correctly around Android 10 immersive mode did start being handled a little differently with users being able to readily enable it even without the app being explicitly built for it. In the meantime I will dock the phone when I can and when I can't I will either use the website or be careful with the app. It may also be time for me to start looking at newer phones. -
@Rahul-Balaggan I also have the problem Granny Gertrude mentioned, that the “read” counters for manga don’t show up yet. Was this also a matter of the data transfer mentioned a few days ago, and just waiting on the queued metadata to finish propagating? If so, any idea or rough estimate when read records will be restored?
Also a second question, more of a feature request (apologies if it’s a duplicate, mobile is awful for searching the forums for this): the read counters don’t indicate completion if the number of pages is lower than the issue or chapter with the highest page count of the series; they still show blue (in progress)instead of green (completed). Is this a known bug planned for addressing?
If relevant: iPad Mini, 5th gen, iOS v18.0.1
-
@gooey the read history not being present is an issue with the maintenance, yes. We are working on restoring it all.
As for your second request. It is one of the reasons we did the backend update. So once all these issues are resolved we should have that resolved as well
