Posts by pajtaz

Did you check what your settings are for recording lifetime in Kodi? Go to Settings -> PVR & Live TV -> Recording and see what your setting is for "Default recording lifetime". Default setting is "99 days" so if you did not change this, every time you schedule a recording from Kodi it will tell Tvheadend to set the lifetime to 99 days.

You also need to check DVR Log retention time (days) in Tvheadend (Configuration - Recording - Digital Video Recorder Profiles). I believe this is set to 90 days by default in Tvheadend. If this setting is there, I believe Tvheadend will simply remove the recording from the list even if it was set to Forever.

Anyway, check these two settings and see if they are correct and if changing them fixes your problem.

Changing User Agent did not help. It was an issue with Chromium itself, this specific version.

After reading some forums I found out that somebody managed to get Chrome addon with Chrome rather Chromium. See post and thread here: Chromium?

So I went to this user's site and downloaded few different versions he made. Installing version 65 instead of the addon available in LibreELEC repository made it work. Case closed for now.

What do you mean? How do I do that?

Hello,

This is a specific issue with trying to use Ziggogo in Chrome addon. I am hoping someone can help me. There was a user who said they managed to run Ziggogo in Chrome addon but that user is not replying to my message. Maybe someone else can help.

In this post a user stated they successfully played videos on Ziggogo.tv on NUC machine running LibreELEC: Google Chrome addon no audio

I also have NUC with LibreELEC 8.2.5 on it and Chrome addon. I am also a Ziggo customer in Netherlands and I tried Ziggogo.tv in the Chromium (Chrome addon). I could not play anything. I kept getting the message, "het afspelen via deze browser wordt niet ondersteund", which means the playback is not supported by this browser. I tried changing various settings in the Chrome addon but could not get it to work.

Can anyone help?

Well, I fixed this problem myself. Since Kodi was not recognizing KEY_FAVORITES and the other two buttons shared the "key id", I figure maybe there is a way to change the way Kodi recognizes the buttons by changing the name of the button. So I listed all button names by SSH-ing into LibreELEC and running "irrecord -l namespace". After a bit of trial and error, I found button names for KEY_FAVORITES and KEY_EXIT that Kodi recognizes and that are unique.

In order to use my Favorites button on my remote as Context Menu button, I used KEY_TITLE for the button. In order to use Exit button on my remote as "go to home screen" button, I used KEY_HOME. What I did was open up my remote control keymap file in "/.config/rc_keymaps" and edit the file to change the KEY_FAVORITES to KEY_TITLE and KEY_EXIT to KEY_HOME. I saved then went edited "/.kodi/userdata/Lircmap.xml" file to also change KEY_FAVORITES to KEY_TITLE and KEY_EXIT to KEY_HOME. I kept the <title> for KEY_TITLE and <epgsearch> for KEY_HOME. I then used Keymap Editor to assign KEY_TITLE to Context Menu in Global. I did not have to do anything for KEY_HOME.

Once I did this, I rebooted and now remote control works like it did in Kodi 16.1 and LibreELEC 7.0.2. Problem solved!

You are right, I realized you had a different problem after I posted a reply. I read your post too quickly.

Anyway, can you make the SMB share using commands in Linux instead of making a share in LibreELEC? That could make it faster.

Tonyrh,

Root cause could be the way that Kodi mounts SMB shares. Sometimes the access to these Kodi mounted SMB shares is fast and sometimes it is slow. It varies between which operating system is accessing the SMB shares. I had a similar/same issue and posted about it in Kodi forum. see the thread here: Kodi forum post

In short, the main way to get always fast access to SMB shares in Kodi is to manually mount them as described here: Mount Network Share

If you do this, you should always have fast access, no matter from which operating system and machine. If you still have problems with speed then I would not know what the problem is and how to fix it. Just make sure if you mount the SMB shares manually to remove them from Kodi first (by removing them inside of Kodi).

Hello,

This issue is on LibreELEC 8.2.5 on x86_64 machine. I have two problems with using the remote control that I did not have with LibreELEC 7.0.2 on imx6 machine (Cubox). I have attached the log so you can see what happens when I hit the buttons.

First issue is that KEY_FAVORITES does not get recognized by Kodi even though it is received by Kodi. I tried using Keymap Editor and when clicking this button nothing was happening. So I checked the log and in the log this line appears without being followed by "OnKey" line:

19:52:05.579 T:140290439489216   DEBUG: LIRC: Update - NEW at 24221436:16c 0 KEY_FAVORITES devinput (KEY_FAVORITES)

In my Lircmap.xml in Userdata folder, this button is assigned to <title>, which is then assigned to operation of ContextMenu in default remote.xml in <global>. With exact same Lircmap.xml this button worked as ContextMenu in LibreELEC 7.0.2.

Second issue is that KEY_BACK and KEY_EXIT share the same key id. When pressed, Kodi recognizes it as key id=216 for both buttons, even though they are actually different buttons with different codes. I first saw this in Keymap Editor and in the log, you can see it also:

19:52:15.799 T:140290439489216   DEBUG: LIRC: Update - NEW at 24231656:ae 0 KEY_EXIT devinput (KEY_EXIT)
19:52:15.799 T:140290439489216   DEBUG: OnKey: menu (0xd8) pressed, action is fullscreen
19:52:16.484 T:140288722986752   DEBUG: CWebServer[8080]: request received for /jsonrpc
19:52:19.048 T:140290439489216   DEBUG: Previous line repeats 3 times.
19:52:19.049 T:140290439489216   DEBUG: LIRC: Update - NEW at 24234906:9e 0 KEY_BACK devinput (KEY_BACK)
19:52:19.049 T:140290439489216   DEBUG: OnKey: menu (0xd8) pressed, action is fullscreen

In my Lircmap.xml, these two buttons are assigned to <back> for KEY_BACK and <epgsearch> for KEY_EXIT, the same as in 7.0.2. Again, in LibreELEC 7.0.2 both of these buttons had different key ids and operated as intended. In 7.0.2 uUsing Keymap Editor I was able to assign KEY_EXIT to activatewindow(home) so I used it as universal exit key. Trying the same in 8.2.5 does not work because Keymap Editor recognizes both buttons with key id of 216.

Can someone please help me fix this? Maybe someone can explain how does the code that is seen by LIRC get translated to key id. I searched many forum posts on both LibreELEC and Kodi forums but cannot find an explanation. If I know how this is done then I can change the key id of these buttons and get them to work.

Currently this is an issue for me primarily when using the TV Guide and wanting to exit to Home at any screen. I was able to do both of these things before. Thank you in advance.

01_KODI.log

Lircmap.xml.txt

Thank you vpeter. That worked. I am surprised this was not caught earlier.

Hopefully rest of the build goes ok.

Hello,

I have the exact same problem as posted in this thread that was never resolved: Openssl compilation issue for 8.2.5 / 9

I am trying to compile 8.2.5 on Ubuntu 16.04.6 on 64-bit machine. Original poster did not really explain how he solved the issue and nobody is replying to the post any more. There must have been many people with exact same issue if it occurs for 8.2.5 compilation on the recommended Ubuntu build machine.

Can anyone please help me get over this issue?

I have the exact same issue as OP, compiling 8.2.5 on Ubuntu Server 16.04.6 LTS. Doing vpeter's suggestion did not change anything even after wiping the entire build folder.

What is the final solution? I do not understand what sammyrc did when he said he ran the entire shell script from the Makefile manually. Can anyone help me with this?

I have read so many forum posts on many different websites but I cannot find an answer to a simple question. It is possible for a device running LibreELEC/Kodi to take control over CEC WITHOUT power cycling the device?

This issue was discussed multiple times across multiple forums but nobody ever answered a simple question of whether it is possible to send a command by a device running LibreELEC/Kodi to take control over CEC without power cycling. The issue is simple: whichever device (of the ones connected over HDMI and using CEC) powers on last, that device takes control of CEC commands. If the device running LibreELEC/Kodi is powered on after TV and AVR, that device will be the one who can control TV and AVR over CEC (in my case, to control volume up or down on the AVR). However if the device running LibreELEC/Kodi remains powered on and TV and AVR are switched off then some time later they are turned on, the device running LibreELEC/Kodi cannot control TV or AVR any more (unless it is power cycled).

I am running LibreELEC on Cubox-i4x4 and I can control volume of AVR using Yatse remote control app if Cubox was powered on last. As soon as TV is power cycled, the TV takes control and I cannot control volume of AVR using Yatse any more. This is due to TV taking control over CEC. Why cannot the same signal that takes control of CEC be sent again by my Cubox without power cycling it?

Please help me understand whether this is possible and if it IS possible, how can I take control over CEC without power cycling. If it is not possible then this issue can finally be explained to everyone. Thank you ahead of time.

I use HDHomeRun 4DC (HDHR3-4DC). It's great but it's an overkill if you only need one tuner. I sold my USB tuner Hauppauge WinTV DualHD since I got the HDHomeRun 4DC. I think the WinTV Dual is ok but I believe the support is there for only one tuner. There's a whole discussion on LibreELEC forum about this.

Otherwise there should be other USB tuners that you can use. The only thing I can say is that having one box (your Raspberie Pie 3) doing TV tuning and recording using the USB tuner might slow it down too much. My Cubox could not handle watching TV with the USB tuner and recording. Maybe for this reason a network tuner is the better option. Just my thoughts.

I posted this on the Yatse forum. Somebody there should be able to help.

This may sound crazy but I witnessed something yesterday that freaked me out. It also made me concerned for security of Yatse Android remote control app.

We use Kodi for live TV. We were watching live TV, just simply watching a channel. My wife was browsing Facebook on Chrome on her Android phone (she removed the Facebook app). As she was browsing, there was a sponsored ad for AliExpress Shopping App. In the ad there was a button for "Shoppen". She clicked on that button and the playback of the live TV stopped. It was equivalent to clicking stop on the remote control or clicking stop button on any iPhone, Android or other remote control app (such as Yatse).

I was able to repeat this every time with this particular ad (AliExpress Shopping App ad on Facebook). I have recorded a video of this occurring. You will see that I click on the button while TV is playing, Playing stops and goes back to the TV guide, which happens if you normally stop playback of a channel after you clicked on the channel in the TV guide.

My wife's phone has the Yatse app installed. I figure that's the way that clicking on the button in the ad caused Kodi to stop playing the live TV stream. So I went into Yatse, removed Kodi from the list of devices and repeated the test. As I suspected, nothing happened when clicking the button in the ad. So obviously clicking on the button in the ad was somehow sending a signal through Yatse to stop playing the live TV stream to Kodi. I did notice that clicking on the button should open a pop-up but her Chrome settings prevent pop-ups. Besides the pop-up, nothing else seems to happen when clicking the button. You can see this in the video.

So can anyone explain what is going on? It is obvious that somehow Yatse gets activated and sends a stop stream signal to Kodi when clicking on the button in the ad. But that should not be allowed to happen, unless I am missing something. Is this an Android security issue or Yatse app issue or Facebook ad issue or some combination of both? This really freaked me out. This means having Yatse installed on the Android phone could allow anyone to control Kodi through web pages, intentionally or unintentionally.

I am really curious what developers have to say.

Any progress on this?

Thank you. It seems the decoder was completely rewritten in Krypton for iMX. This will be a nightmare to understand.

Where in the code is this? Sounds like the same problem.