Kodi Community Forum

Full Version: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
(2016-11-15, 18:15)gendo Wrote: [ -> ]@Milhouse can you kindly add https://github.com/kodi-pvr/pvr.filmon/pull/56 to tonight's build.

Yes.
(2016-11-15, 19:47)Solomalee Wrote: [ -> ]any ideas?

Not without a log, preferably a debug log.
@Milhouse
https://github.com/raspberrypi/firmware/issues/676

seems to be fixed with latest update. can you confirm any change regarding to this problem?
(2016-11-16, 01:33)mezo Wrote: [ -> ]@Milhouse
https://github.com/raspberrypi/firmware/issues/676

seems to be fixed with latest update. can you confirm any change regarding to this problem?

@popcornmix is best placed to answer that - I didn't see anything suggesting that had been fixed in the last build.
(2016-11-14, 17:37)bill_orange Wrote: [ -> ]
(2016-11-14, 02:36)Milhouse Wrote: [ -> ]
(2016-11-14, 00:58)bill_orange Wrote: [ -> ]Your screen looks very much like mine with only incidental differences. I am not running a static IP. I seems to be that is unlikely to be the problem since I can connect, and play KODI remotely through the web interface. The only problem is having sound come out the local device (stream) from Kodi remotely.

I strikes me as unlikely to be the Choir front end or the browser since I am seeing the same behavior in Yatse.

Here is a log file.

http://sprunge.us/eYTj

Maybe there's a problem accessing local content via the virtual file system (vfs). Could you try some old builds to see if this is a recently introduced problem. If older builds behave differently (ie. they work) then identifying the first non-working build would be the next step.


Well that went badly. I tried to go back to the first build in the update list and it crashed KODI. I tried to go back even further to #0202 and it crashed the OS (rainbow screen only). Right now I am loading the 7.0.2 release to get up and running again. I am not sure this feature ever worked. I looked in the Chorus git and there were problems all the way back in 2014 / 2015. https://github.com/jez500/chorus/issues/116

They seemed to confirm your suspicion that it is a malformed link into the virtual file system.

**edit**

7.0.2 exhibits the same behavior. On another forum a KODI 16.1 user reported the same problem. I don't see any practical way to regress far enough back to find out if this a problem from the beginning or just something really old. If necessary can you suggest a way to regress to 2014 or before?

At the request of a user on the Chorus2 forum I tried putting some music on the SD rather than an external drive. Streaming to the local device works fine in this circumstance. This really looks like problems with the addressing passed to the browser add-on.
I notice that on build #1114 I occasionally get the little thermometer symbol in the top right. Scanning the library is a circumstance that causes it to appear. On build #1114 has overclocking been increased or has the threshold that causes the thermometer to appear changed?

Can someone scan their library and reproduce this?
New LibreELEC.tv Krypton build #1115: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.8.8 #1 Tue Nov 15 23:38:06 GMT 2016 armv6l GNU/Linux

# vcgencmd version
Nov 14 2016 16:19:30
Copyright (c) 2012 Broadcom
version 4a839311e7b5fc3422a8e6a8623b30b52891e0ea (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20161115233703-#1115-g4f365ca [Build #1115]

# Kodi version
(17.0-BETA6 Git:47b4ddf). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (4f365ca6, changelog) and tip of XBMC master (47b4ddf5, changelog) with the following modifications: Build Highlights:
  1. New 4.8.8 kernel
  2. PVR.FilmOn fix
Build Details:
  1. LibreELEC.tv:
    • libva: bump to libva-1.7.3 and libva-intel-driver-1.7.3 (PR:929, 1 commit, 2 files changed)
    • linux: update to linux-4.8.8 (PR:934, 3 commits, 28 files changed)
  2. XBMC:
    • Json fixes (PR:10927, 2 commits, 4 files changed)
    • [VideoPlayer] VideoPlayerVideo: use default deinterlace method from P… (PR:10934, 1 commit, 1 file changed)
    • paplayer: fix replay gain (PR:10924, 2 commits, 9 files changed)
    • [PVR] Fix recordings url encoding. (PR:10930, 2 commits, 5 files changed)
  3. pvr.vbox:
    • Added getting channels in batches of 100 (PR:154, 2 commits, 1 file changed)
    • Added updating recording margins in backend (PR:156, 1 commit, 2 files changed)
    • Added margins to recording (#157) (635e0694)
  4. newclock5:
    • Commits no longer in build:
      • mvc: squash: report true for SupportsExtention pt 2 (4114216d)
      • paplayer: fix replay gain (c0ea3fb9)
      • Remove the "avoid clipping" replay gain setting (40426def)
  5. kernel 4.8.y:
    • New commits in this build:
      • fixup: fb: Use basic types for dma addresses as these are also included from user code (875e8ced)
    • Commits no longer in build:
      • Revert "Register the clocks early during the boot process," (a999a266)
      • Revert "Revert "Register the clocks early during the boot process,"" (79d1f77b)
      • fixup! brcmvirt_gpio: Create coherent buffer and push to firmware (86f35ff6)
      • fixup! rpi-ft5406: Create coherent buffer and push to firmware (8449d49b)
      • fb: Add missing include (56bc3994)
      • fixup: Add to right file (87720689)
      • fixup: Use basic types as this may be used from user code (63baed03)
  6. Additional commits/pull requests/changes not yet merged upstream:
    • Added: [pkg] PR:56: Change user agent as filmon was blocking old one (pvr.filmon)
Kodi restarts when i stop livetv channel on latest build
http://sprunge.us/Cddi
(2016-11-16, 06:11)gendo Wrote: [ -> ]Kodi restarts when i stop livetv channel on latest build
http://sprunge.us/Cddi

Is this a new behaviour with build #1115? Does it happen with build #1114?
(2016-11-16, 06:15)Milhouse Wrote: [ -> ]
(2016-11-16, 06:11)gendo Wrote: [ -> ]Kodi restarts when i stop livetv channel on latest build
http://sprunge.us/Cddi

Is this a new behaviour with build #1115? Does it happen with build #1114?

I happens with fixed filmon addon.. so i need to extract addon from today's build and install in older build.. but in essence could be any build in the past week..
will test tonight once i'm home..
(2016-11-16, 06:11)gendo Wrote: [ -> ]Kodi restarts when i stop livetv channel on latest build
http://sprunge.us/Cddi
Same for me when pvr.filmon enabled in #1115, plays filmon live stream fine, but then crashes kodi on stop of playback.

Image

kodi debug crash log

However with pvr.film disabled and tvheadened enabled no crash occurs

kodi debug log

So imagine pvr.filmon fix incomplete requiring further re-work with regard filmon API changes Sad
the change in filmon addon is trivial so it should not result in a kodi crash.. so i suspect problem is somewhere else..
(2016-11-16, 01:33)mezo Wrote: [ -> ]@Milhouse
https://github.com/raspberrypi/firmware/issues/676

seems to be fixed with latest update. can you confirm any change regarding to this problem?

There is no fix for that issue. Are you saying your problem has gone away?
Can you identify the exact build that resolved it?
(2016-11-16, 09:10)gendo Wrote: [ -> ]the change in filmon addon is trivial so it should not result in a kodi crash.. so i suspect problem is somewhere else..
Fair enough, but easy to provoke crash with pvr.filmon enabled, here is another debug crashlog this evening after enabling addon, waiting for channels to be loaded before selecting one playing it and the switching between it and another live channel.

Crash occuring at moment of switch https://gist.github.com/Mike-KL/97bafd19...aaa6b810f4
Debug includes verbose libcurl logging enabled.

---edit---With tvheadened enabled and switching between channels not able to provoke a crash
(tvheadened backend/frontend both running on same rpi2)
(2016-11-16, 15:04)popcornmix Wrote: [ -> ]
(2016-11-16, 01:33)mezo Wrote: [ -> ]@Milhouse
https://github.com/raspberrypi/firmware/issues/676

seems to be fixed with latest update. can you confirm any change regarding to this problem?

There is no fix for that issue. Are you saying your problem has gone away?
Can you identify the exact build that resolved it?

#1113 fixed it. i went back till #1112 and there the problem started again.