Does anything happen with the registered bug reports here?
They languish unloved until sometime replies 
I've no idea what the issue is but the first step is updating to the current Alpha release. If the problem still exists it can be investigated, while all development on our Jarvis/7.0 build ceased months ago.
ute it shouldn't block anyone who already registered with an @yahoo.com address from accessing the forum. I'm hoping this is a temporary change while we figure out something that will prevent bots registering with yahoo accounts.
Have you tried copying the binaries from a recent Ubuntu install?
The root cause has been identifed (changes in diskutil info output) and will be corrected in the next update to the app. It also looks like macOS sierra has a bad user experience with the app due to the more restrictive enforcement of gatekeeper, but that's a separate issue.
Try an alpha build on a spare SD card - let us know
giannis1711 - the dmesg log shows a fully working card *but* you have enabled the local wireless hotspot feature. This means your card is acting as an access point; hence you cannot use it to connect to other networks.
You can get decent Pi starter kits from people like The Pi Hut. The kit will ship with a "noobs" SD card that might contain OpenELEC as the pre-loaded mediacentre OS unless they finally exhausted the stock of OE imaged cards, but 30 seconds with our USB-SD creator app will correct that 
Other sources of kits are pimoroni.com and modmypi.com .. and since yesterday the official Raspberry Pi - Teach, Learn, and Make with Raspberry Pi shop although that kit has stuff you don't need for a mediacentre and is more expensive. Still, all of them kick back a percentage to the Pi foundation and it's a great cause.
Or you remove the USB drive from the Pi and connect it to the computer you're reading the forum on and format things there.
Connman simply routes traffic from the private 192.168 tethering subnet to the internet connection (e.g. eth0) so the answer should be "Yes" as long as you configure proxy details on the client devices that access the tethered access point. The tethering config that you can set in Kodi only applies to Kodi itself not the whole OS. If it doesn't work you can do "touch /storage/.config/debug.connman" then reboot and tail the journal to look at what connman is doing (output is very verbose but somewhat human readable) in case there's an error, but I suspect there isn't anything. If it really doesn't work, it's probably not designed to work that way. The connman tethering feature is originally created for a mobile phone OS to create a simple mobile hotspot. It's not something that will ever be enhanced so if it doesn't work the solution is to get a proper wireless router..
Streaming to an LE box over BT is not supported. Only streaming from the LE box to BT speakers.
kodi-send --action=PlayerProcessInfo
kodi-send --action=PlayerDebug"dmesg | paste" and "lspci -nn | paste" and share the URLs here
And with v7.90.005? .. there was a fix for an OOM issue in Kodo 17b1 (but no guarantee it's the same issue).
a) The error message is just a warning, it can be ignored
b) The 7.0.3 build you are using is not official (we stopped at 7.0.2) so who knows what mixed up extra commits it contains
PlayerProcessInfo .. and yeah it's fcuking annoying
FWIW, nouveau works well enough on my revo ION1 box, most issues crop up with live tv, progressive scan content works without problems.
Do you have the nouveau changes in a git repo anywhere?
It normally depends on the device (the GPU in use) and what's in the HDMI chain. It's simple to test without the AVR inline.