Posts by Iridium

You have already posted This which is a duplicate. Whilst you *think* it might get your question answered quicker, alas it will in fact stop people from answering.

So don't duplicate posts or you risk being blocked.

You are using addons that are banned by Kodi.

As such, no support will be offered on this thread, nor any new threads until *ALL* banned addons are removed.

At first I would try and find out *why* your wifi is dropping out. If using the internal wifi try removing anything metal that might be in the way of your router. Alternatively buy a USB adapter with a better antenna which can be positioned to get better reception.

As to the script, I would run it in a terminal and see what the output is.

Try removing the dtoverlay and use the latest LE version. Also try commenting out dtparam=audio=on in config.txt

If that doesn't work, a lot more information will be required. See Here

What version of LE are you using and on what Raspberry PI?

Can you set the prefix of the title as [Solved] (If it really is solved) Tnx

You didn't actually mention what H/W nor LE release you are using, so any answer will be useless.

Yes, there are many. However as you didn't think it was worth while mentioning what H/W nor release of LE you are running - I'll just give everything I know about.

Many standard linux utilities are available in standard LE, with more available in LE system-tools and network-tools addons.

iftop, bwm-ng available in LE network-tools addon

nmon, htop available in LE system-tools addon.

speedometer: See Here

netdata: See Here

*If* you find something that you think might be useful for LE users, please request a future request and we'll see if it is possible.

No I use the SSD for booting and storage (No SD card is needed). This does however create a backup of 240GB but a restore is only minutes. I use cloud storage to backup changed files.

Most people boot from SD and store recordings on SSD/HDD.

The other alternative is to have LE on the SD card but have /storage and recordings on a SSD/HDD. This means all I/O is on the SSD/HDD.

If I was you, I'd keep things simple and first *try* LE and TVH and see how you get on - you can always change things later.

Basically ease of backup. Also a HD recording is about 2G so there is not a lot of room (even on a 64GB SD card) for many recordings. Generally, booting LE off a SD card and having a SSD/HDD for recordings is the way to go.

The downside of a separate SSD/HDD is you'll need a separate powered USB HUB.

I've been running TVH on a RPi3 for ages and I haven't seen any significant I/O on the SD card. Depending on your DVB adapter USB/SPI you may not be able to record HD due to USB conflicts and speed of USB drives.

Personally, I run a RPi3 booting off of a 240GB SSD via a USB caddy with a Raspberry Pi DVB hat (SPI) and I can run 3 HD recordings simultaneously (All on the same MUX) with only a few errors.

Generally the RPi2/3 is fine for TVH but you may need to tweak the H/W depending on you recording requirements.

I have a feeling this behaviour is similar to many DVB programs like W_Scan which require access to the tuner. If TVH is running, then they cannot get access to the hardware.

So to use dvbsnoop and other DVB programs you'll need to shutdown TVH first to free up the adapter.

It would help if you could explain exactly what you have done so far and any error messages you get.

More information required.

1/ How and where did you download the addon?

2/ What commands are you using and what is the output from the command.

Original post deleted

The *information* you are following, is for a Raspberry Pi. I don't own or know anything about a C2 so can't help anymore. Maybe someone else can help.

Personally, I prefer booting from SSD (and I know it is not what the question asked) As you have a RPi3 it's possible to boot from USB without a SD card. A USB SSD caddy is about £8 and a 120Gb SSD is around £20 a good alternative to a SD card (Albeit a *bit* more expensive)

Some time ago, there was an issue building on 18.04. I had to switch back to 16.04 to get it to work. Not too sure if it is still an issue but you could try on 16.04 (VM?)