Posts by chewitt

Kodi Krypton uses a completely different video caching process to older Jarvis releases. The positive of this is that untold playback gremlins are resolved and the codebase is considerably cleaner. The negative is that caching takes a lot longer and this impacts the channel zap speed. There is basically nothing you (or we) can do without reverting/modifying very large chunks of code; which probably breaks more than it fixes. The issue has been communicated at loud volume and with crystal clarity to the required Kodi developers and Kodi Leia should make a great leap forwards (or backwards, depending on your point of view) for this issue. Leia is tentatively scheduled towards year end.

xrandr --output HDMI1 --mode 3840x2160 --rate 60.00

^ something like that

You need to figure out what package installs the host XML::Parser module on your distro, then the build will continue.

autostart.sh is run at the start of userspace boot and the script will execute fully before boot continues; i.e. if you don't want to block boot you will need to (background)& tasks in the script. NB: If you background things there is no guarantee your tasks have finished before Kodi starts. It provides lots of possibilities for fixing and breaking things

The calibrate system in Kodi is a bit dumb because it only calibrates the current refresh rate, e.g. the Kodi GUI default at 60Hz. If you have "adjust refresh rate" enabled and play a DVD at 23.98 (23.976) Hz this will not be calibrated. If you play PAL content at 25Hz (doubled to 50Hz) it will not be calibrated. You need to manually step through each supported refresh rate (or the rates your media will need) and calibrate them all. The fact that you will make the same adjustment in all refresh rates is the dumb part, but at least you only need to do it once..

Try adding the modeline manually via xrandr.. it wouldn't be the first time the Intel driver had a bug!

I don't think this is possible. Library views track watched/unwatched status, but I don't think there is DB tracking of when something was watched, and because Videos views are not Library views there is no persistence of watched/unwatched status. It will show within the current GUI session but reboot and everything will show as unwatched again.

Find the Stalker support thread in Kodi forums and report the authentication issue there, else you'll be forever stuck on an old release.

Don't save the image to the same SD card that you will try and write the image to

What channel is the router broadcasting on?

mglae nice spot

milhouse it would be nice if we used the UUID scheme consistently.. perhaps something to put on the team to-do list?

systemctl stop kodi
mv /storage/.kodi/userdata/guisettings.xml /storage/.kodi/userdata/guisettings.old
systemctl start kodi

^ this will 'lose' previous Kodi GUI config (but not sources/thumbs etc.) and restart with a clean(er) config. Any change? - I don't see anything obvious in the log file.

Kodi does have some default fanart (a wordcloud of text in bronze colour on a black background) but if that's not being show it's picking up the art from somewhere else. In my own workflow for music I have a separate music source folder for problem scrapes. This allows me to move a single album that i've ripped from disc and scrape the source and a) not have it take aeons to scrape/update my large library, b) the log files only show a few items and not thousands, so they're human readable. It also makes it easier to target a single Album with picard to ensure the meta tags are set/saved properly.. because that's ultimately where the mismatch is probably occurring (or some stray .nfo files are in the filesystem).

I've edit the sig to something more acceptable.

At one point we were looking to absorb the capabilities of the OE era config add-on, but since RPi3 came along with enough CPU to decode MPEG2 in software without the license, the need for it among our userbase greatly reduced. There is also a strong correlation between providing a tool that encourages people to overclock their device and the number of people reporting random issues caused by overclocking.

There activity on supporting RK chips, but efforts are focussed on their current generation devices like RK3328 and there is low appetite for trying to accommodate their older ones. Things are also dependent on the Kodi Leia codebase so there's nothing that we'll show in public for a while yet.

Quote

[ 3.143965] sd 2:0:0:0: [sdb] 7761920 512-byte logical blocks: (3.97 GB/3.70 GiB)

[ 3.144376] sd 2:0:0:0: [sdb] Write Protect is off

[ 3.144382] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00

[ 3.144788] sd 2:0:0:0: [sdb] No Caching mode page found

[ 3.144792] sd 2:0:0:0: [sdb] Assuming drive cache: write through

[ 3.157644] sdb: sdb1 sdb2

[ 3.159528] sd 2:0:0:0: [sdb] Attached SCSI removable disk

[ 5.092941] EXT4-fs (sdb2): couldn't mount as ext3 due to feature incompatibilities

[ 5.094643] EXT4-fs (sdb2): couldn't mount as ext2 due to feature incompatibilities

[ 6.661835] EXT4-fs (sdb2): recovery complete

[ 6.666472] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)

[ 22.312011] ### sdb2 is removable. suspend/resume may not work

[ 22.312794] ### sdb1 is removable. suspend/resume may not work

Display More

^ looks like a 4GB card device being detected.

The error is clear in the first two images. The syslinux.conf or extlinux.conf is configured for boot=LABEL=System and disk=LABEL=Storage and those partition labels do not exist on the boot device. It should be using boot=UUID=blah something like below:

DEFAULT virtual
TIMEOUT 50
PROMPT 0

LABEL virtual boot=UUID=2605-0052 disk=UUID=c1d54db6-83d0-4a9e-b662-e7099f9edbf0 quiet tty vga=curren

So i'm wondering if another bootloader and traces of an older OE install are present on the 1TB /dev/sda device? - because using disk labels in the boot config is how things used to be done. LE has only ever used the UUID method.

thread moved to the Amlogic support area