View Single Post
Old 01-09-2022, 05:19 PM   #1
JJTech
Nerd
JJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongueJJTech can tie a knot in a cherry stem with his or her tongue
 
JJTech's Avatar
 
Posts: 52
Karma: 22352
Join Date: Dec 2020
Location: USA
Device: Kindle Basic 3 (2019)
Kindle .active_content_sandbox

I've recently noticed the .active_content_sandbox folder on my kindle. This puzzled me, because according to the internet, all active content had been disabled before my kindle even came out (it's a 2019 edition).

I did some preliminary experiments, and it appears to contain several caches and databases related to the built in apps (experimental browser, store, help, etc.). They were mostly .localstorage files, which turned out to be regular sqlite dbs that contain the settings and history for the apps. Interestingly, I was able to replace the cached storefront.html, and display my own page in place of the store. There were also some additional apis available on window.kindle, which I would like to experiment with.

Has anyone else experimented with this? Do you think this could be used to develop anything interesting (i.e. a jailbreak or similar)? Or at least (a) custom app?
JJTech is offline   Reply With Quote