(Unofficial) Android/Win10 Rokujouma Reader. Nice Things status: can not be had.

_08

version 0.1.10 aka yup, they sure aren't decimal
Mostly just bugs getting fixed:

Horizontal paged reader should work again (although loading indication is still bad and switching between single-paged and dual paged may require a restart)
Prevented bad things from happening if you log in with a second account. Do NOT log in with a different account without resetting progress if you're still using an older version
Series page has new and unfinished layout
Clicking series starting with "Infinite" will no longer do a thing it's not supposed to do
Some internal stuff

I'll make some longer post in a week or two.

@chrisg Thanks for suggestions. I pretty much never considered that because I just scroll continuously. I'll add flipping with volume buttons soon-ish but adding touch-screen control may be tricky.

_08

First, a little update because everyone does that nowadays.
version 0.1.11

You can log in with your username now
Volume's page got ebook options back. Now with premium epubs (just sends volume's page link to browser, or a download link if you own it)
Data storage is reworked a bit. Things may've got a bit faster and app data shouldn't inflate that much (it still does)
Couple of minor bugs fixed

As for a long post, now that there are more users than you can count on one hand and a have a bit of free time, I decided to post a to-do list, so you can point out if I'm missing something in the roadmap.
Feel free to mention even super-small things — those tend to be both easy to implement and easy to miss/forget about.
Note: below "page" mostly refers to application screens, not a book's page.

TODO:

Properly test to get rid of random crashes
The ever-growing list of series should be on a separate page and with thumbnails (preferably with optional grid view, but that may be a pain to add)
Filtering/sorting options for lists of series or volumes (There's a ton of potentially useful options I can come up with: show all, show series unread preview, show favorites, show owned series, hide series with expired unread parts i.e. things you can't read anyway, ...). An option to show list of parts for series.
Various changes to the navigation between pages.
Maybe actually describe offline-reading part and/or add explicit "'save' for offline" button. (Right now it's just a three-bird-killer cache for faster loading, less network usage and offline usage in case network isn't accessible)
Pop-up tools on the reader page: more detailed status (network, progress), text settings, TTS, bookmarking, seeking. Also better network/sync status indications in general.
Keyboard controls
Marks on the progress% bar: Images, Headings, max read progress etc
Switch to Realm Database (new and sexy mobile-oriented RDBMS) for caching: less wasted storage, faster startup and web updating, no WinPhone or armeabi support though and there are quirks with threads. Sticking with SQLite
Transitions between parts in the paged reader
Less bad image zooming in android
Add something to the android's splash (startup) screen. I actually have a .txt with a bunch of quotes from prepubs for that but I doubt it's a good idea to use them when it stays on screen for two seconds.

Pie in the sky:

Push notifications
Rewriting UI to platform specifics instead of Xamarin.Forms (faster loading, better performance, more capabilities)

Now excuse me while I go drown in all those new prepubs.

fozzedout

There seems to be an issue with the latest when doing TTS: it just zips through the entire part until it hits the end without doing any TTS.

_08

@fozzedout Fixed. Not sure why the old version worked but not the new one. Next time try to mention the platform (Android/UWP) because things may be different on those, either thanks to my code or framework's.

version 0.1.12

Fixed android's TTS not starting up properly, and some other minor TTS bugs.
Fixed crash when volume preorders are viewed without logging in.

ChrisG

Unfortunately, 0.1.10 and newer all crash when started, both on my current phone with Android 6.0, and my old phone with Android 4.4.4. They only work on my tablet with Android 8, but that's a bit too big for reading novels. 0.1.9 runs OK on all devices.

_08

@chrisg A somewhat late reply because apparently I was too busy reading new rokujouma to notice your post.
First, it's probably not that much about android version because it works on 5.0 and 6.0.
I think I added most of dangerous things in 0.1.11, not 0.1.10, so that's a bit weird. You can try a new version because I did fix a couple of potential crashes (though they only happened occasionally, not always) and removed some things added in .1.11. If it works, check the logs by clicking "Log" on the about page, I wrapped the code for background color detection (that I added in 0.1.10) into a try-catch statement and the error starting with "Error while getting display info" will appear in the logs if it occurs. Take a screenshot if you get that (and maybe check if the default theme or background color is different on non-working devices). Other relatively big thing I added in .0.10 was a library for pop-ups so I made a package without that in the google folder 0.1.13/test/ and you can try that as well if normal build doesn't work. Before all that you should try clearing app data with android's tools, but you probably already did while reinstalling and all.
If all above fails and you have adb with drivers you can get error logs by running adb logcat > log.txt, searching log.txt for RokujoumaReader and searching for E AndroidRuntime: somewhere nearby.

version 0.1.13

Data storage is reworked again. It shouldn't unreasonably grow in size anymore. I recommend clearing data with OS tools or reinstalling app to get rid of old data because I'm not entirely sure the app will manage to clear it all by itself. Some things will be a bit slower until I optimize some more.
Everything in horizontal reader is faster and hopefully more stable.

Edit: I guess caching in the latest version deadlocks a lot, gonna fix that soon.

_08

version 0.1.14

Got rid of deadlocks introduced in 0.1.13
Horizontal reader now can be full-screened as well

ChrisG

Thanks for your efforts. 0.1.14 fails to install on all devices, I get a parsing error. 0.1.13 installs and shows the list of Rokujouma volumes, but clicking on a volume hangs.

_08

@chrisg Try again with 0.1.14, the package I uploaded earlier was unsigned. 0.1.13 deadlocks a lot which I didn't notice right away because it works better in some conditions. And check the log (or just click on volume, pop-up will be transparent if what I think would fail did fail).

_08

version 0.2.0

Added manga support with ~~both~~two available image resolutions (x1280 and x2048). It has zoom but I don't have much good things to say about that zoom. Progress tracking supposedly works too.
Since manga reader needed a zoom button (for devices where you can't pinch-zoom) I added a menu in paged reader. Some buttons don't even work, though.
Dropped Windows Phone support
Volume buttons on android can be used for page flipping (and you can't disable that). Z/A keys on windows (will change later).

Known issues:

Switching from x1280 to x2560 image quality may not work right away (will only be partially rendered), reopening chapter helps. Sometimes canvas will not be properly sized and only a small square in the corner would get rendered.
There really is a lot of bad things about that zoom
Page flipping animations don't really look nice if you're zoomed in
Manga reader is totally going to break like next week

chocolatkey

@_08 fyi there's also the 1600 resolution (also the win-x64 app crashes when I click on the manga or LN vols)
Edit: I took a look at your code, congratulations on the unmixing! I didn't think anyone would be motivated enough to take that approach

_08

@chocolatkey said in (Unofficial) Windows Phone/Win10/Android Rokujouma Reader. Now in the faraway corner of Windows Store.:

@_08 fyi there's also the 1600 resolution

Whelp. Can't use bool now.

~~Seems like some cast becomes invalid~~One library is acting up without extra configuration and causes exception when compiled with .net native but not in regular builds. Seems like it crashes on the first run, too. Should check that later.

Edit:
version 0.2.0b (UWP-only)

Fixed volume's list which was consistently crashing

_08

JNC has 69 series and Xamarin.Forms has 1337 open issues on Github. No better time for a new version.

version 0.2.2:

Fixed manga reader broken by minor API change. Also supports all 3 image resolutions now
Some minor bug fixes and performance improvements
(experimental) Faster metadata synchronization using incremental updates via https://rrapi.azurewebsites.net/api/Updates/2019-05-31T12:00:00
(experimental) Series list page. Kinda slow and not very functional yet.
Shoutouts to whoever legalized long-ass names to make things harder for me

smashman42

@_08

Wasn't the UI for this app dark before? Can it be optional, like matching the dark mode switch? I like dark all the things

_08

@smashman42 Night mode switch explicitly sets reader (as in, thing with actual prepub text and nothing else) colors to #00/#FF black&white. Everything else follows the system theme colors. I just happen to have white on on windows and grayish on android as seen on the first post (updated couple of days ago).

smashman42

@_08 The UI has switched to white on Android for me with v0.2.2 when all previous versions where grey

_08

@smashman42 I didn't change anything color-related in my code but I updated some of tools which could in theory affect it. I uploaded a couple of 0.2.2b builds on google drive in case you want to experiment with that: _Plain.apk is built with newest tools and libraries, _VS17_SDK26_Forms34.apk is built with older MSBuild, targets older android SDK and uses older Xamarin.Forms. It's pretty unlikely that whatever you find will help to resolve that because I can't reproduce it myself so reporting or fixing that won't be easy. Maybe it'll just resolve itself sometime later.

smashman42

Plain made no difference, the older SDK one wouldn't let me install it over the top - I'll try wiping app data/cache/uninstalling when I get a chance.

The device is an LG V30+ stuck on 8.0.0 atm (LG is infamously crap with updates after all, though supposedly I'll eventually get 9.x) so I was hoping the older target one might have worked.

If you can't reproduce it then it makes it super hard to do anything, I'll just live with it if I can't get that older target one to install. I can't complain much about something that's free after all!

Edit: the older target version is the same. Meh, I'll live.

Which version should I be using for future upgrade versions - regular 0.2.2 or 0.2.2b plain?

_08

@smashman42 said in (Unofficial) Android/Win10 Rokujouma Reader. 40% faster crashes for the same price.:

Plain made no difference, the older SDK one wouldn't let me install it over the top

I forgot to bump up the version for apks except for plain and apparently android won't easily let you downgrade.

The device is an LG V30+ stuck on 8.0.0 atm (LG is infamously crap with updates after all, though supposedly I'll eventually get 9.x) so I was hoping the older target one might have worked.

I only have 5.0. and 6.0 so it's not about your version being old. I certainly need to set up the emulator some day.

Which version should I be using for future upgrade versions - regular 0.2.2 or 0.2.2b plain?

Both will work but 0.2.2b has two or three bugs fixed.

_08

To commemorate Microsoft killing WinPhone (again) new version is uploaded to MS store.
version 0.2.3:

Version uploaded to MS store. Same as 0.2.4 except for a little bug with recent parts list and some experimental features disabled

version 0.2.4:

Various bugs fixed (403 images being stuck in DL queue and causing significant CPU usage, non-JFIF JPEGs possibly causing crashes maybe something else I forgot)
Android's theme is explicitly set to dark
Manga is disabled by default, needs to be enabled using a switch with cursed animations