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-26, 18:22)Gaylord Culbreth Wrote: [ -> ]There seems to be no way to change Estuary background to custom wallpaper...

Anyone? ....?
(2016-11-26, 12:25)marty29ak Wrote: [ -> ]
Quote:Same here. 3 crashes last 3 hours on #1124
All is stock, no overclock. CPU temp reached 75 degrees C for the first time since i have the RPi3 on idle.

Now updated to #1125

The problem is also in the version # 1125 yet.
Have three RPI 3 all have the same problem.

Image
Today I had the same crash on my pi 2 during watching livetv mpeg2 with advanced deinterlacing.
(2016-11-26, 18:55)doldi Wrote: [ -> ]ok, bill orange - mine is not so big lol...

but i have to testing in that case 2 RPi's (2/3) with identical 2,5 Amp powersupplies.
Do you know somthing about eBääh devices - hmm, i don't know.
2 pices from Rpi i have but in waste for sometimes...hour over hour i'm searching and searching...you know?
This Rpi was bought as new from RS-online here in germany....from Angelika lol

I think your 6 degree C lower temperature than mine can be attributed to your large heat sink. It is 5 or 6 times larger than mine and probably is coupled to the CPU better. It should not be necessary to run a heat sink on a PI3. Since the CPU speed appears unchanged, maybe something is going on with the new kernel.

I quickly Googled Raspberry Pi Overheating. I got a whole bunch of hits on posts within the last 7 days or so. Suspicious. I am running a weather station on a PI3. The CPU load is very low, It is 45 - 50 degrees C. To me it looks like the problem relates to load. Perhaps the new Kernel build is more "efficient".
@bill_orange
... but you have seen, that my max temp was also near 70°C on searching/new build the libary?

Al my Pis have so much big heat sinks, since RPi 1. I don't like high temps on cpu/gpu on principle - i think it's better with a good passiv cooling - my RPi2 is also so equipped.

And yes - sometimes i overclock ;-)

Good luck on fault analysis....sorry for no better idea/solution
(2016-11-26, 21:57)Gaylord Culbreth Wrote: [ -> ]
(2016-11-26, 18:22)Gaylord Culbreth Wrote: [ -> ]There seems to be no way to change Estuary background to custom wallpaper...

Anyone? ....?
Not currently possible.
(2016-11-26, 23:27)Milhouse Wrote: [ -> ]
(2016-11-26, 21:57)Gaylord Culbreth Wrote: [ -> ]
(2016-11-26, 18:22)Gaylord Culbreth Wrote: [ -> ]There seems to be no way to change Estuary background to custom wallpaper...

Anyone? ....?
Not currently possible.

Planned for future?

...If not last version where background change posssible.

Thanks!
(2016-11-26, 23:39)Gaylord Culbreth Wrote: [ -> ]Planned for future?

...If not last version where background change posssible.

Thanks!

Not sure, try asking in the Estuary forum.
New LibreELEC.tv Krypton build #1126: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.8.10 #1 Sat Nov 26 21:07:56 GMT 2016 armv6l GNU/Linux

# vcgencmd version
Nov 26 2016 13:28:47
Copyright (c) 2012 Broadcom
version 6f567a4db96231f764d5a9a5b11b153009d13d5b (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20161126210614-#1126-g1a9b633 [Build #1126]

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

Based on tip of LibreELEC.tv master (1a9b6336, changelog) and tip of XBMC master (3067efc4, changelog) with the following modifications: Build Highlights:
  1. New firmware with extra 16MB disabled by default (enable with total_mem=1024 in config.txt)
  2. VideoPlayer: change time parameter of SeekTime from int to double
  3. ffmpeg: update to 3.1.5-Krypton-Beta6
Build Details:
  1. Firmware (Nov 26):
    • bootcode: Allow top 16M to be enabled with total_mem=1024
    • next: Update to latest master branch
    • bootcode: revert: Enable use of top 16M on Pi2/Pi3. See: link
  2. LibreELEC.tv:
    • docker: update to 1.12.3 (PR:981, 1 commit, 4 files changed)
    • system-tools: add nmon (PR:979, 2 commits, 3 files changed)
    • script.config.vdr: update to 100 (PR:986, 1 commit, 4 files changed)
  3. XBMC:
    • [PVR]Small fixes and optimizations (PR:10986, 2 commits, 6 files changed)
    • VideoPlayer: change time parameter of SeekTime from int to double (PR:10985, 3 commits, 29 files changed)
  4. kodi-theme-Estuary:
  5. inputstream.mpd:
  6. inputstream.rtmp:
    • adapt to api change - DemuxSeekTime (816635c7)
    • bump version to 1.0.3 (55437ac7)
  7. inputstream.smoothstream:
    • inputstream api version bump to 1.0.6 (b15e6e60)
  8. pvr.argustv:
  9. pvr.demo:
  10. pvr.dvblink:
  11. pvr.dvbviewer:
  12. pvr.filmon:
  13. pvr.hdhomerun:
  14. pvr.hts:
  15. pvr.iptvsimple:
  16. pvr.mediaportal.tvserver:
  17. pvr.mythtv:
  18. pvr.nextpvr:
  19. pvr.njoy:
  20. pvr.pctv:
  21. pvr.stalker:
  22. pvr.vbox:
  23. pvr.vdr.vnsi:
  24. pvr.vuplus:
  25. pvr.wmc:
  26. newclock5:
    • New commits in this build:
      • fixup! ffmpeg: Revert: matroska_read_seek Fix used streams for subtitles index compensation (19f48ff9)
      • DemuxMVC: fixup after SeekTime API change (d61b1b72)
  27. kernel 4.8.y:
    • New commits in this build:
      • ARM: dts: Restore dtbs_install functionality (f0a9a6ff)
  28. Additional commits/pull requests/changes not yet merged upstream:
    • Added: [env] patch: ffmpeg: update to 3.1.5-Krypton-Beta6
    • Added: [env] patch: Generic: enable USB_MON=m
    • Added: [env] patch: merged upstream
After the problem with Bluetooth in last night's build, it will be necessary to re-enable Bluetooth in LE Settings > Services > Bluetooth once you have booted into #1126.
(2016-11-26, 13:11)doldi Wrote: [ -> ]hi milhouse, next problem:
settings/Skin/config ->Thema : chance curial or flat - RPi will rebot after shown a grey baar instead mouse-
arrow...
RPI make a reboot without chancing anything of settings and i have no mouse.

Yes, testing with #1126 (RPi3, total_mem not set, ie. top 16MB not in use) I have been able to reproduce a crash (although not reliably): crashlog

I also experienced a (so far one-off) crash when enabling mouse support: crashlog

After trying to enable mouse support (which crashed kodi), I was able to successfully enable mouse support once kodi had restarted. I then changed Estuary Skin Theme to curial using the mouse, and Kodi crashed again. Both crashlogs above.

I managed to capture a debug-enabled crash (with a build similar to #1126) after repeatedly changing Theme using the mouse: crashlog and crashlog

I've also seen a corrupted mouse pointer (which may be the cause of the crashes?) so something is definitely a bit flaky with mouse support.

I've tested mouse support and Theme changing on #1126 on a Skylake NUC and haven't seen any problems so it appears to be RPi specific for now.
On #1126 with a fresh install I'm not able to install VDR addon. There is a compatibility issue.
An upgraded system which has VDR installed doesn't have this problem when updating the VDR addon
hi milhouse and popcornmix

a little something i have noticed:
builds after # #1119 (last good) have passtrough problems for me.

I connected my RPi over HDMI to a splitter and connect them via optical spdif to 6.1 Yamaha-Receiver.

If i watch dvd's with multichannel sound there is always silence on start - i have to reset my HDMI Switch to get sound a with builds #1120 and higher.

btw. also i miss the "next chapter button" over progress bar (We've had all that before?).

Ok, that's the reason, why i had edit some posts from me in the last days - but now i'm 100% sure - have tested and compared with builds above #1119 on this cloudy/rainy day here in germany ;-)

think a log is not usefull, don't see anything serviceables....

for interest: on sattelit tv ist there also dd5.1 sound (like here germany over astra) with your builds possible?
I am not sure that this has been discussed, but the interface seems to be sluggish when switching out of videos. It takes a few seconds to load the thumbnails interface (it used to be immediate in openelec). I am using a raspberry pi 3 so hardware speed shouldn't be an issue.

Does anybody else notice that?
(2016-11-26, 21:08)popcornmix Wrote: [ -> ]I've still not seen this issue.
I was hoping that leaving it in place a few days might result in some information to help reproduce the issue.
But, as we don't seem to be getting there I've reverted the change.

You can manually enable the extra 16M with total_mem=1024 in config.txt if you weren't having issues.

Didnt have a crash with anyting below 1024, it's running stable on #1126 and total_mem=1023.

arm: frequency(45)=1000104000
core: frequency(1)=499999000
h264: frequency(28)=499999000
isp: frequency(42)=500000000
v3d: frequency(43)=0
uart: frequency(22)=47999000
pwm: frequency(25)=0
emmc: frequency(47)=250000000
pixel: frequency(29)=74177000
vec: frequency(10)=0
hdmi: frequency(9)=163683000
dpi: frequency(4)=0
core: volt=1.3625V
sdram_c: volt=1.2500V
sdram_i: volt=1.2500V
sdram_p: volt=1.2500V
arm=703M

on total_mem=1024, it crashed two times in ~3hrs...
(2016-11-27, 23:03)hanspeter Wrote: [ -> ]Didnt have a crash with anyting below 1024, it's running stable on #1126 and total_mem=1023.

That may be interesting. It may suggest the arm is accessing memory in 1008M-1009M range
which would fail when total_mem=1024, but would be okay with total_mem=1023 (1007M-1008M is okay)
which does narrow the possibilities down a little.

Anyone else experiencing the crashing, I'd be interested if total_mem=1023 is also good for you.