NOTE! This site uses cookies and similar technologies.

If you not change browser settings, you agree to it.

I understand

WETEK Play

[Release] OpenELEC 6.0.1

The OpenELEC 6.0.1 release has been published. Users running OpenELEC 5.95.1 thru 6.0.0 with auto-update enabled will be prompted on-screen to reboot and apply the update once it has been downloaded. Users running older OpenELEC releases or with auto-update disabled will need to manually update. If you would like to update from an older OpenELEC release please read update instructions/advice on the wiki before updating. Manual update files can be obtained from the downloads page.

OpenELEC 6.0.1 is a maintenance release so there are no new features. The main fixes are:

  • libCEC has been bumped to 3.0.1 to solve some outstanding issues for RPi/RPi2 users.
  • Firmware to support the Cubox-i4pro Bluetooth chipset has been added.
  • SSL issues seen with some HTTPS streams are resolved with an update to embedded CA certificates.
  • Firmware for Intel wifi devices has been updated to resolve (or at least improve) some networking issues.
  • Kodi Isengard DVB add-ons have been updated and pushed to the official repo.
  • Boot partition size for new installations has been increased to 512MB.

To view a complete list of GitHub changes since 6.0.0 click here: https://github.com/OpenELEC/OpenELEC.tv/compare/6.0.0...openelec-6.0

Official add-ons (e.g. VDR and its many sub-components) and Unofficial add-ons have also received some attentions. The repos were needing some TLC but now contain current (or newer) versions of most add-ons.


Posted: 5 hours 55 minutes ago by jorara #157576
jorara's Avatar
jorara wrote:
cityblue2001 wrote:
jorara wrote:
I have just upgraded my Intel NUC DC3217IYE to OpenELEC 6.0.1, but I have a problem with WiFi on the NUC.

Upgrade from what version? 5.x or 6.0.0?

It's probably issue #4333, the problem is known and a solution is being worked on.

It sounds a LOT like issue #4333. I'm having the problem both after an upgrade from 5.0.8 and after a fresh install of 6.0.1.

I just tried following this guide to add entropy at boot and it worked like a charm. Now my wifi is enabled at startup every time. Thanks for the hint cityblue2001 :cheer:
Posted: 20 hours 9 minutes ago by jorara #157545
jorara's Avatar
cityblue2001 wrote:
jorara wrote:
I have just upgraded my Intel NUC DC3217IYE to OpenELEC 6.0.1, but I have a problem with WiFi on the NUC.

Upgrade from what version? 5.x or 6.0.0?

It's probably issue #4333, the problem is known and a solution is being worked on.

It sounds a LOT like issue #4333. I'm having the problem both after an upgrade from 5.0.8 and after a fresh install of 6.0.1.
Posted: 23 hours 30 minutes ago by cityblue2001 #157534
cityblue2001's Avatar
jorara wrote:
I have just upgraded my Intel NUC DC3217IYE to OpenELEC 6.0.1, but I have a problem with WiFi on the NUC.

Upgrade from what version? 5.x or 6.0.0?

It's probably issue #4333, the problem is known and a solution is being worked on.
Posted: 23 hours 33 minutes ago by jorara #157533
jorara's Avatar
I have just upgraded my Intel NUC DC3217IYE to OpenELEC 6.0.1, but I have a problem with WiFi on the NUC.

I can enable WiFi and it works fine, but after a reboot WiFi is disabled. Can anybody tell me why OpenELEC doesn't remember that WiFi should be enabled by default?

I can see that settings are updated in /storage/.cache/connman/settings, but it doesn't get any further than the cache file.

I have tried reinstalling from scratch, but as soon as I activate mounting (via autostart.sh or *.mount files) of any nfs share on my server, WiFi is not enabled automatically.

I have tried enabling debugging. The result can be seen in the attached kodi.log. There are some errors but I can't determine if they are related to my wifi issues.

Regards,
Jørgen
Posted: 1 day 8 hours ago by mhoogenbosch #157499
mhoogenbosch's Avatar
michael.afonso wrote:
Version 6.01 no DTS in LG TV!! Version 5.0.8 Works fine.. with passthrough active.. Please fix it..
i'd suggest to stay at 5.0.8 .. DTS to TV speakers...
Posted: 1 day 16 hours ago by nickr #157492
nickr's Avatar
michael.afonso wrote:
Version 6.01 no DTS in LG TV!! Version 5.0.8 Works fine.. with passthrough active.. Please fix it..

Posts like this very rapidly become tiring. Your "please fix it" attitude is demanding when you have no right to demand anything.

You provide no debug log, no details of your hardware (beyond a "LG" tv - no model number)
Posted: 1 day 16 hours ago by michael.afonso #157491
michael.afonso's Avatar
Version 6.01 no DTS in LG TV!! Version 5.0.8 Works fine.. with passthrough active.. Please fix it..
Posted: 2 days 2 hours ago by macgyom #157465
macgyom's Avatar
I had to be able to use my rpi. I will install another sdcard with 6.0.1 to log default for you
Posted: 2 days 5 hours ago by klojum #157444
klojum's Avatar
macgyom wrote:
I have update from 6.0.0 to 6.0.1 on a RPI B+.

It bumped into a reboot, and turned my Rpi to unusable

I tried to do a clean & fresh install :
Format my SD card (SanDisk 8Go Class 10) with SDformatter
Copy Openelec 6.0.1 img file to SD card with Win32 imagedisk
boot into my Rpi and reboot in random again.

Doing a downgrade to 6.0.0 solce this Pb !

Have somebody the same problem ? and a solution ? in a future update ?

You already wiped off the 6.0.1 image before we could even try one single test. How are we to deduce the problem from that? Sorry, but performing magic tricks is not our second hobby.
Posted: 2 days 6 hours ago by macgyom #157440
macgyom's Avatar
chewitt wrote:

The OpenELEC 6.0.1 release has been published. Users running OpenELEC 5.95.1 thru 6.0.0 with auto-update enabled will be prompted on-screen to reboot and apply the update once it has been downloaded. Users running older OpenELEC releases or with auto-update disabled will need to manually update. If you would like to update from an older OpenELEC release please read update instructions/advice on the wiki before updating. Manual update files can be obtained from the downloads page.

OpenELEC 6.0.1 is a maintenance release so there are no new features. The main fixes are:

  • libCEC has been bumped to 3.0.1 to solve some outstanding issues for RPi/RPi2 users.
  • Firmware to support the Cubox-i4pro Bluetooth chipset has been added.
  • SSL issues seen with some HTTPS streams are resolved with an update to embedded CA certificates.
  • Firmware for Intel wifi devices has been updated to resolve (or at least improve) some networking issues.
  • Kodi Isengard DVB add-ons have been updated and pushed to the official repo.
  • Boot partition size for new installations has been increased to 512MB.

To view a complete list of GitHub changes since 6.0.0 click here: https://github.com/OpenELEC/OpenELEC.tv/compare/6.0.0...openelec-6.0

Official add-ons (e.g. VDR and its many sub-components) and Unofficial add-ons have also received some attentions. The repos were needing some TLC but now contain current (or newer) versions of most add-ons.

Read more...

I have update from 6.0.0 to 6.0.1 on a RPI B+.

It bumped into a reboot, and turned my Rpi to unusable

I tried to do a clean & fresh install :
Format my SD card (SanDisk 8Go Class 10) with SDformatter
Copy Openelec 6.0.1 img file to SD card with Win32 imagedisk
boot into my Rpi and reboot in random again.

Doing a downgrade to 6.0.0 solce this Pb !

Have somebody the same problem ? and a solution ? in a future update ?
Posted: 4 days 6 hours ago by powerarmour #157324
powerarmour's Avatar
Hopefully the installer is fixed on the next release, so I wouldn't worry about trying to expand the boot partition right now.
Posted: 4 days 6 hours ago by cityblue2001 #157319
cityblue2001's Avatar
soyxan wrote:
Hi,

I have updated from 6.0.0 on my RPi2, do I need to partition again my SD in order to increase its size, or is it increased automatically during the update?

Thanks!

You don't _need_ to partition again, however with the smaller partition you currently have you may find that a future upgrade fails due to insufficient space. The increased partition size in 6.0.1 is a precautionary change to avoid problems in the future - if you don't take advantage of it now then expect problems in the future.
Posted: 4 days 7 hours ago by soyxan #157318
soyxan's Avatar
Hi,

I have updated from 6.0.0 on my RPi2, do I need to partition again my SD in order to increase its size, or is it increased automatically during the update?

Thanks!
Posted: 5 days 4 hours ago by JimmySmith #157256
JimmySmith's Avatar
Thank you for the update! libCEC was quite critical for me, now I can confirm 6.0.1 working fine and update went without problems
Posted: 1 week 4 hours ago by Falcon83 #157155
Falcon83's Avatar
Is the xVDR plugin available again in the new release?
Posted: 1 week 7 hours ago by Roi #157139
Roi's Avatar
Hello to all,

I sucessfully updates to 6.0.1 from 6.0. But I'm experiencing problems which I also had with 6.0.

Sometimes Kodi (not the OS itself) is restarting just after it has loaded. I see the start logo again, then Kodi is loaded again.

Sometimes the Kodi frontend freezes - but the OS is working (I can login via SSH and reboot the box).

The biggest problems I'm experiencing are the ones with the VDR VNSI addon. Sometimes it load properly, sometimes not. If not, the problems can either be: the channel list is not fully loaded and stuck somewhere, caching the stream stays at 0% and nothing else is happening anymore. In both cases the Kodi frontend also (like mentioned above) freezes and I need to reboot the box via SSH.

Maybe someone can give me a hint where to look for information in log files. I would glad to help, also to get rid of the problems. Maybe I just need to adjust some settings?

Thanks a lot and cheers,
Roi
Posted: 1 week 9 hours ago by freakshow999 #157134
freakshow999's Avatar
So my Nuc that has been running flawlessly updated to 6.0.1 automatically and now UI sounds are terribly low.
I have to turn my receiver up to nearly full volume to hear any of them at all. Audio on video files seems to been uneffected. It's just the UI sounds but fairly annoying none the less...This is passthrough all audio codecs over HDMI.
Any ideas?
Posted: 1 week 12 hours ago by klojum #157127
klojum's Avatar
Gparted can be fast enough as long as the target device is fast. It's not Gparted's fault that some SD cards are slow at their writing speeds.
Posted: 1 week 16 hours ago by powerarmour #157116
powerarmour's Avatar
klojum wrote:
I'm sure it's not the most romantic thing to do, having to resize partitions on existing OpenELEC machines with Gparted, but it won't take you weeks to do so. It will also still be a lot quicker than the alternative.

Gparted is not exactly fast at partition resizing, and I think it defaults to converted FAT16 partitions to FAT32 also, which breaks EFI on x86 hardware.
Posted: 1 week 1 day ago by klojum #157057
klojum's Avatar
onizuka wrote:
Don't want to be a pain, but is it possible someone could rebuild the installer to format to the new partition size? I know that there is a gparted work around...it's just that it can be cumbersome compared to a clean install. Especially when you have to upgrade many instances. (My parents have 4 OE Chromeboxes alone :S )
I'm sure it's not the most romantic thing to do, having to resize partitions on existing OpenELEC machines with Gparted, but it won't take you weeks to do so. It will also still be a lot quicker than the alternative.

The installer will be adjusted to the new system partition size, so we wont bump into system size problems for anytime soon. But of course, that only applies to fresh installations.
Posted: 1 week 1 day ago by cityblue2001 #157056
cityblue2001's Avatar
@matth: I've just run a test using the following script (which is basically just a proof of concept - use at your own risk etc.):
#!/bin/bash
set -e

BIN=$(readlink -f $(dirname $0))

# Set DISK to the SD card device eg. /dev/sdb, /dev/sdc etc. - check dmesg for details
DISK="/dev/sde"

# Directory of untarred files
IMAGE=${BIN}/oe-files

# Mount point for SD card
MOUNT=/media/openelec/System

# Now create the partitions on $DISK:
umount ${DISK}* 2>/dev/null || true

parted -s "$DISK" mklabel msdos
parted -s "$DISK" mkpart primary fat32 -- 1MiB 512MiB
parted -s "$DISK" mkpart primary ext2 -- 516MiB -2cyl
parted -s "$DISK" set 1 boot on

partprobe "$DISK"
while [ : ]; do [ -b ${DISK}1 ] && break || sleep 0.25; done
sleep 1

mkfs.vfat "${DISK}1" -I -n System
mkfs.ext4 -F -O ^has_journal -E stride=2,stripe-width=1024 -b 4096 "${DISK}2" -L Storage

mkdir -p ${MOUNT}
mount ${DISK}1 ${MOUNT}

cp -r --preserve=timestamps ${IMAGE}/target/SYSTEM ${MOUNT}
cp -r --preserve=timestamps ${IMAGE}/target/KERNEL ${MOUNT}/kernel.img
cp -r --preserve=timestamps ${IMAGE}/3rdparty/bootloader/* ${MOUNT}

sync
umount ${MOUNT}
rm -fr ${MOUNT}

It assumes two things:

1. The SD card is /dev/sde - change this for your system. No liability accepted if this wipes your system disk
2. Before running the script, untar the contents of OpenELEC-RPi2.arm-6.0.1.tar (or whatever the latest OpenELEC RPi* release is) and rename the untarred contents "oe-files"

Let's compare the two methods, using an 8GB NOOBS SD card (in a USB3 SD adapter in an x86 PC running Ubuntu):

First, the scripted method, creating optimally sized partitions - irrespective of SD card size - with no further resizing required by the end-user:
$ time sudo ./create_sdcard.sh
mkfs.fat 3.0.28 (2015-05-16)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
mke2fs 1.42.12 (29-Aug-2014)
/dev/sde2 contains a ext4 file system labelled 'Storage'
        created on Fri Feb  5 06:02:49 2016
Creating filesystem with 1804288 4k blocks and 451584 inodes
Filesystem UUID: 5731c1d0-687d-4456-8424-04ad3133b245
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

real    0m13.502s
user    0m0.012s
sys     0m0.244s

And second, writing the 570MB disk image, which then requires the expansion of the second partition by the user:
$ time sudo dd if=OpenELEC-RPi2.arm-6.0.1.img of=/dev/sde bs=1M
548+0 records in
548+0 records out
574619648 bytes (575 MB) copied, 53.1009 s, 10.8 MB/s

real    0m53.109s
user    0m0.004s
sys     0m0.516s

13.5 seconds vs. 53.1 seconds. You could even use Raspberry Pis as your duplication devices - the time difference between the two methods will be greater still as writing images will be even slower.

If you create SD cards in bulk there's your solution - not using the disk image, and certainly not moving/resizing the partitions. Plus, as a bonus, your customers/end-users have an improved first-run user experience.
Posted: 1 week 1 day ago by onizuka #157052
onizuka's Avatar
Yes, it's 100% automatic when run from the installer from USB. Here's to hoping someone updates the installer to create the new partition size for us non-tech savvy folks!
Posted: 1 week 1 day ago by chewitt #157049
chewitt's Avatar
There are three reasons for the increase:

#1. Debug builds are almost double the size of a normal build and don't fit in the current 256MB partition space. It's not a common requirement to run debug builds but as we become more refined as a distro the easy bugs have been fixed and there's a greater chance investigations need proper tools. Debug builds need to be used in-situ without the user having to clean-reinstall so we need a larger partition.

#2. Retroplayer changes are on the horizon for Kodi 17.0 (maybe earlier with some beta builds) and the additional code and dependencies make a noticeable bump to the standard SYSTEM file size. Debug versions weigh in around 330MB.

#3. Over time we moved from 160MB to 200MB to 250MB and each time we reach a boundary we inconvenience another generation of OE users with a reinstall and there are now ~485k users (350k+ booting from SD cards) so instead of making another little step we elected to make an arbitrary large leap that we are confident avoids the need for further little steps. The average min size required by most Linux distro installers is 512MB so that was the value chosen. Of course Bill Gates once said "640k should be enough for everyone" and we all know how that turned out, but hand on heart I don't see another boot partition increase for the foreseeable future.

So to apologise; pi vendors writing cards were honestly not considered (nobody on staff raised the issue) when this was debated. The enlarged space has no impact on the "compressed size" we care about for downloads/bandwidth but the image must be expanded before writing if you want a bootable card and if you're shipping 10k SD cards a month (as some are) this extrapolates to an additional 1-2 working days/month of card writing. Somewhere in the logistical chain time always translates to money so we're sorry about the extra work, but we made the bump because we needed to.

NB: In future it would be good to have more contact with some of the vendors in this space (some are known to us, most are not) so feel free to drop me an email (chewitt@oedomain) so we better understand your business(es) and what you need from us as a distro.
Posted: 1 week 1 day ago by cityblue2001 #157046
cityblue2001's Avatar
matth wrote:
Just the boot partition full of empty space grew.

And a size increase of 400% is not "a bit".

Increasing the FAT partition from 256MB (which leaves no room for future SYSTEM growth) to 512MB is not a 400% increase... as you said, it's mostly empty space, and since this compresses well it has barely any impact on the compressed image size. The uncompressed image size however has doubled to about 570MB, but this is an essential change.

If I were you I'd investigate a more optimal solution for creating your SD cards - I gave you some pointers - although I still find it hard to believe that writing an extra 256MB is so much of a problem - how much longer does it take, 20-30 seconds? Business must be brisk! ;)

An optimised SD card creation process would also mean your customers don't have to go through the filesystem expansion process, so you'd also be offering a better service.
Posted: 1 week 1 day ago by matth #157044
matth's Avatar
klojum wrote:
Yes, OpenELEC grows a bit, just like any other piece of software out there. Windows used to install from nine 1.44MB floppies for a 20-25MB install. Now a clean basic install for Win10 requires some 15 GB of diskspace. When Foxit Reader started out with a 1.5 MB installer, it ridiculed Adobe Reader for being bloated with its 35MB installer. Now, Foxit Reader's installer is 41MB in size, and Adobe Reader is up to 72MB. But, who is complaining? Look how a Fiat 500 has grown over the years. I think we're still doing okay for OpenELEC.

What is the disk size of the SD cards you are using & selling? If you are still selling 2 GB SD cards, you're not being realistic.

OpenELEC didn't grow.
Just the boot partition full of empty space grew.

And a size increase of 400% is not "a bit".
The size of the SD we are using (8GB by the way) is totally irrelevant of the image burn time which my post was about.
I wasn't complaining about the extra size, but just commenting on the longer burn time due to writing the larger boot partition's empty space.

But I see now (due to the other poster) that having to resize the boot partition and then moving the system partition is too risky to make it viable.

[Release] OpenELEC 6.0 released

The OpenELEC team is proud to announce OpenELEC 6.0 (6.0.0)

The most visible change is Kodi 15.2 (Isengard). Beginning with Kodi 15.0 most audio encoder, audio decoder, PVR and visualisation addons are no longer pre-bundled into OpenELEC but can be downloaded from the Kodi addon repo if required. PVR backends such as VDR and TVHeadend will install needed dependencies automatically. For further information on Kodi 15.1 please read http://kodi.tv/kodi-15-2-isengard-final-release/.

We now officially support WeTek's WeTek_Play device with a build that installs to internal NAND and dual-boots with Android on an SD Card. The iMX6 build extends support to all Solidrun CuBox-i/TV, Solidrun Hummingboard devices and the OSMC Vero. We recommend CuBox-i2eX / Hummingboard-i2eX or better devices.

Read more ...


Posted: 1 week 2 days ago by romdogg #156999
romdogg's Avatar
Hi, sorry. I dont know any legit adds and repos for opeenlec xbmc. Can you share some? Also, regarding to my old post, what if i use a wifi range extender? Will it improve the connectivity of my apple tv1? Thanks. Sorry to be a pain. Please reply.
Posted: 2 weeks 2 hours ago by chewitt #156581
Posted: 2 weeks 3 hours ago by Rico_s #156573
Rico_s's Avatar
Hey.

Anyone know whats new/fixed in 6.0.1?

Regards
Posted: 2 weeks 5 hours ago by HiassofT #156570
HiassofT's Avatar
panusha wrote:
Or could someone please explain me how to update the firmware manually?
Download boot/start_x.elf and boot/fixup_x.dat from the RPi firmware Github repository and replace start.elf and fixup.dat on your boot partition with these files (rename them first to get rid of the "_x" in the filenames).

You can do this while OpenELEC is running (don't forget to remount your boot partition read/write before) or simply on another PC - the boot partition is FAT, so no problem to do that on a Windows PC or MAC.

so long,

Hias
Posted: 2 weeks 6 hours ago by Oral-B #156568
Oral-B's Avatar
Mmh, no sign of a 6.0.1 upgrade here... :huh:
Posted: 2 weeks 8 hours ago by mhoogenbosch #156562
mhoogenbosch's Avatar
Both my nuc and pi2 got a notifiy message saying 6.0.1 had arrived. I installed it on both of them and everything still works :)

Is there going to be a new thread for this release, or are you going to pass on this?
Posted: 2 weeks 22 hours ago by klojum #156536
klojum's Avatar
panusha wrote:
Could you please urgently update the firmware so that I get it as an automatic update for OpenELEC?
Wow... And what do we get in return for that "please urgently update"? A small number of developers/volunteers have just been working their a..es off on the latest OpenELEC builds, in their own limited free/spare time, mind you. Although I can understand the frustration as well as the eagerness to have a working setup, there are some 499,999 other users of which some also have their wishes and complaints. So why not put your request onto the OpenELEC bug/feature tracker, and it will be taken into consideration. See github.com/OpenELEC/OpenELEC.tv/blob/master/CONTRIBUTING.md .

panusha wrote:
AFAIK, "rpi-update firmware" doesn't work on OpenELEC.
You know correctly, OpenELEC has no package manager whatsoever. But you could also start compiling your own OpenELEC builds with whatever firmware updates you need. See wiki.openelec.tv/index.php/Compile_from_source .
Posted: 2 weeks 1 day ago by panusha #156500
panusha's Avatar
Hi,

I encounter a bug when watching IPTV (h264) on Raspberry Pi 2. It's described here github.com/raspberrypi/firmware/issues/499 and has been fixed around two weeks ago. I'm on 6.0.1 and it seems as if the necessary firmware update has not been included in the 6.0.1 update for Raspberry Pi 2.

Could you please urgently update the firmware so that I get it as an automatic update for OpenELEC? Or could someone please explain me how to update the firmware manually? AFAIK "rpi-update firmware" doesn't work on OpenELEC.


Thank you very much.
Posted: 3 weeks 2 days ago by luizmpbah #155995
luizmpbah's Avatar
why did not I think of that ?

I ill try when I go home.
Posted: 3 weeks 2 days ago by klojum #155992
klojum's Avatar
You could try and change your DNS servers.
Use Google's DNS servers: 8.8.8.8 and 8.8.4.4

If your provider is really blocking Kodi/OE urls, I would like to know their explanation.
Posted: 3 weeks 2 days ago by luizmpbah #155989
luizmpbah's Avatar
I Found the problem, But still dont Know How to solve it.

After all the tests, and still getting the same problem, My Wife Asks me to try do conect to the 3g access point of her Iphone, as I got a USB wifi card a try to do it, and updates started as well, same happened with the repositories that I could'nt get in.

reset my router and tryed to connect to it, and got the problem again,

Result, something in my internet provider is blocking the urls of the repositories, I am at Work now and the links are Working good here.
Next steps, contact the internet provider?
is There another ways?

Thanks for all Replys, you ara amazing, thats wy i Love Open Source.
Posted: 3 weeks 3 days ago by klojum #155952
Posted: 3 weeks 3 days ago by luizmpbah #155946
luizmpbah's Avatar
nickr wrote:
Looks like a temporary failure to get the addons list, viz:
14:32:10 T:139717014185728 ERROR: CCurlFile::Open failed with code 0 for addons.openelec.tv/6.0/Generic/x86_64/addons.xml

That file is certainly reachable for me from a browser right now, I suggest you try again.

The internet doesn't always work!

This is What I got If I click On What Link: from my Browser:
Forbidden

You don't have permission to access /6.0/Generic/x86_64/addons.xml on this server.
Posted: 3 weeks 3 days ago by nickr #155937
nickr's Avatar
Looks like a temporary failure to get the addons list, viz:
14:32:10 T:139717014185728 ERROR: CCurlFile::Open failed with code 0 for addons.openelec.tv/6.0/Generic/x86_64/addons.xml

That file is certainly reachable for me from a browser right now, I suggest you try again.

The internet doesn't always work!
Posted: 3 weeks 3 days ago by luizmpbah #155936
luizmpbah's Avatar
luizmpbah wrote:
And Now?

Klojum, thanks for the help.
<script src="//pastebin.com/embed_js/udkFaqmg"></script>
<iframe src="//pastebin.com/embed_iframe/udkFaqmg" style="border:none;width:100%"></iframe>

pastebin.com/udkFaqmg

Thanks for All Replys, and for the Pacience!

A used openelec 5 for 1 year, and 2 days ago I decided to upgrade, so I Did a fresh instal, and wen I start the configuration, de repositories Did'int work, try reinstal 3 times, download again and made a new Boot flash-drive, download and instal the Openelec 5 again, and try de same configuration that wolks perfectly for 1 year, but sitll with same problem.
In the Openelec 6 I click on the repo (oficial or unoficial) and nothing rappers. And the updates return a message of fail.
On Openelec 5, a clic on de repos and a get incide than but if a try to instal something, the instalation fail.

Somebody help Me??
Posted: 3 weeks 4 days ago by chewitt #155922
chewitt's Avatar
There has been an outbreak of stevejobsitis among the developers resulting in a few "just one more thing" commits. Nearly there :)
Posted: 3 weeks 4 days ago by Corwyn #155919
Corwyn's Avatar
gaelic wrote:
thibault wrote:
chewitt wrote:
The 6.0.1 release is currently in private testing and fingers-crossed should be out soon. Once shipped team focus moves to 7.0 beta. This should not be a huge task as there's been lots of activity in the master branch recently. If anything 6.0.1 is going slow due to the amount of concurrent 7.0 activity. Another reason is that we've been using milhouse builds with a "manageable audience" to shift testing of larger and/or more experimental changes away from the "big audience" that a public beta attracts. Moving that kind of testing to an earlier point in the development cycle should (again, fingers crossed) result in fewer gotchas during beta and a shorter beta period.

Many thanks for this update on 6.0.1 from the dev team!

Is it already here?

:huh: "head meet desk"
Posted: 3 weeks 4 days ago by klojum #155918
klojum's Avatar
Can you see it already on the OpenELEC download page? :-)
If it's not listed, it's not there yet.
Posted: 3 weeks 4 days ago by gaelic #155916
gaelic's Avatar
thibault wrote:
chewitt wrote:
The 6.0.1 release is currently in private testing and fingers-crossed should be out soon. Once shipped team focus moves to 7.0 beta. This should not be a huge task as there's been lots of activity in the master branch recently. If anything 6.0.1 is going slow due to the amount of concurrent 7.0 activity. Another reason is that we've been using milhouse builds with a "manageable audience" to shift testing of larger and/or more experimental changes away from the "big audience" that a public beta attracts. Moving that kind of testing to an earlier point in the development cycle should (again, fingers crossed) result in fewer gotchas during beta and a shorter beta period.

Many thanks for this update on 6.0.1 from the dev team!

Is it already here?
Posted: 3 weeks 4 days ago by thibault #155907
thibault's Avatar
chewitt wrote:
The 6.0.1 release is currently in private testing and fingers-crossed should be out soon. Once shipped team focus moves to 7.0 beta. This should not be a huge task as there's been lots of activity in the master branch recently. If anything 6.0.1 is going slow due to the amount of concurrent 7.0 activity. Another reason is that we've been using milhouse builds with a "manageable audience" to shift testing of larger and/or more experimental changes away from the "big audience" that a public beta attracts. Moving that kind of testing to an earlier point in the development cycle should (again, fingers crossed) result in fewer gotchas during beta and a shorter beta period.

Many thanks for this update on 6.0.1 from the dev team!
Posted: 3 weeks 5 days ago by luizmpbah #155828
luizmpbah's Avatar
And Now?

Klojum, thanks for the help.
<script src="//pastebin.com/embed_js/udkFaqmg"></script>
<iframe src="//pastebin.com/embed_iframe/udkFaqmg" style="border:none;width:100%"></iframe>

pastebin.com/udkFaqmg

Thanks for All Replys, and for the Pacience!

A used openelec 5 for 1 year, and 2 days ago I decided to upgrade, so I Did a fresh instal, and wen I start the configuration, de repositories Did'int work, try reinstal 3 times, download again and made a new Boot flash-drive, download and instal the Openelec 5 again, and try de same configuration that wolks perfectly for 1 year, but sitll with same problem.
In the Openelec 6 I click on the repo (oficial or unoficial) and nothing rappers. And the updates return a message of fail.
On Openelec 5, a clic on de repos and a get incide than but if a try to instal something, the instalation fail.
Posted: 3 weeks 6 days ago by klojum #155812
klojum's Avatar
No...

We're trying to avoid that people are splattering their log files here all over the forum. Use pastebin website for your logs.

Also, don't cut out the part where YOU think the problem is. Most of the time, other causes start a problem before that.
Always pastebin full kodi logs on your pastebin website of choice. Not here. Post only the URL to your log here.
Posted: 3 weeks 6 days ago by luizmpbah #155810
luizmpbah's Avatar
This Way?

14:32:10 T:139717014185728 ERROR: CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
14:32:10 T:139717014185728 ERROR: CCurlFile::Open failed with code 0 for addons.openelec.tv/6.0/Generic/x86_64/addons.xml
14:32:10 T:139717014185728 ERROR: Open - failed to open source <addons.openelec.tv/6.0/Generic/x86_64/addons.xml>
14:32:10 T:139717014185728 ERROR: Failed to read directory listing addons.openelec.tv/6.0/Generic/x86_64/addons.xml for repository repository.openelec.tv.
14:32:12 T:139716418594560 NOTICE: Thread FileCache start, auto delete: false
14:32:14 T:139716418594560 NOTICE: Previous line repeats 1 times.
14:32:14 T:139716418594560 NOTICE: Thread JobWorker start, auto delete: true
14:32:16 T:139716234020608 NOTICE: Thread FileCache start, auto delete: false
14:32:17 T:139717307803392 NOTICE: Previous line repeats 1 times.
14:32:17 T:139717307803392 ERROR: CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
14:32:17 T:139717307803392 ERROR: CAddonInstallJob[metadata.album.universal]: MD5 mismatch after download special://home/addons/packages/metadata.album.universal-2.5.1.zip
14:32:17 T:139716410201856 NOTICE: Thread JobWorker start, auto delete: true
14:32:17 T:139716401809152 NOTICE: Thread FileCache start, auto delete: false
14:32:22 T:139716418594560 NOTICE: Previous line repeats 4 times.
14:32:22 T:139716418594560 ERROR: CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
14:32:22 T:139716418594560 ERROR: CAddonInstallJob[metadata.artists.universal]: MD5 mismatch after download special://home/addons/packages/metadata.artists.universal-3.6.2.zip
14:32:23 T:139716234020608 NOTICE: Thread FileCache start, auto delete: false
14:32:24 T:139717307803392 ERROR: CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
14:32:24 T:139717307803392 ERROR: CAddonInstallJob[metadata.common.allmusic.com]: MD5 mismatch after download special://home/addons/packages/metadata.common.allmusic.com-3.1.1.zip
14:32:26 T:139716410201856 ERROR: CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
14:32:27 T:139716234020608 NOTICE: Thread FileCache start, auto delete: false
14:32:27 T:139716418594560 NOTICE: Previous line repeats 1 times.
14:32:27 T:139716418594560 ERROR: CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
14:32:32 T:139716418594560 ERROR: Previous line repeats 2 times.
14:32:32 T:139716418594560 ERROR: CAddonInstallJob[metadata.common.fanart.tv]: MD5 mismatch after download special://home/addons/packages/metadata.common.fanart.tv-3.1.3.zip
14:32:33 T:139717307803392 ERROR: CCurlFile::FillBuffer - Failed: Server returned nothing (no headers, no data)(52)
14:32:33 T:1397
Posted: 3 weeks 6 days ago by klojum #155808
klojum's Avatar
Take your pick:
kodi.wiki/view/Log_file/Easy
kodi.wiki/view/Log_file/Advanced
or directly via SSH:
pastebinit ~/.kodi/temp/kodi.log
Posted: 3 weeks 6 days ago by luizmpbah #155807
luizmpbah's Avatar
I am newbee, now can I get this debug log?

[Beta] OpenELEC 6.0 Beta 5 released

The OpenELEC team is proud to announce the 5th beta of OpenELEC 6.0 (v5.95.5)

The most visible change is Kodi 15.1 (Isengard). Beginning with Kodi 15.0 most audio encoder, audio decoder, PVR and visualisation addons are no longer pre-bundled into OpenELEC but can be downloaded from the Kodi addon repo if required. PVR backends such as VDR and TVHeadend will install needed dependencies automatically. For further information on Kodi 15.1 please read http://kodi.tv/kodi-15-1-isengard-maintenance-release/.

We now officially support WeTek's WeTek_Play device with a build that installs to internal NAND and dual-boots with Android on an SD Card. The iMX6 build extends support to all Solidrun CuBox-i/TV, Solidrun Hummingboard devices and the OSMC Vero. We recommend CuBox-i2eX / Hummingboard-i2eX or better devices.

Read more ...


Posted: 3 months 1 week ago by nickr #150668
nickr's Avatar
Errrr I hope you weren't thanking me, but if you were thanking the oe dev team , then +100.

Sent from my U65GT using Tapatalk
Posted: 3 months 1 week ago by wobwob #150655
wobwob's Avatar
Awesome! Thanks for the great work.

Cheers
Posted: 3 months 1 week ago by nickr #150646
nickr's Avatar
6.0 released, see new thread.

Sent from my U65GT using Tapatalk
Posted: 3 months 1 week ago by AnDas #150562
AnDas's Avatar
blackbox wrote:
can't believe it that you are a lucky person. I got a Wetek box (openElec-edition) and i regret having it. I just hope that its stability will be given very soon. Have lots of troubles with it like permanent kodi restarts because it crashes out of nothing, Live-TV stops after a few seconds from time to time because of "EPG scan" and "channel scrambled" or similar error messages (which are not true), and even my USB hard disk stopped getting power from it. Every now and then it starts working, but stops soon too. Also the remote control is bad as it can get. I need to use the Kodi-app from my phone, otherwise i'd get nuts. I really hope 6.0 will be released soon and I really hope that it will work then.
Off topic: hard reset your box because I have three of them and they are working like a charme with this version of openelec.
Posted: 3 months 1 week ago by cityblue2001 #150538
cityblue2001's Avatar
Dalton63841 wrote:
On github, should I be watching the master branch, or the 6.0 branch? I'm thinking... Once stable, it becomes the master branch right?

openelec-6.0 is the "stable" branch. Master is for unstable (there's also an openelec-next branch which is also unstable, right now perhaps even more so than master as openelec-next is based on gcc5.2 while master is still using gcc4.9). Note that a term such as "unstable" doesn't mean master or openelec-next are actually unusable, it's just a acknowledgement that new changes in these branches are most likely minimally tested and can (on thankfully rare occasions) cause problems.

Once changes in master have been tested and considered stable, they'll be merged into openelec-6.0 (not all though - some changes that land in master will not go into openelec-6.0).

If you're worried this project is dead, keep an eye on master. If you want to see what is coming in OpenELEC 6.0, keep an eye on openelec-6.0. If you want to see what's coming in OpenELEC 7.0, keep an eye on openelec-next. The master branch is by far the most active branch right now.
Posted: 3 months 1 week ago by Dalton63841 #150537
Dalton63841's Avatar
On github, should I be watching the master branch, or the 6.0 branch? I'm thinking... Once stable, it becomes the master branch right?
Posted: 3 months 1 week ago by cityblue2001 #150509
cityblue2001's Avatar
blackbox wrote:
can't believe it that you are a lucky person.

Agree this is the wrong thread for your comment, but also amazed this is your first and only post - if the problems are that bad you might want to create a more appropriate thread where your issues can be investigated. Nothing is going to be fixed unless people are made aware of the problems in the first place.
Posted: 3 months 2 weeks ago by pomah #150504
pomah's Avatar
Hi

This thread is to talk about the progress of beta 5, for any other questions about the development go to the correct topic in the forums.

As mentioned by me before for more up to date information about what is going on and being updated follow github, it is all right there.

Please move this discussion to that place and leave this to post feedback about beta 5.
Posted: 3 months 2 weeks ago by blackbox #150500
blackbox's Avatar
can't believe it that you are a lucky person. I got a Wetek box (openElec-edition) and i regret having it. I just hope that its stability will be given very soon. Have lots of troubles with it like permanent kodi restarts because it crashes out of nothing, Live-TV stops after a few seconds from time to time because of "EPG scan" and "channel scrambled" or similar error messages (which are not true), and even my USB hard disk stopped getting power from it. Every now and then it starts working, but stops soon too. Also the remote control is bad as it can get. I need to use the Kodi-app from my phone, otherwise i'd get nuts. I really hope 6.0 will be released soon and I really hope that it will work then.
Posted: 3 months 2 weeks ago by Undutchable #150494
Undutchable's Avatar
Frank-NL wrote:
5.95.5 is as stable as it can get for me so I'm not complaining :silly:

"Hear, hear"
Posted: 3 months 2 weeks ago by Frank-NL #150488
Frank-NL's Avatar
5.95.5 is as stable as it can get for me so I'm not complaining :silly:
Posted: 3 months 2 weeks ago by Roby77 #150436
Roby77's Avatar
As said several time people that want to try jarvis build can find all links on kodi forum

Fritsch build is more updated with kernel for user >braswell and have all picture quality optimisation plus fernetmenta mod ( i use it for my haswell chromebox)

Milhouse build are based on fritsch and fernetmenta mod (more conservative about kernel test)

Milhouse also provide rpi2 jarvis buid
Posted: 3 months 2 weeks ago by cityblue2001 #150435
cityblue2001's Avatar
aptalca wrote:
Hey, when are we gonna get that?

Just kidding, of course.

You can have it now.

forum.kodi.tv/showthread.php?tid=238393

;)
Posted: 3 months 2 weeks ago by aptalca #150434
aptalca's Avatar
klojum wrote:
Okay, people. Just a brief statement hoping things will cool down a bit.

Actually, cityblue2001's post is not far from the truth. Yes, some team members have had changes in their professional and/or personal lives during the last 12 months. Resulting in a smaller total amount of spare time available for the OpenELEC project. We are all hobbyists and volunteers, doing what we love to do. But life has its own quirks and priorities. Also, the OE developers live/work in different parts of the globe, resulting in different time zones. Some things, big or small, you cannot alter easily.

So no, the OpenELEC project is not dead. Things are just going slower and a bit more agonizing than we had wished for. In terms of communication things can always be improved, internally or externally. As already stated by others, it's not simple to indicate how far a new release is from being 'released'. OpenELEC has always strived to use the latest and greatest of Linux kernels and tools to support as many hardware devices possible. Unfortunately, that ambition also has its drawbacks. We cannot simply support every piece of hardware out there. Wifi dongles, anyone? Also quite regularly people enter OE's IRC channel asking why OpenELEC does not start on their 6-9 year old computer. There is only so much that can be done.

OpenELEC 6.0 (with Kodi 15.2) was already up for release, but last minute glitches forced us not to go forward. It sucks, but we will take this hurdle as well eventually. Thank you for your patience, we soon hope to celebrate the release of OpenELEC 6.0.

Look at this guy's signature. He is using OpenELEC Jarvis and playing 4K :P

Hey, when are we gonna get that?

Just kidding, of course.

Thanks so much for the update. Great to know that things are moving forward.
Posted: 3 months 2 weeks ago by stevellion #150431
stevellion's Avatar
Thanks for the update. Always nice to get something, but I also believe we should all have patience, especially when we consider this is not a commercial business. I truly appreciate the OE project and I find it the most appropriate solution for small devices that will be pretty much dedicated to Kodi.
Let's all send a donation to thank for the effort.
Posted: 3 months 2 weeks ago by klojum #150430
klojum's Avatar
Okay, people. Just a brief statement hoping things will cool down a bit.

Actually, cityblue2001's post is not far from the truth. Yes, some team members have had changes in their professional and/or personal lives during the last 12 months. Resulting in a smaller total amount of spare time available for the OpenELEC project. We are all hobbyists and volunteers, doing what we love to do. But life has its own quirks and priorities. Also, the OE developers live/work in different parts of the globe, resulting in different time zones. Some things, big or small, you cannot alter easily.

So no, the OpenELEC project is not dead. Things are just going slower and a bit more agonizing than we had wished for. In terms of communication things can always be improved, internally or externally. As already stated by others, it's not simple to indicate how far a new release is from being 'released'. OpenELEC has always strived to use the latest and greatest of Linux kernels and tools to support as many hardware devices possible. Unfortunately, that ambition also has its drawbacks. We cannot simply support every piece of hardware out there. Wifi dongles, anyone? Also quite regularly people enter OE's IRC channel asking why OpenELEC does not start on their 6-9 year old computer. There is only so much that can be done.

OpenELEC 6.0 (with Kodi 15.2) was already up for release, but last minute glitches forced us not to go forward. It sucks, but we will take this hurdle as well eventually. Thank you for your patience, we soon hope to celebrate the release of OpenELEC 6.0.
Posted: 3 months 2 weeks ago by aptalca #150429
aptalca's Avatar
tonybeccar wrote:
Wow that's a lot of fighting...
But seriously, everyone, beta versions are there since always, and they contain release candidate versions of Kodi... because actually Kodi 15 isn't finished yet, they are on RC2 right now... latest beta contains that version, or the previous one... so really it's a matter of "naming" also... OE cannot be stable until Kodi es stable also. Beta works like a charm for me, downloaded a couple of days ago, solved my problems, more stable than 5.0.8.

Just a clarification, kodi had 3 stable versions since the last OE stable (5.0.8)
15.0, 15.1 and 15.2 (recently released)
most of the issues that caused the .1 and .2 releases were android related and should not effect OE
Posted: 3 months 2 weeks ago by Corwyn #150428
Corwyn's Avatar
cityblue2001 wrote:
Corwyn wrote:
Considering the waste of time this discussion has been, compared to a minute every week or two to post "still alive", what do you think? If it keeps the natives quiet, can or hurt?

I'd be tempted to set up a post bot. :)

Do what you think best, I for one still support your efforts, I'm just trying to be the calm voice of reason ;)
Posted: 3 months 2 weeks ago by cityblue2001 #150427
cityblue2001's Avatar
Corwyn wrote:
Considering the waste of time this discussion has been, compared to a minute every week or two to post "still alive", what do you think? If it keeps the natives quiet, can or hurt?

I'd be tempted to set up a post bot. :)
Posted: 3 months 2 weeks ago by Corwyn #150426
Corwyn's Avatar
cityblue2001 wrote:
Or would "Still alive, not dead yet - see github" posted once a week do the job? ;)

Considering the waste of time this discussion has been, compared to a minute every week or two to post "still alive", what do you think? If it keeps the natives quiet, can it hurt?
Posted: 3 months 2 weeks ago by cityblue2001 #150425
cityblue2001's Avatar
Corwyn wrote:
If you can, weekly, or bi-weekly, post that you're still alive and working on it, that might be enough to drive PhD the hoards.

Dare I say it, but a good indication that a project is no longer being actively developed is... Github (or whatever source code management tool the project is using).

A lack of new commits means one of two things - there are no bugs left to be fixed, or the project is dead. OpenELEC continues to receive regular updates on Github, and it continues to be supported on Github with new issues and pull requests being submitted, and also on the forums. There are also test builds of OpenELEC available (based on Kodi 16) which is where OpenELEC will be in 6 months time. Progress continues to be made, the only change is that releases have (hopefully temporarily) slowed. If people are champing at the bit for the latest Kodi, you have choices - there's no need to wait for a "stable" release.

This project is absolutely, categorically not dead, but it seems that unless people get a potted summary every week they're not going to believe it remains alive. I'm not really sure what needs to be posted other than a bunch of technical commits from Github, and I for one can't be arsed to do that (as it's not necessary) but maybe someone else will step up to the plate - I wait with baited breath...

Or would "Still alive, not dead yet - see github" posted once a week do the job, that's all that really needs to be said! ;)
Posted: 3 months 2 weeks ago by cityblue2001 #150423
cityblue2001's Avatar
Gump wrote:
Cityblue2001, are you in any way associated with any of the devs or member of the OE core team?

Yes.
Gump wrote:
You're telling us that the (few) devs are currently heavily engaged in other projects, job changes or - even worse - may face personal challenges.

Some of that is true, some of that is also speculation on my part (just to make the point - as it could be true, but it's personal/private stuff and none of my business). None of us know what goes on in each others lives, we don't know each other personally, and it's not for me to ask, or expect to be told (fortunately, the bit about the wife/child/cat probably isn't true) ;)

All I do know is that time is being sunk elsewhere rather than on OpenELEC, and that's totally fine with me as although the pace has slowed, progress is still being made and there is no loss of commitment to the future of OpenELEC.

I also know there's not going to be a great deal of difference between Beta5 and OE 6 Final, and the people holding off from installing a beta and whining about the delays for a stable release are just making a lot of noise for absolutely no reason.

And if anyone wants to test newer (Jarvis/Kodi16) OpenELEC builds *today* there are several sources out there (check the Kodi forum for both RPi and x86 builds), and they will offer a better experience than you will have even with OE6 stable - a lot of people are using these builds as their daily drivers without problems.
Gump wrote:
You also say the comments made here on next (beta) releases were unofficial Yet, my impression was that chewitt was sort of a OE spokesman who would provide reliable Information. At least he claimed to have a recieved a WhatsApp message from the devs about the plan to release a new beta last weekend..

Nobody has been asking for a release date, but some sort of heads up from time to time as well as feedback if (even vague) commitments could not be fulfilled would just be polite .

There's one person that pushes the button on a release, and it's not me, or Chewitt. We do get feedback from direct conversations that a new build is planned either for tomorrow, or the weekend, or next week and that information is often passed on to you in good faith, but when the release doesn't happen according to "the plan" this seems to cause more problems than it solves. Much of the communication about dates is couched in vague terms such as "hope to get release out xxxxx" but for some reason people take it as a certainty that it will happen on the given date, which is unfortunate - as I've alluded to previously it currently only takes one thing to happen in real life for the plan to be derailed.

I do know that a Beta 6 (5.95.6) is being worked on, and it will be released "soon" (crosses fingers, touches wood etc.). ;)
Posted: 3 months 2 weeks ago by Gump #150419
Gump's Avatar
tonybeccar wrote:
.., but no point in discussing this matters which can maybe hurt the few people who are making their best for "one of the best media center softwares out there" (that's a quote from a user here).
Tony, I almost 100% agree with you and appreciate that someone is trying to calm down the emotions. Just one important remark: OE is not KODI. KODI is running on several distros/platforms. OE is just one of them - also to me the one I liked best so far...
Posted: 3 months 2 weeks ago by Corwyn #150418
Corwyn's Avatar
I think this has gotten a bit out of hand here. People need to step back, take a breath, go for a walk, or whatever you do to cool off. The war of words is going to lead to serious bad consequences.

As an IT professional is over 30 years, I've been involved with many beta projects, both closed and open source. I've rarely seen regular updates on projects, until a release is published for testing or final distribution, and that's usually regular notes, and todo's with possible requests for specific tests to be performed and reported on. That is the norm.

We all want OE6 to release, we're all waiting for it. The devs are working in their spare time to get it done. We know they're working on it, and the project isn't dead. So please, let them do it, help of you can, but this discussion is only causing bad blood right now, and could end with the project being closed down out of anger. Don't let that happen.

Devs: understand, your users aren't necessarily computer savvy or literate, and come from a fast food world, patience isn't in their current vocabulary. Try to have a thicker skin, and do what you do best and love, you're project, as you can. If you can, weekly, or bi-weekly, post that you're still alive and working on it, that might be enough to drive PhD the hoards.

Let's all try to keep our heads.
Posted: 3 months 2 weeks ago by Gump #150417
Gump's Avatar
Cityblue2001, are you in any way associated with any of the devs or member of the OE core team?

You're telling us that the (few) devs are currently heavily engaged in other projects, job changes or - even worse - may face personal challenges. For any of this I have my deepest respect and understaning if this is the reason for their silence.
However, if this is just guessing and also not official, it might as well be the case that the devs have compeltely given up on OE, are helpless over a major issue or are completely at odds with each other.

You also say the comments made here on next (beta) releases were unofficial Yet, my impression was that chewitt was sort of a OE spokesman who would provide reliable Information. At least he claimed to have a recieved a WhatsApp message from the devs about the plan to release a new beta last weekend..

Nobody has been asking for a release date, but some sort of heads up from time to time as well as feedback if (even vague) commitments could not be fulfilled would just be polite .

[Beta] OpenELEC 6.0 Beta 4 released

The OpenELEC team is proud to announce the fourth beta of OpenELEC 6.0 (v5.95.4)

The most visible change is Kodi 15.1 (Isengard). Beginning with Kodi 15.0 most audio encoder, audio decoder, PVR and visualisation addons are no longer pre-bundled into OpenELEC but can be downloaded from the Kodi addon repo if required. PVR backends such as VDR and TVHeadend will install needed dependencies automatically. For further information on Kodi 15.1 please read http://kodi.tv/kodi-15-1-isengard-maintenance-release/.

We now officially support WeTek's WeTek_Play device with a build that installs to internal NAND and dual-boots with Android on an SD Card. The iMX6 build extends support to all Solidrun CuBox-i/TV, Solidrun Hummingboard devices and the OSMC Vero. We recommend CuBox-i2eX / Hummingboard-i2eX or better devices.

Read more ...


Posted: 4 months 6 days ago by andal1208 #149245
andal1208's Avatar
Hey,

Installed beta4 on friday by just installing it over 5.0.8 and resetting the settings, everything was fine, suspend/resume worked as before.
Yesterday I tried to wake my NUC (DN2820FYKH), but just black Picture. The Power button was lit. After a manual reboot it was fine.
To verify I've installed beta4 from scratch, some behaviour: WHen I suspend OE for a short time it'S fine, but resume will fail after a couple of hours.

I've noticed this in previous betas before, but it looks like I'm the only reporter

I forgot to look for the logs, if there are some I'll post them later..

Hi ScotchTape,
I had the same problem with my NUC DN2820FYKH. I changed the Boot OS in the BIOS from "Windows 7" to "Windows 8" and the problem disappeared. Now it is waking up properly and works like a charm.

Hope this helps,
Andreas
Posted: 5 months 1 week ago by chewitt #146909
chewitt's Avatar
Ankerstjerne wrote:
Would it be possible to get a 5.09 build with kodi 15.1 instead of waiting for the system part? I am pretty happy with the 5 branch..so that solution would work fine for me

It's technically possible to do this, but it won't be happening. Official development is focussed on 6.0 and although this has been a comparatively slow release to earlier ones, it is moving forwards. Working on 5.0.x would be moving backwards.
Posted: 5 months 1 week ago by Ankerstjerne #146908
Ankerstjerne's Avatar
Would it be possible to get a 5.09 build with kodi 15.1 instead of waiting for the system part? I am pretty happy with the 5 branch..so that solution would work fine for me

Thanks
Posted: 5 months 1 week ago by LennyX #146898
LennyX's Avatar
Beta 4 doesn't run very good for me:
  • Completely lost EPG (VDR/VNSI-addon)
  • Kodi-addon for Emby stopped working

As this derives me of my complete audio/video collection (managed by an Emby server) and reduces PVR to a dumb TV, this are showstoppers. Downgrade to beta3 made everything work again.

Anybody else with this problems? Searching the web did not help me.
Posted: 5 months 1 week ago by nickr #146878
nickr's Avatar
bob808 wrote:
is anyone else getting a continual boot loop after enabling livetv - with both tvheadend or mediaportal client it starts pulling in channel details but part way though it restarts - not a full reboot, but back to the 15.1 logo and then to kodi - starts loading channels/epg, and restarts again. The only fix I can get is to pull the network out (pvr is on remote system) and then disable livetv.

Rolling back to stable release this doesn't happen. I did an upgrade install, and a hard reset before setting up.
You probably need to update to the latest pvr addons.

Sent from my U65GT using Tapatalk
Posted: 5 months 1 week ago by soyxan #146862
soyxan's Avatar
I am experiencing CEC problems with the last beta.

My RPi2 is connected through HDMI cables this way:
RPi2 -> Samsung Sound Bar (HW-E450) -> Samsung TV (UN46ES6800)

I have to reboot several times the Rpi2 in order to get CEC working.

You can see in the following log a first boot with CEC not working, a reboot, and then the CEC works (although not having the same behaviour at it has on 5.0.8, I will explain this bellow).
pastebin.com/JBSZkyFs

In 5.0.8 when I chose the Openelec CEC source on my Samsung TV, the Sound Bar was automatically turned on and the Sound Bar source changed automatically to the HDMI input (where Rpi2 is connected). With this beta, the behaviour is different: The Sound Bar is turned on automatically but it stays on the TV ARC (TV Audio Return Channel) input, and I have to manually change the input to the HDMI to see the Openelec interface.

Thanks!
Posted: 5 months 1 week ago by bob808 #146860
bob808's Avatar
is anyone else getting a continual boot loop after enabling livetv - with both tvheadend or mediaportal client it starts pulling in channel details but part way though it restarts - not a full reboot, but back to the 15.1 logo and then to kodi - starts loading channels/epg, and restarts again. The only fix I can get is to pull the network out (pvr is on remote system) and then disable livetv.

Rolling back to stable release this doesn't happen. I did an upgrade install, and a hard reset before setting up.
Posted: 5 months 1 week ago by Rimnac #146780
Rimnac's Avatar
I am running an ASUS Chromebox modded, and since the upgrade I lose my network connection almost any time I suspend and resume. This didn't happen on the 5.0.8 release (last one I used). I can provide any more information if needed - this is my first time making a report so I definitely don't mean to leave things out!

Thank you!
Posted: 5 months 1 week ago by lollo78 #146718
lollo78's Avatar
Hi, I have a lot of difficulty with PVR.
I installed TVHeadend (server and client) from Openelec standard and dev repository, configured all and it works fine for a little time. Or at least until (I think) I uninstalled VDR and IPTV Simple client (I instelled it in the same time of TVHeadend). I uninstalled VDR because I prefer TVHeadend and IPTV Simple Client because has a lot of bug in this Isengard beta.
Maybe, now some libs or files are corrupted or missing or maybe it's a firmware/driver issue into the tuner support...
Let me explain the issue:
with Avermedia HD Volar A867 DVB-T Tuner USB, chip Afatech af9035, installed into raspberry with firmware version=11.5.9.0 (dvb-usb-af9035-02.fw) I can't play the Live TV channels. Sometimes an error appear ("no free adapter") and sometimes I can play one channel but if I switch to others channels, I listen only audio without video.
But I don't know how (incredible) the first time I installed and configured TVHeadend (see up) all works fine.
And more: if I power off raspberry, at next boot I have to unplug and replug the tuner or it is seems dead (no led activity).
I tried also with another tuner (Afatech af9015; dvb-usb-af9015.fw), unistalled TVHeadend a lot of time (and make fresh configuration) but I have always the same issue.
I don't know if it is a bug, but., plaese, any suggestion to solve it?
Thanks a lot


EDIT:
I made another try and some research for the first of the two tuner tv tested.
If I understood well, there is an issue with the tuner tv driver and Kernel 4.x
The product is: ID 07ca:a867 - AVerMedia Technologies, Inc. AVerTV DVB-T (A867)
The dvb-usb-af9035-02.fw provided with Openelec seems an old release (it would be works on the old kernel 3.x): firmware version: LINK 11.5.9.0 - OFDM 5.17.9.1.
The author of the driver (Antti Palosaari) in late 2012 has released another driver: LINK 12.13.15.0 - OFDM 6.20.15.0, available on palosaari.fi/linux/v4l-dvb/firmware/af9035/
So, I putted the latest dvb-usb-af9035-02.fw (09-Dec-2012 20:17) into /storage/.config/firmware and now seems that at least one of the issues is resolved: no more "dead tuner at reboot". Now, the led activity lights up at raspberry power up. But... the most important issue remains. The tuner doesn't work.
With both driver, 11.5.9.0 and 12.13.15.0, with dmesg I see
4.858165] mxl5007t_soft_reset: 521: failed!
4.858178] mxl5007t_attach: error -121 on line 907
Don't ask me how, but at the first installation all works fine for me (channel sync, zapping and so on). After a reboot, or maybe after unplugged the tuner with TVheadend started, or may after remove the other backend, It doesn't work anymore.
And now I'm at this point (I can't see any channel and appear a TVheadend error: "no free adapter")...

Dear Openelec dev, could you contact Pasolaari to patch with him this driver?
I don't have competences to talk with him about this, but I will be very glad and happy to make the beta tester for you.
Thx

Now I go to test again and make some research for the other tuner tv that doesn't work...


EDIT 2:
The second usb tuner tv is a
ID 15a4:9015 Afatech Technologies, Inc. AF9015 DVB-T USB2.0 stick
the default Openelec driver is version 4.95.0.0 and is dmesg is:
[  177.262323] usb 1-1.2: new high-speed USB device number 5 using dwc_otg
[  177.359943] usb 1-1.2: New USB device found, idVendor=15a4, idProduct=9015
[  177.359976] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  177.359991] usb 1-1.2: Product: DVB-T 2
[  177.360007] usb 1-1.2: Manufacturer: Afatech
[  177.360021] usb 1-1.2: SerialNumber: 010101010600001
[  177.429637] usb 1-1.2: dvb_usb_v2: found a 'Afatech AF9015 reference design' in cold state
[  177.442872] usb 1-1.2: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw'
[  177.511826] usb 1-1.2: dvb_usb_v2: found a 'Afatech AF9015 reference design' in warm state
[  177.872422] usb 1-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[  177.872724] DVB: registering new adapter (Afatech AF9015 reference design)
[  177.892801] i2c i2c-3: af9013: firmware version 4.95.0.0
[  177.894845] usb 1-1.2: DVB: registering adapter 0 frontend 0 (Afatech AF9013)...
[  177.912084] tda18271 3-00c0: creating new instance
[  177.918159] TDA18271HD/C2 detected @ 3-00c0
[  178.150569] Registered IR keymap rc-empty
[  178.151065] input: Afatech AF9015 reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/rc/rc0/input0
[  178.151347] rc0: Afatech AF9015 reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/rc/rc0
[  178.151378] usb 1-1.2: dvb_usb_v2: schedule remote query interval to 500 msecs
[  178.151398] usb 1-1.2: dvb_usb_v2: 'Afatech AF9015 reference design' successfully initialized and connected
[  178.151601] usbcore: registered new interface driver dvb_usb_af9015
[  179.430748] tda18271: performing RF tracking filter calibration
[  180.049442] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[  180.049952] tda18271_read_extended: [3-00c0|M] ERROR: i2c_transfer returned: -71
[  180.049969] tda18271_powerscan: [3-00c0|M] error -71 on line 507
[  180.049981] tda18271_rf_tracking_filters_init: [3-00c0|M] error -71 on line 602
[  180.049992] tda18271_calc_rf_filter_curve: [3-00c0|M] error -71 on line 663
[  180.050002] tda18271c2_rf_cal_init: [3-00c0|M] error -71 on line 688
[  180.050007] tda18271: RF tracking filter calibration failed!
[  180.050090] usb 1-1.2: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000)
[  180.141828] tda18271: performing RF tracking filter calibration
[  182.893793] tda18271: RF tracking filter calibration complete

I tried aldo with the newst firmware from palosaari.fi/linux/v4l-dvb/firmware/af9015/ but the issue is the same:
I can play only one channel, but If I try to play another channels I can listen only audio, without video (the image freezes on the latest frame).

This is the dmesg of the firmware 5.1.0.0:
[    4.754868] DVB: registering new adapter (Afatech AF9015 reference design)
[    4.814257] i2c i2c-3: af9013: firmware version 5.1.0.0
[    4.817091] usb 1-1.2: DVB: registering adapter 0 frontend 0 (Afatech AF9013)...
[    4.817422] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    4.817991] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.851905] tda18271 3-00c0: creating new instance
[    4.856790] random: nonblocking pool is initialized
[    4.868423] TDA18271HD/C2 detected @ 3-00c0
[    5.102518] Registered IR keymap rc-empty
[    5.103093] input: Afatech AF9015 reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/rc/rc0/input0
[    5.103768] rc0: Afatech AF9015 reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/rc/rc0
[    5.103796] usb 1-1.2: dvb_usb_v2: schedule remote query interval to 500 msecs
[    5.103816] usb 1-1.2: dvb_usb_v2: 'Afatech AF9015 reference design' successfully initialized and connected
[    5.103990] usbcore: registered new interface driver dvb_usb_af9015
[    6.468602] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.471292] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[    6.798658] tda18271: performing RF tracking filter calibration
[    7.565334] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[    7.565845] tda18271_read_extended: [3-00c0|M] ERROR: i2c_transfer returned: -71
[    7.565859] tda18271_powerscan: [3-00c0|M] error -71 on line 507
[    7.565868] tda18271_rf_tracking_filters_init: [3-00c0|M] error -71 on line 602
[    7.565877] tda18271_calc_rf_filter_curve: [3-00c0|M] error -71 on line 663
[    7.565886] tda18271c2_rf_cal_init: [3-00c0|M] error -71 on line 688
[    7.565891] tda18271: RF tracking filter calibration failed!
[    7.565944] usb 1-1.2: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000)
[    7.655664] tda18271: performing RF tracking filter calibration
[    8.756332] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[    8.756811] tda18271_read_extended: [3-00c0|M] ERROR: i2c_transfer returned: -71
[    8.756823] tda18271_powerscan: [3-00c0|M] error -71 on line 479
[    8.756833] tda18271_rf_tracking_filters_init: [3-00c0|M] error -71 on line 602
[    8.756841] tda18271_calc_rf_filter_curve: [3-00c0|M] error -71 on line 663
[    8.756849] tda18271c2_rf_cal_init: [3-00c0|M] error -71 on line 688
[    8.756855] tda18271: RF tracking filter calibration failed!
[    8.761484] tda18271: performing RF tracking filter calibration
[   11.349036] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[   11.349803] tda18271_read_extended: [3-00c0|M] ERROR: i2c_transfer returned: -71
[   11.349814] tda18271_powerscan: [3-00c0|M] error -71 on line 507
[   11.349823] tda18271_rf_tracking_filters_init: [3-00c0|M] error -71 on line 602
[   11.349831] tda18271_calc_rf_filter_curve: [3-00c0|M] error -71 on line 663
[   11.349840] tda18271c2_rf_cal_init: [3-00c0|M] error -71 on line 688
[   11.349845] tda18271: RF tracking filter calibration failed!
[   12.227198] tda18271: performing RF tracking filter calibration
[   15.477446] tda18271: RF tracking filter calibration complete

This is the dmesg of the firmware 5.24.0.0:
3.912083] usb 1-1.2: dvb_usb_v2: found a 'Afatech AF9015 reference design' in cold state
[    3.914748] usb 1-1.2: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw'
[    3.930613] Console: switching to colour dummy device 80x30
[    4.001287] usb 1-1.2: dvb_usb_v2: found a 'Afatech AF9015 reference design' in warm state
[    4.361508] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    4.361651] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.402068] usb 1-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[    4.402208] DVB: registering new adapter (Afatech AF9015 reference design)
[    4.443280] i2c i2c-3: af9013: firmware version 5.24.0.0
[    4.444829] usb 1-1.2: DVB: registering adapter 0 frontend 0 (Afatech AF9013)...
[    4.474056] tda18271 3-00c0: creating new instance
[    4.479975] TDA18271HD/C2 detected @ 3-00c0
[    4.708636] Registered IR keymap rc-empty
[    4.709057] input: Afatech AF9015 reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/rc/rc0/input0
[    4.709585] rc0: Afatech AF9015 reference design as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/rc/rc0
[    4.709607] usb 1-1.2: dvb_usb_v2: schedule remote query interval to 500 msecs
[    4.709622] usb 1-1.2: dvb_usb_v2: 'Afatech AF9015 reference design' successfully initialized and connected
[    4.709722] usbcore: registered new interface driver dvb_usb_af9015
[    4.765299] Bluetooth: Core ver 2.20
[    4.765405] NET: Registered protocol family 31
[    4.765415] Bluetooth: HCI device and connection manager initialized
[    4.765438] Bluetooth: HCI socket layer initialized
[    4.765451] Bluetooth: L2CAP socket layer initialized
[    4.765490] Bluetooth: SCO socket layer initialized
[    4.772209] usbcore: registered new interface driver btusb
[    5.184976] random: nonblocking pool is initialized
[    6.020617] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.023465] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[    6.421967] tda18271: performing RF tracking filter calibration
[    8.171819] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[    8.173220] tda18271_read_extended: [3-00c0|M] ERROR: i2c_transfer returned: -71
[    8.173236] tda18271_powerscan: [3-00c0|M] error -71 on line 507
[    8.173245] tda18271_rf_tracking_filters_init: [3-00c0|M] error -71 on line 602
[    8.173253] tda18271_calc_rf_filter_curve: [3-00c0|M] error -71 on line 663
[    8.173262] tda18271c2_rf_cal_init: [3-00c0|M] error -71 on line 688
[    8.173267] tda18271: RF tracking filter calibration failed!
[    8.173341] usb 1-1.2: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000)
[    8.270886] tda18271: performing RF tracking filter calibration
[    9.225792] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[    9.226312] tda18271_read_extended: [3-00c0|M] ERROR: i2c_transfer returned: -71
[    9.226324] tda18271_powerscan: [3-00c0|M] error -71 on line 507
[    9.226333] tda18271_rf_tracking_filters_init: [3-00c0|M] error -71 on line 602
[    9.226341] tda18271_calc_rf_filter_curve: [3-00c0|M] error -71 on line 663
[    9.226350] tda18271c2_rf_cal_init: [3-00c0|M] error -71 on line 688
[    9.226355] tda18271: RF tracking filter calibration failed!
[    9.306593] tda18271: performing RF tracking filter calibration
[   10.266311] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[   10.266796] tda18271_read_extended: [3-00c0|M] ERROR: i2c_transfer returned: -71
[   10.266807] tda18271_powerscan: [3-00c0|M] error -71 on line 507
[   10.266816] tda18271_rf_tracking_filters_init: [3-00c0|M] error -71 on line 602
[   10.266825] tda18271_calc_rf_filter_curve: [3-00c0|M] error -71 on line 663
[   10.266833] tda18271c2_rf_cal_init: [3-00c0|M] error -71 on line 688
[   10.266838] tda18271: RF tracking filter calibration failed!
[   11.140938] tda18271: performing RF tracking filter calibration
[   12.936567] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[   12.937087] tda18271_read_extended: [3-00c0|M] ERROR: i2c_transfer returned: -71
[   12.937102] tda18271_powerscan: [3-00c0|M] error -71 on line 507
[   12.937111] tda18271_rf_tracking_filters_init: [3-00c0|M] error -71 on line 602
[   12.937120] tda18271_calc_rf_filter_curve: [3-00c0|M] error -71 on line 663
[   12.937128] tda18271c2_rf_cal_init: [3-00c0|M] error -71 on line 688
[   12.937133] tda18271: RF tracking filter calibration failed!
[   13.815264] tda18271: performing RF tracking filter calibration
[   17.147009] tda18271: RF tracking filter calibration complete
[   17.151861] usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-71
[   17.152396] tda18271_read_regs: [3-00c0|M] ERROR: i2c_transfer returned: -71

It's so frustrating, because this two adapter could be supported (wiki.openelec.tv/index.php/Supported_TV_Tuners).
So, now, I don't know how to find a good DVB-T HD Tuner that works good with my setup (latest Openelec build, Raspberry Pi2).
Please, could you advice me someone of it so I can buy it?
Thx a lot
Posted: 5 months 1 week ago by soyxan #146706
soyxan's Avatar
popcornmix wrote:
soyxan wrote:
Yes now is working fine! Omxplayer HW acceleration should be enabled by default in RPi2 right? Why is not?

omxplayer is a default on pi1, but not on pi2.

I don't know why omxplayer is working with passthrough for you, but dvdplayer is not.
dvdplayer works with passthrough on all my test platforms, so it's not an easy thing to debug.

What is the make and model of your tv and soundbar?

My TV is Samsung UN46ES6800 and the Soundbar is a Samsung HW-E450.

I am not sure if Omxplayer setting was enabled on 5.0.8, but passtrough on that version was working fine.
Enabling Omxplayer acceleration has any drawback?

If you need anything else let me know.
Posted: 5 months 1 week ago by popcornmix #146703
popcornmix's Avatar
soyxan wrote:
Yes now is working fine! Omxplayer HW acceleration should be enabled by default in RPi2 right? Why is not?

omxplayer is a default on pi1, but not on pi2.

I don't know why omxplayer is working with passthrough for you, but dvdplayer is not.
dvdplayer works with passthrough on all my test platforms, so it's not an easy thing to debug.

What is the make and model of your tv and soundbar?
Posted: 5 months 1 week ago by soyxan #146691
soyxan's Avatar
popcornmix wrote:
soyxan wrote:
Just upgraded my RPi2 from 5.0.8 to beta 4 and now audio passtrough to my Samsung soundbar is not working (no sound at all), if
Does enabling omxplayer in video/accleration settings make a difference?

Yes now is working fine! Omxplayer HW acceleration should be enabled by default in RPi2 right? Why is not?
Posted: 5 months 1 week ago by alextz #146689
alextz's Avatar
After update from 5.0.8 my wifi adapter is not up after each reboot. I have to go manually into Openelec addon and enable it.

Any ideas how to fix this?

01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
Posted: 5 months 1 week ago by popcornmix #146668
popcornmix's Avatar
soyxan wrote:
Just upgraded my RPi2 from 5.0.8 to beta 4 and now audio passtrough to my Samsung soundbar is not working (no sound at all), if
Does enabling omxplayer in video/accleration settings make a difference?
Posted: 5 months 1 week ago by soyxan #146611
soyxan's Avatar
Just upgraded my RPi2 from 5.0.8 to beta 4 and now audio passtrough to my Samsung soundbar is not working (no sound at all), if I disable audio passtrough, sound is fine.

That was working right on 5.0.8.

I disabled Sync Playback to Display (which was enabled during the upgrade, as I never enabled it on 5.0.8) as suggested but nothing changes.

I have uploaded the log here:
pastebin.com/5j5aSKBM

The log reflects several tries to get it working (even disabling the passtrough), anyhow the last 2 movies played in the log were with the passtrough enabled.

Thanks!
Posted: 5 months 1 week ago by dproff #146596
dproff's Avatar
New problem for me that just started last night. I am getting continuous partial reboots. black screen followed by booting from the kodi loading start not the openelec boot. I have a log file capturing one of these events but logging is also terminated when this happens. My kodi computer only connects to my server inconsistently so I cannot get to the log file now. My device is a Dell quad core computer.

I thought that disabling TV PVR and rebooting fixed the problem, but I was wrong. It just took a longer interval to begin the reboots. The service app I use is Israel Live TV.

I tried to upload a log file so it may be there now. It did not successfully email to me however.

log file is here: xbmclogs.com/ps7yzbwga
Posted: 5 months 1 week ago by X-Dan #146592
X-Dan's Avatar
Hi,

Just a quick message to say that the Beta 4 is working perfectly on my setup (flac, 720p, 1080p, etc..):

RPI 2
Hifiberry digi+
Wifi usb dongle
FLIR usb dongle (for IR)

To all dev, thank you to your really great work. I hope the final version will be out soon :-)
Posted: 5 months 1 week ago by ScotchTape #146588
ScotchTape's Avatar
Hey,

Installed beta4 on friday by just installing it over 5.0.8 and resetting the settings, everything was fine, suspend/resume worked as before.
Yesterday I tried to wake my NUC (DN2820FYKH), but just black Picture. The Power button was lit. After a manual reboot it was fine.
To verify I've installed beta4 from scratch, some behaviour: WHen I suspend OE for a short time it'S fine, but resume will fail after a couple of hours.

I've noticed this in previous betas before, but it looks like I'm the only reporter ;)

I forgot to look for the logs, if there are some I'll post them later..
Posted: 5 months 2 weeks ago by real_larry #146542
real_larry's Avatar
Did a test with a clean install of beta4 on rpi2 today to experience the behavior of pvr/tvheadend and Hama-MCE remote. Installed only a few addons, like scrapers, weather, language and tvheadend client. Copied advancedsettings.xml and sources.xml from OE 5.0.8 and did some puny modifications. Database is mysql based. OE configured like the others of my OE setups.
I couln't find any issue. Everything is working so far - at least to gain a read-to-run system as I did no deeper tests. But TV, Video, Audio and Pictures are working as normal, all needed buttons of the Hama-MCE are working (except yellow). No crashes nor anything similar after two hours of watching, hearing, zapping and winding.

Just my 2c.
-
Larry
Posted: 5 months 2 weeks ago by popcornmix #146538
popcornmix's Avatar
lollo78 wrote:
I'm start thinking that this parameters didn't works in Openelec 5.0.8.
5.0.8 didn't include the sdhost driver or the sdcard overclock settings at all.
Than my readbufferfactor (2.0) it was ignored?
Note 4 is the default with OpenELEC - are you really trying to reduce the setting?
I see the mouse cursor on the up-left side of the screen also if I disable "mouse and touch support" inside the System -> Input device option. This is very annoying: I use retroarch and also during playng I see the cursor.
This has been fixed, but OE hasn't updated to that version. Should be in next update.
Posted: 5 months 2 weeks ago by lollo78 #146518
lollo78's Avatar
Hi guys,
the only solution for me it was to delete the MySQL kodi user:
I'll go to recreate all the databases, but al least, now Kodi starts with my advancedsettings.xml.

I notice some "bug" or strange things using my working/previous configuration (Openelec 5.0.8) on this beta 4:

1) Another stuck (for me) at boot is config.txt file (cannot mount tty xyz_asdaf :D).
I can't boot with
dtoverlay=sdhost,overclock_50=100
sometime boot and sometime no with
dtoverlay=sdhost,overclock_50=84
seems to work with
dtoverlay=sdhost,overclock_50=63
but I have to test it more. I'm start thinking that this parameters didn't works in Openelec 5.0.8.

2) In my advancedsettings.xml i have setted:
<cachemembuffersize>20971520</cachemembuffersize>
<readbufferfactor>2.0</readbufferfactor>
but into the log I see:
01:00:05   5.561922 T:1968373760  NOTICE: Loaded settings file from special://xbmc/system/advancedsettings.xml
01:00:05   5.562265 T:1968373760  NOTICE: Contents of special://xbmc/system/advancedsettings.xml are...
                                            <?xml version="1.0" encoding="UTF-8" ?>
                                            <advancedsettings>
                                              <showexitbutton>false</showexitbutton>
                                              <fanartres>720</fanartres>
                                              <imageres>540</imageres>
                                              <video>
                                                <busydialogdelayms>750</busydialogdelayms>
                                              </video>
                                              <samba>
                                                <clienttimeout>30</clienttimeout>
                                              </samba>
                                              <network>
                                                <readbufferfactor>4.0</readbufferfactor>
                                              </network>
                                            </advancedsettings>
Than my readbufferfactor (2.0) it was ignored?

3) I paired my Blutooth PS3 controllers. I see the mouse cursor on the up-left side of the screen also if I disable "mouse and touch support" inside the System -> Input device option. This is very annoying: I use retroarch and also during playng I see the cursor.

4) RSS scrolling stuttering (is not fluid). And sometime the GUI is laggy. But with dtoverlay=sdhost,overclock_50=63 it's stable.

Maybe I'm crazy, but I hope that this can help to improve Openelec 6
Posted: 5 months 2 weeks ago by klojum #146512
klojum's Avatar
As in use the "Wait for network" option?

Apparently, the music database is there (it is 'running'), but the database table 'version' is not tbere. Sounds more like a Kodi database creation mess up. Delete (or rename) the current MyMusic52 database, and restart Kodi.
Posted: 5 months 2 weeks ago by chewitt #146510
chewitt's Avatar
lollo78 wrote:
If I remove advancedsettings.xml and reboot, Kodi works again.

Add a 10 seconds startup delay to Kodi via the settings addon. Fixed?
Posted: 5 months 2 weeks ago by lollo78 #146506
lollo78's Avatar
Hi guys, I really need help.
I fresh installed Openelec 5.95.4 (previous I was on 5.0.8): works fine, but when I upload my advancedsettings.xml file, Kodi doesn't start (stuck on black screen).

I use a NAS and a shared MySQL library.

At the end of the log (full log here: pastebin.com/Ypuxh8YZ) I see:
14:27:49 105.815857 T:1968582656 ERROR: SQL: The table does not exist
Query: SELECT idVersion FROM version

If I remove advancedsettings.xml and reboot, Kodi works again.

This is the first time that happen me this issue and I don't know how to solve it.
Please, I need to use the MySQL library...
What I have to do?
Thx

[Beta] OpenELEC 6.0 Beta 3 released

The OpenELEC team is proud to announce its 3rd Beta of OpenELEC 6.0. Internally this will be known by the less-catchy name OpenELEC 5.95.3.

The OpenELEC 5.95 release series are test releases (beta) for OpenELEC-6.0.
OpenELEC-6.0 will be the next stable release, which is a feature release and the successor of OpenELEC-5.0.

The most visible change is the update from Kodi-14.2 Helix to Kodi-15.0 Isengard (rc 2). Beginning with Kodi-15 most audio encoder, audio decoder, PVR and visualisation addons are no longer included in our base OS, but they are available via Kodi's addon manager and must be installed from there, if needed. Our own PVR backends such as VDR and TVHeadend will install needed dependencies automatically. Other than that, please refer to http://kodi.tv/kodi-15-0-isengard-rc-2/ to see all the changes in Kodi-15.

Read more ...


Posted: 3 months 2 weeks ago by nickr #150106
nickr's Avatar
Try reading the last few pages of the 5.95.5 thread.

Sent from my U65GT using Tapatalk
Posted: 3 months 3 weeks ago by darkxfuneral #150063
darkxfuneral's Avatar
kodi 15.2 is out. where is new OE? :(
Posted: 5 months 2 weeks ago by PaulFinch #146201
PaulFinch's Avatar
nickr wrote:
Is there a reason you aren't just letting it use the standard DB names?
Not really ... Except i really don't like kodi's db naming and globaly, the way kodi deals with his dbs.
Posted: 5 months 2 weeks ago by nickr #146193
nickr's Avatar
Is there a reason you aren't just letting it use the standard DB names?
Posted: 5 months 2 weeks ago by PaulFinch #146180
PaulFinch's Avatar
Just manually updated my cubox i4 from 5.0.8 to 5.95.4.
No issue observed so far

I just had this tiny problem while upgrading the mysql database.
My db were named Kodi-VideoNN and Kodi-MusicNN, it looks like it didn't like the special character (was ok in previsous kodi versions).
I had to rename the DB in mysql and in advancedsettings.xml (removed the dash) and the db upgraded correctly.
I guess this is related to kodi, not openelec.

My remote (Harman Kardon AVR171 configured with specific ir-keytable) stil works correctly.

So far, So good.
Posted: 5 months 2 weeks ago by musicadi #146151
musicadi's Avatar
My Wetek Play box just told me the update was available and ran the update.

Everything seems to work, only I get an orange screen instead of the logo screens :)

P.S. I'm talking about Beta 4
Posted: 5 months 2 weeks ago by kapiszon53 #146142
kapiszon53's Avatar
It looks like this version has a kernel md5 mismatch, I downloaded and copied twice, no luck.
Posted: 5 months 2 weeks ago by jan #146138
jan's Avatar
wow hidden goodies

just copy the link of choice on the download page
change 5.95.3 to 5.95.4 and you are good to go
Posted: 5 months 2 weeks ago by Grael #146135
Grael's Avatar
Have you read the thread you post in? ;-)
Posted: 5 months 2 weeks ago by lollo78 #146133
lollo78's Avatar
Hy guys, kodi 15.1 is out and Openelec is stucked on 5.95.3.
There isan ETA for Openelec 6.x (based on latest Isengard) or all the devs are "missing"?
:D
Posted: 5 months 2 weeks ago by sebj #146132
sebj's Avatar
it's not "available", it's hidden! :P
Posted: 5 months 2 weeks ago by Fredouye #146131
Posted: 5 months 2 weeks ago by tergo #146125
tergo's Avatar
aptalca wrote:

I tried to ask in the github thread whether the people had issues with regular usb keyboard keys in the latest betas but no one answered.

I experience the MCE remote issue with both a VRC-1100 and also a Asus/Philips remote that came free with my At3IONt-I deluxe.

To answer your question, ordinary wired USB keyboard works fine.

Many of the remotes in question are indeed not eHome/RC6 compatible remotes. However they are generally grouped under the MCE banner, just put under a separate category to RC6:
kodi.wiki/view/List_of_MCE_remote_controls

Arguing about whether they should be called MCE or not doesn't help to resolve the issue. All the devs know for many years what they are and how they operate like a keyboard. sraue even bought a VRC-1100 but was unable to reproduce the bug. And fritsch also. So the problem is something more mysterious.
Posted: 5 months 2 weeks ago by Fantasticn #146120
Fantasticn's Avatar
Yep. I can confirm that. Running OpenElec 6.0 beta 1, 2, 3 and all Nightly Builds from Nerdcamp (including latest) original Microsoft MCE-Remotes and clones (e.g. so-called "Origin-MCE") are working fine on different PCs using external IR-sensor or internal IR-sensor of the Intel NUC, except for the power-button not powering down and waking up the PC anymore.

Using Auvisio and Hama-Remotes instead (looking similar to MCE-Remotes but using different IR-sensor, not compatible with original MCE-IR-sensor or internal IR-Sensor of the Intel NUC) a lot more buttons are not working anymore, like Stop, Back, etc..

But it was mentioned a few times that this problem was already identified and a fix was expected for Beta 4. So let's wait and see.

Brgds,

FantasticN
Posted: 5 months 2 weeks ago by aptalca #146116
aptalca's Avatar
lysin wrote:
aptalca wrote:
rwss wrote:
I wonder if the remote problems are related to a few brands. I've seen problems with the remote that goes along with the Samsung tv of my nephew, he also putted new battery's in the remote. The ok button was not working. On my own remote that comes with my Philips tv I don't have any problems. We both are using the latest Openelec beta.
Remote issue has nothing to do with mce remotes. Mce remotes have been reported many times to work fine with the betas.

The problem is with mce "clones", the knock off remotes that register as usb keyboards. Perhaps the issue is because of the recently removed option "remote sends keyboard presses"? Who knows?

I tried to ask in the github thread whether the people had issues with regular usb keyboard keys in the latest betas but no one answered.

There is no problem with the remote, the problem is with the system itself. If you posted int he github issue you should have noticed that there are a few methods to get the remote to *almost* work (linking some files, accessing via vnc) and besides, its more than proved that the system is receiving input, just isn't processing it right.
I didn't mean the mce clones were all broken. I meant the problem occurs with mce clones and not real mce remotes ;)

Of course, the problem is likely with how the system processes the input. That's why I asked again whether the regular usb keyboards work properly (since their input should be comparable to the mce clones).

Unfortunately the only machine I have that's running 15.1 is an android one and not running openelec so I can't test it
Posted: 5 months 2 weeks ago by lysin #146109
lysin's Avatar
aptalca wrote:
rwss wrote:
I wonder if the remote problems are related to a few brands. I've seen problems with the remote that goes along with the Samsung tv of my nephew, he also putted new battery's in the remote. The ok button was not working. On my own remote that comes with my Philips tv I don't have any problems. We both are using the latest Openelec beta.
Remote issue has nothing to do with mce remotes. Mce remotes have been reported many times to work fine with the betas.

The problem is with mce "clones", the knock off remotes that register as usb keyboards. Perhaps the issue is because of the recently removed option "remote sends keyboard presses"? Who knows?

I tried to ask in the github thread whether the people had issues with regular usb keyboard keys in the latest betas but no one answered.

There is no problem with the remote, the problem is with the system itself. If you posted int he github issue you should have noticed that there are a few methods to get the remote to *almost* work (linking some files, accessing via vnc) and besides, its more than proved that the system is receiving input, just isn't processing it right.
Posted: 5 months 2 weeks ago by aptalca #146107
aptalca's Avatar
rwss wrote:
I wonder if the remote problems are related to a few brands. I've seen problems with the remote that goes along with the Samsung tv of my nephew, he also putted new battery's in the remote. The ok button was not working. On my own remote that comes with my Philips tv I don't have any problems. We both are using the latest Openelec beta.
Remote issue has nothing to do with mce remotes. Mce remotes have been reported many times to work fine with the betas.

The problem is with mce "clones", the knock off remotes that register as usb keyboards. Perhaps the issue is because of the recently removed option "remote sends keyboard presses"? Who knows?

I tried to ask in the github thread whether the people had issues with regular usb keyboard keys in the latest betas but no one answered.
Posted: 5 months 2 weeks ago by driver140771 #146101
driver140771's Avatar
There's a Beta4 based on 15.1 planned for this weekend.

? :(
Posted: 5 months 2 weeks ago by slipx06 #146100
slipx06's Avatar
Actually it's the last snapshot in May that's the only working version on my system. Got it from snapshots.openelec.tv All the new builds don't seem to work.


Sent from my iPad using Tapatalk
Posted: 5 months 2 weeks ago by rwss #146098
rwss's Avatar
I wonder if the remote problems are related to a few brands. I've seen problems with the remote that goes along with the Samsung tv of my nephew, he also putted new battery's in the remote. The ok button was not working. On my own remote that comes with my Philips tv I don't have any problems. We both are using the latest Openelec beta.
Posted: 5 months 3 weeks ago by Roby77 #146082
Roby77's Avatar
my apologize...i was thinking that fritsch build was based on oe git master
github.com/OpenELEC/OpenELEC.tv/commits/master
Posted: 5 months 3 weeks ago by Roby77 #146081
Roby77's Avatar
reread my post i only suggested an ir receiver that work out of the box

byez
Posted: 5 months 3 weeks ago by slipx06 #146079
slipx06's Avatar
Roby77 wrote:
give a try to fritsch build

better video quality and acceleration / video scaling

forum.kodi.tv/showthread.php?tid=231955

Unfortunately my problem is still present in these builds. Crashes when playing with HW acceleration enabled.


Sent from my iPad using Tapatalk
Posted: 5 months 3 weeks ago by slipx06 #146078
slipx06's Avatar
Roby77 wrote:
give a try to fritsch build

better video quality and acceleration / video scaling

forum.kodi.tv/showthread.php?tid=231955

Unfortunately my problem is still present in these builds. Crashes when playing with HW acceleration enabled.


Sent from my iPad using Tapatalk
Posted: 5 months 3 weeks ago by lysin #146075
lysin's Avatar
Roby77 wrote:
i never experienced remote problem using hp and dell usb ir receiver on my two htpc ( chromebox and assembled pc)

if anyone have problems i suggest to buy hp ir + remote for a max amount of € 20 on ebay

now as nickr i'm using fritsch build

lol... yep, you find a problem, so just go around it until it gets bigger and annoys a lot more people.

Stupid mentality...

Don't forget only a fraction of users use beta releases. Once you get it out of beta, a lot more people will come saying that it broke their remote.

Specially in these kind of remotes that were so popular.

[Beta] OpenELEC 6.0 Beta 2 released

The OpenELEC team is proud to announce its 2nd Beta of OpenELEC 6.0. Internally this will be known by the less-catchy name OpenELEC 5.95.2.

The OpenELEC 5.95 release series are test releases (beta) for OpenELEC-6.0.
OpenELEC-6.0 will be the next stable release, which is a feature release and the successor of OpenELEC-5.0.

The most visible change is the update from Kodi-14.2 Helix to Kodi-15.0 Isengard (beta 2). Beginning with Kodi-15 most audio encoder, audio decoder, PVR and visualisation addons are no longer included in our base OS, but they are available via Kodi's addon manager and must be installed from there, if needed. Our own PVR backends such as VDR and TVHeadend will install needed dependencies automatically. Other than that, please refer to http://kodi.tv/kodi-15-0-isengard-beta-2/ to see all the changes in Kodi-15.

Read more ...


Posted: 6 months 3 weeks ago by nickr #143923
nickr's Avatar
Because the raspberry pi has access to this hardware function via pretty open access to the SOC. Plus some dedicated devlopers. You want MVC - get rapsberry pi.
Posted: 6 months 3 weeks ago by rudizone #143869
rudizone's Avatar
Why does the Pi2 can play MVC and the generic builds can´t?

I realy need MVC playback in kodi, i wanna pay 100$ Addon or what ever, when it works :silly:

sry for bad english ^^
Posted: 6 months 4 weeks ago by maulbongo #143595
maulbongo's Avatar
I also got an Ubuntu installation and there also kodi 15 and all the screensavers are available.
Seems they were forgotten while building openelec?
Posted: 6 months 4 weeks ago by hefla #143577
hefla's Avatar
nickr wrote:
hefla wrote:
maulbongo wrote:
Hi folks,

Since update to 6.0 beta, my screensaver euphoria, solarwinds, plasma and vizualisation projectm are gone.
I got the legay nvidia, because I got an ion graphic card.
Before all was fine.

Is there any way to get these screensavers back? I´m on the OpenELEC-Generic.x86_64-5.95.2.tar and only have ugly screensavers :(

Does this extract from the first post help?
Beginning with Kodi-15 most audio encoder, audio decoder, PVR and visualisation addons are no longer included in our base OS, but they are available via Kodi's addon manager and must be installed from there, if needed.

Thanks, didn´t see that! :/ Doesn´t look like either the plasma or euphoria screensavers are available form there (Add-ons -> Install from repository -> All repositories -> Screensaver). Does anyone know if it´s possible to copy them from a Helix installation?
Posted: 6 months 4 weeks ago by nickr #143522
nickr's Avatar
specialists wrote:
SavellM wrote:
Any update to Kodi RC1?


same question :P

You can keep an eye on what is happening here github.com/OpenELEC/OpenELEC.tv - you'll see master is updated to RC2 a couple of days ago and that there have been commits today. Things happen when they happen.
Posted: 6 months 4 weeks ago by nickr #143514
nickr's Avatar
hefla wrote:
maulbongo wrote:
Hi folks,

Since update to 6.0 beta, my screensaver euphoria, solarwinds, plasma and vizualisation projectm are gone.
I got the legay nvidia, because I got an ion graphic card.
Before all was fine.

Is there any way to get these screensavers back? I´m on the OpenELEC-Generic.x86_64-5.95.2.tar and only have ugly screensavers :(

Does this extract from the first post help?
Beginning with Kodi-15 most audio encoder, audio decoder, PVR and visualisation addons are no longer included in our base OS, but they are available via Kodi's addon manager and must be installed from there, if needed.
Posted: 6 months 4 weeks ago by hefla #143513
hefla's Avatar
maulbongo wrote:
Hi folks,

Since update to 6.0 beta, my screensaver euphoria, solarwinds, plasma and vizualisation projectm are gone.
I got the legay nvidia, because I got an ion graphic card.
Before all was fine.

Is there any way to get these screensavers back? I´m on the OpenELEC-Generic.x86_64-5.95.2.tar and only have ugly screensavers :(
Posted: 7 months 2 days ago by Fantasticn #143317
Fantasticn's Avatar
LDDD wrote:
Well, thank. Unfortinately all of them still have the problem of not booting on the iMac as described above. So I am still stuck with nerdcamps version as of June 4th (only version I found that is booting fine and has at least Kodi 15 Beta 1).
Posted: 7 months 3 days ago by h3ld3rkid #143285
h3ld3rkid's Avatar
It's out version 6 for rasp2?
Posted: 7 months 3 days ago by corb06 #143267
corb06's Avatar
Yeah I was also wondering about the RC version.
Posted: 7 months 3 days ago by lovetheshirt #143232
lovetheshirt's Avatar
SavellM wrote:
Any update to Kodi RC1?

I just asked the same question :)
Posted: 7 months 4 days ago by SavellM #143213
SavellM's Avatar
Any update to Kodi RC1?
Posted: 7 months 6 days ago by DDD #143106
DDD's Avatar
Debug.Logs?
Posted: 7 months 6 days ago by Pienoet #143100
Pienoet's Avatar
I saw with the update the libcec is updated to 3.0.
With this update the connection with cec is very bad on my cubox -i4 pro.
Everytime when i shutdown my samsung the connection with cec is lost and when turn my tv on it is getting harder to get connection with cec then when in beta 1.
Sometimes i have to press a couple of times on my tv remote to get connection or i have to reboot a couple of times.
Posted: 7 months 1 week ago by Klaus Heynen #143065
Klaus Heynen's Avatar
Hi,
It seems the VCN addin is not working anymore.
Dispmanx is not starting at all.
Did anybody got VNC runing or did find a workaround ?
Cheers Klaus
Posted: 7 months 1 week ago by LordFz #142972
LordFz's Avatar
hi,

i have a strange problem with my remote : the "OK" Buttom does'nt work with 6.x releases but if i run 5.x still working fine.

IRW :
OpenELEC (official) Version: 5.95.2
OpenELEC:~ # irw
1c 0 KEY_ENTER devinput
1c 0 KEY_ENTER_UP devinput
1c 0 KEY_ENTER devinput
1c 0 KEY_ENTER_UP devinput
1c 0 KEY_ENTER devinput
1c 0 KEY_ENTER_UP devinput
[    1.461560] input: PHILIPS MCE USB IR Receiver- Spinel plusf0r ASUS as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.5/6-1.5:1.0/0003:0471:206C.0001/input/input6

here the log : sprunge.us/WVMM
Posted: 7 months 1 week ago by jumbleknot #142856
jumbleknot's Avatar
Does anyone know if the HD Audio passthrough issue (audio dropouts every couple of minutes on DTS HD or Dolby HD tracks) will be resolved for the imx6 platform in OpenElec 6? I am currently running OpenElec 5 on a Cubox i4 Pro connected to a Marantz sr7007 via HDMI, and this is my only complaint. Great piece of software!
Posted: 7 months 1 week ago by _Manfred_ #142808
_Manfred_'s Avatar
Dear OpenELEC-Team,

I have an Debian Server Jessie with Kodi 15 Beta 2 installed. This machine is an ASROCK N3700 and used as Kodi Server. Via Upnp I share Videos. Since upgrade of my Raspberry PI2 to OPENELEC 6.0 BETA 2 the RPI2 can´t reach the Kodi Server anymore.
Another Windows 7 Client with Kodi reaches the Server via Upnp (14.2/15 Beta 2).

The logfiles from the RPI2 and the Kodi Server you can find under:
sprunge.us/DXYT
sprunge.us/MOMH

Thanks for Support!

Regards
Manfred
Posted: 7 months 1 week ago by levi.baker88 #142799
levi.baker88's Avatar
levi.baker88 wrote:
Posted on Kodi.tv also:

I am experience an issue with both beta 1 and 2 where recently added media would not be shown in my libraries. I have 'Update Library on Startup' enabled but had to manually search for new content via the context menu on all my media sources for it to be found. No issue with kodi 14.X.

I am using Windows Network (SMB) to file share over 5GHz AC Wireless.

Debug url:

sprunge.us/gQPK


**1st response:
Cold you try 2 things, please:

1. enable "wait for network"-option in Openelec settings
2. try using Confluence as a skin, to be sure, the issue isn't skin related.

**My response:
Okay, I acquired another movie for testing with the following results:

1. Enabled this setting, all it did was prolong OpenELEC booting and still didn't update the library unless I went to the source and scanned for new content.
2. Yes, Confluence is the current skin.
levi.baker88 wrote:
levi.baker88 wrote:
Jocke.Sve wrote:
Have You tried "XBMC Library Auto Update" Add-On?
addons.kodi.tv/show/service.libraryautoupdate/
This works fine for my RPi2's anyway (NAS with SMB wired connection)

No I haven't as I never needed that add-on with 14.XX. I can try though.

Well, it seems this has magically fixed itself haha. I will get another debug log up for comparison soonish.

This is working beta 2 debug.log:

sprunge.us/gJVX
Posted: 7 months 1 week ago by Fantasticn #142786
Fantasticn's Avatar
sraue wrote:
Fantasticn wrote:
Tried OpenElec 6.0 Beta 2 on my iMac 27 inch (Model: 2011, 2,7 GHZ Intel i5/AMD HD6770mobility Graphics) but it is not starting. It crashes when booting. Already had problems running Beta 1 (also crashing when booting). But now I can at least use SSH to access the system. So the problem now seems to be something else in Beta 2.

Here ist the crash-log:
pastebin.com/GGua4TAH

can you paste /var/log/Xorg.0.log ?

Hi,

I am back from vacation and here is the requested log:

pastebin.com/PpvrkWun

Thanks for your support!

Regards,

FantasticN
Posted: 7 months 2 weeks ago by littlecb #142751
littlecb's Avatar
Thank for info


รวดเร็ว ทันใจ ทุกคู่ ทุกแมต กับฟุตบอลสดวันนี้ ได้ที่นี่ บอลสดวันนี้
Posted: 7 months 2 weeks ago by TRaSH #142707
TRaSH's Avatar
they always want a full debug log not a partial log where you think the issue could be.
use the following command
cat /storage/.kodi/temp/kodi.log | pastebinit
then paste the link here to the debug log
Posted: 7 months 2 weeks ago by Purge #142706
Purge's Avatar
Beta 2 freeze every 10-20 min in video playback

sprunge.us/TRaR
Posted: 7 months 2 weeks ago by BEBER2410 #142698
BEBER2410's Avatar
Hello, Thanks for this release ..
I run with OE 6.0 beta 2 generic since one week on intel system core i5 with intel graphics.
I notice a very better picture. The colors are nearer the reality ... I think the intel driver get a lot of improvements ...
BUT !! I have one video crash (with the audio still playing). This bug was solved before V6 and I was surprise it reappears ...
Someone else notice that ?
Regards,
Beber

[Beta] OpenELEC 6.0 Beta 1 released

The OpenELEC team is proud to announce its 1st Beta of OpenELEC 6.0. Internally this will be known by the less-catchy name OpenELEC 5.95.1.

The OpenELEC 5.95 release series are test releases (beta) for OpenELEC-6.0.
OpenELEC-6.0 will be the next stable release, which is a feature release and the successor of OpenELEC-5.0.

The most visible change is the update from Kodi-14.2 Helix to Kodi-15.0 Isengard (beta 1). Beginning with Kodi-15 most audio encoder, audio decoder, PVR and visualisation addons are no longer included in our base OS, but they are available via Kodi's addon manager and must be installed from there, if needed. Our own PVR backends such as VDR and TVHeadend will install needed dependencies automatically. Other than that, please refer to http://kodi.tv/kodi-15-0-isengard-beta-1/ to see all the changes in Kodi-15.

Read more ...


Posted: 7 months 3 weeks ago by levi.baker88 #142114
levi.baker88's Avatar
I'll have a crack with beta 2 and see if the issue has gone, apparently there has been some issue with scrapers/metadata fetchers in Kodi, but possibly rectified with 15.0 beta 2.
Posted: 7 months 3 weeks ago by nickr #142103
nickr's Avatar
levi.baker88 wrote:
To be honest, I wasn't aware that you could capture that type of information in a debug report or if it was indeed an OpenELEC or Kodi issue, I'm assuming one hand talks to the other.
Now that you know, we await your log.
Posted: 7 months 3 weeks ago by levi.baker88 #142087
levi.baker88's Avatar
To be honest, I wasn't aware that you could capture that type of information in a debug report or if it was indeed an OpenELEC or Kodi issue, I'm assuming one hand talks to the other.
Posted: 7 months 4 weeks ago by nickr #141864
nickr's Avatar
levi.baker88 wrote:
Not sure if there is a particular issue thread for 5.95.

Hardware:
Intel NUC5i5RYH

Network:
SMB

Issue:
Update when well, OpenELEC booted ridiculously quick along with Kodi 15.0. All files were still and the sources were still okay, however Kodi didn't want to recognise some newly added TV Shows. I removed the original source and added again, fault still there.

Went back to OpenELEC 5.08 / Kodi 14 and those newly added TV shows were recognised upon start up.
And you give no logs of scanning not working on 5.95.1. waste of a post.
Posted: 7 months 4 weeks ago by Purge #141852
Purge's Avatar
SSH is nor working for me :

A start job is running for OpenSSH server daemon (1min30sec)
is displaying at boot. After 90 sec openelec starts

And after that i cant connect via ssh : connection refused

I try to set "wait for connection on boot" but that dont work for me.

Is there a way to get ssh going ? or is there another way to get accesses to /etc ? I need that for my hyperion.config.json

EDIT

Sorry ,after rebooting my PC (not HTPC) everything works fine :whistle:
Posted: 8 months 1 day ago by levi.baker88 #141755
levi.baker88's Avatar
Not sure if there is a particular issue thread for 5.95.

Hardware:
Intel NUC5i5RYH

Network:
SMB

Issue:
Update when well, OpenELEC booted ridiculously quick along with Kodi 15.0. All files were still and the sources were still okay, however Kodi didn't want to recognise some newly added TV Shows. I removed the original source and added again, fault still there.

Went back to OpenELEC 5.08 / Kodi 14 and those newly added TV shows were recognised upon start up.
Posted: 8 months 4 days ago by wwessel #141615
wwessel's Avatar
wileecoyote wrote:
I updated one of my chrome boxes, whenever I take it out of standby the fan runs full blast. I have to reboot to fix. Has anyone else experienced this?

The same behaviour here on my Asus Chromebox. The fan speed goes down after a few minutes or after reboot.
Posted: 8 months 5 days ago by fazzer #141494
fazzer's Avatar
fazzer wrote:
Has the UPnP problem on the Raspberry Pi 2 been fixed with this version?

Sorry I should have been more specific. The issue relates to the UPNP server shutting down after a period of time. Also on startup the UPnp server won't start up and you have to select upnp off and then on in the settings (but eventually it will witch itself off again)

openelec.tv/forum/134-usage/75765-upnp-not-working-on-raspberry-pi-2#138449
Posted: 8 months 6 days ago by Fantasticn #141468
Fantasticn's Avatar
Im getting this as an answer

Linux OpenELEC 4.0.4 #1 SMP Tue May 19 10:49:18 CEST 2015 x86_64 GNU/Linux

Seems I am on 4.0.4 now.
Posted: 8 months 6 days ago by nickr #141467
nickr's Avatar
There has been a move from linux kernel 4.0.2 to 4.0.4, or something like that. What kernel do you have (uname -a should tell you).
Posted: 8 months 6 days ago by Fantasticn #141465
Fantasticn's Avatar
nickr wrote:
nickr wrote:
There are nightlies I'm sure. Not sure where to find them though.
there are references to updated versions here forum.kodi.tv/showthread.php?pid=2022490#pid2022490

Thanks very much for the link. I tried

OpenELEC-Generic.x86_64-6.0-devel-20150604234527-r20968-g3b284eb

provided by Krautmaster and it seems to be working just fine. OpenElec startet and after re-installing PVR-client everything is operating. Whatever fix has been included in that built, I hope it will also be included in the next official release.

Best regards,

FantasticN
Posted: 8 months 6 days ago by flipside #141449
flipside's Avatar
chewitt wrote:
leripe wrote:
Yeps, smb doesn't work as good as nfs. And what I understand is that nfs is better anyhow.

I'm feeling pedantic tonight. SMB and NFS are both mature and performant protocols and neither is "better" than the other. If an issue is resolved by switching from one to the other the problem is/was a shitty network, not the protocol.

turns out @chewitt was absolutely correct , an update by Synology had caused samba to crash when the inbuilt VPN client was set to auto reconnect
Posted: 8 months 6 days ago by nickr #141448
nickr's Avatar
nickr wrote:
There are nightlies I'm sure. Not sure where to find them though.
there are references to updated versions here forum.kodi.tv/showthread.php?pid=2022490#pid2022490
Posted: 8 months 6 days ago by nickr #141444
nickr's Avatar
Openelec mounts every partition on local disks by default, so the OSX partition will be getting mounted.
Posted: 8 months 1 week ago by Fantasticn #141427
Fantasticn's Avatar
I do have an OSX partition that I can boot from as an alternative. That was one of the benefits of the tutorial that I was following to get OpenElec installed on the iMac. However, I am not using it at all. I keep it "just in case". But the relevant partition for OpenElec is EXT3.

Brgds,

FantasticN
Posted: 8 months 1 week ago by nickr #141418
nickr's Avatar
There are nightlies I'm sure. Not sure where to find them though.
Posted: 8 months 1 week ago by nickr #141413
nickr's Avatar
So you don't have an OSX partition at all?
Posted: 8 months 1 week ago by Fantasticn #141412
Fantasticn's Avatar
nickr wrote:
Looks like a kernel crash alright. I can't find anything on a quick look, but a search of some kernel mailing lists or something may detect a problem peculiar to iMacs perhaps, and then perhaps the team can fix it for the next beta (you do realise this is beta software?)

Hi nickr,

thank you very much for your reply and your investigation into the problem. Yes, I know OpenElec 6.0 is beta. But the idea behind is to try it out and report errors, isn't it? That is exactly what I am doing, hoping that you guys may find a solution maybe for the next built :-) If you have something like a nightly version that I should try out I am absolutely willing to do it. I can also get the logs another time (if that helps) because they might have expired since the last time I uploaded them in the other post.

As to the file-system: It should be EXT3. I was follwing these instructions when setting up OpenElec on the iMac:

openelec.tv/forum/66-multiboot/69349-dual-boot-osx-with-mac-mini-2012

I think the iMac is relying on regular notebook-hardware (mobile i5, ATi/AMD mobilty etc.). So maybe the problem does not only affect Macs, but other PCs with similar hardware as well.

One again thank you for your support!

FantasticN
Posted: 8 months 1 week ago by nickr #141409
nickr's Avatar
Thinking further, I haven't seen a problem like this reported eslewhere, so let's look for something peculiar to Mac. I see from the crash message that hfsplus module is loaded, that is a OSX filesystem, and most people (with non Mac hardware) would be unlikely to have an hfs partition and wouldn't load that module. So my suspicions would point there.

But this is only a guess and I am not sure how to turn off loading that module to test.
Posted: 8 months 1 week ago by nickr #141408
nickr's Avatar
Fantasticn wrote:
I am deseprately trying to update OpenElec on my iMac 27". All versions 5.0.x were running just fine. But upgrading to 5.95.1 does fail. Exact description can be found here

openelec.tv/forum/110-update-openelec/76832-openelec-6-0-beta-on-imac-27inch-not-booting

Attached find the screenshots, showing where the iMac hangs when booting (on-screen logging activated).

My problem is, that I have been able to upgrade all other media pcs in my network but not the iMac. Since OpenElec 5.95.1 does use a different databse number I am ot able to share the database anymore via MySQL. So I have to find a way to upgrade the iMac or have all other media pcs dowgrade again.

Thanks for any help!

FantasticN
Looks like a kernel crash alright. I can't find anything on a quick look, but a search of some kernel mailing lists or something may detect a problem peculiar to iMacs perhaps, and then perhaps the team can fix it for the next beta (you do realise this is beta software?)
Posted: 8 months 1 week ago by bledd #141375
bledd's Avatar
powerarmour wrote:
bledd wrote:
Doesn't NFS have less overhead, so it's easier for the Pi to handle it, I know with the Pi, my media experience was far nicer with NFS over SMB.

Not really, SMB worked fine on a 33Mhz 486, as previously said it's not the protocol it's the layout of the network.

Makes an interesting read on the topic..

openelec.tv/forum/124-raspberry-pi/66123-benchmark-smb-vs-ftp-vs-nfs


Seems the lower CPU usage is where the main benefit for using NFS lies. Along with a 'slight' increase in speed.
Posted: 8 months 1 week ago by Fantasticn #141356
Fantasticn's Avatar
Sorry. Posting was duplicated somehow.
Posted: 8 months 1 week ago by Fantasticn #141355
Fantasticn's Avatar
I am deseprately trying to update OpenElec on my iMac 27". All versions 5.0.x were running just fine. But upgrading to 5.95.1 does fail. Exact description can be found here

openelec.tv/forum/110-update-openelec/76832-openelec-6-0-beta-on-imac-27inch-not-booting

Attached find the screenshots, showing where the iMac hangs when booting (on-screen logging activated).

My problem is, that I have been able to upgrade all other media pcs in my network but not the iMac. Since OpenElec 5.95.1 does use a different databse number I am ot able to share the database anymore via MySQL. So I have to find a way to upgrade the iMac or have all other media pcs dowgrade again.

Thanks for any help!

FantasticN
Posted: 8 months 1 week ago by levi.baker88 #141293
levi.baker88's Avatar
I'm pretty keen on updating to 5.95 so that I can use Kodi 15.0, I'm only using the basic functions of OpenELEC/Kodi on my 5th Gen NUC.

I don't foresee there being any problems as the hardware is all new and generic so to speak. Is anyone currently running 5.95 on a 5th Gen NUC? I tried searching to no avail.
Posted: 8 months 1 week ago by Foodog #141249
Foodog's Avatar
Lenovo Keyboard works but the TrackPoint mouse is sluggish to the point of physically hurting a finger!! PIA for Openelec V.1.05 fails completely. Hopefully this will be corrected either by the author or Openelec, I have 15 systems running with just renewed year long subscriptions on 11 of them so we cannot upgrade to 6.01. Fortunately it is a Beta hopefully corrections will be made in future Beta..

OpenELEC 5.0.7 Released

The OpenELEC team is proud to announce OpenELEC 5.0.7.

OpenELEC-5.0 is the next stable release, which is a feature release and the successor of OpenELEC-4.2.

The headline change is the update from XBMC 13 (Gotham) to Kodi 14.2 (Helix) and the big switch from XBMC to Kodi branding. Both project teams have conducted a major find/replace but if you spot residual mentions of XBMC anywhere please let us know. The name change affects more than the GUI; all references in code have been changed and in the OpenELEC filesystem /storage/.xbmc will be recreated as a symlink to /storage/.kodi to ensure hardcoded paths in addons or scripts continue to work. For information on Kodi 14 you can find on http://kodi.tv/kodi-14-0-helix-unwinds/.

Due to the potential for typo-bugs and breakage from Kodi renaming YOU ARE STRONGLY ADVISED TO MAKE A FULL BACKUP before performing a manual update and perform a “Reset System Settings to defaults (Soft Reset)” after the update if you update directly from OpenELEC-4.x or earlier.

Please note many addons and skins remain to be ported by their developers. This is out of our control and until this happens, they will either not work or be marked as broken by Kodi. If an addon or skin is essential to you, please confirm with its developer prior to upgrade if it is compatible with Kodi (Helix).

Read more ...


Posted: 7 months 3 days ago by lovetheshirt #143231
lovetheshirt's Avatar
Yes, I am using 5.0.8 it's great.

Any ideas when we are going to see Kodi 15 RC1? They have it launched on other platforms.
Posted: 8 months 2 weeks ago by nickr #140773
nickr's Avatar
Mysteriously 5.0.8 never had a formal announcement, but it exists. Use 5.0.8.
Posted: 8 months 2 weeks ago by spjsche #140772
spjsche's Avatar
Wonderful product, but I cannot locate version 5.0.7 anywhere, I can certainly find 5.0.8 for download.
Perhaps a typo somewhere...
Posted: 9 months 2 weeks ago by JSL #138633
JSL's Avatar
Hi All..

Getting super weird crashes didn't use to get any before upgrading to 5.0.8

Please help if possible..
18:34:10 T:139770575447808  NOTICE: COutput::OnStartup: Output Thread created
18:34:10 T:139771698186112  NOTICE: VAAPI::Close
18:34:10 T:139770368624384  NOTICE: COutput::OnExit: Output Thread terminated
18:40:38 T:139770385409792 WARNING: CDVDMessageQueue(video)::Get - asked for new data packet, with nothing available
18:40:38 T:139770377017088 WARNING: CDVDMessageQueue(audio)::Get - asked for new data packet, with nothing available
18:41:01 T:139771112318720   ERROR: Read - Error( -1, 22, Invalid argument ) - Retrying
18:41:23 T:139771112318720   ERROR: Read - Error( -1, 22, Invalid argument )
18:41:23 T:139771112318720  NOTICE: CDVDPlayer::OnExit()
18:41:23 T:139771112318720  NOTICE: DVDPlayer: eof, waiting for queues to empty
18:41:23 T:139771112318720  NOTICE: Closing stream player 1
18:41:23 T:139771112318720  NOTICE: CDVDMessageQueue(audio)::WaitUntilEmpty
18:41:23 T:139771112318720  NOTICE: Waiting for audio thread to exit
18:41:23 T:139770377017088  NOTICE: thread end: CDVDPlayerAudio::OnExit()
18:41:23 T:139771112318720  NOTICE: Closing audio device
18:41:23 T:139771112318720  NOTICE: Deleting audio codec
18:41:23 T:139771112318720  NOTICE: Closing stream player 2
18:41:23 T:139771112318720  NOTICE: CDVDMessageQueue(video)::WaitUntilEmpty
18:41:23 T:139771112318720  NOTICE: waiting for video thread to exit
18:41:23 T:139770385409792   ERROR: Got MSGQ_ABORT or MSGO_IS_ERROR return true
18:41:23 T:139770385409792  NOTICE: thread end: video_thread
18:41:23 T:139771112318720  NOTICE: deleting video codec
18:41:23 T:139771112318720  NOTICE: Thread BackgroundLoader start, auto delete: false
18:41:23 T:139771698186112  NOTICE: CDVDPlayer::CloseFile()
18:41:23 T:139771698186112  NOTICE: DVDPlayer: waiting for threads to exit
18:41:23 T:139771698186112  NOTICE: DVDPlayer: finished waiting
18:41:23 T:139771698186112  NOTICE: VAAPI::Close

I assume you only need the Kodi log? If you need anything else please advise..
Posted: 9 months 3 weeks ago by mentat #138370
mentat's Avatar
Brian B wrote:
It seems there is a newer 5.0.8 or .9. Are these imminent? That is, should I wait another week or two?

B.

OpenELEC 5.0.8 has been available for device update and from the download section for just over 2 weeks now (just no release announcement posted).

It's been working great (for me) on my RPi2 device.
Posted: 9 months 3 weeks ago by Brian B #138366
Brian B's Avatar
It seems there is a newer 5.0.8 or .9. Are these imminent? That is, should I wait another week or two?

B.
Posted: 9 months 3 weeks ago by DDD #138327
DDD's Avatar
Backup your 421 and try it
Posted: 9 months 3 weeks ago by Brian B #138307
Brian B's Avatar
So is it finally safe to upgrade from 4.2.1 or "if it ain't broke don't fix it?"

B.
Posted: 9 months 3 weeks ago by JSL #138189
JSL's Avatar
DDD wrote:
copy 506 zip in your update share and reboot.
if you don't provide logs and infos about your system, this issue maybe never can be fixed.

Would love to grab the logs to share.. If you're able to let me know which log files the info would be in.. I am really new to the openlec world..
Posted: 9 months 3 weeks ago by DDD #138185
DDD's Avatar
copy 506 zip in your update share and reboot.
if you don't provide logs and infos about your system, this issue maybe never can be fixed.
Posted: 9 months 3 weeks ago by JSL #138184
JSL's Avatar
I am on 5.0.8 and it is still getting random playback freezes.. The screen will freeze but the audio continues.. if i hit stop the system will be completely frozen.. never had this problem in 5.0.6

How do I go back to 5.0.6 without reinstalling? (hoping there is a way)
Posted: 9 months 4 weeks ago by Sanjeev #138018
Sanjeev's Avatar
Hi, Thanks & Congrats!
Is Cinema Experience compatible with default skin- Confluence, in this version.
Regards
Posted: 9 months 4 weeks ago by spinmaster #137962
spinmaster's Avatar
doug wrote:
5.0.8 hardly changed anything from 5.0.7. Probably not worth the effort.

Even if the changelog is (very) small - it still makes sense to announce it on the news page. This is were most people look first - and they get confused when a different version is available for download which is not (yet) listed on the frontpage.
Posted: 9 months 4 weeks ago by popcornmix #137851
popcornmix's Avatar
DDD wrote:
So then in 5.0.9 it should be fixed?
The hvs_priority issue? Was fixed in firmware here, so as long as OE bumps the firmware (they usually do) it will be in next release.
Posted: 10 months 1 hour ago by doug #137779
doug's Avatar
5.0.8 hardly changed anything from 5.0.7. Probably not worth the effort.
Posted: 10 months 4 hours ago by Telgar #137763
Telgar's Avatar
I am surprised not to find the info anywhere so I'll dare ask the obvious: why is there no announcement (and thread on) of the new 5.0.8 release ?
Posted: 10 months 5 hours ago by DDD #137757
DDD's Avatar
So then in 5.0.9 it should be fixed?
Posted: 10 months 6 hours ago by gda #137753
gda's Avatar
DDD wrote:
in what OE version this hvs_Priority would be fixed in? 5.0.8?
Look at this post, with 5.0.8 he had the problem and fixed it afterwords.

Gerald
Posted: 10 months 11 hours ago by DDD #137726
DDD's Avatar
in what OE version this hvs_Priority would be fixed in? 5.0.8?
Posted: 10 months 2 days ago by sfnava #137603
sfnava's Avatar
Many thanks popcorn mix, now it works like a charm.
Posted: 10 months 4 days ago by popcornmix #137453
popcornmix's Avatar
Does adding "hvs_priority=0x32fc" to config.txt fix it?
Posted: 10 months 4 days ago by sfnava #137449
sfnava's Avatar
Since upgrading to 5.0.7 and now to 5.0.8 on a Raspberry Pi 2, it appears that the video signal is randomly lost for a split second while watching streamed video from the internet.

---> Same problem on Raspberry 2 watching live TV OE 5.0.7 and 5.0.8 It seems that only happened on HD Channels but not in SD Channels or HD/SD Movies .
Posted: 10 months 6 days ago by Hawke84 #137345
Hawke84's Avatar
anyone else getting problems with network shares after resume from standby? openelec.tv/forum/69-network/75853-openelec-5-0-5-no-network-shares-after-resume
Posted: 10 months 1 week ago by GemNEye #137167
GemNEye's Avatar
For X86 releases there is an unofficial Chromium browser addon that can be used if you have enabled the Advanced OE repository.

OpenELEC 5.0.6 released

The OpenELEC team is proud to announce OpenELEC 5.0.6.

OpenELEC-5.0 is the next stable release, which is a feature release and the successor of OpenELEC-4.2.

The headline change is the update from XBMC 13 (Gotham) to Kodi 14.2 (Helix) and the big switch from XBMC to Kodi branding. Both project teams have conducted a major find/replace but if you spot residual mentions of XBMC anywhere please let us know. The name change affects more than the GUI; all references in code have been changed and in the OpenELEC filesystem /storage/.xbmc will be recreated as a symlink to /storage/.kodi to ensure hardcoded paths in addons or scripts continue to work. For information on Kodi 14 you can find on http://kodi.tv/kodi-14-0-helix-unwinds/.

Due to the potential for typo-bugs and breakage from Kodi renaming YOU ARE STRONGLY ADVISED TO MAKE A FULL BACKUP before performing a manual update and perform a “Reset System Settings to defaults (Soft Reset)” after the update if you update directly from OpenELEC-4.x or earlier.

Please note many addons and skins remain to be ported by their developers. This is out of our control and until this happens, they will either not work or be marked as broken by Kodi. If an addon or skin is essential to you, please confirm with its developer prior to upgrade if it is compatible with Kodi (Helix).

Read more ...


Posted: 10 months 2 weeks ago by madas #136464
madas's Avatar
I'm using a Cubox i4 and my boot problem is back. I was running the DEV build from 22nd Feb and everything was fine. I upgraded to 5.0.6 and now when the Cubox boots up my tv just flashes every 10 seconds but stays black. If I disable CEC on my TV the box boots ok, then once it has booted I can re-enable CEC and everything is fine (till the next boot). Reverted back to Dev build from 22nd Feb and its all fine again.

TV is a Samsung UN55ES7150

Anyone else experience this? I see some references above to a CEC error but i'm not sure which error they are referring to.
Posted: 10 months 2 weeks ago by seo #136381
seo's Avatar
jack33978 wrote:
how do i update to new kodi.i dont see anything for g-box mx2

you wont see anything about gbox mx2. go ask for support somewhere else.
Posted: 10 months 2 weeks ago by jack33978 #136358
jack33978's Avatar
Im not a complier of any sorts.or i would give it a shot at making my own linux for the g-box mx2..if any body can help me here..very thankful
Posted: 10 months 2 weeks ago by jack33978 #136357
jack33978's Avatar
how do i update to new kodi.i dont see anything for g-box mx2
Posted: 10 months 3 weeks ago by squarooticus #135960
squarooticus's Avatar
The changelog says "linux: Enable all buttons on the TiVo Slide Pro remote", but the select button on my remote still doesn't do anything. Is this an issue of the kernel now having support for all the buttons, but the key map in Kodi itself not having been updated?
Posted: 10 months 3 weeks ago by MajorTom1352 #135750
MajorTom1352's Avatar
No, my issue is not the shutdown or reboot itself, these things work as designed, even with my skin, Xperience1080.
When I initiate a shutdown (or suspend) the Cubox enters a dead state. That is normal for a shutdown, and also ok for suspend, but to wake up the box again, I have to remove the power cable and insert it again. There is no other way to get the box out of this state.

I think this can be improved by enabling the wol feature in the network driver.
Posted: 10 months 3 weeks ago by Brujo #135744
Brujo's Avatar
MajorTom1352 wrote:
Wow, that's the first time I heared that a shutdown is skin-dependent. Can you tell me more about that? I always thought that the shutdown is a Kodi functionality, not a skin funtion. So what exactly happens when you shutdown the system? Can you bring it up again without pulling the power cable? I'm very interested in having a system which does not need a physical interaction to switch it on.

So is your issue within the default skin?

To answer your question - well yes & no it looks like it have to do with the renaming of things during the change from XBMC-> Kodi and "different" functions like XBMC.Powerdown() and just Powerdown() and so on... and which function is used is defined per skin in the DialogButtonMenu.xml
(see also: forum.kodi.tv/showthread.php?tid=221575)
Posted: 10 months 3 weeks ago by MajorTom1352 #135724
MajorTom1352's Avatar
Wow, that's the first time I heared that a shutdown is skin-dependent. Can you tell me more about that? I always thought that the shutdown is a Kodi functionality, not a skin funtion. So what exactly happens when you shutdown the system? Can you bring it up again without pulling the power cable? I'm very interested in having a system which does not need a physical interaction to switch it on.

What I did so far is: All my devices (TV, Cubox, Receiver) have a network connection.
- I installed a linux service that pings my TV in regular intervals
- If TV is on, Kodi service is started. If TV is off, Kodi will be killed by the service

That works quite good, but is not what I want. I want a system which comes up again when I want to view a movie or whatever. I don't want a box which has network activities all the time just to see if someone has switched on another device.

I guess it's just a small step to hit that target, nearly everything is prepared...
Posted: 10 months 3 weeks ago by rays #135680
rays's Avatar
Try all last released 5.0.x on raspberry PI2
thanks for 5.0.6 release but always same problem to enter manual IP4 address and save the settings.
I can change dhcp to manual and then enter correct ip, netmask, gateway, dns. If i save the configuration dhcp always appaears on the openelec program settings.
Is there a specific order to enter informations in different fields to definitely enter in manual ip configuration ?
thanks for help if a workaround is founded.
Posted: 10 months 3 weeks ago by Brujo #135666
Brujo's Avatar
MajorTom1352 wrote:
Thank you very much for your hard work, this is an awesome piece of software!
Just a question: I have a cubox i4 pro, which works very well for me. There are just 2 issues left for me. One is the CEC bug, which is already in the issue list and the other one is the shutdown issue. When I select to shutdown or suspend the box, it enters a dead state, a powercyle is the only way to bring the box up again, that's clear so far. I was wondering if the WOL feature could help here. In the cubox forum, they said that the hardware is prepared for WOL. Correct me if I'm wrong, but the only thing that keeps the box from a proper wakeup is the network driver, which does not support WOL. Is there a chance in the near future that this feature will be implemented in the driver?

let me guess you do not use the default skin - I faced the shutdown / reboot issue when not using Confluence
Posted: 10 months 3 weeks ago by didier.bastogne #135619
didier.bastogne's Avatar
Hi,

it works fine on my CuboxTv and the VDR VNSI server seems more stable but it completely break my raspberry Pi B system, it rebooted many time during the update process (update from 5.0.5 to 5.0.6) and then finally started on 5.0.6 but when I see the kodi 14.2 RC2 logo, kodi crash and restart..

I'll try to rebuild my rpi on an old version or a fresh install of 5.0.6

Didier B
Posted: 10 months 3 weeks ago by MajorTom1352 #135612
MajorTom1352's Avatar
Thank you very much for your hard work, this is an awesome piece of software!
Just a question: I have a cubox i4 pro, which works very well for me. There are just 2 issues left for me. One is the CEC bug, which is already in the issue list and the other one is the shutdown issue. When I select to shutdown or suspend the box, it enters a dead state, a powercyle is the only way to bring the box up again, that's clear so far. I was wondering if the WOL feature could help here. In the cubox forum, they said that the hardware is prepared for WOL. Correct me if I'm wrong, but the only thing that keeps the box from a proper wakeup is the network driver, which does not support WOL. Is there a chance in the near future that this feature will be implemented in the driver?
Posted: 10 months 3 weeks ago by sabamimi #135495
sabamimi's Avatar
Thx for this Release!
Keep up your work!
Most stable Release since 4.2.1 for BYT Users.

+1
Thanks
Posted: 10 months 3 weeks ago by fetterbr #135418
fetterbr's Avatar
borisnanev wrote:
The problem with CEC driver disconnect when TV is switched off still exist.

same here, i thought it was my tv.. but i can see after i reboot kodi it connects and than a few second later says disconnect
Posted: 10 months 4 weeks ago by borisnanev #135380
borisnanev's Avatar
The problem with CEC driver disconnect when TV is switched off still exist.
Posted: 10 months 4 weeks ago by NetMan939 #135362
NetMan939's Avatar
Thank you :cheer:
Posted: 10 months 4 weeks ago by inspector71 #135349
inspector71's Avatar
Woohoo, found the changelog. Thanks!
Posted: 10 months 4 weeks ago by Nick #135325
Nick's Avatar
Thx for this Release!
Keep up your work!
Most stable Release since 4.2.1 for BYT Users.
Posted: 10 months 4 weeks ago by mhoogenbosch #135307
mhoogenbosch's Avatar
and as ever, the update installed fine :) running smooth on two machines.
Posted: 10 months 4 weeks ago by nickr #135296
nickr's Avatar
Thanks, keep up the good work!
Posted: 10 months 4 weeks ago by magy77 #135251
magy77's Avatar
Best release for a long time! Keep going
Posted: 10 months 4 weeks ago by Guido.e #135248
Guido.e's Avatar
Looks to be running stable on rpi2 with Samsung 16gb evo 10 class (for now).
Posted: 10 months 4 weeks ago by DDD #135240
DDD's Avatar
thanks

Advertisement