For non-x86 devices it depends on uboot configuration. If the device uses the manufacturer provided uboot (which is the case in 99.99% of Amlogic boxes) it will not be possible as the console config is not required for Android so is missing from the uboot config. For SBC devices where we provide uboot (and in the future when running a mainline kernel where we can force CMDLINE options) it's possible to have a console same as Generic.
Posts by chewitt
-
-
my Amazon FTV lost its purpose when i started downloading 4K HDR rips
Prove that you download "4K HDR rips" from a non-piracy source and we'll consider providing further support.
-
P2P technologies (torrent etc.) are perfectly legal tools in 99.9% of the world legal systems, but the content that 99.9% of people use those legal tools to access would fall under our definition of piracy, and a hint of piracy will normally see us refuse support until a Kodi debug log (that proves the box is clean if piracy add-ons) is provided. You mentioned P2P streams and in the ~7 years that I have been involved with the project I still didn't witness a legitimate/non-piracy use of 'P2P' video streaming. It is not impossible that a legitimate service exists; merely improbable.
-
If you want to use MythTV you'll need to provide your own MythTV server as we don't ship one. We do provide Tvheadend though; so clean reinstall the OS to the SD card (as it's quicker than clearing stuff out) and then add Tvheadend (server) from the "services" section of our add-on repo. Go to the web interface on your_box_ip:9981 and follow the basic setup wizard there. If tvh (not Kodi) can see the Hauppague hardware; drivers are good and then you'll get somewhere. If no hardware, use the driver select add-on to load the (not in-kernel) Hauppague drivers and rinse-repeat. Once you have TVH server configured and finding channels etc. you can go back to our repo and load the Tvheadend (client) from the Kodi PVR add-ons section. Kodi GUI loads the client at startup; which talks to the TVH server which runs in the background.
-
So I hope you can see just part of the reason why I have removed this, you may think it is a bad or a poor decision on my part but I couldn't care less because I am fed up of the constant trouble it causes.
GDPR-2 I'm pleased to see this direction as the wider team recognised it as a long-term support burden some time ago. One of our goals has always been "ease of use" and box installs are inherently more challenging than SBC devices due to multiple "how to make it boot an SD card" methods required - and adding the frequent complexities of internal installation on-top results in a range of box unique issues that tiring to repeatedly solve. It's true that an eMMC install is always going to be fastest, but team testing shows the performance of a good SD card reduces the gain to marginal levels unless the underlying box has inferior components (and crap hardware is always going to be crap hardware). An easier install process results in more people having a positive experience with LE, and thats something we care about more than appeasing the overall small (but increasing) percentage of users who purchase sub-$25 black box junk from far-east bulk buy websites. Caveat Emptor..
-
I haven't looked deeply into HiSilicon requirements, but for anything vaguely official to go into LE's github repo (even as an experimental branch) the technical direction needs to be mainline kernel/uboot with DRM/GBM for rendering and a V4L2 (integrated with ffmpeg) driver to create a zero-copy (mem2mem) graphics pipeline. We have learned from our experiences of Amlogic and Rockchip. As long as those criteria are followed and/or there is a clear plan/vision on how to get there .. we're all ears.
-
GitHub - chewitt/LibreELEC.tv at leiot-8.0
^ out of date and possibly not complete, but might give some hints
GitHub - plexinc/LibreELEC.tv at libreelec-8.2.2-plex
^ swaps Kodi for Plex
-
Piracy add-on websites profit from affiliate revenue on VPN sales from people who use their endless stream of bullsh1t guides and howto links, so nearly all of them contain some form of warning/advise text that recommends using a VPN.
-
I'm not a major wireless expert, but the essence of the problem is that if the 5GHz connection persistently shows the better connection it will be used. If it does not, and it persistently falls back to 2.4GHz, the solution is to fix radio coverage so 5GHz is superior, not forcing the driver to hold onto the inferior connection.
-
TVA and KodiTips are piracy promoting scum. People who @link their accounts with ours are often found in our block list.
External Content twitter.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy. -
and your twitter handle is?
-
The "wetekdvb" module contains code that detects specific properties unique to WeTek hardware, and if not detected, the driver will not run.
DVB drivers on Amlogic are a mucking fess. YMMV.
-
Check the port. My Synology has mariaDB on 3307 not 3306.
-
Provide a Kodi debug log. If it objects to something there will be a log entry.
-
Everything WORKS fine.
^ in this case there is no problem. Watch movies not logfiles.
-
C2 is an S905/GXBB device which means no HDR.
-
Any idea what it could be?
experimental unreleased software?
-
The question is whether Kodi needs support to be compiled in or it can be bolted on afterwards?