Posts by chewitt

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

No log .. no problem

False. Our default disk layout for the Generic image is two partitions in a GPT partition scheme. If you want to install to the disk manually boot the installer in live mode or use an Ubuntu LiveUSB to create a GPT disk, first partition is 512MB and second is remaining space. Make both ext4 and install syslinux to the first partition. Now copy the KERNEL, SYSTEM and extlinux.conf to the first partition. That's all the installer does.

Not possible as-is or out of the box. It would need someone to repackage the code as a binary add-on. That means it's possible, but unless you write the code or find a willing volunteer it's unlikely to happen.

You probably need to tweak the key-repeat time settings for the remote control. We set some sensible defaults but some devices need a little adjustment. As there are multiple device-dependent methods for doing this you'll need to explain what you're using?

It's not an add-on that we provide or create so our ability to diagnose/support the issue is limited. You're better off posting the question/issue to the Kodi forum support thread for the add-on - where its author will see the post.

In what previous release were they working?