I've been thru the same issue. My solution was a cheap $10 USB 2.5/5Ghz wifi adapter with a decent antenna (Something like This) and I haven't had any problems. Set to 5Ghz I can stream from my NAS upstairs to my LE downstairs without issues.
Home plug is another solution but a real pain trying to find a "clean" socket.
It might help the community if you include basic debug files - see Here
It would seem we might have been barking up the wrong tree.
I tested using a generic BT USB dongle and an Amazon BT speaker.
I tried 8.2.5 on a Rpi 1 B+ and experienced everything you explained. Audio not working via BT, occasional crashes of Kodi and frequent disconnects of BT. Audio was heard, but only via HDMI – even when audio was set to Puleseaudo BT.
I then tried (with the same BT hardware) 8.2.5 on a RPi2 and BT worked as expected – audio via the BT speaker.
I then tried 8.2.0.1, 8.2.3 and even 7.0.3 on the Rpi 1 with the same results – no BT audio.
Seemed to always error on “pa_stream_write failed”
I'll try and debug further, but if anyone else has any pointers, it would be appreciated.
I've tried Raspbian on both RPi1 and RPi2 and BT works. (Not via the web browser!)
Related posts:
Update (2018-06-03)
I tried a newly compiled LE9 (Latest git) with little improvement - in fact worse as the BT kept disconnecting.
Turning off is not the same as disabling, however it's worth a try. Yet, I'm not optimistic.
By virtue that you have tried all the other RPi distros, and you get different results would seem to suggest that it is a HW issue as the distros mentioned all use the same basic SW.
You could try Archlinux but I don't believe there is any active Kodi implementation.
At the end of the day the RPi Zero is a real bottom end SBC and designed for educational purposes and not high end media systems
AFAIK the HW is the same, or at least very similar.
If I read the thread correctly, yes it works but not continuously, whether this is due to the strength of the BT signal, or the processor speed I'm not too sure. I don't have a Zero nor a RPI3 to test it on but I did do some work on Kodi and BT and it was a right pain in the donkey.
You could try disabling wifi by adding dtoverlay=pi3-disable-wifi in config.txt How (It should work on a Zero) and try moving closer to to the Zero to discount a distance issue.
If it still doesn't work, try another distro to see if it's a LE issue or Kodi.
It would seem Here that the internal BT chip is the problem, especially if used alongside the internal Wifi.
This might help dm-crypt
A quick search shows many examples. This should work on a Pi.
INPUT="$1"
for i in *.mkv ; do
ffmpeg -i "$i" -bsf:v h264_mp4toannexb -sn -map 0:0 -map 0:1 -vcodec libx264 "$i.ts"
mv "$i.ts" "$i.mpg"
sleep 3
doneFrom Here
HEVC (H.265) files require more horsepower to play. Stay away from these files with a RPi
blueribb is correct - there is no way the RPi3 can normally play HEVC at 1080p. Maybe the RPI3B+ might be able to but I haven't tried. I tried a milhouse build on a normal RPi3 which had a few tweaks and seemed to work at 720p.
Easiest way is to use "Handbrake" to convert to X264 - although not on a Pi unless you have a few weeks to spare 
** DO NOT ** Install EXODUS - it is a banned KODI addon - See Here
It's possible that the drives are not mounting because they do not have enough power. Use a powered USB Hub and try again.
CvH If I understand it correctly, the file advancedsettings.xml is located on a windoze NAS and wants to link to the Pi which I assume is running LE.
Why! I have no idea, but the only reasons I can think of is either, they are running multiple Kodi systems and want to have a central file (Which in my opinion is a bad way of doing it - far better to have a mysql DB for all instances) or it's easier to edit on the windoze box.
If I understand you correctly, you want to split the audio output so that the front channels go via the HDMI whereas the rear channels go via the audio sockets. Whilst I don't think it's possible, as Klojum mentioned the quality would not be acceptable and I think you'd find a slight delay between the two - which would be noticeable.
You'd be better off buying a cheap amp.
Works well RPi1 and good documentation. Will need to see how well the removal strategy works, but certainly useful.
My starting script is:
./rsync_tmbackup.sh /storage /storage/backup/ /storage/config/rsync_tmbackup_exlude.txtas rsync_tmbackup.sh <Source> <Destination> <Exlude file>
With <exclude file> /storage/config/rsync_tmbackup_exlude.txt containing:
- /.kodi/addons/
- /backup/
- /Music/
- /temp/
- /lost+found/
However, it doesn't like excluding /backup/ and so includes it in the next run. Not too sure of it's the syntax or doesn't like <Destination> being part of the <Source>.
Update: There was a space at the end of - /backup/<space> which was causing the folder not to be excluded.
Oh well, back to basics. I'll continue putting the SD card in the photocopier as a backup solution 