Every "App" ´that uses the api requires api keys. Every Samsung, iPhone whatever App that makes usage of it has its own api keys.
If you use for example the Samsung TV client app, Samsung and Youtube knows what you are looking because the owner of the keys has extended logs what happens with it. So if you are saying that you don't need to enter keys at the Samsung client, it means you don't need to because Samsung has done it for you with their own keys.
Stalker server -> Kodi stalker client -> Tvheadend server is not working
Stalker server -> Tvh Server -> whatever is maybe ish working (not sure what the Stalker server is able to do)
boot you pc and attach your hdd, then enter dmesg | paste via ssh (Accessing LibreELEC [LibreELEC.wiki]) and post the link here.
now reread the log, you also pull the addons from RPi2 that might create problems
Do you mean
Stalker Server -> Tvheadend Server -> Kodi Tvheadend Client ?
strange, the file is there and the rights look also okay
you should try to manual refresh the repo, there is a new version available since yesterday
If you shutdown do you see terminal Text at the end? If so could you make a photo of it?
Do you use standby/hibernate ?
you should use
git clone https://github.com/LibreELEC/LibreELEC.tv.git LE-VDR
cd LE-VDR
git checkout libreelec-9.0
PROJECT=WeTek_Play ARCH=arm scripts/create_addon vdr-addonand have a look here
LibreELEC.tv/packages/addons/addon-depends/vdr-plugins at libreelec-9.0 · LibreELEC/LibreELEC.tv · GitHub
you need to add a new plugin and try to compile it
PROJECT=WeTek_Play ARCH=arm scripts/build vdr-plugin-yourname
pls post the output of
dmesg | paste
here is patch for 3103b for upstream kernel
likely its the same that does not build with latest kernels, he wanted to push a fix for it soon so it should be doable soon 
no idea how this should work 
but if it works for you that great news
try power on the Screen before you start the device, maybe an edid problem, I guess Kodi is running and you just get no output at the screen.
Pretty sure 22 is the last cron job to run just ahead of the crash
those logs look pretty normal 
do you know if it happens in a similar timeframe ?
reboot and maybe cron some script
uptime >> /storage/uptime.txt
Also can you try different SD card and powersupply just to rule that out, we saw already very strange things.
Do you have some other devices around ? Maybe try it there if the same happen, it could be some kernel problem from the RPi, can't rule that out.
problem found and fixed, pls try again
erbas pr with the drivers is pending and should be merged sooner or later, intrgration into that images may take a bit more time because we need to figure out how to do it actually - thats the fun if every moving part + the dvb drivers are at the same linux subsystem
