Report (old) App Bugs Here!
-
@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.
-
@legitpancake The app splits paragraphs so continuity will always be broken to an extent as long as TSS reads from the text boxes the app presents. And it won't be any other way with external TTS. Dunno about "dies on page break" part, but one may have to dig a lot to find a cause and even more to find a workaround.
I guess you can set font to tiny size for uninterrupted TTS.Edit: Tiny font also shows that an app miscalculates height at least a bit.
-
@_08 It's probably better to have the TTS read from a hidden non-split version of the part.
We'd program something that stripped the html completely and just made it one giant string and send that to the TTS function. -
@sam-pinansky Sure, but I didn't mention that because you just said that calling TTS from your side is tricky. Also, not one giant string but paragraph-by-paragraph.
-
I've done my own TTS stuff before on Android (TTS for SMS Messages), and there is a max char limit to what you can send - 8kb I think.
I would have thought that the per page split would have been adequate, but yeah, there are many other variables in that as well. I note that other epub readers with TTS generally split on fullstops - probably for speed of converting text to speech.Hmmm I might have a poke around with the API, see what's what.
-
My only problem with the TTS is that it doesn't turn the page automatically. It just starts reading from the page behind (like the series page or latest page on mobile).
-
Ran into a major bug with the android beta. Several prepubs were unreadable beyond the first page.
Device is a Galaxy Tab S3, running Android 8.0.0
-
@animej Could you tell me a few examples of which ones? Did it matter if you changed the font size in one of the prepubs that worked and then went back?
Also what do you mean by unreadable? As in, they wouldn't load more than 1 page?
-
@sam-pinansky Had this happen to me too on my Pixel C.
Usually occurred on parts that have a lot of text at the start of the part like Kokoro Connect. Making the font significantly larger and reading past where the first page at the smaller font ended before changing the font back would usually fix it.
Worst offended was Dendro volume 7 part 7 which wouldn't even load the first page.
-
@sniper_samurai I’m not exactly exactly sure what you mean by “a lot of text at the start” since like, aren’t they all text?
-
@sam-pinansky Formatting, the parts for Kokoro Connect tend to fill more of the screen with text on my tablet than others, this could be due to less line breaks being used. I reckon it is an issue to do with the way pagination is done on the beta app compounded withe larger screen sizes of tablets.
-
@sniper_samurai in other words you mean it has longer paragraphs.
