You are on the cloned forums!
A new app Beta released for Android! Ver 2.0.1
-
Some more details: It is apparently /just/ Amagi Brilliant Park #1, so far. I can view any others in Paginate or non-Paginate, but Amagi #1 Part 1 seems to not want Paginate mode. I tried it on another device, and it's the same.
Works fine in Simple though for that part.
-
Something is wrong with the latest update.
Ever since then, my phone's battery drain skyrocketed to twice as much per hour.
It's been happening since Aug 28th, the same day that the new update hit.
I've done some tests and the drain occurs as soon as I open the beta app and remains until I restart.
The increase battery use affects all apps, not just the JNC app.
-
@village-idiot What?
Can you say which version of the beta exactly you are on? -
2.0.3
-
Most device nowadays have battery stats built-in. You may want to take snapshot of your device battery consumption to backup that claim.
-
Has the beta app not been working for anyone else?
When I open a part, it's blank except for the loading circle and it just goes on and on. First occurrence was 12 hours ago and it still happens now.
Android Nougat, Samsung J7 Core (Asian market name), latest beta version
-
@cosm1cfall Re-Log in. Your session expired.
-
@village-idiot that worked. Thanks for the help!
-
Are there people who are trying the latest beta that are doing fine? I haven't seen much response aside from that odd battery issue (I have no idea what that might be), so if not I will make preps to actually release it.
-
Ok, so It's really annoying when the app randomly logs me out (sometimes in the middle of reading) but won't tell me that I've been logged out. So then I end up losing my reading progress and when I try to open up a new chapter, it just sits there loading indefinitely with no indication that I need to re-login.
-
The app on iOS is pretty good in my opinion. I would like the progress percent on parts' thumbnails back, but I understand if they were intentionally removed. I've never been logged out of my app yet.
-
Sometimes in continuous page view, sometimes it gets stuck trying to load an image and requires exiting/resuming the Part to continue.
-
Is there any way to force-reload while reading a chapter? A very common issue I run into is that whenever I encounter an image in a chapter, the app just continues loading and loading and loading indefinitely just before the page with the image (as in tapping to the next page would bring me to the image, so the app doesn't let me actually go to the next page, because it hasn't loaded yet).
So the solution is to exit the chapter, then select it again, and resume from where I left off, which has the app load everything properly. It brings me a couple of pages back from where I was, but I can just page forward to the image (which loads correctly) and onwards.
It's a consistent fix, which does make me think there's something which makes image loading "stuck" when I open a chapter for the first time, as opposed to reloading it afterwards.
-
@sam-pinansky said in A new app Beta released for Android! Ver 2.0.1:
Are there people who are trying the latest beta that are doing fine? I haven't seen much response aside from that odd battery issue (I have no idea what that might be), so if not I will make preps to actually release it.
I have had no issues with the current version. Page turns are quick, and releases load fairly fast.
-
@sam-pinansky Will you fix the part where touching a part/series on the list causes it to undergo the fading animation even if you're just swiping the list instead of actually pressing on the link to go to the part/series?
-
@Rahul-Balaggan Thanks for redirecting me here!
Repost my questions
This is my 1st time using beta version, I don't know whether its a bug or you forgot to implement it but:
1/ Reading percentage / Complete status is not displayed per part
2/ When switching the screen from vertical to horizontal, the text and menu are limited to only half of the screen compared to old version@Rahul-Balaggan has resolved for me point 1
Thanks!
-
Okay, I've done a number of tests keeping an eye on the battery. I can say that if the phone is off or the app is not in focus, I cannot get any background battery drain.
That said, for some reason while using the app, it does seem to cause what I consider excessive drain - it actually pops up as one of my most battery intensive apps, even if I've only used it for a very short time (2 mins).
-
@sam-pinansky said in A new app Beta released for Android! Ver 2.0.1:
Are there people who are trying the latest beta that are doing fine? I haven't seen much response aside from that odd battery issue (I have no idea what that might be), so if not I will make preps to actually release it.
Generally fine, although as some have commented the loss of % in list can make it harder to find unread stories and some of the releases are not in order of release which makes it easier to accidentally miss part.
Stay shiny, y'all.
-
@shiny said in A new app Beta released for Android! Ver 2.0.1:
@sam-pinansky said in A new app Beta released for Android! Ver 2.0.1:
Are there people who are trying the latest beta that are doing fine? I haven't seen much response aside from that odd battery issue (I have no idea what that might be), so if not I will make preps to actually release it.
Generally fine, although as some have commented the loss of % in list can make it harder to find unread stories and some of the releases are not in order of release which makes it easier to accidentally miss part.
Yea, though I’m thinking maybe if it’s gone for good, @Sam-Pinansky what do you think of a button or link somewhere on the series page that will directly ‘resume to last read’ position or something without us having to go search for the exact chapter. That would come in very handy.
Oh and also, a prompt at the end of each chapter to exit or automatically load next chapter. Something like what we have when the chapter loads and asks whether we want to resume or not. I think the web version has this (if not then I must’ve confused it with some other site but it’s still a very nice feature to implement ux wise)
-
So apparently this doesn't fix the text cut off issue? Is this issue on the radar and where is it on the roadmap? So far I kept my old phone, which doesn't have the issue, with me for reading but honestly that's a frickin bother.
