Technical Storage

Home › Technical reference

Storage

• Two stores: the settings storage (about 5 MB, shared by progress, watched marks and settings) and the TV's database (IndexedDB) for big copies: Home's saved rows, IPTV playlist copies, USB drive indexes, the Trakt history. Saving to the database doesn't hold StremioK up.
• When the settings storage is full, what matters wins: saving progress, watched marks, settings, addons or playlists clears regenerable caches (saved Home rows, playlist copies, show info, saved manifests) until it fits; if it still can't be saved, you're told and it's in Diagnostics.
• When the database is full: something large that doesn't fit gives up Home's saved rows first, then a USB drive's index, then playlist copies, one kind at a time. A small item refused (the TV does that for a while after an install, or while it reclaims space) gives up nothing: it's tried again a minute later, up to three times (the Trakt history meanwhile in the settings storage). Each refusal is noted in Diagnostics with the item's size, what the TV allows and uses, and its free space. The Trakt history is saved again only when it changed.
• TV storage (Diagnostics › Storage) shows how much the TV says the database uses of what it allows, how much of that is StremioK's own data and how much the database's own (old versions of items saved again), each item with its size, how many times it was saved since StremioK started, and whether it's no longer used or also in the settings storage; then the settings storage's largest items and the TV's free disk space. What the TV allows StremioK follows that space: roughly a fifteenth of it.
• Tidying up deletes the database and writes StremioK's data back into a new one. The 2017 TV's database doesn't always clear old versions out itself (seen full, with 0.6 MB of StremioK's own in 16 MB, refusing every save), so StremioK also does it on its own when they take more than half of what the TV allows: half a minute after launch, or when a save is refused.