[Dangerzone]

The forum mods prefer that people not paste large text from logs files. Better off using Pastebin,

Yep, "[Errno 1] Operation not permitted:" shows that it is a permissioning problem.

I cant work around that via LazyTV. But there might be a solution if you are able to get to a command line:

Save the contents of this http://pastebin.com/7FKiv33E to a python file, named_anything.py, making sure to replace the CLONE_NAME and that the ADDON_PATH is correct for your system.

Then on the command line (assuming you have python installed) just run: sudo python named_anything.py.

I dont know jack about Android devices, but that is my best effort.

I finally got a chance to try this, but my AFTV isn't rooted, and doesn't recognize "sudo" or "python". Thanks anyway

First of all this app is amazing so thank you for all your hard work and I generally use it for the movie aspect of it which is great!

I use kodi on a fire TV stick and a Windows PC. I was able to get a clone of the app to work correctly on the fire TV stick by doing this very roundabout way (Had it setup on the PC first so I figured I'd try):

1) Made a clone of LazyTV on my PC

2) Using adb, pushed the scripts.lazytv.lazytvclone folder (from /userdata/addons) to the matching location on the fire stick.(the push function will recursively send the folder and all of its contents)

3) Using adb, pushed the scripts.lazytv.lazytvclone folder (from /userdata/addon_data) to the matching location on the fire stick

NOTE: In both of the previous steps the folder did not exist on the fire stick so the push function creates it

4) Restarted Kodi on the fire stick and when it booted up I had a working clone of LazyTV to use different settings with

In theory all you should really have to do is pull the original scripts.lazytv folder from the fire stick, make a copy of it, change the name of the folder and descriptions inside of the addon.xml file (change the addon id to whatever you want the clone named, in this case scripts.lazytv.lazytvclone), and push it back to the device. Doing this for both /addons and /addon_data should make a functioning clone unless I'm missing something that the python clone script is doing on top of all this.