Update LE 20190304 images.
Installed latest update then used LibreELEC backup option to re-install my user environment and addons from a recent Backup.
Don't know if its related (but message appear after first re-boot from installing and completing back-up intialisation) now upon full restarts of KVIM2, I get following Failed Message before LibreELEC appears to boot into OS and operate fine?
VIM2 lite WiFi should be able to work with the right combination of firmware/nvram files but VIM2 max was still lacking mainline driver support last time I looked; although that was last summer .. I'll get around to it eventually.
For overall info be aware (according to Khadas) that an updated v1.4 VIM2 Pro and MAX with "in particular" update Wifi module, will soon be available.
See further detailed Khadas information on changes between VIM2 V1.2 & V1.4 pdf here
Thanks for information on key areas of change/update to build 20190225
To clarify my second point, I installed build 20190227 this evening. (You removed 20190225 build and replaced with 20190227?)
1st I attempted to install tar file of 20190227 build into update folder of my VIM2 whilst it was up and running on my network (20190211 build)
Then rebooted VIM2 to in theory allow it to perform a restart and automatic install of 20190227 over existing 20190211.
As previously mentioned "just for general information" this method of updating to latest build onto SD appears not work. No problem at all, just providing feedback as this method of updating works for other frequent alpha/beta builds.
In order to get to my previous LibreELEC set-up with few addons installed/configured etc, I made use of available and very good LibreELEC backup option in LibreELEC settings, to create a back-up before installing your latest build (clean img.gz build onto wiped SD using "LibreELEC USB-SD Creator" ) then used backup restore; to get back to my previous addon setup, with your latest build.
Note: Above method of works well, avoiding a manual setup of addons I require after every update to your latest build 
New image 20190225
Would it be possible/practical to advise what has been added/modified between each of your builds with expected improvements?
For example ref my previous post, clean installed 20190221_test_dvb on SD and quickly tested on KVIM2 Pro. I personally noted following known issues :-
Thanks for working on and confirming new builds are available 
PS Is it possible to download latest tar into LibreELEC update folder and update then re-boot to update, without need to destroy previous build on SD with user settings saved etc (know I can create a back-up if not)
If you are wanting stable usable install for S912 device. I would for the moment (from experience with Khadas Vim2 device) suggest coreELEC 9.x
See lInk above
Thanks for response, can count on me as a familiar kodi Leia user, available to usage test Kodi 18 and/or 19 version of LibreElec on my VIM2 Pro.
New image ver 20190211
Curiosity tested 20190211 on Vim2 Pro and have following observations/feedback. (Most if not all I appreciate will be known to balbes150/developers)
Unable to install over previous existing "running" balbes150 libreelec build on an SD. (Placing tar into update folder then rebooting Vim2 does not appear to work?)
Installing on same SD via PC as a new clean image, then booting Vim2 works absloutely Fine. (i.e. Run from SD card with no altered files, using Upgrade Mode Press and hold power - Short Press Reset - Count to 10 - release power)
WiFi - currently not working for Vim2 (WiFi Drivers for 4.X kernel, not available?)
Build works well with wired connection, moving around GUI installing a few addons then testing Live video streaming before graphics crash kicks in.
Graphics display does not show horizontal glitches in Kodi GUI as with earlier builds. (ongoing improvements to PANFROST open source driver for Mali GPU?)
Graphics crashes occur for me after reasonably short period of playback of live tv channel, always with almost vertical to 45 degree lines up from bottom left corner of 4K Monitor.
Can provide kodi log, debug log but imagine not so useful at this early stage?
Recently purchased Khadas Vim2 Pro 1st for its ability to run Android (Necessary for ensuring sane continous access to all existing UK TV Catchup Apps) and 2nd (really 1st) to explore latest develpment activities towards a fully enabled version of latest Libreelec for a S912 device to run off SD or eMMC.
Hedged a bet on S912 becoming Libreelec supported device post offical release of Leia, from recent posts in this thread from chewitt.
Reason for my logic, is whilst I love using Kodi/Libreelec daily, I dont currenly believe suppport for all UK TV Catchup Add-ons will gain traction in same way as apps are developed for Andriod or IOS devices. (Hoping I am wrong on this point, moving forward post Leia release)
Can't wait to commence/support via user testing a nightly version of Libreelec on Khadas Vim 2 Pro
Imagine MerlinElMago is refering to software and abilty to view/control PiJuice features from within Libreelec, using an addon service?
GitHub - PiSupply/PiJuice: Resources for PiJuice HAT for Raspberry Pi - use your Pi Anywhere
OK miss-understood issue, I also see Milhouse has checked when cdl.m3u renamed to cdl.m3u8 and posted reply in Kodi forum to wwark
gilles0606 wwark if its helpful?
Just tested cdl.m3u file provided in 1st post of this thread on my rpi3b+ running latest nightly #0609 of Libreelec for rpi and live playback commences OK
Also tested on Win10 with recent nightly of Kodi from Files... and playback is ok too
Not by any chance watching a live tv channel on 1st device and then trying to watch another/different live tv channel on second device. I have had message you mention couple of times in that usage situation. (Both devices can only watch same channel live streamed across network at same time)
raspi0w & chewitt , For info this current situation in modprobe.d folder etc
(not currently in situation/location where I can try again with cfg80211.conf copied to modprobe.d folder)
login as: root
[email protected]'s password:
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (official): 8.2.2 (RPi2.arm)
LibreELEC:~ # cd /storage/.config/modprobe.d/
LibreELEC:~/.config/modprobe.d # ls -al
total 3
drwxrwxr-x 2 root root 1024 Dec 21 18:54 .
drwxr-xr-x 13 root root 1024 Dec 16 00:37 ..
-rw-r--r-- 1 root root 616 Feb 26 2017 disable-spdif-for-hd-audio.conf
LibreELEC:~/.config/modprobe.d #
LibreELEC:~/.config/modprobe.d # modprobe -D cfg80211
insmod /lib/modules/4.9.59/kernel/net/rfkill/rfkill.ko
insmod /lib/modules/4.9.59/kernel/net/wireless/cfg80211.ko
LibreELEC:~/.config/modprobe.d #Sprunge.es is up atm, but as it seems to keep going offline, grabbed copies of previous files, here they are on pastebin.com
Please Note: I am leaving location where I have been having problems to connect in a few hrs so will not have an opportunity to gather more information or try anything else to achieve a connection at currnet location. (So if I am only one with problem don't worry etc)
Thought I was getting somewhere with ssh, connman and wifi.config file in /storage/.cache/connman but that may have been something to do with file having incorrect parameters or similar. (did not really know what I was doing, just challenging myself to learn a little more)
Freebox-63910C.config file contents (Note Name = switched to SSID = <in hex>)
[global]
Name = Freebox-63910C
Description = Freebox-63910C Wifi service config file
[service_wifi_Freebox-63910C]
Type = wifi
SSID = 46726565626f782d363339313043
Passphrase = <correct passphrase was inserted here>*A in front of Freebox-63910C (connection I wanted to achieve) indicating connman aware of what to do, but with a connection failure result when trying to switch connection via ssh
LibreELEC:~/.cache/connman # connmanctl scan wifi
Scan completed for wifi
LibreELEC:~/.cache/connman # connmanctl services
*AO Moto G (4) 1708 wifi_b827eb4963d5_4d6f746f2047202834292031373038_managed_psk
*A Freebox-63910C wifi_b827eb4963d5_46726565626f782d363339313043_managed_psk
FreeWifi wifi_b827eb4963d5_4672656557696669_managed_none
FreeWifi_secure wifi_b827eb4963d5_46726565576966695f736563757265_managed_ieee8021x
LibreELEC:~/.cache/connman #
LibreELEC:~/.cache/connman # connmanctl connect wifi_b827eb4963d5_46726565626f782d363339313043_managed_psk
Error /net/connman/service/wifi_b827eb4963d5_46726565626f782d363339313043_managed_psk: Operation aborted
LibreELEC:~/.cache/connman #With further testing hopefully additional useful information. Essentially I ssh'd into rpi3 when rpi3 & PC both connected to hotspot provided by motog phone. Following is image of networks visible in kodi (along with confirmation of connected to motog hotspot)
Then running connman commands in ssh and specifically "connmanctl scan wifi" which immediataly updated kodi's view of avaiable networks.
Unfortunately any attempts to complete connection to Freebox-63910C (selecting and entering phass-phrase in kodi) failed and after long wait would drop back and automatically reconnect to kodi (updated view with only motog hotspot visible again?)
login as: root
[email protected]'s password:
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (official): 8.2.2 (RPi2.arm)
LibreELEC:~ # ps faux | grep connmand
320 root 0:00 /usr/sbin/connmand -nr --config=/etc/connman/main.conf
608 root 0:00 grep connmand
LibreELEC:~ # ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr B8:27:EB:49:63:D5
inet addr:192.168.43.82 Bcast:192.168.43.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:678 errors:0 dropped:0 overruns:0 frame:0
TX packets:750 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:712900 (696.1 KiB) TX bytes:98727 (96.4 KiB)
LibreELEC:~ # connmanctl scan wifi
Scan completed for wifi
LibreELEC:~ # connmanctl services
*AO Moto G (4) 1708 wifi_b827eb4963d5_4d6f746f2047202834292031373038_managed_psk
FreeWifi_secure wifi_b827eb4963d5_46726565576966695f736563757265_managed_ieee8021x
Freebox-63910C wifi_b827eb4963d5_46726565626f782d363339313043_managed_psk
FreeWifi wifi_b827eb4963d5_4672656557696669_managed_none
LibreELEC:~ #
LibreELEC:~ # paste /storage/.kodi/temp/kodi.log
http://sprunge.us/LKgX
LibreELEC:~ # dmesg | paste
http://sprunge.us/gFSM
LibreELEC:~ #kodi.log and dmesg, Where I can see within kodi.log, failed attempts to connect to Freebox-6391C
(where I know I was entering wifi password correctly)
ERROR: ## LibreELEC Addon ## connman::dbus_error_handler ## ERROR: (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)Yes creating a backup then trying with clean install is an idea.
Additional Notes just for information.
I moved rpi3 closer too Wifi Router but this made no improvement to visibity of specific routers 2.4ghz WiFi signal to rpi3.
Other possible weak Wifi connections in area appeared/dissappeared; but never closest router of interest/need so that why I believed its broadcasting on channel 13 to be main issue. (Checked with wifi anlysyzer app on motog phone)
I could connect rpi3 to my motog phone acting as wireless mobile hot spot (thats how I connected from another device to get dmesg log) and have/had no problems connecting to router wirelessly at home. (Actually this is when I updated rpi3 manually to 8.2.2 before travelling to visit family etc)
Switched from DE to FR and this is what's recorded in cfg80211.conf after reboot of rpi3
options cfg80211 ieee80211_regdom=FRThanks for your help
Away from home with rpi3 and Librelec 8.2.2 installed and unable to either see and connect to router with wifi channel set to 13
(not my router so no access to change channel even for short period)
I have temp connected to rpi3 in order to check and modify settings that thought would allow/enable channel 13 access on rpi3 but I still have blank "System - LibreELEC - Settings - Connections" window.
Used following method posted by chewitt but unfortuantely does not seem to work in 8.2.2?
WiFi Channel 13 not possible on RasPi 3, regional settings doesn't help
Any ideas/help greatly appreciated.