If you try to start kodi, the startup crashes and you'll find yourself back in the main Fire TV menu.
Kodi should start normally and the user should be able to see the kodi menu.
Kodi crashes after being started with no failure message,.
Wipe kodis' cache and data. You'll lost all your configuration and start with a blank kodi.
Steps to reproduce the behavior:
https://privatebin.net/?3d59b4a26f339272#dndUk2PtqUwmlcu4OjpmKaTEKH8RjT241m5ln0ORcHA=
@lrusak Please take a look on my other issue #15039 : There was a lot of debugging regarding this other issue. Please take a look on our results, it should be re-opened.
Used Operating system:
Profile.xml is corrupted I think its 0 byte.
Same happens sometime to guisettings.xml if a device will powered off when kodi is running.
I'm also getting the same issue on my Bravia Android TV. My power supply needs to be replaced and will completely shut off at times. This last time that it happened, opening Kodi would load but always crashes right before showing the dash. Clearing cache for the app does not work either.
Deleting profile.xml and guisettings.xml got it to work again. And, as M2k80 mentioned, both of those files had a size of 0 byte, which suggests that they went corrupt when powered off incorrectly.
last working build for fire tv basic is:
kodi-20190523-3bb5115b-master-armeabi-v7a.apk dated May 24th (build from 23rd)
any build after that keeps crashing immediately back to Fire TV home menu after the "clearing cache" followed by "preparing for first launch..." message disappears.
reinstalling the kodi-20190523-3bb5115b build will work, so it must be a change from this build to the one after that broke it.
my profile.xml and guisettings.xml are fine so this may not be the exact same issue?
FIrst of all: Thanks for your great information and hints.
I think it could be the issue with the corrupted *.xml-files after power shutdown.
My current workaround is to close kodi before shutting down the fire tv's power circle.
@nuwonda Do you have created an own issue regarding your problem? I would like to see the developers reaction to it.
Nevertheless, I think we can close my issue here.
Thanks for your great support, folks :).