Posts by chewitt

WP2:~/.kodi/addons/metadata.themoviedb.org # head addon.xml 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<addon id="metadata.themoviedb.org"
       name="The Movie Database"
       version="5.0.3"
       provider-name="Team Kodi">
  <requires>
    <import addon="xbmc.metadata" version="2.1.0"/>
    <import addon="metadata.common.imdb.com" version="2.9.2"/>
    <import addon="metadata.common.themoviedb.org" version="2.17.6"/>
    <import addon="plugin.video.youtube" version="4.4.10" optional="true"/>
WP2:~/.kodi/addons/metadata.themoviedb.org # ls -l addon.xml 
-rw-r--r--    1 root     root         26091 Dec 15 11:30 addon.xml

^ this is from an 8.2.2 install which shows the add-on was updated on 15 December. Kodi redirects requests to their add-on repo to mirror servers so it's possible the mirror that you are being sent to has bad/outdated information, but the mirrroring software normally stops that. I suggest you download the zip file direct and "install from zip" manually.

There's two lines that mention wlan0 but nothing related to association with a network and no errors that might give hints. Apart from taking a backup and then doing a clean install I'm not sure what to suggest.

It's either a typo or the key doesn't work, in which case you need to contact the Pi Foundation.

read post #4 again

Nope. Our default config is wide open. It will change in LE9 so iptables restricts inbound connections to RFC1918 networks, but that still wouldn't explain why you cannot connect from a local network.

If you want to influence Kodi features you need to whinge post in their forums.

You need to create a custom /storage/.config/xorg.conf that restricts the modes available to Xorg. The following xorg.conf was something I used with an older Samsung LCD in the past. It defines the specific modes (all 1080p) for output. As long as you don't define 4k modes, they will not be present in the mode pool and Kodi cannot use them. You will need to put Xorg into 'debug' mode and figure out what the Horizontal/Vertical refresh limits and correct 1080p modelines are for your screen. Note that the first parameter of the 23.976 mode can be set to four decimal places to get more accurate mode timing - the default is only two decimal places. It is never possible to get exact 23.976 on an nvidia card but it's possible to get closer than the default.

Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    Option         "DynamicTwinView" "False"
    Option         "NoFlip" "false"
    Option         "NoLogo" "true"
    Option         "ConnectToAcpid" "0"
    Option         "ModeValidation" "NoVesaModes, NoXServerModes, NoEdidModes"
    Option         "HWCursor" "false"
    Option         "UseEDID" "true"
EndSection

Section "Monitor"
    Identifier     "Samsung_LN46A850"
    Gamma          1.0 1.0 1.0
    Option         "DPMS"
    Option         "ExactModeTimingsDVI" "true"
    Option         "PreferredMode" "1920x1080_60.00"
    HorizSync      26-76
    VertRefresh    23-61
    Modeline       "1920x1080_60.00" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
    Modeline       "1920x1080_59.94" 148.3515 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
    Modeline       "1920x1080_50.00" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
    Modeline       "1920x1080_29.97" 74.1756 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync  
    Modeline       "1920x1080_25.00" 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync    
    ModeLine       "1920x1080_24.00" 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
    ModeLine       "1920x1080_23.976" 74.1756 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
EndSection

Section "Screen"
    Identifier     "screen"
    Device         "nvidia"
    Monitor        "Samsung_LN46A850"
    DefaultDepth    24
    Option         "ColorRange" "Full"
    Option         "ColorSpace" "RGB"
    SubSection     "Display"
        Depth       24
    Modes           "1920x1080_60.00" "1920x1080_59.94" "1920x1080_50.00" "1920x1080_29.97" "1920x1080_25.00" "1920x1080_24.00" "1920x1080_23.976"
    EndSubSection
EndSection

No further support will be provided until you provide a debug logfile showing a system without pirate add-on repo's installed.

Check for space on the internal storage. You will need approx 2.5x the size of the update file free for boot to succeed. If you are under the required amount the only option is to download the .tar file on macOS, uncompress, then copy the files over to /storage/.update and reboot. This skips a stage and requires less space. LE (and OE before) have never supported FTP so that's an easy explanation. SFTP (FTP over SSH) should work.

It's possible to set the same min/max protocol configuration from the LE settings add-on. No need for custom files.

Not possible. I bugged Kodi devs to promote it to the main menu for Krypton, but that's all that happened. It has very limited view options. Nothing has changed (so far) in Leia either.

You might need to replace "DE" with the appropriate regdom for wherever you are, i.e. FR for France. Also, don't forget that RPi3 wireless has terrible range. You need to find a way to send us "dmesg" log so we can see what's happening.

SMB1 is being deprecated and removed throughout the entire Windows ecosystem and "browsing" is an SMB1 feature, so once LE/Kodi and MS things update beyond a certain point you need to learn a new way of adding SMB shares. The 8.2.1 release notes are fairly comprehensive on the topic, but you will have to go read them instead of looking for an easy button to press - because there isn't one.

Some of our community developers are burning out from the hassle of trying to support an ever-increasing amount of sh1t hardware that requires over-complex installation hackery and a ever-increasing population of users who are a bit too self-entitled and whiny when their $25 box doesn't deliver the $500 experience they were inappropriately expecting. At the moment I'd estimate that 85% of the support posts in this forum come from devices that represent 8% of our userbase. That's not sustainable.

So we are going to publish a Generic S905 image that community developers can contribute proven changes towards while the core project handle the boring stuff related to building and releasing things. It means the image will have a considerably slower release schedule; but should become more stable over time. To drive stability we will not adopt high maintenance features like "install to internal" storage which are responsible for at least 50% of the installation issue posts in this forum.

Community developers have also decided to bump up to the Android 'Nougat' kernel. However, Amlogic 3.14 kernels are full of crap code so newer doesn't necessarily mean better, and there is a very real risk that this introduces a slew of new bugs. Our challenge is to do as little as possible with this build project as ultimately it will be thrown under a bus the moment a viable mainline kernel option exists. Sadly that will not happen within the Kodi Leia release schedule, so this is a stop-gap. Albeit a stop-gap that will be an important learning experience for the project.

It reminds me of issues seen occasionally when people import configuration from other Kodi platforms (e.g. Win to Linux). Best thing to do is use the log upload function in the LE settings add-on, then share the URL so we can see the config of things and what kind of media is being [not] played?

If you have an RPi3 it's technically possible to boot from USB media (solely) instead of mSD cards.

Either use the USB/SD creator app linked at the top of the downloads page to create a bootable card *or* click the big drop-list link on the same page and select "Raspberry Pi v1 and Zero" and you will see the direct file links for that hardware.

I'm interested in the wireless chipset inside the USB dongle. The information you posted about the Ultra2 is irrelevant.