• 1
  • 99
  • 100
  • 101(current)
  • 102
  • 103
  • 495
v18 LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)
(2017-04-14, 07:30)nuwonda Wrote:
(2017-04-12, 18:22)nuwonda Wrote:
(2017-04-11, 21:45)Leopold Wrote: I posted about a CEC problem. Is anyone else having the same issue? It seems this commit might be the culprit.

did anyone check if this commit is the actual culprit for the current cec problem? i.e. not being able to wake up kodi from dimmed state with tv remote, but works with phone app after which tv remote works again.

I went back to 314 and indeed, CEC is working there. This would support your finding that (some part of) the libcec commit in 315 broke it.

(2017-04-21, 00:23)bill_orange Wrote:
(2017-04-11, 17:58)bill_orange Wrote:
(2017-04-11, 17:39)nuwonda Wrote: nobody else has issues since a few builds waking up kodi from dimmed state with tv remote? I constantly have to use my phone app to wake up Kodi, after that tv remote works again, i am not sure when it started though, has been a while like that, possibly since 32x builds.

You are not alone. I often wake Kodi with Alexa. Alexa sends a JSON string, After that, the remote does not work, unless I reboot, with the TV and Receiver already awake. I noticed the problem about 1-1/2 weeks ago. It is so had to regress that I hoped someone else would tackle it. I would have to cycle TV and receiver off and on repeatedly to the annoyance of my wife.

As a stop gap I have been waking on Kodi by asking Alexa to reboot, twice. First time everyone is awake with no remote. Second time remote works.

Same for you?

Were these issues ever addressed? I still have the same minor CEC problem with build #419.

Not that I know of. I opened an issue in regards to the libcec commit in question (in build 315) on github as well: https://github.com/Pulse-Eight/libcec/issues/342

I am using #314 for now.
After being spared of having CEC issues after all the CEC refactoring lately, unlike some of you, I'm now having to report one as well.

My TV would normally switch back to Kodi as source when turning off my TV (power or standby), followed by turning it on again before the issue was introduced. Now this doesn't happen anymore, forcing my to switch manually every time. Since Kodi is my primary viewing channel, this basically comes down to every time I use the TV.
The slightly odd thing is that entering the AV selection menu on the TV is already enough to make it switch source. The HDMI channel for Kodi will already be selected, so either pressing the back button or the OK button will do the trick, just to make the menu go away.

I've narrowed it down to build #0315 being the first which has the issue, which just so happens to have libcec changes as well. Has anyone else experienced any similar issues?

... Forget that last question, the answer is just one post ahead of me... Consider it a confirmation then, and I'll be joining the conversation in the subsequent tickets. (@Leopold) I created a new libcec ticket since one similar had not been reported yet.
(2017-04-20, 13:16)ElectricPim Wrote: @millhouse, @popcornrmix, could you reproduce them in my recorded pvr ts file?
http://forum.kodi.tv/showthread.php?tid=...pid2572514

Yes. The key difference is when audio is good the codec overlay info shows "rr:1.00" and when audio is bad it shows "rr:0.96" (approximately).
Something is making VideoPlayer think resampling is required when it isn't, resulting in the decoded audio frames having discontinuities.

I need to see if I can reproduce on a generic build (e.g. Ubuntu) so I can report this up the chain.
New LibreELEC.tv Leia build #0421: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.10.11 #1 Fri Apr 21 21:05:45 BST 2017 armv6l GNU/Linux

# vcgencmd version
Apr 19 2017 13:34:02
Copyright (c) 2012 Broadcom
version e49fda6e8d837fd3cbac4900a141dd7fba7ca3e3 (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20170421210355-#0421-g09a540d [Build #0421]

# Kodi version
(18.0-ALPHA1 Git:78cce57). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (09a540d8, changelog) and tip of XBMC master (09e730d5, changelog) with the following modifications: Build Highlights:
  1. Minors
Build Details:
  1. LibreELEC.tv:
    • dvb-tools: update (PR:1550, 2 commits, 9 files changed)
  2. XBMC:
    • [addon] remove all windows.h includes (PR:11977, 1 commit, 9 files changed)
    • FIXUP: select first unwatched broken after select by url (PR:11989, 1 commit, 1 file changed)
    • [PVR] CPVREpgContainer now uses CPVRSettings. (PR:11991, 1 commit, 2 files changed)
    • FIX: [droid] remove dependency on android-support-v4.jar (PR:11994, 1 commit, 3 files changed)
  3. Additional commits/pull requests/changes not yet merged upstream:
    • Added: [env] PR:1552: connman: fix ipv4 IP Forwarding bug
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Having upgraded to #201 (being the last LE 8 build) I've run into the problem of TVheadend no longer recognising my tuner again, which seems to happen most of the time whenever I upgrade and makes me very hesitant to upgrade my brother's installation as he relies on TVheadend.

lsusb shows the device is detected.

Bus 001 Device 005: ID 1b80:e409 Afatech IT9137FN Dual DVB-T [KWorld UB499-2T]
Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 046e:5577 Behavior Tech. Computer Corp.
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

but the GUI under Configuration - DVB Inputs - TV Adapters shows nothing under the TV Adapters folder.

I couldn't pastebin the log as it's too big due to repeated "Debug: NFS: Refreshing context for" messages, so I've uploaded it to https://drive.google.com/file/d/0B1fDI89...sp=sharing
Hi. I've uploaded crashlog from 420,421. Happens when streaming video via network.419 works fine.
It seems to do with the ffmpeg buffer increase. Not sure...
(2017-04-22, 10:51)SpokV Wrote: Hi. I've uploaded crashlog from 420,421.

Where?
With builds #0420 / #0421 Kodi crashes and restarts (see kodi_crash.log) when trying to play a 3D iso file, probably as a result of the ffmpeg buffer changes, #0419 plays correctly.

DEBUG: ffmpeg[5BDE03A0]: Assertion len >= s->orig_buffer_size failed at libavformat/aviobuf.c:535
I've used: paste $(ls -1art /storage/.kodi/temp/kodi_crashlog* | tail -1)
(2017-04-22, 13:21)SpokV Wrote: I've used: paste $(ls -1art /storage/.kodi/temp/kodi_crashlog* | tail -1)
You need to paste the link into your post.

Edit: Also, the method you're using is the one documented in the first post, which will work for all versions of LE, while more recent versions will also nsupport "paste /storage/.kodi/temp/kodi_crash.log".
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2017-04-22, 12:20)popcornmix Wrote:
(2017-04-22, 10:51)SpokV Wrote: Hi. I've uploaded crashlog from 420,421.

Where?

(2017-04-22, 13:21)SpokV Wrote: I've used: paste $(ls -1art /storage/.kodi/temp/kodi_crashlog* | tail -1)

Sorry, my bad. Here it is.crashlog
Hi,
I think found an issue.

When i want to add an video source it's impossible to see my "workgroup share" since version # 0322. (windows smb share)

I have make a clean/fresh install juste for test without any addon and until the build #0321 it works perfect i can see my "workgroup" but when i update from the #0322 impossible to see the "workgroup" (smb share)

All build i have test with fresh install before #0321 works well and all build i have test after #0322 don't shows "smb share"
Same issue with the last build #0421

I think the error comes in the build #0322 "update to samba 4.6.0"

Thank you for all your work and sorry for my bad english
(2017-04-22, 15:35)levil1 Wrote: Hi,
I think found an issue.

When i want to add an video source it's impossible to see my "workgroup share" since version # 0322. (windows smb share)

I have make a clean/fresh install juste for test without any addon and until the build #0321 it works perfect i can see my "workgroup" but when i update from the #0322 impossible to see the "workgroup" (smb share)

All build i have test with fresh install before #0321 works well and all build i have test after #0322 don't shows "smb share"
Same issue with the last build #0421

I think the error comes in the build #0322 "update to samba 4.6.0"

Thank you for all your work and sorry for my bad english

Start reading here:
2554178 (post)

Think your problem will be resolved by editing file smb.conf in /storage/.smb
Change: client max protocol = SMB3
To: client max protocol = SMB1

And restart
I am having some bluetooth issues with your build. My Amazon Fire TV Remote is paired and trusted, standby is enabled in LE but it won't reconnect. Without standby it stays connected but when I reboot my Pi, same issue.

On LE 8.0 it worked flawlessly.

This is what bluetoothctl says when I press keys on my remote[/align].

Code:
[NEW] Device 34:D2:70:67:D2:23 Amazon Fire TV Remote
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: yes
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: yes
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
[CHG] Device 34:D2:70:67:D2:23 Connected: no
New LibreELEC.tv Leia build #0422: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.10.12 #1 Sat Apr 22 23:55:32 BST 2017 armv6l GNU/Linux

# vcgencmd version
Apr 19 2017 13:34:02
Copyright (c) 2012 Broadcom
version e49fda6e8d837fd3cbac4900a141dd7fba7ca3e3 (clean) (release)

# lsb_release
LibreELEC (Milhouse) - Version: devel-20170422234258-#0422-g2fee7b3 [Build #0422]

# Kodi version
(18.0-ALPHA1 Git:78cce57). Platform: Linux ARM 32-bit

Based on tip of LibreELEC.tv master (2fee7b33, changelog) and tip of XBMC master (9d9cc247, changelog) with the following modifications: Build Highlights:
  1. New 4.10.12 kernel
  2. smsc75xx: use skb_cow_head() to deal with cloned skbs
Build Details:
  1. LibreELEC.tv:
    • linux: update to linux-4.10.11 (PR:1546, 7 commits, 9 files changed)
  2. XBMC:
    • [PVR] Search window: Fix very first search after kodi start not working. (PR:11992, 1 commit, 2 files changed)
  3. newclock5:
    • New commits in this build:
      • DVDDemuxFFmpeg: Store probe_buffer on heap (a47821b7)
    • Commits no longer in build:
      • NFSFile: Chank ChunkSize to 128K (b241696a)
      • DVDDemuxFFMPEG: Avoiding truncating max_packet_size to zero (d8a86d17)
  4. kernel 4.10.y:
    • New commits in this build:
      • smsc75xx: use skb_cow_head() to deal with cloned skbs (ab3f594e)
  5. Additional commits/pull requests/changes not yet merged upstream:
    • Added: [env] compare: linux: update to linux-4.10.12
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
  • 1
  • 99
  • 100
  • 101(current)
  • 102
  • 103
  • 495

Logout Mark Read Team Forum Stats Members Help
LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)24