Posts by chewitt
-
-
The hotspot feature in LE is intentionally basic and connman supports SSID/passphrase configuration only - nothing else. If you want wireless router features the best thing to use is .. a wireless router.
-
It might be resolved when we bump to mainline kernels, but there's no schedule on that. If you want a router the best device to use is a router. The last Apple a1rport express that I picked up on eBay was $12 and it performs miles better than any on-box hotspot.
-
You can try other GXM device trees.
-
-
-
If the Aeon Nox developer (who is a Team Kodi member) keeps the add-on updated in the Kodi repo it will be available for install. If it's not kept updated then Kodi may not show it as available and compatible. It's nothing to do with LE.
-
It means we stop using the older Amlogic kernel sources (full of proprietary low-quality drivers etc.) and start using the latest (aka mainline) Linux kernel with modern and higher-quality drivers.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
If you want to use an external DB all devices need to be using the same version of Kodi to ensure the DB versions are the same. Once Leia moves out of RC to full release the DB versions (which correspond to schema changes) shouldn't change often. In the Alpha/Beta period things get bumped more often. There have been quite a few changes recently to solve issues found in the music DB.
-
You need to restore the contents of the .img file to the mSD card, not copy the file to the card. Use our USB/SD creator app or any other USB writer app (rufus, win32diskimager, etc.).
-
Kodi will not support Linux releases that use libhybris and Android mali libs and LE team made the decision to not release any official images without support. As we are not planning to release 9.0 images for S912 we are not building them and the known issue that you ran into has not been fixed. If someone would like to send us a PR with the correct fix (adding support for GL debug .. not removing Kodi code) we can merge it.
NB: LE will have proper support for S912 hardware once we bump to mainline kernels in the near future.
-
You can add "ssh" to kernel boot params to force the daemon to start, or use CTRL+ALT+F3 to access the local console. If the GPU is not supported you can confirm the issue but there's nothing to fix.
-
The wireless drivers used in the 3.14 kernel codebase for WH and WP2 do not support being software switched into AP mode. It's possible to force the card into AP mode at boot time by setting some driver options (which I have long-forgotten) but when tested a few years ago the card doesn't perform that well in AP mode. So the conclusion is .. the tethered hotspot feature is not supported on WH.
-
Enthusiasm for RK is understandable from anyone who's spent time in the Amlogic trenches, but in our experience switching from one SoC vendor to another doesn't solve development problems. It only results in different development problems

-
WeTek's business is focussed on the OTT middleware market and they (and most similar manufacturers in that market) are making a strategic shift towards AndroidTV as that's the direction Google is pushing everything now. As such the latest generation of their devices are not using AOSP and the boot process is locked down per AndroidTV spec. I swapped email with the CEO on this topic a few months ago when the next generation of 'Hub' sized box was announced and WeTek have no plans to release 'Linux' versions of these products.
It's also a market trend that will continue. Over time more manufacturers will become AndroidTV only and the number of manufacturers with AOSP products will concentrate on the low end of the market with cheaper manufacturers who source lower-grade components and take more design short-cuts to increase their profit. This long-term reality is one of the reasons why LibreELEC started to focus more on SBC "board" devices where the manufacturers are invested in Linux support than Android "box" devices where manufacturers are not, and where we see significantly more end-user support issues. Boards aren't as cheap as boxes, but at some point users will realise the experience is much better.
NB: WeTek delivered Netflix 4k support on Android. It was never promised on Linux. One of the "lessons learned the hard way" with dual OS support is that users read the spec for one OS and blindly assume the other OS works the same. It was never the case and WeTek burned a lot of support man-hours dealing with people that can't read. It's definitely a factor in their decision to not release more Linux devices.
-