-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mihon crashes immediately upon launching app #1704
Comments
After installing the app, did you initially open it by tapping |
Yes, I usually open it by tapping the I uninstalled, installed again, and this time it seems to be working ok:
Was the initial way of launching the app really the cause of the issue? Thank you! |
@zomgimobbq Did you do anything to your Mihon folder at some point before or after the crashes started happening? Did you have something downloaded / actively downloading, did you delete the folder / something inside it? Also, did you do a backup restore at any point before, during, or after the crashes? If so, where did that backup come from (another phone or this one? Was it a Mihon backup or one made in one of the compatible forks?) |
No, did not change anything with the folder before or after the crashes. I do not know if I had anything downloaded in the folder. Prior to reinstalling, I only had two titles "added to library", and I did not choose to explicitly download them (if that's even an option). I'm a new Mihon user, so I'm not sure of all the details -- does "adding to library" mean I download those titles? If so, then perhaps I had downloaded files.
No backup restores. This is my first time using Mihon so I have nothing to restore from. |
Spoke too soon. Mihon is back to crashing immediately upon launching :( |
@zomgimobbq I can see in the logs you provided that the crash is always happening when Mihon gets into contact with the storage system. Have you checked that Mihon has the requested permissions, especially for the folder/for storage? Do you use some sort of custom/third-party Android version or is this the one that came with your device? |
I checked Mihon's permissions and originally: Trust the application / allow all permissions was off --> now set to on Current permission settings: Once updated with these permissions, Mihon still crashes immediately upon launching. Attached another log from Logcat reader -- is it still crashing when it gets into contact with the storage system?2025-2-8 hisense touch mihon crash.txt This Android version came with the device. However, this device is from Aliexpress and did originally come with mostly Chinese settings, which I had to switch to English. Not sure if that helps/matters. Thanks again. |
I'm not sure, it looks similar to the previous crash logs. Could you try to uninstall all extensions you have installed right now (check your device's apps listing, they should all start their names with "Tachiyomi", uninstall them all. Then force stop Mihon if it's somehow still alive, and try to open it again. If it crashes again, try clearing Mihon's cache and data (this will wipe your collection as well but it's not recoverable in this state anyway it seems), then try to open it again. In any crash case, please record the logcat output again, thank you. Edit: And if all fails, try uninstall/reinstall, then BEFORE opening the app, grant it the permissions manually in that app info view you screenshot. |
Thank you. I uninstalled all extensions via the apps listing, then opened Mihon again (did not force stop it as it was not open, so force stop button was greyed out). It crashed, and here's the logcat for that. Then I:
2025-2-8 hisense touch mihon crash 3 - after clear cache.txt This is basically the same thing that happened after reinstalling last time: #1704 (comment) Fingers crossed that the issue is solved for good, but last time the crashing behavior came back the next day :< |
Just curious (and just in case), what's the storage location path you are setting the app to? Screenshot your Mihon Settings > Data and storage page |
I have little hope for this being a solution. While I'm not certain, I am getting a weird feeling that this is your OS being weird about Mihon interacting with the storage engine. One line I have seen a few time:
Indicating that the system's storage service is the one dying and leaving behind those massive native stack traces. There's nothing I'm aware Mihon can do when the system's storage service dies like this. Mihon uses the device's storage extensively (obviously), for example, it uses it for caching extension's little badges/images, storing downloaded chapters (both the temporary and permanent ones), as well as maintaining its database of your library, which gets also stored in the storage I'm afraid your device, for one reason or another, is not coping well with Mihon and therefore probably entirely incompatible. Considering it's marketed as some sort of e-Ink-Reader & Music player, maybe that's to be expected. I'll leave this issue open for you to report back if it crashes again (or maybe not? Hope never dies, after all). |
Back to crashing :< Here's the latest logcat The Hisense Touch is a niche product for sure, but many users use it specifically for Mihon/manga reading, and it's one of the reasons I purchased it myself. I wonder why it's not working in this instance. Any last ideas or suggestions? Thanks, and appreciate all your help! |
Haha yeah, it has some random "inspirational" quotes that it shows on the lockscreen, that's probably one of them. Sorry, here's another logcat file. I never know how much of it to grab. 2025-2-11 hisense touch mihon crash.txt No SD card on the device, there's no slot for external storage on it. Appreciate all the investigation! |
Honestly, my theory at this point is that Mihon tries to query the storage service during backup creation (which it normally does on a schedule, e.g. daily). If the schedule drifts or Mihon dies in the background, it'll start making a new backup the next time the app is reawakened (that's apparently a frequent occurrence on my phone). Assuming Mihon doesn't make a fresh backup right after install (which would be sensible), I'm guessing the reason it's working for you for a while until it randomly doesn't comes down to this automatic backup process starting. Obviously, with it stuck in a crash loop like it is for you, it's not possible to change the auto backup frequency settings, so yet another reinstall would be needed to try this hypothesis. If you still wanna try this hypothesis, you can reinstall Mihon (restore a backup if you have one but I'd expect there to be problems), and then set the Automatic backup frequency in the Data and storage menu to OFF. Caution This is a stupid thing to do if Mihon is working fine. It's counterproductive and risky under any normal circumstances. This instruction is specifically to test the hypothesis at hand and should not be taken as a recommendation for literally anyone other than OP. After doing that, just force restart the app for good measure. Not needed but honestly, it can't do harm either. Now, you can see if Mihon works for you for more than like, a day or so. (Incidentally, I believe "Daily" is the default auto backup frequency, so...) This will obviously put you in a somewhat awkward situation regarding your Mihon data. You can also try if a manual backup would work but considering the underlying process is not different enough in my eyes to matter, it will probably crash as well and you might get stuck in a crash loop all over again. IF you want to use Mihon anyway, I'd strongly recommend you use the external tracker services like MyAnimeList, AniList, etc. to at least keep track of what you're reading and your progress on each. It won't magically restore into Mihon if you have to reinstall again but at least you won't have to struggle remembering what that one weird manga you saw two years ago was (assuming any of the trackers have a listing for it). And you could use it to rebuild some parts of your collection next time around. Other than that, keep your Mihon collection smaller so you don't have to spend as much time rebuilding the collection, etc etc. Hope this dangerous workaround will at least enable you to read a bit for a change, instead of manually having to capture logcat output. |
Steps to reproduce
Expected behavior
Mihon does not crash immediately upon launching
Actual behavior
Mihon crashes immediately after launching
Crash logs
I'm unable to grab crash logs natively from within the Mihon app, since it crashes before I can navigate anywhere within the app. Therefore this was pulled via Logcat reader.
I'm not a technical person and not familiar with this process, so I YouTube'd how to use Logcat reader. I hope I did it correctly and have included relevant info.
2025-2-6 hisense touch mihon crash.txt
Mihon version
0.17.1
Android version
Android 11
Device
Hisense Touch
Other details
Currently only using the Weeb Central extension.
App works just fine after initial install if I stay within the app. But once the app is closed, the device turned off, etc. and I try to launch Mihon again, it will exhibit this same crashing behavior. I have uninstalled and reinstalled it three times and each time it has the same behavior: works perfectly fine after initial install and I can use it as normal, but once the app is closed and launched again it will crash.
Thank you for your help.
Acknowledgements
The text was updated successfully, but these errors were encountered: