The hotspot (not access point, hotspot) feature comes from software called "connman" that manages connections in the OS. It was originally written for a mobile phone OS to provide a tethered hotspot, e.g. laptop connects to mobile and shares the mobile connection. As a result it is deliberately simple and the only configuration options are on, off, and the ability to change SSID and passphrase. If you want an access point with access point features and config options, you need to get an access point.
Posts by chewitt
-
-
The file /storage/.cache/services/samba.conf (server) is edited via the LE settings add-on. The contents of guisettings.xml (client) are edited via Kodi Services settings. If Kodi is accessing media from something older or misconfigured that only speaks SMB1 then Kodi settings are correct. If the media host is newer and can handle SMB2/3 then it's better to use them (as SMB1 has large security holes) and Kodi settings are wrong. If media is stored on the LE device there is no need to access anything over SMB so it's irrelevant if the settings are mismatched.
-
Venom is an Exodus fork. No further support.
-
So you have a garbage realtek driver then. Deja-Vu.
-
Depends on what the command is, i.e. what you're trying to achieve. Kodi has a fairly comprehensive XML-RPC api that covers many things.
-
The UK version oif "House of Cards" came first (based on largely the same story-line) and it's a valid response to a query. You either need to provide and nfo file to avoid this, or use the refresh option in the Kodi GUI to select from other available options and then pick the US series.
"Band of Brother" or "Band of Brothers" ?
-
Code
echo "sleep 10" > /storage/.config/autostart.sh && chmod +x /storage/.config/autostart.sh^ run that and see what happens. The script is run at the very start of userspace boot and will stall everything for 10 seconds. Kernel side loading should continue though, and I'm wondering if it's just a case of slow loading kernel drivers.
-
-
Yes "works fine for me" .. but I'm using a wireless device with a well written drivers (ath9k_htc). If you're using something with a garbage Realtek USB wireless driver .. YMMV.
-
Make sure you're using the HDMI connector nearest the power port.
-
LibreELEC.tv/openssl-config at master · LibreELEC/LibreELEC.tv · GitHub
^ put the certs that you need in /storage/.config/cacert.pem and they will be appended to the embedded certs at boot time.
-
I think we reached the point where we need to start mirroring add-ons for download instead of self-host
-
No Linux devices truly support HDR at this time and Kodi has only partial siupport (still work in progress). RPi4 and Intel NUCs (Gemini Lake and newer) are most likely to be best/first supported due to the higher overall levels of development in their ecosystem.
-
Team Kodi made the decision to bring forward the release for Kodi Matrix (v19) to forcibly kick-start the migration to Python3; because most of the add-on developers are sitting on their arses not-migrating their code. I'd previously expect things to play out over the next ~6 months and that would align with the original v19 not-an-agreed-schedule, but now that v19 comes early it will push HDR to v20. That said, v20 is probably a shorter development sprint than normal to compensate. Not that the word "sprint" should ever be closely associated with Kodi schedules
-
crazycat is/was planning to bump things once 5.4 is released, not before. I'm also waiting on LE master branch to stabilise after the Py3 changes before spending time on 5.4 things (not much spare time at the moment).
-
Fix NTP in your network and the RPi will have the correct time. The 11/4/2019 date is the release date of the current glibc version, which acts as the fall-back when NTP fails.
-
connman provides an intentionally simple tethered hotspot as you'd find on a mobile phone (which is what it was written for). If you want the hotspot to do more, you will need to code it to do more. Sources are freely available and the connman mailing list is the place to send your feature enhancement or bugfix patches.
-
We have no plans to add support for any more Realtek chips that require badly written vendor drivers that break with every kernel update. Once their chips become supported in the upstream kernel (and thus becomes simple to maintain) we'll be happy to configure them in out kernels.
Not the answer you're looking for I know .. but that's the answer.