In theory connman can do this but the GUI controls for it are not present in our settings add-on and historically there are mixed reports of success; likely a mix of wireless driver and n00b user issues. TL;DR the tethering functions are VERY basic and are not really suitable. Even if you manage to get it working (and no, there are no wiki articles or guides that explain how) many hours of swearing at network connections will be avoided by getting a proper wireless repeater.
Posts by chewitt
-
-
Fix has been merged so it shouldn't be an issue for anyone from v7.90.007 onwards. Thanks for the investigation work
-
No, any kernel version.
-
Have you removed the SD card and browsed the filesystem on another PC/device? .. it's a simple fix (PR has been submitted) but it's not something that we've really seen before which is odd considering the percentage of our userbase that has Pi hardware
-
Code
systemctl stop kodi.service mv /storage/.kodi/userdata/guisettings.xml /storage/.kodi/userdata/guisettings.old systemctl start kodi.servicethis will remove all Kodi settings (but can be easily reversed) .. set audio again; GUI sounds fixed?
-
Honestly no idea, but which kind of NUC?
-
unfortunately i have openelec so i should probably move to librelec first ...Never a bad idea
-
I'm clueless at remote things so I won't be much help, sorry..
-
is there anything I should remove, things that are duplicated, redundant etc?only the memory of running OE
-
-
This is a comment on testing process not the actual issue:
Kodi completely re-wrote the video playback code since OE 6.0.3 and LE 7.0.2 so there is no value in comparing against those releases. Comparisons with earlier LE alpha releases and milhouse builds are valid; testing on milhouse builds is preferred due to the deeper difference granularity we have on the content in each release. If you're just going to post a +1 comment please don't as it adds no value. If you are not running a NUC don't post in this thread. If you are prepared to assist testing please do so (or continue to) via the milhouse's build thread on the Kodi forum. Thanks.
-
WP2 will be added to our build roster in v7.90.007 which is currently being assembled; another 3-4 days away if everything goes to plan
-
init: make sure /storage is owned by root · LibreELEC/LibreELEC.tv@fdcf909 · GitHub
This should be fixed in LE v7.90.006 via the above commit .. anything earlier (e.g. v7.0.2) has the potential for the issue.
-
The trace doesn't show much; other than it doesn't include the usual references seen when the SD card is bad. It's not a general issue with 1B hardware as we had several staff (one of whom works for pi foundation) successfully test boards with the 006 image; so there's no eureka moment.
-
The install process is already documented in the forum posts you've been linked to and the learning experience that follows is all part of the added value in your decision to purchase a cheap no-name Chinese S905 clone (caveat emptor). There is no single definition of "Mini MX" to code around. There are probably 20+ definitions and some will just work while others will need fiddling. On the +ve it's hard to truly "brick" a box, only to put it into a software state that's beyond your confidence.
-
Solution is in post #3 .. create the LE card and let it install/configure itself normally then resize the ext4 /storage partition to create a third partition on the card that you format as exFAT/NTFS/etc. to be used as media partition that's visible to both OS.
-
If there's a difference in scraping behaviour it's down to changes between Kodi Helix and Kodi Jarvis (or Kryton) not OE vs LE; and from memory there are a few differences. In all cases a debug log showing the scraping is the first step in understanding why something is/is-not happening.
-
The correction that you flagged in the OE commit from 2014 is already present/committed in the kernel we use in current Alpha builds (and Milhouse builds) so I'm not sure what you're asking us to do?