Kodi Community Forum
OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166)
+---- Thread: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 (/showthread.php?tid=224025)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-05-31

(2015-05-31, 15:24)MrNice Wrote: Regarding the bug "Audio Dropout playing HD multichannel music", I still have
hdmi_mai_thresh=0x1412
in config.txt to fix it.

No. Recent firmware sets the mai threshold appropriately.

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - gendo - 2015-05-31

(2015-05-31, 10:55)illiac4 Wrote: On rpi v1 there is always warning for under voltage shown in latest version.

yep same here.. for the time being worked around it by adding avoid_warnings=2 to config.txt

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-05-31

(2015-05-31, 16:32)gendo Wrote:
(2015-05-31, 10:55)illiac4 Wrote: On rpi v1 there is always warning for under voltage shown in latest version.

yep same here.. for the time being worked around it by adding avoid_warnings=2 to config.txt

I've pushed a firmware update that I hope will fix this. Can you confirm, download:
https://github.com/raspberrypi/firmware/raw/master/boot/start_x.elf
https://github.com/raspberrypi/firmware/raw/master/boot/fixup_x.dat

and overwrite start.elf and fixup.dat from your boot partition (/flash).

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - gendo - 2015-05-31

(2015-05-31, 16:48)popcornmix Wrote:
(2015-05-31, 16:32)gendo Wrote:
(2015-05-31, 10:55)illiac4 Wrote: On rpi v1 there is always warning for under voltage shown in latest version.

yep same here.. for the time being worked around it by adding avoid_warnings=2 to config.txt

I've pushed a firmware update that I hope will fix this. Can you confirm, download:
https://github.com/raspberrypi/firmware/raw/master/boot/start_x.elf
https://github.com/raspberrypi/firmware/raw/master/boot/fixup_x.dat

and overwrite start.elf and fixup.dat from your boot partition (/flash).

fixed it thanks

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-05-31

(2015-05-31, 16:57)gendo Wrote: fixed it thanks

Thanks for testing. Should be fixed in tonight's build.

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - doveman2 - 2015-05-31

#530 still showing the same error for me http://pastebin.com/WGTSn5CD

It's obviously working for most people, so have to wonder why it's not working for me?

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-05-31

(2015-05-31, 19:46)doveman2 Wrote: #530 still showing the same error for me http://pastebin.com/WGTSn5CD

It's obviously working for most people, so have to wonder why it's not working for me?

Is this still the language issue? What have you tried so far, clean install? According to your log it seems to be PVR related, what did the maintainer of your PVR client have to say about it?

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-05-31

New OpenELEC Isengard build #0531: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.0.4 #1 Sun May 31 21:02:51 BST 2015 armv6l GNU/Linux

# vcgencmd version
May 31 2015 14:24:30
Copyright (c) 2012 Broadcom
version b127f62bd972cebb74a816b01b90ecfacc226baa (clean) (release)

# lsb_release
OpenELEC (Milhouse) - Version: devel-20150531210205-#0531-gb301e0a [Build #0531]

# vcdbg log msg 2>&1 | grep DTOK
001565.211: Kernel trailer DTOK property says yes

# Kernel device tree status: Enabled

Based on tip of OpenELEC master (b301e0ab, changelog) and tip of XBMC master (cdd0feed, changelog) with the following modifications: Build Highlights:
  1. New firmware
  2. ShaderToy screensaver and visualisation are now installable addons. Download and install the following repository ("Install from zip file"):
    Code:
    https://github.com/popcornmix/repository.popcornmix.storage/raw/master/repository.popcornmix.zip
    Once installed, click on "Check for updates" in the side/pop-out menu, then install the screensaver and/or visualisation from the repository.

    ShaderToy should work with Kodi Helix (all Pi/Pi2 distributions, not just OpenELEC). Ball and Warp screensavers may not work entirely as intended when the "[screensaver] Leave GUI contents available for screensaver" commit is not included (it's included in these test builds).
Build Details:
  1. Firmware (May 31):
    • firmware: Fix for identifying older model B Pi
  2. OpenELEC:
    • OpenELEC-settings: update to 0.6.7 (b301e0ab)
  3. XBMC:
    • revert ecea1fff0 (PR:7213, 1 commit, 2 files changed)
    • Revert "[Fix][subs] Don't try to read a vob sub file without a corres… (PR:7212, 1 commit, 1 file changed)
  4. dcadec:
    • Move WAV tag definitions to common header. (aa1f1df1)
    • Add proper _CRT_SECURE_NO_WARNINGS define. (98f60ba1)
    • Add Visual C compiler bug workaround. (1674472f)
  5. newclock4:
    • New commits in this build:
    • Commits no longer in build:
      • [visualisation] Add shadertoy visualisation (dabfe8a3)
      • [screensavers] Add new gles screensavers (e4d0e813)


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - OurJermain - 2015-05-31

Thank you Millhouse and Popcornmix and all the devs. I love this new build with shadertoy. The screensavers are so beautiful.

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - doveman2 - 2015-06-01

(2015-05-31, 20:24)Milhouse Wrote: Is this still the language issue? What have you tried so far, clean install? According to your log it seems to be PVR related, what did the maintainer of your PVR client have to say about it?

Yeah still the language issue but I don't have any PVR addons enabled, so I don't see how it can be that. The PVR addons are included with the build, so if they could cause this problem even when disabled surely it should affect everyone?

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-06-01

(2015-06-01, 00:50)doveman2 Wrote: Yeah still the language issue but I don't have any PVR addons enabled, so I don't see how it can be that. The PVR addons are included with the build, so if they could cause this problem even when disabled surely it should affect everyone?

I suspect it's something in your advancedsettings.xml - you have this:

Code:
...
                                              <locale>
                                                <audiolanguage>original</audiolanguage>
                                                <charset>DEFAULT</charset>
                                                <country>UK (24h)</country>
                                                <language>English</language>
                                                <subtitlelanguage>original</subtitlelanguage>
                                                <timezone>Europe/London</timezone>
                                                <timezonecountry>Britain (UK)</timezonecountry>
                                              </locale>

and there is this WARNING:

Code:
18:39:18  27.113977 T:1967521792 WARNING: CLangInfo: unable to load language "English". Trying to determine matching language addon...
18:39:18  27.115154 T:1967521792    INFO: CLangInfo: fall back to the default language "resource.language.en_gb"
18:39:18  27.116585 T:1967521792    INFO: CLangInfo: loading resource.language.en_gb language information...
18:39:18  27.131706 T:1967521792   DEBUG: trying to set locale to en_GB.UTF-8
18:39:18  27.163692 T:1967521792    INFO: global locale set to C
18:39:18  27.165077 T:1967521792    INFO: CLangInfo: loading resource.language.en_gb language strings...
18:39:18  27.352907 T:1967521792   DEBUG: POParser: loaded 3341 strings from file resource://resource.language.en_gb/strings.po

Try changing:
Code:
<language>English</language>
to
Code:
<language>EnglishX</language>
in your advancedsettings.xml and see what effect that has on the warning - if the warning changes to reference "EnglishX" then you know they're linked:
Code:
18:39:18  27.113977 T:1967521792 WARNING: CLangInfo: unable to load language "English". Trying to determine matching language addon...

My advice: get rid of the <locale> section from your advancedsettings.xml.

Other than that, what problem is this language issue actually causing?

Edit: Using your <locale> settings I see it causes the "Failed to load language" dialog. This is due to PR7150, added in #0525, as this includes the commit: "show the startup dialogs informing about the fallback language and the migrated userdata once the user interface is really ready for usage". Your <locale> settings in as.xml have always caused a problem prior to PR7150 - the same WARNING is there in #0524, except you'd only hear a "boing" notification sound at startup, with no dialog displayed. The difference now is that with #0525 and later you /will/ have the dialog displayed at startup (in silence, without the "boing"), informing you that your language settings are incorrect.

Solution: It appears the language setting in your <locale> section has always caused a warning, so has always been wrong (or at least, not interpreted correctly), but now Kodi is going to nag you about it... if you think your <locale> settings are correct then you should discuss this in OS Independent, or open a trac ticket.

As for the "Window Translator" errors in your log (which, for some reason, I thought were related to the issue being discussed...), they seem to be mostly PVR/video/tv related, but having thought about it some more and noticed you're not using Confluence, these are most likely being caused by your third-party skin, AppTV, so report it there (if it's a problem). Try using stock Confluence, do the "Window Translator" errors go away? I'll bet they do.

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - mcelliott - 2015-06-01

Is anyone else having trouble with MCE remotes with this new build? I updated from 524 to 531 briefly yesterday, and most of the buttons apart from the cursor buttons stopped working. System is in use by family, so I had to downgrade. Problem fixed. If needed, I can provide logs from 524 and 531 to compare.

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - slack3r - 2015-06-01

About subtitles position issue, look at these samples:

- 1st video: full frame, no black bars -

sub position:
Image

displayed result:
Image

OK, no prob, woks as expected.


- 2nd video with black bars at top and bottom -

sub position:
Image

results:
Image
Image

As you can see, sub is "locked" at the bottom of screen.
Any idea?

Thanks

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-06-01

@doveman2: Good news, PR7220 should fix the language issue - will test it later, and include in the next build.

@mcelliot: Which is the first build with this issue? Is your MCE remote using a USB IR dongle or GPIO?

@slack3r: Are you able to test with x86, to see if this is a common issue for all platforms? Or determine when the problem started? Interesting about black bars as that behaviour (cropping) changed quite a while ago, maybe this is a hangover from that?

RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - doveman2 - 2015-06-01

(2015-06-01, 11:27)Milhouse Wrote: @doveman2: Good news, PR7220 should fix the language issue - will test it later, and include in the next build.

Excellent and thanks for taking a look and giving your advice in your previous post.

To answer your question "Other than that, what problem is this language issue actually causing?", when the error appears, after I click OK to get rid of it I'm stuck on the AppTV logo so can't use it at all. You might be right that it's an issue with that skin though, so I'll test with Confluence if it still happens with the next build.