Unless your shared drive is outside of your local network, LE shouldn't care and should carry on playing without interrupts. Possibly your router may have limited the access.
Try enabling debug, play a movie from the share, unplug the external internet connection from you router and post the output from cat /storage/.kodi/temp/kodi.log|paste if you have issues.
Not teaching you to suck eggs - but are you using the RPi zero/1 image and not RPi2
How are you installing LE onto the SD card? Windoze, OSX, Linux? DD, Windiskimager32 or LE installer?
Please give a detailed account of what you did and what you see (Screen shots if possible or camera snaps).
We're not from Hogswarts and have no wizardly power to guess what is going on, so the more information supplied the better.
I too have noticed buffering issues - albeit I'm still on 7.90.10 - I'm going from a CUBOX (Original) running archlinux as a NFS server going via ethernet to the router then WIFI (300Mbps) adapter to ethernet back into my CUBOX-I4 pro. I monitor both boxes (NMON and tail (kodi log and journal)) and can see the traffic is normal on both sides, but just occasionally (and it is occasionally) it stalls - nothing in the kodi log, no hang on either boxes, CPU is as good as zero - no I/O no network traffic. It's as if it just given up on life. I'm still trying to deduce what is causing it. (I don't think it is LE, but something else in my setup).
Could it be the NFS client? I haven't tried SMB.
I have played around with advancedsettings.xml and have tried many options. Even 1G memory and 40 read factor (Didn't go well)
This works for me most of the time on Kodi 17 (NOT for 16 - cache names are different).
<advancedsettings>
<cache>
<buffermode>1</buffermode>
<memorysize>524288000</memorysize>
<readfactor>20</readfactor>
</cache>
</advancedsettings>
I believe the CUBOXTv only has 1G memory, so best to change memorysize to 262144000 and see if that helps.
If you can replicate the error, then switch on debug mode and send the kodi.log, it might show something.
Go for broke install LE on your PC - If it works. great - if not, restore your backup you made earlier. You DID make a backup - for sure I did!
If anything that could be added along with the date and time would be hostname as I'm sure others have multiple instances of LE and it would be nice to differentiate between backups - So 20170315134221.tar becomes <hostname>.20170315134221.tar.
Not critical but would be nice to have.
LE is not like the Kodi for windoze. It IS the operating system. So you should be able to install LE to a flash drive and boot from that - check it out and if you like it - and all works as expected, install it onto you HDD.
I don't believe LE will change the current backup script as it is duplicated with the Kodi Backup addon.
Your best bet would be to run the backup and then rename it using the Kodi file manager.
It is possible but requires adding a patch to smsc95xx.c and compiling the kernel. (Not tested on LE)
Personally I'd use a bit of black insulating tape 
I think what Klojum is referring to is in the forum rules thread-2.html which I'm sure you read when you signed up.
"Be as descriptive and detailed as possible. We are not mind readers."
From you post I have to ask the same question.
1) Which add-ons, or all addons?
2) A full debug log is always required - it can pin point any issues.
BTW: Do you know that "Tonka" is urban slang for "A girl who is very massive"
Can you provide a snippet (or the whole file) of the file in question (if legal) to an upload site, so we can try and replicate the problem.
WOL relies on having a BIOS that is listening for the magic packet on the network interface.
Raspberry Pis do not have a BIOS that can do that, so WOL is impossible.
From: Raspberry Pi • View topic - Any success using WOL on a RPi
LE has a policy of not offering any support to users who have - or may have - illegal addons.
See Official:Forum rules/Banned add-ons - Official Kodi Wiki
Can you post the url from cat /flash/config.txt|paste and cat /flash/cmdline.txt|paste.
Firstly I would uninstall all skins except confluence. Also check that no files for that skin exist in /storage/.kod/addon_data/skin*
I've seen the lack of text before but that was a memory issue.
If that doesn't help, post
dmesg|paste
cat /storage/.kodi/temp/kodi.log|paste
But, in seriousness you may need to bite the bullet and reinstall.
I actually have 3 RPis and don't know why I didn't think of that.Still, good to have another method if things go south.
Excellent. You shouldn't have any issues now.
BTW: if you have time, could you see if the previous post works. Tnx
I guess you don't have an RPi? It would make life easier
I assume your backup is still valid!
Ok, how about FTP and copy everything from /storage to your OSX.
Remove everything from /storage/* & /storage/.*
Make sure /storage is completely empty.
touch /storage/.kodi/.please_resize_me
Reboot.
If all goes well it should resize.
Copy back everything from your ftp backup.
If that fails post the output of dmesg | paste
When you have no wifi post the output of dmesg | paste
I too don't have an issue with Estuary on a RPi2 or RPi3 (But there again I only have a few addons and nothing else). If you don't like estuary, you can always install confluence, as it's still available for Kodi 17.
