• 1
  • 176
  • 177
  • 178(current)
  • 179
  • 180
  • 187
v17 LibreELEC Testbuilds for x86_64 (Kodi 17.0)
New LibreELEC.tv Krypton build #1121: Generic
(Supercedes previous build)

Code:
# uname -a
Linux NUC 4.8.9 #1 SMP Mon Nov 21 22:24:16 GMT 2016 x86_64 GNU/Linux

# lsb_release
LibreELEC (Milhouse) - Version: devel-20161121222301-#1121-g9b939f5 [Build #1121]

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

Based on tip of LibreELEC.tv master (9b939f52, changelog) and tip of XBMC master (7f0bc8be, changelog) with the following modifications: Build Highlights:
  1. Fix ARCH and CPU with cmake (PR:768) - add-ons should now work
Build Details:
  1. LibreELEC.tv:
    • python : add sqlite dependency for host. (PR:963, 1 commit, 1 file changed)
    • config/version: set ADDON_VERSION to 8.1 (PR:936, 1 commit, 1 file changed)
  2. XBMC:
    • Update README.raspberrypi (PR:10969, 1 commit, 1 file changed)
    • [estuary] fix lost focus in mediasource dialog (PR:10939, 1 commit, 1 file changed)
    • [estuary] fix missing texture log error (PR:10938, 1 commit, 7 files changed)
  3. peripheral.joystick:
    • [buttonmaps/linux] Add Xbox 360 wireless controller mapping (54f8552d)
    • [buttonmaps/linux] Add button maps for 3 controllers: Xbox One, PS4 and GameCube (d09e0c60)
  4. Additional commits/pull requests/changes not yet merged upstream:
    • Added: [env] patch: fixup
    • Added: [env] PR:964: busybox: add getedid script
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-11-22, 01:22)lrusak Wrote: Ah, because we don't include the synaptics driver Wink
Why? :-)

or

Maybe there is another way to handle touchpad without synaptics?
Qui vit sans folie n'est pas si sage qu'il croit
(2016-11-22, 01:34)valdi74 Wrote:
(2016-11-22, 01:22)lrusak Wrote: Ah, because we don't include the synaptics driver Wink
Why? :-)

or

Maybe there is another way to handle touchpad without synaptics?


Why do you need a mouse at all? Kodi really is designed to be controlled with a remote or keyboard.
"PPC is too slow, your CPU has no balls to handle HD content." ~ Davilla
"Maybe it's a toaster. Who knows, but it has nothing to do with us." ~ Ned Scott
(2016-11-22, 01:36)lrusak Wrote: Why do you need a mouse at all? Kodi really is designed to be controlled with a remote or keyboard.

laptop trackpad?
(2016-11-22, 01:47)Matt Devo Wrote:
(2016-11-22, 01:36)lrusak Wrote: Why do you need a mouse at all? Kodi really is designed to be controlled with a remote or keyboard.

laptop trackpad?


Same thing Big Grin
"PPC is too slow, your CPU has no balls to handle HD content." ~ Davilla
"Maybe it's a toaster. Who knows, but it has nothing to do with us." ~ Ned Scott
(2016-11-22, 01:50)lrusak Wrote: Same thing Big Grin

then because it's easier to navigate via a trackpad than a non-backlit keyboard when watching content in bed at night?

what's the downside of including the synaptics driver?
(2016-11-22, 02:36)Matt Devo Wrote:
(2016-11-22, 01:50)lrusak Wrote: Same thing Big Grin

then because it's easier to navigate via a trackpad than a non-backlit keyboard when watching content in bed at night?

what's the downside of including the synaptics driver?

I'd argue that using a keyboard of any type in any circumstance is easier than a mouse Smile

More bloat mainly. We don't exactly target laptops.
"PPC is too slow, your CPU has no balls to handle HD content." ~ Davilla
"Maybe it's a toaster. Who knows, but it has nothing to do with us." ~ Ned Scott
I've uploaded a one-off build based on kernel 4.9.0-rc6, build #1121x: Generic

This works on my Skylake NUC, so should be safe for Intel users, however Nvidia Legacy users should not install this build as the legacy 340.xx driver isn't currently loading (waiting on an updated driver from nvidia). Non-legacy Nvidia users can give it a try as it might work - I'm not able to test this driver. No idea about AMD hardware either, but would be good to know if it works.

As a special treat this build includes the Estuary "Next Gen" skin that will be merged into Kodi master shortly. This is an updated version of the Estuary skin with many fixes and improvements.

Skin related bug/issue reports in the Estuary sub-forum, please. All other feedback, including brief supporting or critical thoughts on the new Estuary (but not bug reports!), in this thread.
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.
Cool! Will have to give this a go. As usual, great work! Smile

EDIT: #1121x works like a charm on my NUC6i5SYK. Maybe I should try the NUC6i7KYK again and see how that works on that.
AppleTV 4K, LG 65E6 OLED TV, Marantz NR1606, Harmony Elite
Thanks Milhouse 1121x works well NUC6i5SYK
I can not confirm the enthusiasm without doubt, the build # 1121x runs very well, however, compared to the build # 1121 of the system start with me with an Intel Nuc5PYYH slower, likewise needs the importing of TV stations (TVH server on the same system ) Even longer than usual (even longer)
New LibreELEC.tv Krypton build #1122: Generic
(Supercedes previous build)

Code:
# uname -a
Linux NUC 4.8.10 #1 SMP Tue Nov 22 21:04:42 GMT 2016 x86_64 GNU/Linux

# lsb_release
LibreELEC (Milhouse) - Version: devel-20161122210303-#1122-gd4d5e7f [Build #1122]

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

Based on tip of LibreELEC.tv master (d4d5e7fe, changelog) and tip of XBMC master (6120ee91, changelog) with the following modifications: Build Highlights:
  1. New 4.8.10 kernel
  2. cmake fixes
Build Details:
  1. LibreELEC.tv:
    • udpxy: fix build after gcc changes (PR:970, 1 commit, 1 file changed)
    • libopenmpt: update to 0.2.7386-beta20.3 (PR:972, 1 commit, 1 file changed)
    • lftp: fix build after gcc changes (PR:969, 1 commit, 1 file changed)
    • steamcontroller: mute python compileall.py output (PR:971, 1 commit, 1 file changed)
    • libopenmtp: fix typo (PR:973, 1 commit, 1 file changed)
  2. XBMC:
    • [cmake] Properly find correct libcec version (PR:10960, 1 commit, 1 file changed)
    • AESinkOSS: Fix compilation after STREAM_TYPE transition (PR:10670, 1 commit, 1 file changed)
    • GUIWindowSlideShow: Protect against empty slides access (PR:10971, 1 commit, 1 file changed)
    • remove unused control id definitions (PR:10936, 1 commit, 4 files changed)
    • [cmake] allow RPi to build with lirc support (#10962) (30f6f3b7)
  3. pvr.vbox:
    • Fixed previous coverity issues (#162) (e4183831)
  4. Additional commits/pull requests/changes not yet merged upstream:
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.
I'll be switching to the Estuary "Next Gen" skin in regular builds starting with build #1123. I'll be using the latest bleeding edge version of the skin, direct from the lead developers personal repository, which should ensure bug fixes (and hopefully to a lesser extent, bugs) will be seen first in these 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-11-23, 05:03)Milhouse Wrote: I'll be switching to the Estuary "Next Gen" skin in regular builds starting with build #1123. I'll be using the latest bleeding edge version of the skin, direct from the lead developers personal repository, which should ensure bug fixes (and hopefully to a lesser extent, bugs) will be seen first in these builds.


That's disappointing, the "next gen" skin is a step backwards in my little opinion. But it may get better
(2016-11-23, 08:51)atoulmin Wrote:
(2016-11-23, 05:03)Milhouse Wrote: I'll be switching to the Estuary "Next Gen" skin in regular builds starting with build #1123. I'll be using the latest bleeding edge version of the skin, direct from the lead developers personal repository, which should ensure bug fixes (and hopefully to a lesser extent, bugs) will be seen first in these builds.


That's disappointing, the "next gen" skin is a step backwards in my little opinion. But it may get better
Why not point out what bothers you and it might make a difference? I personally work with complex systems daily and appreciate any constructive feedback because there's always a chance that I can do something about it Smile
  • 1
  • 176
  • 177
  • 178(current)
  • 179
  • 180
  • 187

Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for x86_64 (Kodi 17.0)11