Posts by chewitt

Current Amlogic builds have limited support for DVB devices compared to Generic/RPi builds due to the ancient 3.10/3.14 kernels in use and we are still experimenting with media_build support. We figured out how to backport and build it, but this then breaks other drivers (e.g. IR things) we consider to be more fundamental and important. If you find something that works, great, but if not an RPi3 as the headend device is a good compromise.

NB: Things will improve for 64-bit devices once we move up to a current kernel as we'll be able to use media_build without hacking, but that's months away and 32-bit hardware will remain on the older kernels (noticing one of your boxes is S805).

Nothing stands out in the log (to me) and I use the same add-on daily and never see the issue described. The BBC are changing their site a lot at the moment which is leading to some iPlayer breakage; the add-on authors need a couple of days to react to changes.

NB: In future please use the native "cat /path/to/log | paste" function. It's easier for you, and us.

If we have to guess which DVB devices are in the box we will have to deploy our crystal ball. When this happens our guesses are usually terse in wording and slow to arrive.

I'm still waiting for a sample of a problem file.

Changes must be applied via a diff patch that works on the original download source; see the "patches" subfolder of a package. Patch files use a simple naming structure and are applied in alphabetical sequence. You can work within the build folders, but only to create the patch. NB: The build system will auto-detect new patch files and on next build run will auto-clean the package build contents in build.LibreELEC-blah erasing any changes that you made there, so ensure you save them all (as diff patches) before rebuilding. If you want a "developer" workflow for changes it's best to have original sources in a git repo and then you only need to change package.mk to update the githash to pick-up your latest changes.

If you want to release a community version of LE for that device via these forums you are welcome. I would not accept it as a formal addition to our roster of build projects as that is not necessary. The 8723bs driver appears to be in the staging area of the 4.12 kernel which is a couple of months away; once available the kernel config and firmware required can be added to the Generic project. If there are other changes required for other areas of hardware support - please submit the changes for review. Having someone actively interested in these devices would be nice as we don't have many (if any) of them among staff.

NB: Our master branch (LE 9.0/Leia) will move to 4.11 kernel in the next ~week when it's released. Once we bump someone normally creates a PR to start accumulating the changes required for the next major version bump (i.e. to 4.12). Please comment and direct people on changes needed.

to be clear, all development should be done against the master branch. We can then assess the changes and make decisions on what items can be backported into the 8.0 branch which has tight change control as it is an active release branch.

If you think we're going to search through 69 posts on pastebin.com to guess which one is relevant you are mistaken.

Install the lcdproc add-on from the LE add-on repo.

Invest the time and update everything to 17.1, because although it's technically possible to do some kind of dual-boot arrangement on a box to allow booting between LE 7/8 - it's one of those topics where "if you have to ask how it's done?" it will take considerably longer to figure that out (there is no pretty howto guide anywhere) than the effort of updating, which most users understand.

No log = No problem

It's hard to comment. My Slice CM3 box died (suspect kids or wife plugged the wrong PSU into it) so I cannot test anything, but I never had issues with the RF remote before. It's not a general issue - else other users would be flagging the problem.

Thread moved to the Amlogic section

Current pi firmwares show a thermometer in the top-right corner when thermal protection kicks in, and even then the pi is capable of running at very high temperatures for an extended period. In other words, if you didn't see the thermometer and it wasn't insanely hot (which is unlikely in a case with heatsinks etc.) the hang was probably software induced and not related to heat.

Kodi debug log please, and any logs from the add-ons itself (if they exist). The add-on was updated the other day to current latest in Kodi github.

Start boot the box, wait a few mins for all the tvheadend stuff to settle, demonstrate the problem, then capture the log.

And please use the native "cat /storage/.kodi/temp/kodi.log | paste" function so we don't have to download stuff you attach to posts. It's easier for you, and over cumulative time, considerably less annoying for us.

zattoo_retro.tar.gz

not our sources or kodi sources, so we have no idea what modifications it contains. I built RPi2 from our sources several times in recent days without issues.

Quote from Rgrevy

Is there anyway i check for network or HDD traffic before going to sleep, to prevent it when its being used remotely

basically, no

Nope. I haven't a clue about RTC issues/workings. Sorry.