Version 5.9.13 is a bug fix release to resolve the biggest crash plaguing the 5.9 versions of Mimi. The crashes have been very difficult to track down, but I believe this release finally fixes most of them. If the leftover crashes still occur too often, I will prioritize fixing them. From what I can tell, that fix will be a refactor. I would like to make sure the previous fix does not cause more issues before tackling the larger code change. Please update your app and email email@example.com if you have any issues.
- Removed the option for paginated board posts. The vast majority of people will see no change. It just makes the app easier to update in the future.
- Changed when board posts get loaded into the list. The logic for loading posts now waits until the list is ready before making changes.
- Fixed a bug that caused the posts in a board to be loaded twice very quickly. It had the potential to put the list into a weird state where it didn’t know the correct item positions. This change should fix most of the crashes.
It has been a short 3 years since I last updated the open source release of Mimi Reader. In that time a few things have changed. The biggest change is that now the open source release builds. You should be able to check it out from github and build a debug build without any extra steps.
You can find the github repo at https://github.com/MimiReader/mimi-reader.
The inevitable bug fix releases have gone out and I am hoping the version rolling out now is stable. Most bugs should be fixed. The largest bug being batch download not working.
A lot of bugs have been fixed, but there is still at least one large one left. Some people are experiencing an issue where tapping on an image in a thread takes them to the wrong image in the gallery. It does not happen on my test devices so tracking it down is taking a while.
The latest release of Mimi includes a fairly big overhaul of the gallery. Preloading media is one of the most requested features. The problem was in how I originally wrote the gallery. Large changes were required to decouple the downloader from swiping between images. While doing that, I converted the whole thing to a language called Kotlin which should help reduce crashes.
If you don’t like preloading, you can turn it off in the gallery settings. By default, it is only enabled when on wifi.
I have had a few bug reports come in for this release that I consider high priority. I will be fixing those as soon as I can. The most requested bug fix is to close the gallery when an image is tapped. That was an oversight on my part when rewriting the gallery. I will try to get it into the next release depending on how difficult it ends up being.
- Added gallery preloading
- Improved gallery grid image quality when preloading is available
- Gallery grid is now square instead of waterfall
- Muting and unmuting audio no longer restarts the video
- Attempted fix of images not loading after browsing in the gallery for a while
- This one never happened to me, but the rewrite should fix the issue. I would like to know if it still occurs.
- Replaced the ViewPager component in the gallery with a RecyclerView.
- This change should make swiping more smooth, but it may change how it feels slightly.
- Replaced the ListView component in the replies dialog with a RecyclerView
- You should not notice any change.
- Fixed post number highlighting in the replies dialog
- Fixed last read position in a thread
- Fixed unread dot not appearing or disappearing at the right time
- Fixed unread count in the navigation drawer not showing correctly
Version 5.9.0 of Mimi has been released on a slow roll out. It will start with a small percentage of users at first. If things look good, I can release it to everyone.
- The app can save files to any SD card mounted
- Updated Google support libraries
- Updated how cookies are stored for chan pass login
- Removed custom SSL implementation that may have caused issues on some devices
- Require an SSL connection when fetching data
- Removed legacy captcha support
There have been a few issues along the way. I am working to resolve them as soon as possible.
It looks like the location of thumbnails changed. I just released an update that should fix the issue.
Version 5.7.6 was just pushed to the Play store. It will be the last release that supports Android 4. All future releases will require Android 5 and above. This change is necessary to maintain what little stability the app has and stay current with Google’s latest libraries.
It looks like 4chan disabled the ability to use the legacy captcha system. Mimi has support for legacy captchas as well as the recaptcha sysem. To change the setting, go into the advanced settings and toggle the “Use legacy captcha” option to off.
Earlier today I pushed an open source version of Mimi Reader to GitHub. It has all of the ads and Crashlytics removed, but otherwise it’s the same app.
To build it, you may need the YouTube API library. It’s not in maven so it’s a static jar file that you can get from Google. Just drop it in the /libs directory after cloning the project. After that, open the project in Android Studio and build it.
Check it out!
The last few releases have included a lot of visual and backend changes. For whatever reason this is the one I decided to call 5.0.
What can you expect in the 4.9 and 5.0 versions?
- Sliding drawer layout so you can choose between three different layouts
- Tons of toolbar colors
- Fully customizable post text color
- Four sorting options for threads, including an option to invert your sort
Those are some of the new user-facing features. However, behind the scenes a lot more has changed. The largest is the integration of RxJava into my database access. Instead of using the ORMLite library, I have switched to a combination of ActiveAndroid with SQLBrite. This combination gives me a lot more control without losing the convenience of model objects. It should also provide a much better base to add more features that will require persistent storage. My plan is to implement thread hiding in a future release.
I just updated the app on the Google Play Store. It should be available in the next 24 hours.