FAKKU Reader Help, Feedback and Bug Report Thread

Agreed one of the devs said it would be easy to add swipe function but I test the reader all the time and he hasn't ever actually done it. I'm not sure if the sites just been too busy recently or if they just don't plan to improve their reader but it's the one thing that worries me about the magazines. From my understanding they will use the reader and as is I'm not a big fan of it and have to wait for DL links to read the books. For the free chapters I can just screenshot them and read them in a pic viewer but the mags are gonna be like 1000 pages and I'd rather not take that many screenshots just to read them.

It could be so. In my case, I read in full screen mode and it is kind of a pain in the ass to have to make the bar appear, press, and then disappear again.

To anyone having issues with touches not being recognized near the edges: What browsers are you using on your phones/tablets? If not Chrome, can you also test how it works with Chrome?

Anyway, I definitely hear you all, and I will be doing some things to hopefully help address these issues. I'll probably increase the size of the page change touch zones somewhat and add that basic swipe support in. I'll make a note here when things get updated so you can all test things out.

S4 Firefox doesn't advanced on edges but if it in more it does. Like half a finger width more. In the center it brings the header and tool wheel controls. On chrome it works on edges but also sometimes the header actives. Same on my s5 and s6 edge. Same browsers and same problems. But I don't read online or on my phone anyways.

Generally speaking I don't recommend trying to tap at the very edges of the screen. From my experience mobile browsers (and some mobile devices in general) unfortunately seem to be rather unresponsive to taps at the very edges of the screen, so it's always advisable to tap somewhat in. The current tap zones in the reader are basically divided width-wise into 25%-50%-25% of the screen's width, where the 25% at the edges are the page change tap zones. I'll probably increase this so that it'll be 30%-40%-30% or I could make it an even 33%-33%-33%.

I vote for 33%

Alright then, an update has been pushed for the reader. You can now change pages via swiping on touch devices (I highly recommend setting the UI direction to right-to-left if you intend to use this especially if you like zooming pages so that they're wider than the screen width), and the page change tap zones have also been made bigger. The reader should also now reliably work in various browsers' private modes. I've also tried some things to hopefully fix the issues that some people (ping @Zenobias @sadmir) were having on their Android devices. Feedback would be appreciated especially with the last one as I couldn't replicate said issues myself.

Not sure what you did but, everything works now. No hangups no weird crashes or black screens. Just works.
I'll test more extensively tomorrow but this is great.

Updates work just fine on Google Chrome, at least swiping does. Not on Firefox, though.

Update:
Moto G 2nd gen - still crashes after the 7th image but that's expected with 1GB of RAM I guess. Doesn't really matter for me since I don't see the point of reading this on such small screen.

Samsung Tab S 10.5
Swiping works 99% of the time, the other one percent is probably nothing to do with the reader itself.
After swiping, sometimes it won't turn to the next page with just a tap but that can usually be fixed with swiping to the next page.
I don't know why but Chrome and Firefox are not as responsive in fullscreen when it comes to taping, swiping works fine. Like I said on a earlier post I can fix that on Firefox by spoofing a desktop user-agent. Maybe the same thing works on Chrome but I haven't tested because I don't really use Chrome all that much.

I'll try on a old Nexus 7(2012) next week but I think it's gonna crash just like the Moto G because of the 1GB of RAM.

I just tested the reader for an hour and it definitely runs a lot smoother now, even though it's still really greedy with the RAM so tabbing out of the browser causes heavy lag, and opening menues also sometimes causes lag. That's not the worst thing ever, though. At least it doesn't seem to crash anymore.

Nonetheless, I still wonder why it started lagging so badly in the first place. I mean, it worked perfectly fine before. There must have been some kind of update my mobile phone doesn't like.

Also, what are the normal image dimensions? I hope they're not retardedly huge so they HAVE to cause lag (*cough* see CoD Ghosts *cough*) on my small device.

Thanks a lot for the update, Daiz. I really appreciate your effort!

Same problem on my end as well.

This thread is for issues with the new reader that is used for premium content, not the old one used for current free content (which is where this next-click bug seems to be happening). I'll pass your message forward, though.

I encountered a strange error when using the reader. Using iOS mobile, Chrome. After Chrome crashed using the reader, I restored it, hit back, then went to read Meanwhile, Onee-chan was... again and then it was messed up like that. I just went back to the homepage and it was all fixed, but yeah. I also haven't been able to recreate it.

Should be fixed now! Was a temporary bug

The favorite button appears to still not be working. https://www.fakku.net/(...)/add returns a 404.

A new update has been pushed for the reader. New in this build is nicer-looking downscaling for non-mobile devices, which should make especially black & white pages look nicer when scaled down in size (eg. when using fit to height). This is somewhat slower than the resizing that's been used in the past, but on the devices its enabled on it should hopefully not make much of a difference performance-wise. One downside with the current approach is that it makes pages look somewhat blurrier, but hopefully the reduction in pattern artifacting should be worth putting up with that.

Feedback would be once again appreciated.