• 1
  • 142
  • 143
  • 144
  • 145(current)
  • 146
OpenELEC Testbuilds for RaspberryPi (Kodi 17.0)
(2016-04-16, 15:00)Milhouse Wrote: All good things come to an end - there will be no further Milhouse OpenELEC test builds.

You can find Milhouse LibreELEC RPi test builds here: http://forum.kodi.tv/showthread.php?tid=269814

Many thanks to everyone that has tested these builds, hope to see you all helping make LibreELEC even better! Smile

Thank YOU!
(2016-04-16, 14:45)steve1977 Wrote: Oh, I forgot that OE collects more than one log. Only the very last is relevant (I booted, played, buffered, stopped). I can repost if helpful?

I don't think it is a network issue. If I do a fresh install of OE on the RPi2, it does work again for a few days or weeks. After that time, the old behavior happens again. It feels almost like some cache running full or something like this?

You're going to have to post a new log, the log(s) you posted seem to be from build #0317.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Yup, I haven't updated for a few weeks. Let me wait until the first LibreElec nightly is up and then repost.
Server: Asus Sabertooth Z77 | Intel Core i5 3.4 GHz | 16 GB DDR3 | 128 GB SSD, 82 TB (9 x 6 TB, 7 x 4 TB)
HTPC 1: Raspberry Pi 2 | HTPC 2: Raspberry Pi 2 | HTPC 3: Raspberry Pi
Noticed in last couple of builds that audio codec/bit-rate etc information when playing music is visible top left of kodi interface with no option to switch on/off using 'o' on keyboard?

Using #0415, crashed Kodi couple of times when playing flac files from library and then stepping back through interface, interface seems to lock up before Kodi crash

Crash Log http://sprunge.us/gALN
Standard log after crash http://sprunge.us/iBjV

Wondering if its time for me to start with a fresh with clean LibreElec install and then switch to tonight's planned LibreElec test-build Blush
RPi4, (LibreELEC 11.0) hdmi0 -> Philips 55PUS7304 4K TV, hdmi1 -> Onkyo TX-SR608 AV Receiver
(2016-04-15, 21:59)ragedogg69 Wrote: Apologies if this has been addressed. I just updated from a January build to the most recent. My only issue is I cannot get .strm files to play. They worked fine on those older builds. I even downgraded back to 0101 and found the .strm files work great. The new builds just fail to play them. Am I missing something?

EDIT: I should note each .strm file contains a single m3u8 file address.

(2016-04-16, 11:08)Milhouse Wrote:
(2016-04-16, 09:55)Dimitriss Wrote: Bump.
Still having this issue on latest build.
Chris Sean's latest build seems to be working fine.
Thanks
Identify the build when this first started happening, somewhere between build #0101 and current builds. Once we know the build that broke strm we can narrow down the exact commit.

#0311 all strm files tested work. #0312 some start to fail. (not all) #0314 more .strm files stop working (not all) and it continues like this until no .strm files work. I hope this helps, if not for openELEC, but libreELEC.
Theater: The PS4/XBONE killer running Kodi 17.3 3D Movie Box: Raspberry Pi running LibreElec 8.0 Alpha BROKEN Family Room: "A6-Pack" running Kodi 17.3 Whole House: FireTV running Kodi 17.3
(2016-04-16, 18:14)ragedogg69 Wrote: #0311 all strm files tested work. #0312 some start to fail. (not all) #0314 more .strm files stop working (not all) and it continues like this until no .strm files work. I hope this helps, if not for openELEC, but libreELEC.

I can't see anything likely in #312. Are you sure that build is worse than #311?
Do you have an example publicly accessible example strm file I can test?
Not according to the forum rules. A strm file containing ustream's ISS feed failed by 0314. That is a tough feed as it is not active when on the dark side of the planet. It is available from ustreams public api. The first failure of a strm file in 0312was a hls m3u8 that also contain a stream authorization token string as well. It is odd that hdhomerun addon works fine as I believe the tuner works usimg .strm files?
Theater: The PS4/XBONE killer running Kodi 17.3 3D Movie Box: Raspberry Pi running LibreElec 8.0 Alpha BROKEN Family Room: "A6-Pack" running Kodi 17.3 Whole House: FireTV running Kodi 17.3
Something interesting here. I try to play an m3u8 file in an addon and it fails in 0416. Try it in a strm file and it fails. But if I send the link to kodi using yatse on android, it works wonderfully.
Theater: The PS4/XBONE killer running Kodi 17.3 3D Movie Box: Raspberry Pi running LibreElec 8.0 Alpha BROKEN Family Room: "A6-Pack" running Kodi 17.3 Whole House: FireTV running Kodi 17.3
Update Kodi 15.2 to v17

Kodi boot to this screen http://www.stefan-blume.com/Foto.jpg and then reboot.

If i do something wrong with the update ?
same here
And here too.
Could not be a Problem of the update himself because my RaspberryPi3 worked until yesterday without problems with this Image, changing the sd card and new installation also brought nothing.
There is nothing new since 4/16/2016, looks like an expiration Date Wink


PS: Ups sorry, fount the new Image with new Name "LibreELEC"
http://forum.kodi.tv/showthread.php?tid=269814
(2016-04-24, 12:27)flowi Wrote: Update Kodi 15.2 to v17

Kodi boot to this screen http://www.stefan-blume.com/Foto.jpg and then reboot.

If i do something wrong with the update ?

(2016-04-28, 21:19)Sully99 Wrote: And here too.

Can't tell without a crashlog. Probably a flakey addon or database.

(2016-04-28, 21:19)Sully99 Wrote: There is nothing new since 4/16/2016, looks like an expiration Date Wink
??

Post #2160.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Same experience here on both x86-Generic and RPi3. The 2016/04/16 build suddenly became unhappy and constantly restarts.

If you care to figure it out (seeing that you're not working on this variety anymore I wouldn't blame you for not caring) here's a crash log: http://pastebin.com/YfDTrCik

This is from after I had entirely deleted the .kodi directory and reinstalled the build from scratch. It would boot up far enough to display the OpenELEC startup wizard and then a few seconds later Kodi crashes and restarts.

I reverted the x86 box to the official beta builds because I wanted to watch TV while I ate dinner but the Pi is still running the broken setup so I can run any tests if bored enough.
(2016-04-29, 03:36)wolrah Wrote: If you care to figure it out (seeing that you're not working on this variety anymore I wouldn't blame you for not caring) here's a crash log: http://pastebin.com/YfDTrCik

Can't really tell you much other than an addon you've installed is causing the problem - it looks like it might be crashing while the addon is trying to use (or simply initialising) inputstream.smoothstream, presumably this is something you've installed as inputstream.smoothstream isn't included by default in this build (it is in the later LibreELEC builds).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2016-04-29, 05:34)Milhouse Wrote: Can't really tell you much other than an addon you've installed is causing the problem - it looks like it might be crashing while the addon is trying to use (or simply initialising) inputstream.smoothstream, presumably this is something you've installed as inputstream.smoothstream isn't included by default in this build (it is in the later LibreELEC builds).

Shouldn't deleting the entire .kodi folder have eliminated any addons? Doing that has seemingly no impact.

Completely wiping out the entirety of /storage temporarily resolved it and it was stable until I connected it to the internet. About 30 seconds after setting up WiFi it was crashing again, so it seems to me like if it's an addon then it's a bundled one which updates as soon as it sees the internet.


Here's a paste showing me wiping .kodi out entirely, then listing the files under /storage/ to show what's left in the writable area of the system, then launching Kodi and getting the same error.

http://pastebin.com/VFeAEjAZ
  • 1
  • 142
  • 143
  • 144
  • 145(current)
  • 146

Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi (Kodi 17.0)6