Report (old) App Bugs Here!
-
Nexus 6p
Android 8.1.0The progress bar hides itself when I start a part I only finished 25% of LDM but that can’t really been seen at all, also I finished all of Isekai Maou but that is hidden as well.

Additionally the search feature is set to case sensitive search.
If I search "My little" with a lower case "L" I get no results, when I search "My Little" my an upper case "L" I am shown "My Little Sister Can Read Kanji"
-
@rahul-balaggan said in Report App Bugs Here!:
The progress bar hides itself when I start a part I only finished 25% of LDM but that can’t really been seen at all, also I finished all of Isekai Maou but that is hidden as well.
As someone who used graphical representation of progress instead of numerical (XX%) wherever
possibleit was easy enough I would think that's intentional (except for the part where "new" is visually 100% read + extra text and larger bar, that sucks). -
@_08 I did consider it might be intentionally but wasn't 100% sure, personally speaking i like seeing a row of "100%" for the stuff i read but it makes no major impact for me in the long run.
-
W.r.t the new beta: On a Nokia 6.1, Android 8.1
- if you attempt to search without entering a term, the app crashes (report should have been sent)
- scrolling pages via swiping sometimes doesn't work well, especially on Gear Drive Part 5
- if you don't swipe long enough, the reader "gets stuck" between pages (but swiping left or right fixes) it

-
Joining in.
- There's no obvious way to clear the filter
- Scrolling down through Rokujouma parts caused only first few dozens of thumbnails to load. The rest remains white even after restarting and clearing cache.
- Paginating seems hella slow, to the point of questioning whether the previous version was better at that.
- There's a position tracker (probably related to new paginator) that changes status on the bottom and it's pretty slow. You can quickly scroll some and then wait few dozens of seconds for it to catch up. Furthermore, you can't leave the part while it catches up.
- Insert image didn't load
- Headings are left-aligned, so much for "Italics/bold/center all parse"
- The tap area for menu on the top is too big. Now if you want to swipe to flip page you have to do it below
- The menu won't go away if you tap the area below and it's not obvious which button makes it go away
- Asking to continue every time can get annoying
-
@_08 What device are you using? Pagination is plenty fast for normal reading speed, but it seems slow if you are trying to flip through the part quickly since it only does the next ~10-15% or so.
Is it all insert images that didn't load or just one?
-
@sam-pinansky said in Report App Bugs Here!:
Is it all insert images that didn't load or just one?
I tried some more and it seems like it only happens on those non-loaded rokujouma parts. Even a cover won't render.
@_08 What device are you using?
Evidently, these things tend to be much slower on hdpi devices and mine has 2560x1600 display. Extra processing power they would have isn't enough especially since it's single-threaded. Mine is a first-gen Kindle Fire HDX (with Snapdragon 800), but I believe you can have similarly bad experience with newer devices.
Pagination is plenty fast for normal reading speed
It probably is but it will be very frustrating if you clicked not to resume and then decide to seek. A page normally takes 3-4s to load, but for some reasons it took over 20s after illustration and the first one can take longer too. And then you can't even press back properly because it gets blocked. Doesn't seem like it will load in advance if you stay on the first page either, so if you somehow ended up with 0% progress and you want to look at the last page the only way to do that is to spend minutes by slowly flipping pages one-by one. With previous version you could at least just go and do something else while it loads and then quickly flip.
Also the pull-to-refresh things makes everything disappear for a while even if nothing happens. Especially useless on the series page.
-
Addendum: On an Amazon Fire HD 10, I cannot get Grimgar 2, Part 1 to scroll at all in portrait mode. In landscape, it works.
-
Currently using an Android Pixel XL, the new app has recently stopped loading parts. I was able to read the latest part of lazy dungeon master this morning, but working within the last hour nothing loads. I am still able to freely navigate to other parts of the interface, but selecting any part causes it to load indefinitely work a spinning circle. It should be noted that this is different from the normal loading screen which mentions paginating and has a progress bar.
-
@karsin Sounds like your log in token has expired, signing back in should fix that issue.
-
@_08 Is it really single threaded? I thought all ARM chips had at least more than one core...
The way React Native works is that one thread is dedicated to the javascript byte-code interpreting and the other is the native app, so if you only have 1 thread it will be extremely slow no matter what...
-
@karsin I will agree with the above. I'll look into something that'll detect if your token has expired and put you back on the login screen.
-
@sam-pinansky I really doubt you do that much work in JS. I can take a look at CPU usage later but iirc it was mostly single threaded.
The speed is probably bottle-necked at rendering labels. Those are actual native android viewsand they are processed on a single CPU thread (plus some GPU rendering).Edit: Seems like work with android views is done on multiple threads and TextView measuring utilizes 40% of a quad-core CPU. JNC app utilizes about 40% as well. "1.6-threaded".
Edit 2: To reiterate, loading the whole larg-ish part old-app style you need to wait ~30s, load it in the new app if you start at 0% it takes about two minutes at the same 40% load. Add that laggy progress indicator and background pagination starts looking really bad in some circumstances.
Also, the listing order (ASC/DESC) inside a serie is reset as soon as you leave the page. -
@_08 Yeah that's about right. To do the pagination we render every sentence in its own text view piece by piece to get the actual rendered height in pixels and when hitting page boundaries we try all possible splitting points.
Having lots and lots of textviews (basically one per paragraph with nested one for styles) can be slow. -
@sniper_samurai said in Report App Bugs Here!:
@karsin Sounds like your log in token has expired, signing back in should fix that issue.
You were spot on, thank you!
-
I know it's not a bug, but could TTS be added please?
-
@fozzedout I've looked into how I can hook into iOS or Android's TTS functions and it's non trivial...
-
How about holding a wake lock while having a part open (https://forums.j-novel.club/topic/313/app-prevent-screen-turning-off)? There should be a ready made component for that.
-
@sam-pinansky the TTS on iOS already works fine, but when it gets to the end of the page it glitches out, and I have to kill it, manually flip the page, and start TTS again. I minimize this problem by making the text the smallest it can get so that the TTS can read the maximum before I have to reset it.
-
Not really a Bug but something which really griinds my teeth sometimes. Can we get a verification if we really want to log out. It happened now atleast half a dozen times that I logged out without wanting to (Which I even wonder why we need a log out button at all....).
Oh and as someone asked before. Would there be a way to get a awake feature? I usually read my books with small fonts and need so a lil more as the 45 seconds till the screen blends out. Would be nice to have a "stay awake" function so I don't need to change it in the settings.