Report (old) App Bugs Here!
-
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.
-
@sam-pinansky Probably, it can be hard to tell when using the app on a tablet using a smaller font size. The paragraphs are easier identified using the app on a phone.
-
@sam-pinansky said in Report App Bugs Here!:
@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?
Changing the font size doesn't seem to have any effect on whether or not I can read beyond the first page. Here's a few that weren't working:
- Gear Drive V1-6
- Realist Hero - V7-4
- Veight - V1-5
- Undead Adventurer - V3-2
Is it possible that this issue is tied to the resume function? I'd read all of those before going to the beta, and I just checked Last Idol's most recent (also read in non-beta version), and resuming allows for page turning, but exiting and choosing to not resume does not allow for page turning.
-
@animej said in Report App Bugs Here!:
@sam-pinansky said in Report App Bugs Here!:
@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?
Changing the font size doesn't seem to have any effect on whether or not I can read beyond the first page. Here's a few that weren't working:
- Gear Drive V1-6
- Realist Hero - V7-4
- Veight - V1-5
- Undead Adventurer - V3-2
Is it possible that this issue is tied to the resume function? I'd read all of those before going to the beta, and I just checked Last Idol's most recent (also read in non-beta version), and resuming allows for page turning, but exiting and choosing to not resume does not allow for page turning.
What happens if you change from swipe mode to scroll mode?
-
@shiny It still won't go further than what is already on the screen
-
Can reproduce "pages won't flip with small fonts" thing, too, but maybe you need a hdpi or big-sized device for that.
- Clear app data
- Open NeeChu (the first part in the list), pages can be flipped
- Go to the first page, set font to micro size, pages can't be flipped anymore, CPU is at 0% and nothing ever happens
Also tried on a smaller device. Flipping with small font works but all of illustrations and most of thumbnails won't show. And the pop-up menu is still confusing as hell. Good thing it's not a public release, I guess.
-
Since last night my Samsung Note 8 beta app cannot load any chapters. I can go and look at the newest updates but when I click on a chapter to read its just on a forever loading screen (not even the pagnation)
-
@bryan Your log in token has expired, logging out then back in should fix this issue.
-
@animej Hmm, sounds like something like an out of memory error? I would think that would crash the app though itself.