MrMC

For at least 2 years, every time (or nearly every time) MrMC updates to a new version, I can no longer launch the program.

It says "loading MrMC" or "starting service" and then crashes back to the home screen.

The only way to fix it is to delete cache AND delete data, then it will finally start back up. I've tried just deleting the cache, but that's not enough.

I haven't even bothered to build my library because I know I'll have to re-add all my sources and re-build the library every 6-8 weeks.

It has reached the point where I'm tired of dealing with it.

The problem is I'm not sure how to get you a debug log. I can't get into the application to upload the log, and the only way to get into this application is to delete data, which "fixes" the problem, at which point the log is no longer useful.

Is there a basic log that is always available that I can SSH into the Shield and grab, or use ES Explorer or something?

To get the debug log you need to install a file explorer/manager. After the crash/freeze of MrMC open the file manager and navigate to Android/data/tv.mrmc.mrmc/files/.mrmc/temp. There you will find the log file. Note that you need to setup your file manager to to show hidden files.

You can copy the log to an external device and then upload it here or you access the dir via smb or something.


Also you can setup the library once and after your done or made changes, just export this lib. Then you just can import the lib if you needed to delete all files.

@Fehritale,

Thanks so much for the help, I got the log and old log and put them on Pastebin here:
Log
Old Log

It seems to be a database error in both cases: Am I doing anything obviously wrong?

Thanks,

-Wes

Just thought of something.

Both of my MrMC devices are set to use MySQL. Is it possible this is happening because one of the devices updates to the new MrMC version, then updates the DB schema, then when the other device tries to update it can't find the "old" schema?

waldo22 wrote: 07 Feb 2020, 21:51 Just thought of something.

Both of my MrMC devices are set to use MySQL. Is it possible this is happening because one of the devices updates to the new MrMC version, then updates the DB schema, then when the other device tries to update it can't find the "old" schema?

Unless you manually deleted the old db on the server hosting MySQL, the previous db should still exist.

Yeah, it's still there.

Any idea why these crashes are happening?

Only deleting data helps, but then of course I have to re-set up all my shares and re-do the settings.