(New) App Feedback
-
@MasterLillyclaw OK, let me know if it happens again
-
This post is deleted! -
Pressing the down key on a connected keyboard twice in quick succession while reading in vertical scroll mode will take you straight down to the end of the part.
-
@nosgoroth thanks for reporting. Keyboard support is an easter egg for now, until the desktop versions of the app come out, but I use it on desktop so am inclined to fix. I am curious though, did you try using a keyboard just because you wanted to see if it works or because you expected it to work? Trying to gauge interest because I thought no one would notice/care on mobile
-
@chocolatkey My use case is weird. I use Airplay mirroring from my iPhone to an Apple TV, then read on the TV while using a bluetooth media remote (it can toggle between sending media keypresses and cursor keypresses) connected to the iPhone to change pages, while the iPhone itself is on the charging pad. It's surprisingly comfortable, and generally all apps I've tried it with support it, somehow.
By the way, I'll just say that it would be super cool if you added support for navigating between parts with cursor keys, but, really, I don't expect you to cater to this one weird use case.
-
Having gotten stuck in a bit of a backlog recently, I think it would be really nice to be able to filter the Releases page by “unread” or “unfinished” prepubs (in conjunction with the “following” filter, meaning I can restrict it to specifically unread prepubs of the series I am following).
Also, when I click the “search” button on the Series page, I think it would make more sense if the keyboard popped up immediately, rather than me having to tap a second time in the search query section for it to appear. After all, if I’m clicking on the search button, it’s because I want to type something in. And on the topic of the search button, when I go to close it, I intuitively want to press the button a second time to make it disappear, but all tapping it again does is hide away the keyboard - the only way to get rid of the pop-up right now seems to be pressing the “x”.
-
This may be a very specific case...but unable to connect while using PdaNet+. As soon as JNC app is opened, it seems like it forces the pdanet connection to close and then errors because there is no internet connection.
Results are same if you connect to pdanet via the wifi+proxy or via wps.
Other apps (Chrome, Play Store, Play Books,...) work fine.
Host: OnePlus 6 - Android 10
Client: Likebook Mars - Android 6.0.1 -
@khaos I've never used PDANet before, is it intercepting HTTPS traffic? Flutter does pin root certificates in the app itself
-
@chocolatkey Hmm, I'd guess it is likely. As it has an option to disguise the tethered traffic as the host device's traffic.
-
I'm guessing this is due to the simultaneous release (and as such, is more of a data issue), but when I hit "next part" on Altina Loose Threads 1 the app goes to Vol 9 part 1 instead of Loose Threads 2 (I'm on Android)
-
A new release (0.6.1) has is now live on both iOS and Android. It adds a light theme, and on Android includes 0.6.0 improvements that didn't make it on Google Play
-
Not sure if it’s just me... or the app, whatever, but I went into piggy duke at random, and got this... fonts shifted from some huge setting to the smaller (preset) setting. (Damn, forum won’t let me up,lad from iPad.... :/. Will try later.)
-
this is something I'm not sure how you could accomplish but when in the app reading if you could make it so someone could report an issue while inside the section by highlighting it or something so it even shows the position of the book to yall when it sent so it can be easer to correct errors and whatnot
-
Small bug with the themes: when swapping between dark/light, the logo will keep the color of the previous theme until the releases/series/account tab is changed.
-
Feature Request (not sure if it's already been requested, apologies if so)
Filter options for the Series page: "Only Manga" "Only Light Novels", also options to filter by each of the imprints as well. -
@pcj Oh, novels vs manga is in there already, just not in an obvious spot. Hit the Search button, then that's one of the options for search results. But if you hit the novel/manga buttons it sorts immediately without waiting for you to put something in the search box.
-
Since the latest release, if I’m in the middle of reading a part and I tap to open/close the progress bar, sometimes it will jostle the text around. It happens on both the light and dark themes and I can’t figure out in what exact circumstances it does or doesn’t act up. But it seems related to how when you first open the reader to 0%, tapping away the bars will initially scoot the text up a little? It’s like the reader can’t decide whether to scoot itself down again or back up or what have you.
-
@masterlillyclaw This has also happen to me though the last time it was a little more than a little though since I have the font increase it probably only seems that way.
I haven't figured out the right or reason for it yet either.
-
On iOS latest beta build, and ever since I downloaded the beta a year ago, there’s a really annoying glitch on the manga reader.
When you pinch and zoom, if the window touches either the far left or far right of the manga page, then it becomes stuck horizontally and you can only move vertically. Otherwise if you try to move horizontally it will move to the next or last page. Only way to fix it is to zoom in or out a tiny bit and try to avoid the left/right margins.This is my main complaint with the manga reader, and getting it fixed would be a major improvement.
-
@legitpancake It's not really a bug, it's just a very rough implementation of a feature that will be improved upon in future builds, namely the ability to swipe to the next/previous page even if you're zoomed in if you try to pan past the edge of the image.
At the moment, it's a very primitive implementation where if you hit the edge of the image, the image panning locks and the page swiping unlocks until the page is changed. I didn't know it would be that bit of an issue in its current, in fact I wasn't sure anyone would even notice. It will be improved upon in future builds
