Posts by chewitt

Ubuntu Pastebin

this was a stock 14.04 minimal install that's had the bare essentials added for building and then a later 16.04 update

cat /storage/.kodi/temp/kodi.log | paste

If you 'paste' the logs I'll look at them. I never download zip files from forums because you never know what people put inside them.

I merged this and the advancedsettings.xml thread.

If you are using WiFi you can test with an Ethernet cable and see if the problem goes away. If it does, some cache tweaking (increasing the cache size) can help to smooth out micro gaps when the cache dips to zero for a few milliseconds. If you're not using WiFi and/or Ethernet does not cure the problem it's because the congestion is upstream and you'll see the cache hitting zero for multiple seconds at a time. In that situation it doesn't matter how big you make the cache, it will not fix the problem. The image you shared shows a stream with <1Mb/sec which means the ratio between incoming data and the default cache is already quite good, so I doubt it's a local issue.

Fusion has nothing to do with network location, but that's not the point: Official:Forum rules/Banned add-ons - Official Kodi Wiki

It has nothing to do with H.265 .. second line from bottom on the far right shows 0% so the video cache is empty. It's possible to tweak the cache settings a bit, but no amount of cache tweaking can make packets arrive quicker from the internet, and in 99.99% of cases that's the issue.

You can enable HTTP debugging and look at kodi.log for retrieval/scraping problems. I have to say that the majority of music I have in my Library doesn't have upstream fanart though, so it may just be your taste in music.

Kodi Krypton contains a major reworking of video code and the Amlogic component is still "work in progress" so you can expect some issues - it's coming along but isn't as complete as the x86/Generic builds.

What (or who) and where are the sources for these builds?

I didn't look at the log .. but I clean built master twice yesterday so it's probably something to do with the build environment. I'm using an Ubuntu 16.04 base for personal and official builds.

This is on our radar but we're advised there are some issues (as well as fixes) with the newer firmware. When pi Foundation folks tell us it's a safe/good point to bump the default firmware we ship; we'll update.

These things happen in multinational development teams. Thanks for flagging it.

The build-system is the only manual there is, sorry.

If you're familiar with the LE build-system you can look at @kszaq's port for the S805 and the work done by wrxtasy for the C2, and the official project for the WeTek Core. If you're not familiar with the LE build-system that's the first thing to figure out. There is no FAQ or guide to follow for adding new devices, but there is a lot of "prior art" in the build-system and everything is in GitHub. The challenge with most Amlogic devices is u-boot. Every device seems to require different u-boot voodoo.

If you pop the codec info on the screen (o on a keyboard) bottom-right on the display that appears you'll see the % value for the video cache. If that's at 80-90-100% the stream is healthy. If it's frequently droppping to 0% it's a bandwidth issue. If you have 80Mb fibre the issue is likely to be somewhere upstream from you, but it doesn't matter where. I see this kind of thing frequently.. but I also expect it as most streams arrive though a VPN tunnel to avoid geoblocking.

If you downgrade (update) from LE back to OE it's best to do a hard reset and then restore the OE backup you created before upgrading, but otherwise that's correct; at the current time things are still quite interchangeable. The main point is to take a backup. This ensures you can either restore stuff directly into a clean install of OE or unpack the backup and selectively restore bits to OE or LE again in the future. If something goes wrong (and sometimes it just does .. computers) your lack of backup is not our problem

Start from a clean LE installation. You can always connect/mount the old OE drive to copy-back information if needed; assuming it's not the drive that failed.

Use the backup function in the OE settings addon .. it creates a tar file in /storage/backup which can be copied off-box.

There's no need to extract anything to a USB drive. Take a backup. Move the backup off-box for safe keeping. Update directly from OE to LE using the normal OE/LE manual update method (drop the tar file in the update-files samba share). Give it a week or two and then throw the backup when you're happy there's no need to go back to OE.